2 ms·
yeah I replied in sibling thread, mostly topic based instances and federation is the problem. (when identity is bound to host) When I first saw Mastodon and to
by bluesign 6y ago
yeah I replied in sibling thread, mostly topic based instances and federation is the problem. (when identity is bound to host)
When I first saw Mastodon and topic based servers, I was thinking "photography" hosts will federate between each other, "developers" between each other etc. If you are a photography liking developer, you will have 2 accounts, one in "photographers in SF" instance, another one "developers in SF" maybe.
- andrewzah 6y agoI do agree that because mastodon became focused around specific niches per host, it made things much more complicated for new users. Do I join mastodon.social? Do I join bsd.network? Do I join writing.exchange? Etc. What I realized was I should have been asking: Do I care about the federated timeline? Do I care if my host blocks other hosts at random? Do I care if my host allows certain things (I.e. pornography with or without a NSFW tag, or at all). Do I know who the host is and can I trust them with my private messages and to not randomly ban me? I personally like seeing the federated timeline as I have discovered some accounts through it. But my host absolutely needs to do some filtering because some hosts will allow -anything-. I never really found much use for the local timeline. So for me, hosting was clearly the best option. I do try to get my friends to consider joining the fediverse, and I offer hosting to them to solve this issue.