@Mastodon
I have a few doubts which I know you may not have answers for, but I'd be interested to see how (if at all) you are thinking about it
1. Gab created it's own instance which was why you were able to blacklist them. What happens if trolls infiltrate Mastodonsocial enmasse
a. How would paid toots' content play out
b. What fact checking tools are available
c. Since usernames aren't unique across instances how do we deal with new ways of phishing
@Mastodon
d. Imagining that most of the new waves of users consolidate on one instance, do you just plan to keep scaling up human moderation
@micahalex @Mastodon
a. imo, paid toots are antithetical to the decentralized, no-ad-revenue based model of Mastodon; that being said, it's entirely possible that a specific instance would implement it, in which case, it would be up to that instance to control the content
b. Good ol' common sense.
c. No technical solutions, with than possibly Keybase integration
d. I think the main mechanism Mastodon has to avoid over saturation of an instance is turning off open registration.
@jump_spider @Mastodon a. By paid toots I also mean bot armies and cloned content meant to overwhelm feeds
@micahalex @Mastodon
- Instance admins can block registration based on email domain; registration can also be semi-open, requiring a registration request that needs approval before the account is made
- Users can mute and block accounts
- The nature of the home timeline is such that it can't be spammed without a user's consent
