Re:Your Organization should run its own Mastodon server
by judge2020 on Monday November 07, 2022 @02:02PM
(#33510573)
A good solution I can see is "choose an interest", with each public mastodon instance having some cheeky emoji and tagline in a list. So if someone typed "makeup" they might filter to the mastodon instance "beauty.social", instead of needing to find beauty.social before even getting started with creating an account.
[ Parent
| on HN ]
Re:Your Organization should run its own Mastodon server
by systemicdanna on Monday November 07, 2022 @02:09PM
(#33510717)
The risk of this approach is that you are not picking an interest. You are picking an environment with a set of rules and regulation, an environment that has certain physical constraints (response time, scaleability), an environment that decides which instances you can federate with.
Try explaining that with an emoji and a fun tagline.
Re:Your Organization should run its own Mastodon server
by snapetom on Monday November 07, 2022 @03:58PM
(#33512337)
Then they type "clubbing" or "cars" or "<insert city>" or whatever and see a shit ton of other instances they get to choose from.
This is a *BAD THING* and it's not surprising people here on HN don't see that.
Re:Your Organization should run its own Mastodon server
by dgudkov on Monday November 07, 2022 @05:52PM
(#33513675)
A person typically have multiple interests. Associating yourself with a single interest is usually a bad idea as sooner or later your would want to talk about something else.
It would be way more natural to have interests as channels for a person's account. People could subscribe to only particular interests instead consuming the full stream of the person's posts. I'm not sure if Mastodon supports this, but it's sorely lacking in Twitter.