3 ms·

Not really? Having alts can be a bit like how people have NSFW alts on Twitter (or, for artists, an art account and a personal one), except if you put them on d

by kixiQu 5y ago

Not really? Having alts can be a bit like how people have NSFW alts on Twitter (or, for artists, an art account and a personal one), except if you put them on different instances you can find a local timeline that's more relevant to the kind of thing you're posting. Some people (notably, it seems, Eugen) think "the point" of federation is to provide a seamless Twitter-like global experience that just happens to be hosted modularly. A lot of the current site culture prefers to consider each instance like a little neighborhood, with federation augmenting a local-first experience. (Conflict over product vision ensues.) But really, no matter what you're looking for, the vast majority of the time you can just use whatever instance and it's fine -- mod drama whole-instance-blocks get a lot of attention, but it's way more of a problem in theory than in practice (especially now you can move your followers if you move instances).

rapnie 5y ago
There is also a fork of Mastodon called Hometown [0] that goes further and provides local-only posting as an extra option. These posts will not be federated but stay on the instance (your Home community). A new application GoToSocial [1] also supports local-only posts. [0] https://github.com/hometown-fork/hometown https://github.com/hometown-fork/hometown [1] https://github.com/superseriousbusiness/gotosocial https://github.com/superseriousbusiness/gotosocial
- mariusor 5y ago
  This is mostly a client problem. Mastodon has propagated some pretty lax behaviour with respect to adherence to the ActivityPub protocol, mostly because their reach is very large in comparison with the other projects, and because they just mapped their existing API on top ActivityPub (which was finalized post Mastodon being popular) and that was their existing use case. The ActivityPub protocol itself makes it very simple to keep activities out of the public view. It's Mastodon, and projects that implement AP as a compatibility layer with it that address everything as public.
- kixiQu 5y ago
  and anyone curious about hometown should read: https://runyourown.social/ https://runyourown.social/ :)

by kixiQu 5y ago

rapnie 5y ago

There is also a fork of Mastodon called Hometown [0] that goes further and provides local-only posting as an extra option. These posts will not be federated but stay on the instance (your Home community). A new application GoToSocial [1] also supports local-only posts. [0] https://github.com/hometown-fork/hometown https://github.com/hometown-fork/hometown [1] https://github.com/superseriousbusiness/gotosocial https://github.com/superseriousbusiness/gotosocial

mariusor 5y ago
This is mostly a client problem. Mastodon has propagated some pretty lax behaviour with respect to adherence to the ActivityPub protocol, mostly because their reach is very large in comparison with the other projects, and because they just mapped their existing API on top ActivityPub (which was finalized post Mastodon being popular) and that was their existing use case. The ActivityPub protocol itself makes it very simple to keep activities out of the public view. It's Mastodon, and projects that implement AP as a compatibility layer with it that address everything as public.
kixiQu 5y ago
and anyone curious about hometown should read: https://runyourown.social/ https://runyourown.social/ :)