Recommended Posts

NASA scientists took time on Wednesday, Nov. 28, to soothe 2012 doomsday fears, warning against the dark side of Mayan apocalypse rumors ? frightened children and suicidal teens who truly fear the world may come to an end Dec. 21.

These fears are based on misinterpretations of the Mayan calendar. On the 21st, the date of the winter solstice, a calendar cycle called the 13th b'ak'tun comes to an end. Although Maya scholars agree that the ancient Maya would not have seen this day as apocalyptic, rumors have spread that a cosmic event may end life on Earth on that day.

Thus NASA's involvement. The space agency maintains a 2012 information page debunking popular Mayan apocalypse rumors, such as the idea that a rogue planet will hit Earth on Dec. 21, killing everyone. (In fact, astronomers are quite good at detecting near-Earth objects, and any wandering planet scheduled to collide with Earth in three weeks would be the brightest object in the sky behind the sun and moon by now.)

"There is no true issue here," David Morrison, an astrobiologist at NASA Ames Research Center, said during a NASA Google+ Hangout event. "This is just a manufactured fantasy."

more

  • Like 2

Well there will be a collision on December 21 2012 but it wont be Nibiru impacting with Earth rather reality impacting with believers of this rubbish.

Oh well better just wait it out at this stage, Just remember that the very people who were accused of hiding the truth were in fact the ones telling the truth all along :rolleyes:

  • Like 1
"I think it's evil for people to propagate rumors on the Internet to frighten children," Morrison said.

?

I didn't know people did that to frighten children. Hmmm... perhaps I should hide my copy of the original (translated to english, of course) Grimm's Fairy Tales. Those are pretty horrific. Shoot, even Mrs. Piggle Wiggle has some scary stories.

people seem to forget the fact that that date on the mayan calendar would have technically happened around March of this year because of leap year that we added in that the mayans didn't do on their calendar

people seem to forget the fact that that date on the mayan calendar would have technically happened around March of this year because of leap year that we added in that the mayans didn't do on their calendar

The Mayan calendar was based on actual days and not solar cycles like our Gregorian calendar is.

So with that said, leap days were irrelevant to the Mayans and Dec. 21st is still technically correct.

Whoever created that Facebook "myth" that went around wasn't very bright. ;)

people seem to forget the fact that that date on the mayan calendar would have technically happened around March of this year because of leap year that we added in that the mayans didn't do on their calendar

Are you being serious?

Of course they didn't count leap years, because it's not based on our calendar....

Do you think that the calendar literally says Dec. 21, 2012??.

Are you being serious?

Of course they didn't count leap years, because it's not based on our calendar....

Do you think that the calendar literally says Dec. 21, 2012??.

that's the whole point, going by their calendar, for us it would of happened around march because of the changes we've made

that's the whole point, going by their calendar, for us it would of happened around march because of the changes we've made

Wow you are really being serious...

The date Dec. 21, 2012 was calculated by MODERN archaeologist based on the Mayans calendar, no the other way around...how the Mayans would know of this thing called year 2012? , just think....

that's the whole point, going by their calendar, for us it would of happened around march because of the changes we've made

It's already been done. There was a conversion from Mayan to Gregorian calendar and that date came to be Dec 21st. Leap days have already been accounted for.

Sad thing is, these people believe in a cover up, but I have not seen a new planet or star in the night skies, or have felt any strange gravitational pulls that would be associated with a close encounter... Have you?

Seriously, look the frak up. There's nothing there. No Nibiru. Sorry.

  • Like 2

ok then, tell me, didn't some scientists find a larger Mayan calendar? or was my friend pulling my leg on that one too? (this is what i get for not doing my own research on it :pinch: )

Sad thing is, these people believe in a cover up, but I have not seen a new planet or star in the night skies, or have felt any strange gravitational pulls that would be associated with a close encounter... Have you?

Seriously, look the frak up. There's nothing there. No Nibiru. Sorry.

Take a cheep camera and point it at the sun... NIBIRUuuuuuu!!!1!1!

This topic is now closed to further replies.
  • Posts

    • 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
    • Tor Browser 15.0.17 by Razvan Serea Protect your privacy. Defend yourself against network surveillance and traffic analysis. Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody from watching your Internet connection and learning what sites you visit, it prevents the sites you visit from learning your physical location, and it lets you access sites which are blocked. The Tor Browser Bundle lets you use Tor on Windows, Mac OS X, or Linux without needing to install any software. It can run off a USB flash drive, comes with a pre-configured web browser to protect your anonymity, and is self-contained. Tor Browser 15.0.17 changelog: All Platforms Updated Tor to 0.4.9.11 Updated NoScript to 13.6.25.1984 Build System / All Platforms Bug tor-browser-build#41821: Update gpg subkeys for boklm Bug tor-browser-build#41827: Update morgan's keychain with renewed key Download: Tor Browser (64-bit) | Tor Browser (32-bit) | 109.0 MB (Open Source) View: Tor Browser Website | Other Operating Systems Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • 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!