this post was submitted on 21 Jan 2025
59 points (100.0% liked)
Fedigrow
753 readers
31 users here now
To discuss how to grow and manage communities / magazines on Lemmy, Mbin, Piefed and Sublinks
Resources:
- https://lemmy-federate.com/ to federated your community to a lot of instances
founded 9 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of 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
Lemmy is still saving thumbnails and (previously) sometimes the whole image! The majority of image issues have been cleared up in my opinion and it works very well. Nearly all of our hosts allow hotlinking as it's basically required for our use cases.
Lemmy also knows when the image is another Lemmy instance (through "magic", or just cross posting). So if you upload once and then use that same link on all other posts then that would still be the same.
The problem I think you have is your usecase also includes posting externally to Lemmy. & to some extent, you don't want those images tied to your Lemmy account. If my users post via my instance then they are welcome to also hotlink the images externally. This is only possible because Reddthat uses a CDN and caches the images as much as possible.
Even if we didn't use a cdn there are plenty of VPS' and proxy software that we could use which would transparently function in the same way. You could even setup your own VPS, some image hosting software like https://chibisafe.moe/ or https://github.com/nokonoko/Uguu or https://github.com/hauxir/imgpush
To sum up:
The 3rd option you can do completely anonymously via crypto.
Thank you for the detailed answer!
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.
I was about to say thank you because I have just been finding some random image downsizer online, then I toss it through an EXIF stripper app on my phone and post. But then I checked and found ffshare appears to be just an Android app :( I guess that is what you meant by "Android, at least". I Lemmy from an iPhone and I'm not about to get an Android emulator on my computer just to use ffshare.
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
ffshare
as 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!
supakaity@lemmy.blahaj.zone implemented a custom image proxy for us.
Interesting, so from your admin perspective do you prefer users to use the Lemmy built-in image upload or use a link to an external hoster?
We let people use the built in uploader, then offload the uploaded image to the proxy, and then redirect requests for the uploaded image URL to the proxy. It was the only way we could really deal with the volume of images without having to either limit images or force them to be external
Interesting, but I guess if you had the choice that every user would use an external hoster, that would be easier for you?
I'm trying to ease the load on instance admins as well
That's not a great user experience, so it's not an ideal approach IMO.
Indeed, but it's okay for me 😅
@Nothing4You@programming.dev and @Die4Ever@programming.dev as I see you from time to talking about databases