- cross-posted to:
- lemmy@lemmy.ml
- announcements@lemmy.ml
- cross-posted to:
- lemmy@lemmy.ml
- announcements@lemmy.ml
You must log in or register to comment.
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:
- It works with all content posted any time before/after the setting was activated
- It lets users decide whether they want to proxy or not
- 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).
Yeah the image proxy will stay off for me. Mangling user’s posts permanently is unacceptable, it’s like the whole HTML escaping thing again. You always want to store the original data in its original form that way you have the freedom to tweak the processing at runtime, and if you fuck it up the data isn’t permanently fucked up (again, like the 0.18 HTML crap that should never have happened).
Damn, I had forgotten about that
The hash tag just adds the community name:
“The hashtag is based on the community name, so posts to /c/lemmy will automatically have the hashtag #lemmy. This makes Lemmy posts much easier to discover.”
Not really putting words in your mouth.
for reference, this is what it looks like on Mastodon, the post to !announcements@lemmy.ml it gets the hashtag for announcements
https://mastodon.social/@dessalines@lemmy.ml/112576601493225058
it’s not really part of the message text, it’s separate
Thank you for this
deleted by creator
If I didn’t type it, it’s putting words in my mouth.
If I want a hashtag, I’ll type one. I don’t give a fuck about Mastodon, and I resent my experience being made worse to accommodate them.
I resent my experience being made worse by reading this
Not everything is about you.
How is your experience worse if you’ll never see the hashtag?
I agree. Lemmy is not Twitter like, it is Reddit like, it is a forum.
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?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.
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.
Oh interesting I will have to look how tessaract does it
- https://github.com/asimons04/tesseract/blob/1.4.0/src/lib/image-proxy.ts
- https://github.com/asimons04/tesseract/blob/1.4.0/src/server/image-proxy.ts
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.
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.
maybe some instances will want “New Comments” to be the default, like old forums
the inclination of people to never adjust default settings
yea lol so many people just will not change any settings on anything
How does automatic hastag inclusion work?
It just puts a hashtag with the community’s name at the end of the post. Like if you post in this community, it would have #fediverse at the end of the post.
Thats cool I guess seems that will help mastodon federation a lot. I dont see why we can’t add arbitrary hashtags for general post tagging tho.
