Haven’t they always, though? Pretty sure since the beginning it purged anything that hasn’t been viewed for something like 6 months or so. That’s why you got a lot of dead links in old Reddit (or others) posts
If you’re just shitposting dank memes, having the pictures deleted after a while shouldn’t be a big problem. If you’re posting something a bit more valuable, consider keeping the pictures on flickr or even pixelfed.
Is pixelfed really a good way to prevent dead links? I don’t know much about it other than that it’s part of the fediverse, so I’d assume any pictures hosted there last only as long as the instance they’re posted to.
Using flickr or google would be a lighter option. If you put some pictures in a place like that, they are probably going to stay there, but the TOS does leave a very convenient backdoor open. If flickr messes up a database migration, or the datacenter gets hit by a meteor one day, and all of your photos disappear, you can’t hold them accountable. Every option has some issues…
While I’d agree for identifying pictures, image hosting that suddenly doesn’t one day becomes a huge problem for a lot of old tutorial-based content. Look at any old car forum for examples.
I was thinking about this problem recently after I got an email from photobucket that I was over the new limit of photos.
I think a more appropriate place to host tutorial content would be on GitHub.
Imgur announced recently they are going to be purging images that haven’t been viewed for x amount of time.
Haven’t they always, though? Pretty sure since the beginning it purged anything that hasn’t been viewed for something like 6 months or so. That’s why you got a lot of dead links in old Reddit (or others) posts
I don’t think so, I’ve never had this happen in the few cases where I revisited an imgur url after years of not visiting it
If you’re just shitposting dank memes, having the pictures deleted after a while shouldn’t be a big problem. If you’re posting something a bit more valuable, consider keeping the pictures on flickr or even pixelfed.
Is pixelfed really a good way to prevent dead links? I don’t know much about it other than that it’s part of the fediverse, so I’d assume any pictures hosted there last only as long as the instance they’re posted to.
If you choose to use Pixelfed, you should probably be active in your chosen instance and donate regularly.
I suppose you’re right, though that’s quite involved when all I want is to host an image.
Using flickr or google would be a lighter option. If you put some pictures in a place like that, they are probably going to stay there, but the TOS does leave a very convenient backdoor open. If flickr messes up a database migration, or the datacenter gets hit by a meteor one day, and all of your photos disappear, you can’t hold them accountable. Every option has some issues…
That’s not necessarily a bad thing, as long as you aren’t using it for archival purposes. I would prefer not everything I post live forever.
While I’d agree for identifying pictures, image hosting that suddenly doesn’t one day becomes a huge problem for a lot of old tutorial-based content. Look at any old car forum for examples.
For that kind of thing, I’d say host the images with the rest of the content.
I was thinking about this problem recently after I got an email from photobucket that I was over the new limit of photos. I think a more appropriate place to host tutorial content would be on GitHub.
deleted by creator