Subscribe to all of them. It isn’t an issue. In the next Lemmy version should have Multi community support too. Which should help solve things a little. (So then you can group them all into one).

Also with it on different domains, it means that there is a benefit for the longevity of the sysadmin (or any) community. As if one domain goes dark the others will work :)

Need a column on the far right, “posting to reddthat”

Thanks. We sorted it!

<3

It’s been sorted on our side! Thanks for the pings

This might be another bug relating to federation, but might also be relating to caching on their end. Or because every Lemmy application keeps their own archive, it’s possible the user display name doesn’t federate on a change but only on a post that they can see? (Or not at all, or only on a timed refresh?)

Lets check after 24/48 hours on those links and we’ll see what they say after that.

I too think it’s possibly a software bug rather than a cache issue. We don’t cache anything if you are signed in, and if it was a cache issue it would show both of the old names on the page rather than only one changing.

Oops! Sometimes we admins like to joke around!

Hey! Sorry for the joke, I didn’t expect it to be seen by a real user!

As we are one of the very few instances that has a no email policy there is very few ways in which we can determine if a person signing up is a bot or a regular user.

Recently a very very specific person or group of people have been abusing Reddthat to create accounts, then ask interesting questions (let’s just say that), and then proceed to delete their account (which deletes all of their posts and comments). This makes it impossible to figure out what they have done unless someone quotes the reply or reports it before they delete it.

I’m sorry you got caught up in the little bit of fun us admins have with writing little anecdotes or fun catch phases!

You are welcome to come say hi on Reddthat any time!

Cheers for the ping :)

Single user? We have 300+ users who actively call Reddthat home and we won’t be going anywhere. We are nearly cash flow positive thanks to our amazing users and recurring donations.

I’ve seen your posts and as your mod on !aom i’d be happy to make you mod of our !rts community to help grow it!

Edit: I know @reddthat@reddthat.com would love the help

Looks easy : https://www.ifixit.com/Guide/Steam+Deck+SSD+Replacement/148989

Edit: Is it worth 30-60minutes of your time, the screwdrivers, maybe the spatchula, and reinstalling steamOS onto the drive?

Federation between Onion and Standard Domains that way tor users would not be isolated

This is the hardest part as you would need to be both have an onion and have a standard domain, or be a tor-only Federation.

You can easily create a server and allow tor users to use it, which unless a Lemmy server actively blocks tor, you’d be welcome to join via it. But federation from a clearnet to onion cannot happen. It’s the same reason behind why email hasn’t taken off in onionland. The only way email happens is when the providers actively re-map a cleanet domain to an onion domain.

This is what Lemmy would need to do. But then you would have people who could signup continuously over tor and reek havok on the fediverse with no real stopping them. You would then have onion users creating content that would be federated out to other instances. & User generated content from tor users also is … Not portrayed in the best light.
I’m sure someone will eventually create an onion Lemmy instance, but it has it’s own problems to deal with.
This is especially true for lack of moderation tools, automated processes, and spammers who already are getting through the cracks.

I can confirm the sections around downvotes as Reddthat has the stance exact what you are talking about (re your child comments)

A downvote disabled instance creates it’s own algorithm/feed/ranking based purely on all other metrics, because as far as the data is concerned, it sees every post having 0 downvotes. It does not take into account external instances.

I can answer the first point.
We’ve already tackled part of that problem with the Parallel Sending feature that can be enabled on instances with a tremendous amount of traffic. Currently the only instance that makes sense to enable that is LemmyWorld and the only reason is so servers in geographical far away can get more than 3-4 activities/second.

With that feature, servers that eventually house and generate the biggest amounts of traffic will be able to successfully communicate all of those activities to everyone else who needs them.

I predict a 10x increase is well in our grasp of easily accessible by all of our current systems. 1000x? That’s a different story which I don’t have the answers too.

😁👍 Happy to be a sacrifice for the greater good

I can’t wait! We’ll finally get to do a real world test for the parallel sending features!! And if all goes well I’ll get to save 5 Euro a month!

Thanks LW

Thank you for the update and it’s good to hear your upcoming plans. Being one of those people in Australia (Reddthat) it will be good to see if it actually works as it’s designed too!
I’d love to save $7/m to not have a server dedicated to batching the federation traffic 😅

When you lay out the timelines for 0.19.3 onwards no time at all has gone by, and having to deal with the issues after .3 has certainly not been fun as an admin. (And I’m only a small server compared!)
Being such a huge player in our Lemmyverse, thanks for taking the time to plan this out as I know how much testing has been done to get us this far.

It’s always a nice experience chatting to the LW team!
Hope your updates go smoothly!

I too would love to know what your experiencing (so I can fix it!)

This is sso support as the client. So you could use any backend that supports the oauth backend (I assume, didn’t look at it yet).

So you could use a forgejo instance, immediately making your git hosting instance a social platform, if you wanted.
Or use something as self hostable like hydra.

Or you can use the social platforms that already exist such as Google or Microsoft. Allowing faster onboarding to joining the fediverse. While allowing the issues that come with user creation to be passed onto a bigger player who already does verification. All of these features are up for your instance to decide on.
The best part, if you don’t agree with what your instance decides on, you can migrate to one that has a policy that coincides with your values.

Hope that gives you an idea behind why this feature is warranted.