Dipping a toe into the future

[rax]

So I've given in and dipped a toe into the future, which for most of you is probably the present. I'm planning to actually swim, or at least float. Help me out here:

• If you're using Twitter, I'm user raxvulpine; let me know so that I can follow you! (Or just follow me, and I'll notice and follow you back.)
• If you're using Facebook, you can friend me by clicking here. (I gave in because my UMass Boston friends are sufficiently from the future that they don't even use email.)
• Expect me to actually write up book reviews and such more frequently now.
• You can be my LinkedIn not-friend-because-that's-not-professional-enough-but-I-have-pink-hair-so-who-cares here. Thanks, jadia .
• Do I need to care about Dreamwidth?
• I've refreshed my personal website. I'm actually not embarrassed by it now! Yay!

What social technologies or mumbledy-whatevers am I missing? I'm going to be going to conferences and talking to people and want to be able to jump into networking with people and not seem like some sort of hopeless luddite. Eventually I will need to write some Javascript to automate the news bits but for now I think this is OK.

Comments

[kelkyag]

That's what I would have thought, but I'm not sure what the auth=digest version of the feed does. That suggests to me that a reader could send an id (openid?) and hashed password to be able to view locked entries via feed. If a feed is only ever unlocked entries, I have no idea what one would want the auth option for.

[xlerb.livejournal.com]

That, I think, is for people running an RSS reader on their own machine. Something like the LJ syndication feature, which consumes an RSS (or Atom?) feed and then displays its contents publicly, would not be using that.