You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imgur recently announced their plans to delete "old, unused, and inactive content". In this case, uploading images using Imageshare to Imgur longer term may not be a good idea, as that content could in theory be lost later on down.
It seems the code is simple enough to switch to another API, but I don't want to recommend any specific one; this is more of a notice than an actual "issue", especially if users consider the images sent to imageshare as ephemeral.
Thank you for this service and code!
The text was updated successfully, but these errors were encountered:
I would say this isn't a massive problem for ImageShare's specific use case, because it's mostly intended for transferring images to another device (where it's downloaded/reuploaded somewhere else) rather than permanent access through Imgur. I've tried to make it ideal for both use cases though (e.g. adding the game title to the Imgur post), so it's still annoying that images might get deleted.
Long-term, I want to look into optional support for authenticating with Imgur through ImageShare. That would fix the images being deleted (Imgur isn't removing media tied to an account), and it would also allow images to be immediately accessible through the Imgur app or site without scanning anything. That would need a special auth flow (Imgur does not directly connect on 3DS/Wii U anymore) and some other features though, so not sure yet if that's feasible.
I agree more image hosting/transfer options beyond Imgur would be good, though. ImageShare used to use ImgBB but the API there was limited. Sending images as attachments via email could also be useful.
Imgur recently announced their plans to delete "old, unused, and inactive content". In this case, uploading images using Imageshare to Imgur longer term may not be a good idea, as that content could in theory be lost later on down.
It seems the code is simple enough to switch to another API, but I don't want to recommend any specific one; this is more of a notice than an actual "issue", especially if users consider the images sent to imageshare as ephemeral.
Thank you for this service and code!
The text was updated successfully, but these errors were encountered: