Recommended Posts

A giant asteroid will make a flyby of Earth over the next few days, and armchair astronomers can watch the action live on their computers.

The near-Earth asteroid 4179 Toutatis, which is about 3 miles (5 kilometers) wide, will zoom within 4.3 million miles (7 million kilometers) of Earth during its closest approach early Wednesday morning (Dec. 12). That's too far away to pose any impact threat on this pass, but close enough to put on a pretty good show through top-notch telescopes, researchers say.

And some of those scopes will be tracking Toutatis' movements for the benefit of skywatchers around the world. The online Slooh Space Camera and Virtual Telescope Project, for example, will both stream live, free footage of the asteroid from professional-quality observatories.

Slooh will webcast Toutatis views from a scope in the Canary Islands off the west coast of Africa beginning at 3 p.m. EST (2000 GMT) today (Dec. 11). Another show will follow at 10 p.m. EST tonight (0300 GMT Wednesday), with footage from an instrument in Arizona. You can watch them at Slooh's website:

http://www.slooh.com

more

Meanwhile ...

ASTEROID FLYBY: Newly-discovered asteroid 2012 XE54 is flying through the Earth-Moon system today approximately 230 thousand km (0.6 LD) from Earth. The space rock is about 36 meters wide, a little smaller than the Tunguska impactor that leveled 800 square miles of Siberian forest in 1908. Using a remote-controlled telescope in New Mexico, astronomers Ernesto Guido and Nick Howes photographed 2012 XE54 streaking among the stars on Dec. 11th:
buzz_strip.jpg

Guido and Howes dedicate this image to the memory of their longtime friend and colleague Giovanni Sostero.

This asteroid will not hit Earth, but it is close enough, and thus bright enough, for amateur astronomers to track using backyard telescopes. When Guido and Howes photographed it this morning, it was shining at magnitude +13.

Astronomers monitoring the asteroid might have noticed an unusual eclipse during the early hours of Dec. 11th. According to calculations made by P. Tricarico, 2012 XE54 "will likely cross the Earth's shadow, causing a partial eclipse of the asteroid a few hours before reaching its minimum distance with the Earth. Asteroids eclipsing during an Earth flyby are relatively rare, with the first known case of asteroid 2008 TC3 which was totally eclipsed just one hour before entering Earth's atmosphere over Sudan in 2008, and asteroid 2012 KT42 experiencing both an eclipse and a transit during the same Earth flyby in 2012."

Stay tuned for updates.

The space rock is about 36 meters wide, a little smaller than the Tunguska impactor that leveled 800 square miles of Siberian forest in 1908.

^ Oh what BS -- the Tunguska explosion was not caused by a meteor or asteroid.

No crater or 'rock' was ever found.

^ Oh what BS -- the Tunguska explosion was not caused by a meteor or asteroid.

No crater or 'rock' was ever found.

It was caused by a rock that popped in atmosphere. They are known as airbursts. There would be little debris left to find.

^ That's merely an unsupported theory -- not an established fact.

Other theories involve comets.

An "airburst" can involve a comet.

I suspect that you lean towards one of the more romantic hypothesis': A black hole? Antimatter? Time travel? Aliens? Perhaps the remanence of Neanderthals inhabiting the Earths interior?

^ Witnesses who actually saw the object stated that it changed course a few times, before the explosion.

As the body neared the ground (forest), the bright body seemed to smudge, and then turned into a giant billow of black smoke, and a loud knocking (not thunder) was heard, as if large stones were falling, or artillery was fired. All buildings shook. At the same time the cloud began emitting flames of uncertain shapes.

It also left considerable radiation behind. (sound like an ice & rock comet ?)

After the event, the skies were lit up at night for days, hundreds of miles away.

At around 7:17 a.m. local time, Evenks natives and Russian settlers in the hills northwest of Lake Baikal observed a column of bluish light, nearly as bright as the Sun, moving across the sky.

Draw your own conclusions. ;)

^ Witnesses who actually saw the object stated that it changed course a few times, before the explosion.

As the body neared the ground (forest), the bright body seemed to smudge, and then turned into a giant billow of black smoke, and a loud knocking (not thunder) was heard, as if large stones were falling, or artillery was fired. All buildings shook. At the same time the cloud began emitting flames of uncertain shapes.

It also left considerable radiation behind. (sound like an ice & rock comet ?)

After the event, the skies were lit up at night for days, hundreds of miles away.

At around 7:17 a.m. local time, Evenks natives and Russian settlers in the hills northwest of Lake Baikal observed a column of bluish light, nearly as bright as the Sun, moving across the sky.

Draw your own conclusions. ;)

How do we know it left radiation behind? We didn't even know what radiation was back then. Also, when you have tons of fine particles suspended in the air, it will reflect light. We've seen this happen with volcanic ash during huge eruptions.

And, "a column of bluish light" sure sounds like a fireball to me, after all, the blue is the hottest part of the flame.

^ Witnesses who actually saw the object stated that it changed course a few times, before the explosion.

As the body neared the ground (forest), the bright body seemed to smudge, and then turned into a giant billow of black smoke, and a loud knocking (not thunder) was heard, as if large stones were falling, or artillery was fired. All buildings shook. At the same time the cloud began emitting flames of uncertain shapes.

It also left considerable radiation behind. (sound like an ice & rock comet ?)

After the event, the skies were lit up at night for days, hundreds of miles away.

At around 7:17 a.m. local time, Evenks natives and Russian settlers in the hills northwest of Lake Baikal observed a column of bluish light, nearly as bright as the Sun, moving across the sky.

Draw your own conclusions. ;)

There is no reason to really dig into the Tunguska event, there is nothing we can learn from it by creating new Hypothesis. There is a lot of evidence supporting the current theory, large explosions in the air can cause the pattern seen, asteroids/comets can explode before hitting the ground if the conditions are right. Finally there is physical evidence backing it up as well. There will not be a better explanation unless a similar event happens again allowing new evidence to be brought forth.

I'm not worried about Toutatis - it's Apophis that is going to give us cause for concern soon enough.

Why is it a cause for concern? It's 17 years from now for starters (well, 16 since it's the end of 2012 I suppose), it won't come anywhere near close enough to hit the planet in 2029, and even if our gravity affects it's orbit, the chance of it going through the keyhole at just the right degree is extremely small. And even then, if it did do that, it's another 7 years after that before anything happens. We have 24 years to plan for Apophis and it's extremely unlikely rendezvous with Earth.

^ Witnesses who actually saw the object stated that it changed course a few times, before the explosion.

As the body neared the ground (forest), the bright body seemed to smudge, and then turned into a giant billow of black smoke, and a loud knocking (not thunder) was heard, as if large stones were falling, or artillery was fired. All buildings shook. At the same time the cloud began emitting flames of uncertain shapes.

It also left considerable radiation behind. (sound like an ice & rock comet ?)

After the event, the skies were lit up at night for days, hundreds of miles away.

At around 7:17 a.m. local time, Evenks natives and Russian settlers in the hills northwest of Lake Baikal observed a column of bluish light, nearly as bright as the Sun, moving across the sky.

Draw your own conclusions. ;)

Here you go, Hum! The Bad Astronomer, Phil Plait, takes a dive into airbursts, just for you. ;)

http://www.slate.com...ees_like_a.html

This topic is now closed to further replies.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!