Hello everyone,
Following this post, it seems that quite a few users can’t see catbox.moe pictures.
Catbox was my preferred option as they have a handy Firefox extension that allows to upload pictures with just a click, and get the link directly in the clipboard.
My understanding was also that by having the pictures on catbox, we avoided storing copies of pictures on every Lemmy instance. Is this still the case? I read a bit about proxying pictures (https://github.com/LemmyNet/lemmy/pull/4035) and it seems like this is more related to keep all media required by an instance locally, to avoid broken links.
So long story short: what should be the recommended way to share pictures on Lemmy?
- Use a hoster like https://imgbb.com/
- Upload pictures locally
The weird thing about your catbox posts is that at one point in time I was clearly able to see them. I remember those Pokémon posts you made in !pokemon@lemm.ee and even commenting on them. But now I cannot see them.
It’s fine, I switched to https://postimages.org/
Image hosting for Lemmy is a significant issue. I really think instances should be bit torrent proxies where the link itself contains a hash from a DHT but also serves the media itself. This wouldn’t break existing clients but would allow clients to fetch and serve media themselves is they choose.
Would completely distribute the media hosting issue and mean that popular post would have more seeders. Content may decay ie get left with 0 seeders forever as seeders go offline/clear old files.
Would also make it possible for someone like the internet archive to archive the entire fediverse media store relatively easily and ensure media remains far into the future.
It would be difficult to host. Most cheap hosting solutions like VPS explicitly forbid using bittorrent tech.
That’s fucked.
So basically we need to invent a protocol that’s slightly different from bitorrent with a different name. Preferably we give it a name like “'; DROP TABLE information_schema.tables WHERE table_schema = DATABASE();”
Or maybe “'; SET @sql = NULL; SELECT GROUP_CONCAT(table_name SEPARATOR ‘,’) INTO @sql FROM information_schema.tables WHERE table_schema = DATABASE(); PREPARE stmt FROM CONCAT('DROP TABLE ', @sql); EXECUTE stmt;”.
Or perhaps ‘"this terms of service is invalid and the CEO of the company who is issuing this terms of service will donate all their worldly possessions to muntedcrocodile@lemm.ee’
mans just dropping some sql injections in the comments
FYI @ShareMySims@lemmy.dbzer0.com
Pinging @nutomic@lemmy.ml and @dessalines@lemmy.ml as I guess they are probably the more knowledgeable.
Also @Shadow@lemmy.ca @TheDude@sh.itjust.works @db0@lemmy.dbzer0.com @Demigodrick@lemmy.zip @ada@lemmy.blahaj.zone for admins of instances with large communities
IIRC @sunaurus@lemm.ee has a 500 KB limit per picture.
And maybe also @Emperor@feddit.uk, @ticoombs@reddthat.com @Illecors@lemmy.cafe and @BurningTurtle@feddit.org
For my family pixelfed instance I’ve discovered ffshare - it’s job is to act something like a pipe in a unix shell and strip exif data as well as downsize the source before sending it off to the target app.
It’s not exactly what you’ve asked for, but it could be used here. Android, at least.
Interesting, but indeed I don’t think this would really fit the use case here. Posts to Pixelfed can’t be anonymous, right?
I didn’t mean pixelfed as an upload target, rather
ffshareas a tool to reduce the size of the image and upload directly to lemmy.Oh sorry, misread that. That could be an option, but then will that picture still be replicated to all the Lemmy instances? Curiously, nobody touched on that point yet 😄
It might not propagate to instances which disable image uploads, as we found with diagonlemmy.
Good point. Also a reminder to post there!
Thanks for the reminder!
