A command-line Fediverse client that doesn’t require a server - GitHub - BentonEdmondson/servitor: A command-line Fediverse client that doesn’t require a server
Allows (requires?) configuration to use whatever you want to handle various media types.
Runs locally and connects directly to the desired “resource” (community, account, etc) across anything(?) on ActivityPub rather than via a server or instance. Among other things, this means your subscriptions, follows, etc remain unknown to anyone.
Lurk-only: Not being actually registered on an instance or formally subscribed or following implies read-only access and that is supported by the lack of any mention of how to enter “post” or “response” mode.
This is an unofficial summary based only on the readme. I have neither inspected the code nor even installed and tried the software.
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(?)”.
A little light on details :)
https://github.com/BentonEdmondson/servitor
Language: Go (100%)
GPL 3.0
Allows (requires?) configuration to use whatever you want to handle various media types.
Runs locally and connects directly to the desired “resource” (community, account, etc) across anything(?) on ActivityPub rather than via a server or instance. Among other things, this means your subscriptions, follows, etc remain unknown to anyone.
Lurk-only: Not being actually registered on an instance or formally subscribed or following implies read-only access and that is supported by the lack of any mention of how to enter “post” or “response” mode.
This is an unofficial summary based only on the readme. I have neither inspected the code nor even installed and tried the software.
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.
This is correct, I just don’t know what you mean by “across anything(?)”.
Poorly phrased :)
I was guessing that it could connect to anything that uses ActivityPub, but wasn’t sure.