These are the two I’m sub’d to:

[email protected]

[email protected] but it’s mostly just pictures of dogs / eye bleach

Keeping an eye on this post to see if any other good ones get posted.

AFAIK, the grouping is done by the API only when you’re viewing a post and by the UI when you’re browsing the feed. Unless 0.19.4 changed this, the call to list posts doesn’t return crosspost data and it has to be done client-side. I’ve grumbled about this a lot lol.

Yeah, like 99% sure, anyway (unless something changed in 0.19.4 I’m unaware of). lol Got an example?

It’ll only show ones the instance knows about, and the URL has to be exactly the same. I’m not sure if there’s an internal limit to the number of crossposts the API will return, but I’ve seen spam posts show at least 7 or 8 crossposts in the list. Any more than that, and I’ve usually already banned the person for spamming.

The posts that show up under “Crossposts” just have the same URL. They don’t have to actually be crossposted. Any post your instance knows about that has the same URL as the one you’re viewing will show up there.

To answer @[email protected] 's question, there’s nothing really special about crossposting in Lemmy. It works the same as creating a new post except it just pre-fills the URL, body, and title as well as adding crossposted from https://instance.xyz/post/12345 to the top of the post body. They’re separate posts and the only link between them is they’re matched on the URL and show up in the “Crossposts” list.

Nice!

It’s possible, yes.

At the very least, the Tesseract UI allows you to group communities and browse them as a single feed. It doesn’t do group posting (yet?) because I’m still not sure how best to implement that (or whether to at all) since it can be spammy.

All that is done in the frontend, and it works, but it would be much better if the backend supported it.

Not sure if other UIs offer similar functionality yet, but it’s definitely possible.

Good to know. And just good in general. lol. It was a fairly simple feature to implement, and I was hoping more UIs would adopt something like that.

Tesseract has for a while, but I’m not sure which, if any, other frontends do.

Ha, thanks. I don’t take half-measures. That’s to say when I delete a post, I purge it as well, so it’s gone gone.

Mine was Thursday, but some asswipes decided to drive-by downvote the anniversary post, so I got demoralized and deleted 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.

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.

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.

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

Perhaps it’s not as active as I’d assumed. I only semi-recently subscribed so mostly have the initial fetch.

Lol, is that why they removed scores from the API? 😆

Interesting.

Still, site bans for criticizing China is just as bad, if not worse as mass community banning.

Yeah, same. Nothing against BH (I understand their reasoning). I end up just crossposting stuff there.

[email protected] also