been thinking about moving my main account to a selfhosted instance but i dont wanna run an instance of anything that exists currently, especially not in public mode
-
been thinking about moving my main account to a selfhosted instance but i dont wanna run an instance of anything that exists currently, especially not in public mode
-
oblomov@sociale.networkreplied to trwnh@mastodon.social last edited by
@trwnh I have a similar issue. I really want to self-host, but I'n not satisfied by anything that exists today. I'd need something like a cross between Vocata, GoToSocial and Streams
-
fentiger@mastodon.socialreplied to trwnh@mastodon.social last edited by
@trwnh Likewise ... when I finally go self hosted, it'll be my own implementation from the ground up ... and I haven't even designed half of it yet
-
bmordue@mastodon.scotreplied to oblomov@sociale.network last edited by
@oblomov @trwnh I hadn't come across vocata yet, interesting readme in that repo, so thank you. I've had similar thoughts re selfhosting. I'm curious to hear in more detail: what is it about the projects you mentioned that is currently lacking? What is your desired set of features that none of them fully implement (yet)? (FWIW, I was personally leaning towards GoToSocial, but will now do some more reading on vocata).
-
oblomov@sociale.networkreplied to bmordue@mastodon.scot last edited by
@bmordue @trwnh I think it's faster to tell you what they DO have that I like.
Streams has a way to effectively implement nomadic identities on top of ActivityPub. But until/unless the FEPs to standardize it <https://wedistribute.org/2024/03/activitypub-nomadic-identity/> gain wider adoption, it's the odd one out with it.
Vocata is exactly what I would expect from an AP server: completely content agnostic, simply fills the graph. But it has no UI.
GoToSocial seems to be the simplest to self-host for single users.
-
oblomov@sociale.networkreplied to oblomov@sociale.network last edited by
Also, none of them does what I would like, which is to use a database only for speed, but actually store the objects as .json files on disks, ideally with an actual XML RDF counterpart to go with them, but that's a different matter.
-
trwnh@mastodon.socialreplied to oblomov@sociale.network last edited by
@oblomov @bmordue yeah i'd like flat file storage with on-the-fly RDF conversion
in more practical considerations, i think gts is doing some interesting things but i disagree with the decisions being made re: "authorized fetch" and "unlisted" posts
i currently personally run an akkoma instance that has a custom MRF to strip Public addressing from all objects, if that gives you any indication of what i think
