Groups | Search | Server Info | Login | Register
Groups > comp.infosystems.www.misc > #186
| From | John <john@building-m.simplistic-anti-spam-measure.net> |
|---|---|
| Newsgroups | comp.infosystems.www.misc, comp.misc |
| Subject | imgur / image-upload API specs |
| Date | 2023-06-28 03:34 +0000 |
| Organization | Building M |
| Message-ID | <86mt0kmf9j.fsf@building-m.net> (permalink) |
Cross-posted to 2 groups.
The recent decision by imgur to delete non-account-associated uploads got me thinking about WWW resource persistence and self-hosting yet again. People used imgur because it was convenient and free; uploading an image and sending a link was a simple process. Imgur also had an API which applications could integrate with, so for example flameshot can just upload your screenshots directly to imgur if desired. Most of these applications just assume you're uploading to imgur, but if some other server implemented the same HTTP API endpoints, it would be a drop-in replacement--but I haven't heard of anything like that! Is anyone aware of open-source servers which implement an Imgur-compatible API, or of efforts to define a "standard" set of endpoints for image uploading and retrieval? Seems like it ought to be an RFC or something but maybe that's a little out of their scope. john
Back to comp.infosystems.www.misc | Previous | Next — Next in thread | Find similar
imgur / image-upload API specs John <john@building-m.simplistic-anti-spam-measure.net> - 2023-06-28 03:34 +0000
Re: imgur / image-upload API specs not@telling.you.invalid (Computer Nerd Kev) - 2023-06-29 09:14 +1000
Re: imgur / image-upload API specs John <john@building-m.simplistic-anti-spam-measure.net> - 2023-06-29 01:49 +0000
Re: imgur / image-upload API specs Computer Nerd Kev <not@telling.you.invalid> - 2023-06-29 13:20 +1000
Re: imgur / image-upload API specs Ivan Shmakov <ivan@siamics.netNOSPAM.invalid> - 2023-06-29 08:12 +0000
Re: imgur / image-upload API specs Eli the Bearded <*@eli.users.panix.com> - 2023-07-03 01:47 +0000
csiph-web