For the latest version of lemmy, hot sort works in the new fashion. There is a pull request with further implementation details linked in the GitHub issue.

Ah, fair enough. My response doesn’t apply then.

You misunderstand what the Hot rank is doing. It’s not balancing newness vs hotness, it’s scaling hotness according to community size. This might feel like newness if you’re focused on vote counts as a proxy for post age, but it’s a different approach. See https://github.com/LemmyNet/lemmy/issues/3622 for details.

There’s a couple ways to think about this:

1. There are a handful of Lemmy communities that are just WAY more active than everything else. The main feeds are kind of lame if you have to scroll 300 posts it to find anything other than a shit post from the same 3 communities. Scaled Hot rank shows a greater variety of communities by making it easier small communities to get ranked hotly.
2. Or you can consider Hotness to be a rough measure of what percentage of people who have seen the post interacted with it. A post with 500 upvotes in a community with 10,000 active users is kind of popular, but only 5% of the people likely to have scrolled passed it cared about it. A post with 50 upvotes in a community with 200 active members is much MORE popular relatively even though the absolute numbers are smaller.

At any rate, this preference toward smaller communities in hot is a recent change and deliberate. While they might further tweak the scaling factors, I wouldn’t expect it to be drastically different. It sounds to me like what you want is Top, Active, or Most Comments. All these are unscaled according to community size and will get you top posts by their absolute metric rather than posts that are doing well relative to their community size.

Have you emailed admin@lemmy.world to try to get reinstated? This all seems like a pretty reasonable explanation if it isn’t repeated behavior.

I feel like you’re combatively advocating for a specific vision and not collecting and processing feedback as your OP suggests, at any rate… you don’t seem to be understanding what I was trying to say at all… but it’s not something I’m going to fight about with someone who is questioning if I know what a multi-reddit is and dismissing client-side techniques as nonsense without seeming to understand why they were being discussed in the first place.

I’ll leave with these thoughts, do with them what you will:

1. I’m not interested in any multireddit feature that reduces sub privacy. I’d consider it a net loss for lemmy.
2. On Reddit, multi-reddits personal in nature. Such a personal multireddit for lemmy doesn’t require interaction with federation or privacy changes.
3. I realize that a shared super-community feature is frequently requested on Lemmy aimed at addressing duplication of communities across instances. I don’t think that’s more than superficially similar to actual multireddits, and I don’t think it’s a good idea because it creates moderation problems that are far worse than the community duplication problems it purports to address.

What you’ve described is one way. It could also be a filtered view based on the subscribed/all feed which provides a single API call that can return material from multiple communities. I’m not suggesting that a client-side only solution is a GOOD solution. But from an information-flow perspective, I’m suggesting that multireddits are a “local” function. Theu are so local that they’re possible without server-side support at all, and especially local enough not to require representation in the federated feed… which is a more significant change with potential impacts to other federated projects like kbin and mastodon… and shouldn’t require relaxing privacy constraints in any case.

Anyway, what’s the feedback on privacy issue with allowing any user to have read-only access to your community subscribe list…

I wouldn’t want this in exchange for multi-reddits. You can a little bit infer the communities someone subscribes to from their comment activity, but as it stands one can choose to privately lurk and this would eliminate that… silently for existing users in the absence of some big series of announcements to make it well known.

Why are multi-reddits a thing that involves federation at all? Multi-reddits as they exist on Reddit itself could be implemented entirely client-side, the server side stuff just syncs the behavior of multiple client apps. Why does the concept of a multi-reddit need to extend outside of the user’s instance?

Another comment links an older article about freenom (the registrar that is having .ML taken away) losing .ga previously and a plan to delete millions of .ga domains that were being used for abuse. Presumably the .ML situation is another abuse cleanup, though I can’t find confirmation.

That then leaves the question of whether the Lemmy instance that went down was correctly flagged for abuse (I heard it was focused on piracy?) or whether an appeal could get it back for them.

https://lemmy.world/comment/1547287

I’ve found several articles similar to this, but transfer of management of a TLD from one registrar to another generally shouldn’t result in breakage of registered domains. And nothing in that article (nor any of the others I’ve found) suggest that Mali plans not to honor existing registrations (which all expire eventually anyway, so they have an orderly way to reclaim things by refusing renewal if they wish).

There’s more going on here that hasn’t been reported (or that I haven’t found) yet.

Tests go in !test@lemmy.ml

Yeah, federation is being creaky globally right now. The GitHub issue list is littered with admins reporting intermittent federation issues.

I wouldn’t expect it to repeatedly prevent communication though. Just maybe some intermittent issues occasionally.

Many servers have been struggling lately, especially lemmy.world. When that happens, they frequently time-out when comments/posts are submitted, even though the comment/post was processed… the client doesn’t realize and behaves to the user as of the comment/post failed. It didn’t fail though.

Lots of people resubmit without checking to realize it actually worked the first (or fifth) time, resulting in dupes. lemmy.world just fixed a bunch of performance problems and submitted PRs to the devs to fix them for everyone else too. With the improved performance, you should see less of these dupes going forward as the number of timeouts is reduced. But it’s another bug that clients get confused about whether a post went through or not. Maybe that will get sorted soon also.