|
||
---|---|---|
.forgejo/workflows | ||
ap | ||
cmd | ||
config | ||
devserver | ||
frontend-noscript | ||
frontend-reactive | ||
mailer | ||
pk-auth | ||
plugins | ||
queues | ||
server | ||
storage | ||
util | ||
.gitignore | ||
authentication-flow.md | ||
bootup-sequence.txt | ||
Code-Style.md | ||
CODE_OF_CONDUCT.md | ||
Containerfile | ||
CONTRIBUTING.md | ||
duck.webp | ||
example_config.toml | ||
featureTargets.md | ||
flags.go | ||
future-useful-libs.md | ||
go.mod | ||
go.sum | ||
goals.md | ||
LICENSE | ||
main.go | ||
masto-api-endpoints.txt | ||
mod-tools.md | ||
README.md |
Linstrom is a new social media server with the focus on providing users, moderators and admins alike simple, yet powerful features to moderate the experience.
Federation
It is planned that Linstrom will federate at least with other Linstrom servers, but also possibly via ActivityPub and ATProto.
It was never intended to be completely standalone, only existing for itself, but rather to join at least one of the growing networks and interoperate with those networks.
Why Linstrom when <insert ActivityPub server here> already exists?
Because of moderation tooling. I have a bunch of friends that happen to be the moderators or owners of various servers with differing software (Sharkey, Mastodon, Akkoma as example). And they all have different woes with their software.
I want to try and make a server that combines the strengths of various project's tooling while also hopefully solving some of the weaknesses.