Comment

Comment on The two most upvoted comments on any Lemmy instance are on Feddit.dk, but you won't see them on your own instance

<- View Parent

catloaf@lemm.ee ⁨1⁩ ⁨week⁩ ago

True, but that’s why I mentioned a cache or cooldown. Once every two minutes is plenty, unless Lemmy really blows up and we have hundreds of instances trying to fetch a very popular post.

You have a point about new sort, but you could approximate it by sorting what’s known to an instance. It’s not ideal, but it’s at least something. Maybe it would make sense to push just that feed, or to fetch a subset periodically.

I read that comment tree, but it doesn’t answer my question. If someone on Mastodon likes a post on feddit.dk, I don’t see any reason feddit.dk can’t communicate that to lemm.ee when I go look at it.

source

Sort:hotnew top

SorteKanin@feddit.dk ⁨1⁩ ⁨week⁩ ago

Once every two minutes is plenty,

That won’t work, because it would have to be once every two minute for every single comment and post forever.

You have a point about new sort, but you could approximate it by sorting what’s known to an instance. It’s not ideal, but it’s at least something. Maybe it would make sense to push just that feed, or to fetch a subset periodically.

I have no idea what you mean by this - you can’t fetch a feed, that’s not at all how the data is organised.

If someone on Mastodon likes a post on feddit.dk, I don’t see any reason feddit.dk can’t communicate that to lemm.ee when I go look at it.

The problem is this: How does lemm.ee know that the like that feddit.dk claims is from mastodon.social actually is from mastodon.social? What prevents feddit.dk from just fabricating a like from mastodon.social? Currently there is no nice mechanism for authenticating such a forwarded like. A malicious instance could send loads of likes claiming they come from other instances.

source