Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Imgur and ImgBB support #31

Open
corbindavenport opened this issue Oct 28, 2024 · 0 comments
Open

Imgur and ImgBB support #31

corbindavenport opened this issue Oct 28, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@corbindavenport
Copy link
Owner

The older PHP-based ImageShare supported up to three different upload options, depending on the device and server configuration:

  1. ImgBB "anonymous" uploads with a server-provided API key - This uploaded photos to the ImageShare ImgBB account with a two-minute automatic deletion timer.
  2. ImgBB uploads with a user-provided API key - This stored photos in the user's own account, but didn't work on the Nintendo 3DS Browser and other browsers that couldn't store cookies properly.
  3. Imgur anonymous uploads with a server-provided API key - This worked the best, but Imgur blocked API access to the main ImageShare server, so it only worked for other people setting up their own servers.

The new version of ImageShare (#28) switched to temporary built-in image hosting as the mechanism for sharing images and videos. This was done primarily because Imgur already cut off API access for the main server, and ImgBB starting to throttle API access on free accounts.

If there is sufficient demand, or someone is willing to do PRs, Imgur and ImgBB could be implemented again as alternative upload methods. There are a few factors to consider for alternative upload methods:

  1. The upload form would have to be customized for each service. For example, ImageShare currently accepts all image and video files, but Imgur only supports a few specific video and audio formats.
  2. Error handling for each service would have to be implemented, with messages displayed to the user.
  3. Images should be deleted from the ImageShare server after they are uploaded to the third-party service.

Third-party hosting support adds a lot more complexity to ImageShare, which is why it was left out of the rewritten version.

@corbindavenport corbindavenport added the enhancement New feature or request label Oct 28, 2024
@corbindavenport corbindavenport mentioned this issue Oct 28, 2024
21 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant