I'm thinking of implementing other means of receiving a SocialDM (configurable by the user). Options include: IM (XMPP), Twitter (DM or @reply), or SMS. I won't pretend to know how I'm going to do this, but what do you want? If you had to pick one of the three?
Auto-complete implemented. But beware: these are just the people you are subscribed to. If the user isn't subscribed back (or isn't in the SocialDM system) then you're out of luck. The "validate" button is your friend. :)
DM-ing: 1) The feed now has a link for people to DM you directly. When your import the service, just click the "Include entry description as a comment" checkbox. 2) You'll see this link showing up at the footer of emails as well. The format is really simple: www.socialdm.com/dm?nick=USERNAME
Suggestion - if you want to send the email via the web interface, could there be a drop down list of people to choose from? I don't know everyone's login ids since FF doesn't show them... I just know them by their user names. It would be nice to not have to go track that info down before sending.
Scoble: While I'm trying to figure-out how to fix my app to accommodate users with massive subscription lists, I've fixed the bug that prevented you from creating an account. You can create an account and DM anyone who is following you. The only problem will occur when someone tries to DM you.
The email address used to contact people has changed (for the better). The new format is [service]+[username]@socialdm.com. Today the only valid service is "ff". So, to contact me you'd shoot an email to: email@example.com. That's it!
Another question that I don't know the answer to: what kind of "feed" should this service provide? It has to provide something, or it won't get to play in FriendFeed's playground. I'd rather not create another Wakoopa, any ideas?
Things are getting better slowly but surely. I now give you: http://www.socialdm.com! Not the sexiest domain ever, but I think it gets the point across. There's still some stuff to migrate (like the email UI) but we'll get there. :) You'll get emails from firstname.lastname@example.org instead of me now
To Scoble's issue: Google's AppEngine will not allow API calls to external services that take too long (>5 sec) or return a file too big (>1 MB). Robert's subscription list is roughly 1.8 MB. I'm going to investigate getting around this and any suggestions are welcome!