Great thread. I've been concerned that *governance* is the part of the solution that will determine if #Mastodon remains viable, scalable and equitable.
The dialogue is focused so much on the work of unpaid mods, which is unfair and doesn't scale.
Really looking forward to seeing the different models that evolve here in response to community priorities and needs.
@lakelady @schock I'm not sure about US but in Canada there are lots of smaller ISP's, most lease the lines from the big players (it's regulated by the CRTC)... Pretty sure it's very similar in Europe... France at least (you can even choose you electricity provider there!)
You always have the choice to pick your own instance, and even run one yourself. It's not a lock-in but I think it could help with mass adoption...
@[email protected] @[email protected] the privacy commissioner of the state Baden-WĂĽrttemberg is hosting an instance open only for state institutions: https://bawĂĽ.social/ there are also quite a few other instances referring to cities, regions and states, but they are often independently run: https://nrw.social https://berlin.social/ https://ruhr.social/ https://freiburg.social/
@brennansv @schock @cd24 @seb yes (need to catch up on the whole thread) - I think hosting an instance and moderation may be separate services and both likely candidates for a government contractor (and as an offering for other orgs and businesses).
It will take more than just setting up the servers. Governments likely need a plan for archiving & record retention (as will any regulated businesses). And managing shared accounts & access /security
Its already happening. Some early forays (Canadian is an NGO):
cira.ca/newsroom/corporate/cira-teams-mastodon-canada-support-canadian-digital-communities
@brennansv @beatty I think the powers should be well separated, just as you separate judiciary/executive in democracy:
- moderators should be able to know e.g. whether a new account belongs to a physical person, how many and which other accounts they have on other instances, and whether they were banned somewhere for some amount of time. For some topical instances, some other details could be legitimate to know, eg place of residence.
1/n
- on the other hand, moderators (and other internet-based services) don't have to know about personal details that would be convenient to identify the person for sure, such as see a proof of name and of address, eg passport or utility bill. This is where the idea of a federated network of #identity providers comes: similar to opencheck.is, they are trusted with information one won't share directly with the service. You use orcid connection, but it could be a passport check.
@brennansv @beatty Exactly! Privacy combined with identity.
If there are multiple federated identity provider, one always has the possibility to give up the identity that was verified with one and start over with another provider. This is like starting a new life under a new name: that gives one a right to error, but comes with a big cost since all one's internet life does start over from zero. I think this is rather balanced between right to be forgotten vs accountability.
Thinking again of the car rental as example:
Car rental company needs to know that you have a driving licence and that they can tell the police who was driving the car *in case* there's something wrong. So id provider can certify to them the *existence* of a valid driving licence and *if the police needs to know* who was driving and *has a warrant* for that, car rental company refers them to the id provider can release to them your name and address.
Same for moderators.
When creating a mastodon account (or making an airBnB rental or whatever), rather than asking you for some specific credential, one would be asked for a reference from a trusted id provider. Depending on the service, the amount of info legitimate to communicate could vary. Eg, just knowing how many such references have already been sent out for this single person to open Mastodon instances would already prevent multis - and so "ban/bad reputation evasion"
3/n
@schock This is an important thread. As a newcomer to this community, it seems to me that a lot of the guidance for prospective new admins is purely technical — what is there to guide admins through the social, legal and governance questions? Having ways to support admins, including options for shared institutions, seems key.
“Looking at running a social network as running software” isn’t that distance from one of the issues the new Twitter leadership has.
@schock The idea that we're going to need some of governance to manage the fediverse* is something about which I've been standing in the corner and frantically waving my arms around about since 2017 or so ;-)
I have written a lot of conceptual design stuff, but not a whole lot of code yet. I'm definitely interested in being part of this discussion, in any case.
* ...and really, it goes way beyond that... [resists temptation to jump on hobby-horse and ride off into the sunset lecturing]
cc: @dredmorbius