Tag: social networking

Posted on
by

Another problem I’ve noticed in my Twitter archive: Lots of URL shorteners and image hosts have shut down or purged their archives.

Sure, bit.ly and is.gd and tinyurl and ow.ly are still around. But in the days before t.co, I used a lot of different Twitter apps that used different shorteners or image hosts.

I have photos posted not just at Twitter and Twitpic, but at phodroid, mypict.me, and twitgoo. In some cases the description and date can point me to the right picture on my hard drive or on this blog (I used to import a daily digest of tweets, and I still sometimes use Twitter as a rough draft for content here). In some cases I can narrow it down to a group of photos — the 2012 partial solar eclipse, for instance.

In some cases, I have NO IDEA what the photo was:

Not sure if the misspelling will be legible in this upload phodroid.com/hvcyxw

— Kelson Vibber (@KelsonV) January 28, 2009

Similarly, I linked to a lot of articles that might still exist, but the short URLs don’t point to them anymore. Services like tr.im, short.to, and awe.sm. StumbleUpon’s su.pr. In some cases a publisher set up their own shortener, and has since dropped it. Again, sometimes I can find it from here. Sometimes the description includes a quote or title that I can search for.

Oddly enough, I found most of my lost awe.sm links by looking at Del.icio.us, which apparently unwrapped the links when they imported from Twitter way back when. It’s still around and searchable. For now. (I should look into what you get from their archive.)

It’s true that these problems are biggest if you were on Twitter before they implemented their own link shortener and image hosting. But a lot of tools (Buffer, for instance) still use their own shorteners for tracking purposes, so you’re not just depending on the tool being around long enough to post your tweet, you’re depending on it to stay around for the rare person who stumbles on an old thread and wants to see what you were talking about.

And even if you didn’t start using Twitter until they hosted photos themselves, Twitter doesn’t include your photos in your archive! If you want to save your own copies in case they go the way of GeoCities or even photobucket, you’ve got to hold onto the originals or download them yourself.

Posted on
by

One of the problems with Twitter’s search capability is that the results are isolated.

I’ve said before that one of the keys to making a social account feel like I own it is that I can find things in it if I want to go back later. You can search your old Twitter posts by adding your username to the query in the regular search form, but it only shows you the matching results, not other posts that might be connected.

If you click on it you can get an actual conversation thread…but only those tweets that are connected as replies, so if you didn’t thread a tweetstorm properly, or if you had a big sprawling conversation with lots of different people, sometimes replying and sometimes posting something new…you can’t see the rest of it.

Worse, if you go back far enough, Twitter doesn’t even have threading. You might see “@friend Inconceivable!” but have no idea what they were saying that you replied to. (And that doesn’t even get into old shortlink and image providers that have shut down, removing content from your post as well.)

I have similar issues with Instagram, which basically has no real search, only hashtag-based timelines to go along with the account-based timelines. In both cases, when you get to a specific post, it’s a dead end. You can’t see anything around it without going back to the author’s profile, even if that author is you. Though depending on how you clicked on the Instagram link, you might get back/forward links.

(This is true for Mastodon as well, but to be fair, Mastodon is still building its search capabilities.)

WordPress, on the other hand, not only usually has next/previous links on each post, but you can view archives by category, tag, month and (for some permalink structures) day. When you find a post, you can see what’s around it. You can get more in the admin interface, but even as a visitor, you can still get the context.

Posted on
by

Things I think about when choosing where to post something original, once I’ve decided to post it.

  1. Audience. Who’s going to be interested in this? Family? Friends? Fans or hobbyists or people in my industry or some other shared-interest group? People looking for troubleshooting help? Do I just want to say something for the record?
  2. Permissions. Who do I want to allow to see this? Am I OK with it being seen by the general public, or do I want to lock it down to specific people?
  3. Type of Media. Long article, short comment, photo, video, link to something interesting? Not much point in linkblogging here these days, while Twitter and Facebook are better suited. A long post is easier to compose and easier to read as an article than as a Twitter thread (though Tweetstorms do have their place). Photos are more likely to be seen on a dedicated photo site than here, but if there’s a story to it, a blog post might work better.
  4. Polish. I’ll sometimes post something off-the-cuff on Twitter or Facebook, then refine or expand it later. Or I’ll post a photo on Instagram in the moment, then when I have time, do a cleaner edit or album on Flickr, or write a story around it here.
  5. Connections. Is it related to something else I’ve already posted? This is why I keep posting funny signs, examples of holiday creep, and convention reports here.
  6. Permanence. Do I want to be able to find it again easily? If so, I’ll probably go with a blog or Flickr (yes, Flickr), because searching for stuff on Twitter or Instagram or even Facebook is such a pain.

