this post was submitted on 07 Jun 2024
175 points (98.9% liked)

Fediverse

28380 readers
1399 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] ptz@dubvee.org 25 points 5 months ago* (last edited 5 months ago) (16 children)

In order to improve interoperability with Mastodon and other microblogging platforms, Lemmy now automatically includes a hashtag with new posts.

๐Ÿ‘Ž๐Ÿป No way to disable this if I don't want hashtags cluttering up my posts. And worse, it's Lemmy putting words in my mouth / speaking for me.

[Re: Image Proxying] The setting works by rewriting links in new posts, comments and other places when they are inserted in the database. This means the setting has no effect on posts created before the setting was activated. And after disabling the setting, existing images will continue to be proxied. It should also be considered experimental.

What an absolutely stupid way to do image proxying. Why not just dynamically re-write image URLs to use the proxy path before serving it via the API?

That way:

  1. It works with all content posted any time before/after the setting was activated
  2. It lets users decide whether they want to proxy or not
  3. Doesn't break images if the home instance pict-rs is broken (which I've been seeing a lot of lately)

If you think "that's not reliable" or "too hard", I've been doing it successfully exactly that way in Tesseract with it's image proxy/cache for over 8 months (on the front end...in a cave...with a box of scraps).

[โ€“] taaz@biglemmowski.win 5 points 5 months ago* (last edited 5 months ago) (2 children)

What a dumb way to do image proxying.

This is about proxying external images, URL rewrite won't work unless the image is also downloaded and hosted by the instance (which seems even worse for many reasons).
Or am I missing something here?

[โ€“] bjoern_tantau@swg-empire.de 9 points 5 months ago

Lemmy will rewrite the image URLs when saving a post.

But instead the URL should be rewritten when loading the post. That way the original URL wouldn't get lost and it would also work for old posts.

[โ€“] ptz@dubvee.org 3 points 5 months ago* (last edited 5 months ago) (1 children)

You're missing a lot.

I've done exactly what I described in my comment for the last 8 months: it's been a UI feature of Tesseract since last October.

It proxies any image or direct video from any source you haven't blacklisted. If you have the proxy option enabled in your settings, all image URLs are re-written to go through the proxy. If not, then it uses the regular URL directly. It also caches with an admin-defined policy.

[โ€“] taaz@biglemmowski.win 6 points 5 months ago (1 children)

Oh interesting I will have to look how tessaract does it

[โ€“] ptz@dubvee.org 5 points 5 months ago* (last edited 5 months ago)

And anywhere it renders an image (markdown, posts, avatars/icons, banners, etc), the image source is set via imageProxyURL(url). There's extra optional params for size and format if the image source is served by pict-rs.

load more comments (13 replies)