Linking to pages and resources on this site is encouraged, but the links MUST be placed on a publically-accessible page. Placing links behind any form of login or access restriction is strictly forbidden.
A myspace email gateway?
A reader of these pages will have noted that I do not get on very well
with myspace. Not to put too fine a point on it, it does my fucking
head in. Even the most minimal interaction with the site tends to make
me feel worse than if I had not so interacted. This manifests itself
in behaviour such as my reaction to a mate's recent email; he sent me
a link to a music video on myspace and I haven't watched it yet, I'm
waiting until I'm in a shitty mood to begin with so I don't take
myself from a good mood to a bad mood by arsing around with myspace.
Especially as the fucking myspace cunts have written the bloody music
video stuff in fucking flash, so I'll have to fuck around similarly to
what's needed with youtube
in order to be able to see the sodding thing. Only I don't know how
the myspace one works so I'll have to figure it out first. Just what I
So I take steps to minimise my interaction with the site. Turning on the notification of messages received is a good start, as it means I don't have to log on to check my messages, only to read them when there are any. I don't have to log on to send messages either - I've hacked together a bunch of shell scripts which enable me to compose a message in my ordinary text editor and then fire it off from the command line, like email used to be. The obvious next step is to eliminate the one remaining reason to log on - reading messages - by automating the process with some additions to the aforesaid shell scripts. Indeed, I could configure my
.forward to pass
the incoming myspace notifications to the scripts which would then
automatically retrieve the message and hand it on to the local MTA for
delivery with the rest of my email.
So this naturally suggests an extension of the idea: hack an SMTP front end onto it to produce a myspace SMTP gateway server. The process of sending and receiving myspace messages would then be indistinguishable from that of sending and receiving normal emails and with any luck I could forget that I was interacting with myspace at all.
And then, me being into free software and all that, I could make my gateway server available to the general public. Then any fucker in the world could send emails to
whatever, supplying their own myspace username and password via
standard SMTP AUTH, and have them delivered to the recipient's myspace
mailbox... and if they set up the appropriate forwarding rule for the
myspace notifications, or registered a
account as their myspace email address, the replies would be delivered
to their ordinary email inbox. As an alternative it would be just as
straightforward to incorporate a POP3 front end for receiving
messages. (Dunno about IMAP, though. Doesn't look like the headfuck
site's message box functionality is rich enough to make IMAP practical
without some fairly horrific kludges and/or loads of state on the
gateway with associated sync problems.)
I think that would be quite cool. There must be other people out there who are only interested in myspace for the message sending/receiving facility, and there must be other people out there who find it a headfuck. I can however see a few problems with it:
So what do I do... only one answer, release the project as a standard open source collaborative development. That way anyone could fix bugs or refreak it to cope with upstream changes or set up their own gateway server to take some of the load.
Update: Now the buggers have incorporated captchas into the message sending procedure, so it can't be done any more. Oh shit.
Back to Pigeon's Cack
Back to Pigeon's Nest
Be kind to pigeons