I use Lensdump - I see you can now upload video too.
Catbox is a weird one - I could see images but not video or the main page through Wi-Fi but it works on mobile signal. After getting my phone repaired it now all works. Which I can't explain.
To discuss how to grow and manage communities / magazines on Lemmy, Mbin, Piefed and Sublinks
Resources:
Megathreads:
Rules:
I use Lensdump - I see you can now upload video too.
Catbox is a weird one - I could see images but not video or the main page through Wi-Fi but it works on mobile signal. After getting my phone repaired it now all works. Which I can't explain.
After getting my phone repaired it now all works.
That's wild ha ha
Lensdump looks cool, but requires an account, correct?
And a donation to create an account fyi. I’m fine w donating to good projects just letting know
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.
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.
Catbox links are usually fucked on my end.
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.
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 [email protected]'
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.
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?
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
Pinging @[email protected] and @[email protected] as I guess they are probably the more knowledgeable.
Also @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] for admins of instances with large communities
IIRC @[email protected] has a 500 KB limit per picture.
And maybe also @[email protected], @[email protected] @[email protected] and @[email protected]
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 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.