this post was submitted on 21 Jan 2025
66 points (100.0% liked)

Fedigrow

913 readers
34 users here now

To discuss how to grow and manage communities / magazines on Lemmy, Mbin, Piefed and Sublinks

Resources:

founded 10 months ago
MODERATORS
 

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?

  1. Use a hoster like https://imgbb.com/
  2. Upload pictures locally
top 50 comments
sorted by: hot top controversial new old
[–] ptz@dubvee.org 32 points 1 month ago* (last edited 1 month ago) (3 children)

Whatever solution you use, just make sure it allows "hotlinking" without having to leave the app/Lemmy web interface to see them. If an image doesn't embed, I won't click outside to see it; I'll just scroll past.

I've not had any problems with Catbox, though (I use it to share gifs larger than my instance allows for uploads). It was down a bit yesterday (was going to share a screen recording demonstrating a new feature), but works fine for the most part.

I have read Yarn (gif archive) is sometimes problematic/unreliable, but I usually wrap those in Tesseract's image proxy which addresses it.

For 95% of cases, I just upload directly to my instance. It's got a 250kb max limit, but we use Tesseract as the default UI which can pre-process uploads to webp prior to uploading which will typically get them under that limit.

[–] jet@hackertalks.com 13 points 1 month ago (1 children)

And allows VPN users too please

[–] CidVicious@sh.itjust.works 5 points 1 month ago

Fuck Imgur.

[–] glimse@lemmy.world 5 points 1 month ago

Catbox links are usually fucked on my end.

[–] drkt@scribe.disroot.org 3 points 1 month ago

I have had nothing but problems with catbox, they ban every IP I've had. I emailed them about it and they said "no we don't". Just keep in mind that random people won't be able to see your post if you use catbox.

[–] muntedcrocodile@lemm.ee 15 points 1 month ago (3 children)

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.

[–] db0@lemmy.dbzer0.com 12 points 1 month ago (3 children)

It would be difficult to host. Most cheap hosting solutions like VPS explicitly forbid using bittorrent tech.

load more comments (3 replies)
[–] Blaze@feddit.org 9 points 1 month ago

Could be a good idea, but that seems like a long term improvement. Here we are looking for a solution that wouldn't require changes to the codebase.

[–] gandalf_der_12te@discuss.tchncs.de 4 points 4 weeks ago (2 children)

The problem with media files is more general, it's not just pictures.

This is also why we've never had a (functioning) video platform on the fediverse: Hosting (storage + bandwidth) costs real money. Actually a lot of money. Who pays for it?

Community hosting of large media files would solve the problem (the instance server would only store a hash value). But, there's a lot of questions/problems, such as:

  • what if all seeders go offline simultaneously?
  • privacy issues (seeders can see who requests their data)
  • legal issues (what if somebody uploads illegal material and you seed it?)
load more comments (2 replies)
[–] Blaze@feddit.org 10 points 1 month ago (4 children)
[–] Illecors@lemmy.cafe 6 points 1 month ago (7 children)

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.

[–] Elevator7009sAlt@lemmy.world 3 points 1 month ago* (last edited 1 month ago)

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.

load more comments (6 replies)
[–] Blaze@feddit.org 4 points 1 month ago

@Nothing4You@programming.dev and @Die4Ever@programming.dev as I see you from time to talking about databases

[–] ticoombs@reddthat.com 4 points 1 month ago (1 children)

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:

  • post once to Lemmy instance and then use that image everywhere
  • use a random image host that allows hotlinking to do the same
  • get your own VPS, setup an image upload and use that (and maybe get a domain too!)

The 3rd option you can do completely anonymously via crypto.

[–] Blaze@feddit.org 3 points 1 month ago

Thank you for the detailed answer!

[–] ada@lemmy.blahaj.zone 3 points 1 month ago (5 children)
load more comments (5 replies)
[–] Demigodrick@lemmy.zip 6 points 1 month ago (1 children)

On a personal level I'm not fussed if people use local storage or offsite - i too can't ever see catbox images so that's the only host I have a problem with.

[–] tamlyn@lemmy.zip 3 points 1 month ago (1 children)

According to catbox uk banned the website. That could be the reason and that's why i refrain from using it beimg on a uk instance

load more comments (1 replies)
[–] Libb@jlai.lu 6 points 1 month ago (6 children)

I never considered the question, sharing the (rare) pictures I post using the Upload Image button.

A few years ago I used this: https://postimages.org/
It worked well but I have no idea how trustworthy it is?

[–] Blaze@feddit.org 4 points 1 month ago

Hello,

Thank you for posting this, another person mentioned them as well: https://jlai.lu/post/14514460/12047196

They don't have a browser extension, but I guess that could be a good solution still

load more comments (5 replies)
[–] fxomt@lemm.ee 4 points 1 month ago (2 children)

Upload pictures locally

Too small for me, personally. I love catbox, but it's frustrating that many users can't see its content. I even had to put a disclaimer in latins description as a warning on how to fix it.

I'll look for image hosters then recommend them here.

[–] fxomt@lemm.ee 9 points 1 month ago (9 children)

Testing out postimages, a host specifically for forums

This is a test image, if anyone has problems with it comment please.

[–] I_Miss_Daniel@lemmy.world 5 points 1 month ago (3 children)

I don't see an image, using Voyager.

I don't see any links either.

[–] CubitOom@infosec.pub 4 points 1 month ago (2 children)

I also use Voyager but I see the test image.

[–] Blaze@feddit.org 5 points 1 month ago

The plot thickens

[–] fxomt@lemm.ee 3 points 1 month ago* (last edited 1 month ago) (2 children)

~~Strange... I_Miss_Daniel@lemmy.world may i know what country/DNS you are using?~~

Nevermind, i saw your other comment

load more comments (2 replies)
[–] Blaze@feddit.org 3 points 1 month ago (4 children)
[–] I_Miss_Daniel@lemmy.world 4 points 1 month ago* (last edited 1 month ago) (1 children)

Only if I follow the link. It took a long time to load. Might have been my 4G.

Edit: after visiting the link then returning, the preview image appeared ok.

[–] Blaze@feddit.org 2 points 1 month ago

Interesting, thanks

load more comments (3 replies)
load more comments (1 replies)

Image seems to embed properly in Thunder on Android.

[–] Elevator7009sAlt@lemmy.world 3 points 1 month ago

Image visible.

Just the Lemmy website, iOS

load more comments (6 replies)
[–] Blaze@feddit.org 3 points 1 month ago

Thanks! If there would be an image hoster with an extension that would be great, I just tried using imgbb for a few posts, and it's just much more cumbersome unfortunately

[–] gandalf_der_12te@discuss.tchncs.de 2 points 4 weeks ago (5 children)

AFAIK, pictures aren't duplicated among instances. When you upload a picture, it generates a link on your instance like https://discuss.tchncs.de/pictrs/image/93df1acb-a898-46c9-bc07-d2b7467c345e.jpeg and that link is shared (copied) from instance to instance.

load more comments (5 replies)
load more comments
view more: next ›