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.

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.

Well, they did it. The FCC voted 3-2 on party lines to scrap Net Neutrality even though 83% of voters across the board want to keep it, even though scrapping it doesn’t help anyone except the giant cable & phone companies and those they decide to bless with their approval, even though it’s the only thing other than trust preventing those cable & phone companies from placing restrictions on how you use the internet and where you go…and you can surely use your imagination as to how that can be abused.

But you trust your cable company, right?

The fight moves to Congress now. They can still nullify the action through the Congressional Review Act – ironically, the same method they used earlier this year to wipe out privacy rules that the FCC put in place under the last administration.

Write Congress. Call your Senators. Call your Representative. Battle for the Net.

On Thursday, the FCC is planning to vote to allow your cable company to decide which news sites you get to access, which streaming sites you get to use, intercept your search queries, charge you extra for accessing specific sites (even if you already pay a subscription to the site in question), etc.

Oh, they’re not framing it that way of course. They’re framing it as removing an “unnecessary and burdensome” regulation.

But Title II Net Neutrality is the only legal framework in place that’s preventing, say, AT&T from blocking Skype, or Verizon from blocking tethering apps, or Comcast from slowing down Netflix until Netflix paid them extra — all things that happened in the decade leading up to the rule being adopted.

It’s also keeping ISPs from doing what they do in countries that don’t have net neutrality, like offering different internet packages based on which sites you use. Yeah, they look like cable TV packages. It would suck to be a startup company that’s not included in one of those packages, wouldn’t it? Tricky to make any headway against the entrenched giants.

And just think what might happen if a cable company decided to downgrade (or even paywall) access to news sites or organizations or discussion forums or activist groups that they don’t like, while making it easier to connect to those that they do approve of.

“Please, the Internet was fine before it, so why do we need it?” The Internet was built on the principle. It only became an official, legal requirement after ISPs started violating it, and even then it took several tries to build a requirement that held up in court. And phone companies are still trying to push the envelope with bundling and zero rating.

“But competition will solve it!” Really? How much competition is there when you only have two choices for your ISP, the local cable company or the local phone company, both of which are giant conglomerates — and both of which have violated net neutrality in the past?

“The FTC can regulate it!” Nope, we tried that. Verizon sued for the right to arbitrarily block websites and won, which is why the FCC reclassified internet providers under Title II a few years later.

“This is a matter for the states. Let them handle it.” Verizon and Comcast are lobbying for the FCC’s decision to ban states from creating their own net neutrality rules.

Net Neutrality solves a real problem, and while we may be able to find better solutions, that’s no reason to throw out the solution we have today. Congress can stop the FCC from voting tomorrow, but only if they hear from you today! Go to Battle For the Net and call your Representative and Senators before the FCC votes to sell us all out in favor of your cable company.

Groot reminds us that Net Neutrality is critical to internet freedom, and we should call Congress TODAY, before Thursday’s FCC vote to eliminate the only thing preventing your cable or phone company from blocking competition, burying news they don’t like, and shaking down startups.

Unless you trust your cable company to have your best interests at heart, head over to Battle for the Net and get Congress to remind the FCC that they work for you, not Verizon and Comcast.

Amazing what Groot can fit into just three words, isn’t it? 😉

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.