Fediverse

Media

There is a new functionality for users to list all images they have previously uploaded, and delete them if desired. It also allows admins to view and delete images hosted on the local instance.

When uploading a new avatar or banner, the old one is automatically deleted.

Instance admins should also checkout lemmy-thumbnail-cleaner which can delete thumbnails for old posts, and free significant amounts of storage.

This is great news, and addresses what was until now a big shortcoming... a user had no way of managing uploaded images and admins had to crawl through the DB to manage or delete them.

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).

This is buried toward the bottom of the release notes so I'm bringing it up here:

Added instance-level default sort type

Any admins out there considering changing their instance sort settings or asking people on their instance if they'd like this changed, given that we can individually set sorting anyway? Taking into account the inclination of people to never adjust default settings (I remain deeply curious about this tendency, as an aside), I think it might be worth at least bringing up to one's instance community.

If they decide they want it to remain the same, all good, and even better, it raises some people's awareness that they can change it themselves.

How does automatic hastag inclusion work?