The code is completely written in JavaScript, so all the code is readable if you look at the source, which is also available on the GitHub page. https://stablenarwhal.github.io/LemmyInstanceMover/js/script.js

It looks like it uses a Lemmy API endpoint to transfer account settings.

Runs entirely in js? https://github.com/StableNarwhal/LemmyInstanceMover

The Billie Irish

That makes sense.

A late pattern in Reddit was personal subreddits - communities named after the account that created them. They were infrequently used, but it provided a smoother pipeline for people who lurked or commented in existing communities to become comfortable making posts and moderating communities themselves.

Ideally these communities would be prevented from appearing in the “Trending Communities” list or local/global feeds unless someone other than the owner was subscribed to them, but wouldn’t be private in the sense that no-one could see them. Just they wouldn’t get wide distribution.

Another pattern is the “Country Club” post - where individual posts in a community could be limited to people verified to post in restricted threads. This comes from BlackPeopleTwitter. The individual verification method is likely not the only way to achieve this. People who comment or vote could be limited to only those who share the instance, are subscribed to the community before the post is made, or are members of instances whitelisted by the community.

Both of these patterns are interpretations of ‘private’ to mean ‘restricted’ and not ‘secret’.

You can see beehaw has a lot less activity now then it had last year.

Fediverse Observer and FediDB show a drop in active users, but the pattern of peak in July 2023 and then a slow regression isn’t unique to Beehaw, and is a pattern seen across the Threadiverse.

You left, but Beehaw being willing to give teeth to the concept of defederation is the reason I joined. I don’t think the decision hurt their user-count. It definitely helped distinguish their culture from the rest of the Fediverse.

Fediverse links to current communities:

• !piefed_meta@piefed.social
• !piefed_help@piefed.social

Hello!

Thatz your sharpnez! Thatz your powa!

I’m really happy for Eugen’s success, and am grateful for his essential contribution to widespread adoption of the ActivityPub protocol, even though I don’t agree with him on a lot of things.

I think it was honest for him to acknowledge Google’s role in sidelining the XMPP protocol, and while I don’t want to quibble about the other mitigating factors, I do take issue with him comparing the trajectory of ActivityPub with SMTP with the visible adoption and mutually assured destruction of major corporations in maintaining email’s nominal interoperability.

If people haven’t read it yet, they should check out (already Fedi-famous for his article on Enshittification) Cory Doctorow’s article Dead Letters – about how it is impossible for even a well-known public figure with access to the best server infrastructure and technical know-how to run a small private email server hosting completely legal content serving nothing resembling spam in the age of Gmail, Yahoo, and Microsoft Outlook. There are several ways that federating with Meta can kill this movement, and ActivityPub becoming the new email is one of them.

Basically, if we allow Meta, BlueSky, and Twitter to federate, the very network effects Eugen mentions make it more valuable for them to federate with each other than any smaller server. Predictably they will underfund moderation staff who make errors or their faulty algorithms automatically de-federate smaller servers due to false-flagging spam. Small operators will have to work harder and harder until it is basically impossible for them to overcome the error or fix the problem and re-federate. Eventually small groups that aren’t directly sponsored by one of the giants will be weeded out, as their users migrate to more reliable services. Even if the disconnections and undelivered messages are not the fault of the sysops, they will be scapegoated, and eventually more and more will throw up their hands and leave the rigged game.

While having a protocol you championed become the defacto web standard may feel like a great accomplishment, the Fediverse will never be a “Social Web” until the tools we use to communicate are incapable of being taken from us by corporations. Eugen’s vision of a social media ecosystem where any small developer can write a platform and have access to the entire ActivityPub network is at odds with his enthusiasm for the emailification of ActivityPub.

There are social obstacles to building the “Social Web” and as good as the Activity Pub protocol is, the true technical solution is Solidarity.