So yeah, that’s why I still post some things here, why I only post other things on Twitter, why I post different things to Flickr and Instagram, why I sometimes cross-post, re-post, and re-edit. Am I overthinking it? Maybe, but it’s not like I go through a full checklist every time – this is less a recipe and more trying to write down what I’ve been doing anyway.

Posted on
by

I figured out exactly what bugs me about Twitter and Facebook showing your friends’ “likes” in the timeline. It’s not just that they’re public — that’s true on Tumblr or Flickr or Instagram too, but you only see them when you choose to look for them.

It’s that broadcasting likes in the newsfeed blurs your intent.

  • A “like” is a message to the original post’s author (and a bookmark for yourself).
  • A retweet or share is a message to your friends or followers.

Putting them in your followers’ feeds turns a “like” into a message to them as well, even though it’s not what you intended. (If you wanted to share it, you would have shared it, right?) It’s a step above completely frictionless sharing, but it still messes with the signal/noise ratio of the timeline.

Posted on
by

Sophos reports that Facebook is testing a feature to hide new posts from your timeline so they don’t feel so permanent. Of course they’re still searchable until you actually delete them, so they’re still permanent in that sense.

What’s odd: Facebook posts don’t feel permanent to begin with, even though they effectively stick around forever.

Thinking about it, two things make an internet post feel permanent to me:

  1. Can I count on it sticking around?
  2. Can I count on finding it again?

Facebook, despite a lot of improvements over the years, is a mess. The newsfeed algorithm means you can’t just keep scrolling back. The timeline view isn’t reliably complete. Search is kind of a crap shoot. Don’t get me started on trying to find a particular old post on Twitter!

And that’s dealing with sites I can expect to stay online over time. A post on a forum, or a comment on someone else’s blog, or any social network could easily vanish in someone’s server crash or business shutdown.

If I can’t count on being able to find what I post a few years down the line, it feels like it’s temporary, even if it isn’t.

This is one reason that my Flickr portfolio feels more permanent than my Instagram photos: I can find them without resorting to third-party apps. If I want to find a particular photo on Instagram, I have to page down through my profile until I find it. On Flickr, I can find a 10-year-old photo of a fountain in seconds by searching for “fountain” and expanding the “Your photos” section of the results.

Then again, running my own site is only reliable as long as I can afford it. If something happens to me, and I can’t pay for hosting anymore, what then? I figure I’d simplify things down to where I could get a basic, super-cheap hosting plan. Make the blogs read-only so they can be served statically from a shared server or S3 bucket, or move them to WordPress.com, or just be willing to let them crash under load. But what if I’m incapacitated and can’t convert it? Or just plain not there anymore? If I really want to keep my corner of the web up “permanently,” I’m going to have to make a plan ahead of time.

Otherwise my carefully preserved photos, articles, and extended musings will be toast…leaving behind as context only broken links and all my supposedly (but not really) ephemeral offhand remarks on Twitter and Facebook.

Posted on
by

It shouldn’t make any difference that Twitter renamed Favorites★ as Likes♥. It’s a coat of paint. But labels do matter. Just like “friend” and “follower”, “like” and “favorite” (and hearts and stars) conjure up different expectations.

Twitter says, “You might like a lot of things, but not everything can be your favorite.” Paradoxically, I find “likes” to be more specific. The star-and-favorite model comes out of Internet Explorer*, and modern browsers still use stars for bookmarks. This made “favorite” seem a little more versatile, anything from a stamp of approval to a simple check-back-for-later.

“Like,” on the other hand….

After years of requests for a “dislike” button, Facebook finally admitted that “like” isn’t sufficient to respond to everything, and will be expanding to multiple reaction buttons. I know Twitter keeps trying to be more like Facebook, but c’mon — even Facebook knows people don’t want to “like” sad news.

*Microsoft didn’t want to call their bookmarks “bookmarks.” Nobody wanted to use the same terminology as anyone else back then. They tried to call links “shortcuts” too.