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).
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?
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.
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.
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).
“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.”
👎🏻 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.
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:
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 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
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.I agree. Lemmy is not Twitter like, it is Reddit like, it is a forum.
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.
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.
Not everything is about you.
I resent my experience being made worse by reading this
How is your experience worse if you’ll never see the hashtag?
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
deleted by creator
Thank you for this