Photobucketocalypse

by Kelson Vibber, 2017-07-12

Back in the old days, before you could upload photos straight to Facebook or Twitter or Tumblr, if you wanted to share pictures online you had to host them yourself. Or if you used something like LiveJournal, you could use their limited image galleries. But with space and bandwidth at a premium in those days, you could run into limits fast.

That’s where sites like Photobucket and Imgur came in. You could upload your images there, and then put them on your fan site, or your journal, or whatever. They were also good for posting anonymously, as in communities like Fandom!Secrets. And they’re still good for posting images in places like Ebay listings, or online forums (yes, they still exist) that don’t provide their own hosting.

=> Remember Fandom!Secrets?

But you know the problem with hosting your stuff with a third party. You can’t guarantee they’ll stick around. And while Photobucket isn’t closing up shop yet like GeoCities did (taking with it an entire generation of online fandom), they’ve suddenly blocked hotlinking (the main way people used it!)…unless you pay up $399/year for an advanced account.

=> GeoCities, RIP: Fandom’s Lost Pages | PCMag: Photobucket Breaks Image Links Across the Internet. | BuzzFeed minces no words, calling it “ransom.”

So an awful lot of images across the internet have stopped working overnight.

I’m starting to think about all my photos that are hosted on Flickr, now that Verizon owns it. I don’t think they’re likely to do something similar, and Flickr’s paid service is a lot cheaper than Photobucket’s. But Yahoo was never quite sure what to do with it, and Verizon… well…

It might be time to move my “pull in remote Flickr embeds” project off the back burner, just in case.

=> Tech | Self-Hosting

=> Previous: (Ir)replaceable? | Next: Why am I still blogging? (And why about this stuff?)

=> Originally posted at K-Squared Ramblings | Log Home

Proxy Information
Original URL
gemini://hyperborea.org/log/2017-07-12-photobucketocalypse.gmi
Status Code
Success (20)
Meta
text/gemini;lang=en-US
Capsule Response Time
538.09143 milliseconds
Gemini-to-HTML Time
1.179329 milliseconds

This content has been proxied by September (3851b).