The Mesoamerican Long Count calendar is a non-repeating, vigesimal (base-20) and base-18 calendar used by several Pre-Columbian Mesoamerican cultures, most notably the Maya. For this reason, it is sometimes known as the Maya (or Mayan) Long Count calendar. Using a modified vigesimal tally, the Long Count calendar identifies a day by counting the number of days passed since a mythical creation date that corresponds to August 11, 3114 BCE in the Gregorian calendar. The Long Count calendar was widely used on monuments.

The Long Count calendar identifies a date by counting the number of days from a starting date that is generally calculated to be August 11, 3114 BCE in the proleptic Gregorian calendar or September 6 in the Julian calendar (or −3113 in astronomical year numbering). There has been much debate over the precise correlation between the Western calendars and the Long Count calendars. The August 11 date is based on the GMT correlation (see Correlations between Western calendars and the Long Count calendar section elsewhere in this article for details on correlations).

The completion of 13 b'ak'tuns (August 11, 3114 BCE) marks the Creation of the world of human beings according to the Maya. On this day, Raised-up-Sky-Lord caused three stones to be set by associated gods at Lying-Down-Sky, First-Three-Stone-Place. Because the sky still lay on the primordial sea, it was black. The setting of the three stones centered the cosmos which allowed the sky to be raised, revealing the sun.[1]

Rather than using a base-10 scheme, like Western numbering, the Long Count days were tallied in a base-20 and base-18 scheme. Thus 0.0.0.1.5 is equal to 25, and 0.0.0.2.0 is equal to 40. The Long Count is not consistently base-20, however, since the second digit from the right rolls over to zero when it reaches 18. Thus 0.0.1.0.0 does not represent 400 days, but rather only 360 days.

The following table shows the period equivalents as well as Maya names for these periods:

To View the Source code in PHP, read the extended more text.

TwitterBomb 1.15
Community Release by Chronolabs co-op

Twitter Bomb allows you to place segments of a tweet into a database, and aggregate via services like twitterfeed.com tweets based on a sentence formed from a matrix of basis of sentences. You will be able to run a campaign on twitter and have your sentences randomly made from the segments of sentences known in this applicaion as the 'base' of the phrase.

Since this version there is also now two type of campaigns you can run, either a phrase bombing, or a scheduled tweet. You can import a list from a text file or log file, where each line is periodically tweeted on twitter as per your schedule. Including tabled filters for easy use and maintence as well as harvesting plugins that allow you to develop with TwitterBomb to retireve information from other sources like API, databases, text files, SOAP ports or many other places like modules on your website.

TwitterBomb 1.15 is the new Stable Release, we don't expect to be doing anymore releases of this application which is XOOPS 2.4 compatible as it is full of features and has all the nessecary details for expansion with plugins but after this we will be migrating to the module class wrapper making it only 2.5 compatible.

There is a mirade of options with this application. You can specify URLS to pass someone too included in the URL can be the phrase in a URL Encoded string so you can direct people to search engines and topics to do with the sentence.

Check out TwitterBomb in action YouTube with this How To Instruction Video:

• Bit.ly URL Shortening
• Mounts as Twitter Application
• oAuth Classes
• Following Cron Job
• Gathering Cron Job
• Tweeting Cron Job
• Following Log
• Trending Keyphrase

• Filters
• Tag Module
• Asiigning twitter usernames to a nick
• Tweet Scheduler
• tweet Importing
• Usage Log
• Filter Plugins for Tweet Scheduler
• Logging Plugins
• Keyphrase Harvesting Plugins
• .htaccess SEO
• Exclusive and Inclusive Categories
• Ban Protection
• Activity Hit Count & Latest Time
• URLs for Tweets
• Part Base of Sentences
• Campaigns
• Categories
• Sentence Makeup Matrix
• Twitter Usernames

• Config Specification
• oAuth Actions
• Cron Jobs
• User Details MD5 Miscalculated
• Broad Criteria Selection for Campaign and Category
• User Additions of Twitter Usernames
• WSDO on Keyphrase Matrix
• WSDO on Keyword (Sentence) Matrix
• .htaccess SEO is inclusive of go.html
• Category Save on Campaign Trail in Admin List
• Two Fields missing from SQL File
• Feed Cache
• SEO URL for RSS using wrong ending
• Only one campaign feed showing
• Missing Twitter Username after @ in feed
• Language Constants

Xpayment 1.34
Modular Gateway and Modular Modules for Payment Transactions
Community Release - Sponsored By Chronolabs Co-op

Xpayment is a module that allows you to write customised payment gateways, as well as having modular hooking stratum in the module with a second plugin section for modules and responses to invoices.

Complete with Gateway plugins you can easily customise this module for your payment gateway in a few files. There is many benefits to using xpayment as the standard for intergrating payment into your modules. It has a modular plugin system for gateway invoice responses so your module will know when an items has been paid for.

Perfect for intergrating any shopping or purchasing with other XOOPS Modules, with modular plugins for transactional functions in other modules.

Also with Warehouse PLC Plugins and other functions which allow you to intergrate your payment gateway with other systems in your business.

• Control Panel Invoice Filters

• Centralised Language Constant's
• Automated Tax based on IP Location - IPDB
• Fraud Testing on Transactions
• Invoice ID Protection
• .htaccess SEO
• Fee Compensation
• Security Deposit
• Secure JSON Payment Button
• Email Permissions
• Gateway Permissions
• Diverse Modular Plugin
• Plugin Gateway systems
• Modular Plugin and Action hook
• Easy Form Post from any module
• Itemised invoicing
• Multicurrency
• Tax Itemisation
• Recursive Billing with Cron

• Paypal
• Zombaio
• CCBill
• 2Checkout.com

• WSOD on ID provided for Invoice
• PHP Versioning Error with JSON Adaptorl
• Invoice Status not being marked Paidl
• Gateway Transaction Cursor Not being marked
• Mailer Fields being Specified
• Template Formating

Welcome to web design in a co-op. As a co-op member you will receive all the benefits of being a member of one of the driving forces in web design.

We are looking for translators in the following languages:

• Arabic
• Bosian
• Brazillian
• Chinese Traditional
• Chinese Simplified
• Czech
• Danish
• Dutch
• Finnish
• French
• Galican
• German
• Greek (Role Taken)
• Gujarati
• Hebrew
• Hindi
• Hvastski
• Hungarian
• Italian
• Japanese
• Korean
• Malaysian
• Persian
• Polish
• Portuguese
• Romanian
• Russian (Role Taken)
• Slovenian
• Spanish
• Swedish (Role Taken)
• Thai
• Turkish
• Urdu
• Vietamese

• Multilingual Text Editor – Suggest Notepad
• Sourceforge - Full Username
• Contact Phone Number
• A Computer or Access to a Computer
• TortoiseSVN or Similar SVN Software

#Gaysex on AustNet

Austnet is the Australian Internet Relay Chat (IRC) main hub for the asia pacific with servers throughout the asia pacific including sydney, perth, singapour, hongkong and many other places.

#gaysex is one of the channels on there and even though at the moment it isn't overly active, I have been asked to make a breif site that can promote the channel through the web and hopefully attract some more users.

The site was made with the following XOOPS applications:

• Multisite
• XCenter
• TwitterBomb
• IRC
• SmartFAQ
• Profile
• MyAlbum-p
• Spiders
• Xortify
• Xforum
• Tags
• Lawsuit

• http://gaysexchat.asia
• http://gaysexchat.us