fedidev

A while back I mentioned the idea of “Fedify Studio”—a web-based toolkit for #ActivityPub debugging and development. I’ve been quietly working on shaping that idea into something more concrete.

This is a list of my favorite side projects and open-source work, collected into a single list so I can pin it to my profile. Replies are welcome!- I'm the creator and lead dev of ModShark, a standalone auto-moderator for Sharkey instances. There's a severe lack of good moderation features for fediverse nodes, but I hope to improve the situation with ModShark and other independent tools.- I occasionally publish fedi-admin-scripts, a small collection of scripts, queries, and documentation for admins of Sharkey and Akkoma instances. The goal here is low-effort knowledge sharing for the benefit of other admins.- One of my larger projects is AP-WAF, a plugin-based extensible firewall for ActivityPub software. I hope it can bridge the feature gap between different fediverse servers by moving low-level moderation and security features into the middleware layer.- I'm building ActivityPubSharp, an implementation of ActivityPub in C#. I'm using a novel approach to model AP's dynamically-typed extensions model in a type-safe way without sacrificing C#'s efficient, strong typing model.- I built little-log-scan as a tool to track botnets and other internet threats. LLS ingests webserver logs through a series of heuristic rules to detect known vulnerabilities, identify payload types, and aggregate metadata. The output is structured for easy research analysis.- As time allows, I'm building Lavender FE - a "universal" frontend for fediverse instances. Lavender is designed to seamlessly integrate multiple accounts, regardless of the instance or backend software.- I curate a list of DotNet-ActivityPub-Projects, which is exactly what it sounds like. My goal is to index all projects that implement ActivityPub using C# or another CLR language.- What started as a meme is now the Expressions AS Extension, an ActivityStreams extension meant to introduce protocol-level support for non-text communication. I hope that Expressions can enable new federated communication modes that are more comfortable to neurodivergent people.- I contribute to Letterbook, a next-generation fediverse server offering simple operation and powerful safety tools. Letterbook incorporates a unique architecture that avoids many of the classic limitations faced by fedi server projects.- I also contribute to Sharkey, a soft-fork of Misskey offering extensive quality-of-life improvements. Sharkey is designed as a safe extension of Misskey's native feature set, providing widespread improvements with minimal risk.#OpenSourceSoftware #FediDevs #FediDev #Introduction

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

Hey @bjoern @Karlitschek @nextcloud #activitypub #fedidev

Been thinking about [fediverse wiki] after @2chanhaeng@hackers.pub mentioned it today. Some ideas:

One consequence of trying to separate identity hosting from the other components of the system is that it makes the other components harder to bootstrap. If I run just one component of my instance in isolation, how can I authenticate to it in order to configure/manage/test it, if I don't have an identity that I can use?The answer might be to use a did:self identifier. The flow would look something like Management CLI tool generates a JWT describing a did:self identifier, and stores the private key locally Admin uses scp or something to copy this JWT to the right place on the server The server now has the ID's public key and so the CLI tool can prove that it "owns" the identifierWhich seems like a reasonable fix for the classic problem of "how do you create the first user", and also a useful fallback for when the system is too badly borked to be able to look up real identities.Another interesting property of did:self is that seems to be possible to add extra metadata, such as a human-readable name, to the ID, by using standard JWT claims - without needing the data to appear in the DID document.Of course these identities will only be visible to the server they're copied to, not to the whole network, but that shouldn't be a major problem.(Cue the peanut gallery, with their suggestions of "it's easy, just do so-and-so", because everything looks easy when you take it out of context...)#ActivityPubDev #FediDev

#activitypub #fediverse #fedidev

TIL: #Mastodon specifically treats actor URIs with the pattern https://<domain>/actor as instance actors.

Alright it's late and i need to go to bed, but here's a draft FEP to do full account migration with posts and whatever other kinda objects you want to bring with you. It's a trivial expansion of existing ActivityPub/streams systems and supports gradual migration as it's implemented and after an account migration. It should be possible to migrate pretty much everything this way, both private and public objects.

If we were to do a regular online Fediverse meeting —

RE: mastodon.social/@reiver/115300I just did a videochat with @sl007 —(This is the first time we chatted.)We talked about a number of Fediverse related things.One of those things was — having a regular (online) meeting.A regular (online) meeting for Fediverse developers, for those who care about the Fediverse as a social movement, and for those who care about the success of the Fediverse.I have heard others say this, too, over and over again.(And, at times, we have had them before.)#Fediverse #FediDev #SocialWeb