Free myspace stuff software for linux

WWW::Myspace is a Perl module to access MySpace.com profile information from Perl.

WARNING - DO NOT USE THIS MODULE FOR MASS MESSAGING OR COMMENTING.

Myspace will cripple or disable your account:

Older accounts:

Messages will appear in your Sent folder but not in the receivers inbox, although theyll be able to see it if theyre paging through from another message. The receiver will get a "New Comments" notification and be able to see your comment, but it wont appear on the profile page.

Newer accounts:

If you created your myspace account in or after June 2006 (approximately), and you use a "bot" (including this module) to send messages, your message sending ability will be disabled and your account may be deleted. This is due to security features myspace has implemented to prevent spam abuse by people using multiple accounts.

SYNOPSIS

WWW::Myspace.pm provides methods to access your myspace.com account and functions automatically. It provides a simple interface for scripts to log in, access lists of friends, scan users profiles, retreive profile data, send messages, and post comments.

use WWW::Myspace;
my $myspace = WWW::Myspace->new ($account, $password);
OR
my $myspace = new WWW::Myspace; # Prompts for email and password
unless ( $myspace->logged_in ) { die "Login failed: " . $myspace->error }

my ( @friends ) = $myspace->get_friends();

This module is designed to help you automate and centralize redundant tasks so that you can better handle keeping in personal touch with numerous friends or fans, or coordinate fan communications among multiple band members. This module operates well within MySpaces security measures. If youre looking for a spambot, this aint it.

WWW::Myspace works by interacting with the site through a UserAgent object, using HTTP::Request::Form to process forms. Since by nature web sites are dynamic, if you find that some interaction with the site breaks, check for a new version of this module (or if you go source diving, submit a patch). You can run "cpan -i WWW::Myspace" as a cron job or before running your scripts, if appropriate, to make sure you have the latest version.

MySpace Blog Editor is an extension which allows you to post directly from within Firefox to your MySpace blog.

The MySpace Blog Editor allows you to post directly from within Firefox to your MySpace blog aswell as save notes, drag and drop formatted text from webpages, handle images and much more.

WWW::Myspace::Data is a WWW::Myspace database interaction.

SYNOPSIS

This module is the database interface for the WWW::Myspace modules. It imports methods into the callers namespace which allow the caller to bypass the loader object by calling the methods directly. This module is intended to be used as a back end for the Myspace modules, but it can also be called directly from a script if you need direct database access.

my %db = (
dsn => dbi:mysql:database_name,
user => username,
password => password,
);

# create a new object
my $data = WWW::Myspace::Data->new( $myspace, { db => %db } );

# set up a database connection
my $loader = $data->loader();

# initialize the database with Myspace login info
my $account_id = $data->set_account( $username, $password );

# now do something useful...
my $update = $data->update_friend( $friend_id );

Unofficial Myspace Toolbar provides a way to automatically login to Myspace.

Automatically login to Myspace, instantly access your messages, view hidden comments, create styled comments/bulletins and more with this intuitive and customizable toolbar!

NEW! Myspace Notifications: Find out if you have new comments, bulletins, etc without logging into myspace.

The toolbar can automatically hide when you are not using Myspace. To toggle this feature, click the "m" on the status bar.

Linux documentation can be found in man pages, info files, HOWTOs and FAQs, and elsewhere. (For example, also the kernel Documentation directory contains a lot of good stuff.) A nice index for the man pages in Fedora Core 2 is found at the superman site.

Man pages belonging to programs are usually distributed together with those programs. Therefore, the Linux man-pages distribution mainly contains the pages for system calls and library routines, special devices, and file formats.

However, it also contains documentation for a number of programs, in cases where the authors or maintainers of the program do not distribute man pages themselves.

KMyIRC provides an IRC client for KDE which strives to be useful and easy without being bloated.
It was created because it was felt that the other KDE-based IRC clients were either not user-friendly or burdened with features that are not useful to the average IRC user.
Enhancements:
- Fixed bug in /part command
- Added member varibale "KMIChannelWindow::parted" to class KMIChannelWindow
- Added /leave command
- Added new ircMessage parsing object
- Added logging facility for raw irc messages
- Added some more irc-servers and groups to global config file (kmyircrc)
- Added some widgets to raw irc message window for logging stuff

PHAT is a browser-based network management solution with a heavy lean toward switches, routers, and other traffic handlers which can be used to control either a single node, subnet, or vlan.
As you can probably see if youre reading this, PHAT is not the worlds most useful tool... yet. The reason I released this code in the first place was because I found myself in a vicious cycle: I didnt want to release the code until it was a little cleaner, a little more useful, and less dependent on site-specific stuff (currently, PHAT is quite reliant on NIS for example). However, I really havent had all the time in the world to devote to coding (Im also a sys/network admin), so getting PHAT to this presentable state has been tough (obviously, as I still dont consider it very presentable). I realized the only way to be useful was if I just released it for better or worse, and let people have at it.
Right now, the only things PHAT can really do depend on NIS, and MySQL. However, the NIS stuff should go away soon, and its not very hard to understand whats happening. Anyone with a decent level of networking and PHP expertise should be able to rip out the NIS stuff and replace it, or abstract the stuff altogether. The MySQL stuff will go away too, but not tomorrow or next week. As more people get involved who have more experience in dealing with ADODB or the PEAR DB stuff well move toward one of those.
In addition to reading this file, you really should read the source files as well, as I have a tendency to write really verbose stuff in there.
So, in a nutshell, I picked the release name "pseudocode" because thats exactly what PHAT currently is. Its a proof of concept. Everything has been done in a very brute force manner and has been tested just enough that theres some evidence that this stuff can work and I can demo it for a few interested local parties :)
At this stage in the game, ideas reign supreme. The only thing that rules over talking about ideas is coding prototypes for them.
Enhancements:
- PHP 4.x: As far as I know, any 4.x version works. I always use the latest version of PHP, and the version I used initially was 4.1x, I dont exactly remember which one.
-
- Apache: This has only ever been tested on Apache. UNIX/Linux: PHAT, at this stage, still makes a couple of systemcalls that are *nix specific. Its been tested on Linux and
- Solaris. This dependency should eventually go away.
-
- NIS: This dependency really has to go away. Abstracting the things PHAT uses NIS for right now is the first order of business.
-
- MySQL: I want to use the PEAR or ADODB stuff, but havent been overjoyed with either one. I dont want to have PHAT be dependent on any one database.