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.20 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 on YouTube with this How To Instruction Video:
New Features Include:-
* Search & Retweet then Follow Campaign * Odds Alotment.
Some Features Include:-
* 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
Bugs Fixed:-
* Endless Loop in Twitter Search Routine (Fixed Retweet Backend & Cron) * 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
- Add uploadimg function in utils class (Voltan) - Add setpermission function in perm class (Voltan) - Add upload image for topics (Voltan) - Add delete option for images (Voltan) - Add Breadcrumb function in utils class (Voltan) - Add contentDefault function in page class (Voltan) - Add homepage function in utils class for manage module index page (Voltan) - Improve permission page (Voltan) - Add topic URL function (Voltan) - Add function for show subtopic contents in main topic (Voltan) - Add Rebuild Alias function (Voltan) - Add Set and reset Next and Previous function automatically (Voltan) - Add change topic order whit AJAX (Voltan) - Add new options for make URL (Voltan) - Add Show/hide topic in index page (Voltan) - Add support for module admin class (Voltan) - Add option for attach file for contents (Voltan) - Fix bug in delete pages (Voltan)
Please test this version to help us improve and fix bugs
Following DJ's (aka phppp) and Kris' resignation from XOOPS Council, the remaining Council members have agreed that the available seats should be reassigned as soon as possible.
As you may know, the Council is responsible for overall management and direction of the XOOPS Project. The XOOPS activities are divided in several teams, and the Team Coordinators/Leaders are then members of the XOOPS Council.
Due to Core and Design Teams fragmentation and lack of coordination, the XOOPS Council decided to designate temporary leaders who will be assuming the responsibility of recruiting and reuniting members for these teams. It is the XOOPS Council's wish to have each team electing their own leaders in January of 2012.
As of now, after being invited and kindly agreeing to assist us, the new Council members are:
- Core Team: Nicolas Andricq (ForMuss) from France - 2010 Innovator of the Year, who was the Development Leader of XOOPS 2.5.0, with its many innovative features
- Design Team: Eduardo (Bitc3r0) from Mexico - a winner of several XOOPS Innovation Awards for his work such as EXM Admin theme, or RM Common Utilities, and several modules and themes, among them the current theme on http://www.xoops.org
The community also proposed to have a Council member who is representing the users. We liked the idea and therefore we've invited Mark Boyden (mboyden) from USA, who created many XOOPS sites, both pro bono and for profit.
Mark has been always very supportive of XOOPS (see his blog) and since his livelihood depends in part on XOOPS success, we thought that he'll be a very good addition to the Council.
Currently remaining on the Council are:
- Modules: Ricardo Costa (Trabis) - International: Rune Hauge (Runeher) - Marketing: Michael Beck (Mamba)
Please become active and join one or more of these teams. The XOOPS Council is looking forward to reactivating and reengaging of all these teams, hoping they can express and fulfill what they wish for and from XOOPS.
A TBDev tracker is a server that assists in the communication between peers using the BitTorrent protocol. It is also, in the absence of extensions to the original protocol, the only major critical point, as clients are required to communicate with the tracker to initiate downloads. Clients that have already begun downloading also communicate with the tracker periodically to negotiate with newer peers and provide statistics; however, after the initial reception of peer data, peer communication can continue without a tracker.
This is a Private tracker; a private tracker is this TBDev tracker that restricts use, by requiring users to register with the site. The method for controlling registration used amongst many private trackers is an invitation system, in which active and contributing members are given the ability to grant a new user permission to register at the site. Invitations, typically sent via email or an invite code system, are normally granted to active users who have uploaded a pre-determined amount or meet specific upload-to-download ratio requirements.
Trading invites for different sites is highly frowned upon in the private Torrent community as it allows anti-piracy groups to infiltrate private trackers more easily. Most private trackers monitor how much users upload or download, and in most situations, enforce a minimum upload-to-download ratio.
Some of the allure of private tracker versus a public one are: higher speeds, a tighter community, and safer downloads. Private trackers implement a strict set of rules, so generally files containing malware are extremely uncommon. Many private trackers keep in close contact with each other, so bad users (who trade invites or attempt to fake their ratio) can be quickly blacklisted. Almost all private trackers implement a passkey system, where each user is given a personalized announce URL so if there is unauthorized distribution, it can be pinpointed to the user responsible. Some private trackers have a higher level of security than others — many sites only allow their users to refer to their site as an abbreviation, and never as the site's full name or URL. Other trackers restrict invites to outstanding members, and many trackers, to increase security, have eliminated the invite system altogether. An example of a private tracker is Oink's Pink Palace, which was forcibly shut down in late 2007 by law enforcement officials.
The downside is that in a closed community it can be hard for all members to maintain the required ratio. Competitions may be offered, with prizes of improved ratios. Some trackers will exchange ratio credit for donations. Some trackers will also use "free leech" systems to improve the users ratio. When downloading a free leech torrent only the upload gets logged in, the download is ignored. Usually large torrents are offered as free leech. Seeding to a ratio of at least 1 is still recommended even for free leech torrents.
Xquiz allows you to place forms based on questionairs to a user into a database, and then display them based on permissions on the user interface. You will be able to run a questionairs as well as score with a checkbox, option or select on the form and have your questionair emailed to you as well as the responses recorded in the database.
XQuiz 1.05 RC is the release candidate and is based on 'formulair 3.33', it has been refactorised as well as made slightly functionally different with an inclusion of a scoring system put in place for checkboxes, radio options as well as select and multiselect. With the current features of forumlair but designed as a questionair application, this will allow you to collect information based on form inputs as well as export those results into a CSV.
There is a mirade of options with this application.
Xortify is a network security drone that uses Web 2.0 techniques to link between your XOOPS installs and other via a Server Cloud. This will prevent security intrusions to your xoops with accurate deceptive notation of the intruder and prevent any farmed attacks. It is an accessory and required Protector to be installed an running to be part of the hookup. Otherwise it will run without protector just make sure you deselect protector as a provider.
It will display a template if you are banned and is an accessory to protector or any other firewall technology. The site itself is driven from http://xortify.chronolabs.coop and mirrored at http://www.xortify.com .. Cloud computing is web 2.0/3.0 stuff it used a SOAP or JSON, XML or Serialisation to exchange on the API backend to work, this will eventually be included in xoops as a support class.
A cloud computing process is one which staggers multiple networks sometime and mainly unknown to the webmaster into a network or cloud of data. In this example it is IP and Netaddy names to control access lists.
This will prevent predators from exposing your network to lag and other attacks from link farming, often this means many xoops are attacked in occasions which is all the time caught by protector, this way if an attack is in process across a large spectrum of links, your site will down itself to your sourced attack even if it is discovered on a completely unaffiliated site that is link farmed to yours or on a XOOPS User list.
Xortify is a cloud solution to protectors Bad IPs, if someone attempts to hack your site and becomes a bad IP it will then send the IP to the Ban Cloud on Xortify.com and its paired cloud Xortify.chronolabs.coop. It will also poll the server to make sure it has the latest ban list so your website will be aware of malusers before they attack through farming IP from services like Google or bing.
Watch this video to understand more about Xortify!
Spiders is a robot manager tool, that imports a list of all crawler and scanner robots on the web. It allows you to use XOOPS Permissiveness to control the data that robots list online your site. It will also log the robot in using a post loader and display when the robot is online on you 'Whos Online'.
Do you want your robots like GoogleBot, Yahoo Slurp! and others to log in and identify on your xoops installation? Then spiders is for you!!! The robot text file used is taken from an online resource of Robot data and stores it in your database. Remember to adjust your mainfile.php to include the post loader after the common file is loaded. Robot Manager (Spiders) is a good way to control what your site displays in search engines.
Watch this video to understand more about spiders!
New Features
Pre PHP 5.2 Compatibility
Search Functions Included
Some of the Features
Clean Robots-all.txt with over 200 bots
Try Exceptions added to API Calls for seemless entry
If you haven't set permission throughout your XOOPS Site for Robots then it is a simple case of uninstalling and re-installing then importing the current robots-all.txt. However if you have set permissions then I suggest you follow the steps as so. a) import robots-all.txt b) change 'Protected Keywords from Useragents' in Robot Managers (spiders) preferences to contain at least these keywords without the carriage return ::