A little light on details :)

Yeah sorry, that’s my bad, I meant to link it. This is a very good summary.

The media type handler is preconfigured with a good default that can be optionally overridden.

Runs locally and connects directly to the desired “resource” (community, account, etc) across anything(?) on ActivityPub rather than via a server or instance.

This is correct, I just don’t know what you mean by “across anything(?)”.

Source is available here (GPLv3): https://github.com/BentonEdmondson/servitor

It is written in Go.

This is a client I’ve been working on that doesn’t require you to have a server. Let me know what you think.

This is a client I’ve been working on that doesn’t require you to have a server, so you don’t have to deal with defederation, your server going down, etc. It works with Mastodon in addition to PeerTube, Lemmy, etc.

Yeah, I’m surprised there aren’t any others at this point. Especially considering activitypub has been around for 5 years

This is a program I’ve been working on. It is structured like an RSS reader, so all your subscriptions are stored locally. It works with Mastodon, PeerTube, etc, and is designed more so for technical users.

This is a Fediverse client that I’ve been working on. It is structured like an RSS reader, so it doesn’t require a server. This means you don’t have to worry about defederation, servers going down etc. Let me know what you think.