Avviso contenuto: Reflecting on some of the hurdles for procuring a Fediverse instance for the US Government. There are a lot of hoops to jump through, but is it worthwhile?
The post Could the US Government Self-Host a Fediverse Server? appeared first on We Distribute.
h
In our report yesterday about President Biden and the White House opting in to ActivityPub federation, there were a number of responses from people wishing that the White House (and other organizations) would simply self-host their own server to be a part of the network. I agree with this sentiment, and have been thinking about the requirements that would make this kind of thing possible.
Here are my thoughts, based on my limited experience working for both tech startups and government.
Why Would Anyone Want This?
There are a number of people in the Fediverse that would like all forms of government to stay the heck away from the network, citing the problems of bringing the military-industrial-complex and surveillance capitalism to our cozy little space on the Internet. Depending on which government we’re talking about, what their policies are, and how they interact with the network, this isn’t necessarily an unreasonable reaction.
However, there are a number of benefits that bringing government to self-hosted infrastructure might bring:
Government Officials – Communicating with and representing their constituents.
Service Notifications – Are there outages on certain train lines? Are roads closed down? Has a natural disaster occurred?
Bureau Interactions – interacting with municipal services, civic organizations, and emergency / non-emergency services for a variety of jurisdictions.
Department Information – easy promotion and access to studies from, say, the Department of Labor, or the Department of Energy.
Legislature – coverage of meeting notes, policies passed, votes on the House or Senate floor.
As of today, these things primarily exist within the domain of corporate social media. You’re more likely to see a smattering of accounts across Twitter, Facebook, and Threads, and those accounts might be pretty limited in what they’re able to actually accomplish, since they’re not even running on government infrastructure.
The fact of the matter is, being able to directly access all of the things listed above could be a boon to users of the Fediverse. Rather than trying to rely on a Facebook page or Twitter account to get necessary information, it could be seen from verified accounts on your timeline, with receipts, and would be accessible to journalists, researchers, developers, and citizens alike.
Technical and Organizational Hurdles
There are a number of hoops to jump through, so let’s talk about them. Before diving in: I’m aware of the effort being done by the European Union as well as some EU governments. I think those are great, and give us some kind of playbook to look to for examples. These musings are more focused on the United States.
Funding
The first headache with any government project is setting aside the funds and people to work on it. A political figure could introduce a bill with provisions to set aside a budget for such a program, but then there are questions pertaining to who actually carries out this effort. How much of the work is being contracted out to another business or agency? What’s the criteria for “winning” the contract, and who carries out what tasks?
Procurement
Then there’s the choice of software itself: the platform and its dependencies need to be audited, examined, and vouched for. Off the top of my head, relatively few Fediverse platforms actually fulfill this expectation: I believe that Mastodon may be one of the few that has actually gone through this process, but there may be significant differences between a security audit by a compliance group, and a security audit by a government.
Aside from choosing an official platform to stake operations on, there’s also the matter of finding an ideal third-party vendor. Currently, managed Fediverse hosting services are still in their infancy, and I’m not sure they’re up to scratch for what a government entity demands: comprehensive compliance requirements, service-level agreements, user training and onboarding materials, and promises pertaining to security upgrades and threat mitigations.
There may also be requirements for custom development, for example, integrating federal single sign-on, such as ID.me or something similar. There would also need to be a deployment strategy for various users, departments, and bureaus. It may be possible for an existing government IT provider to adopt Mastodon or another platform and develop everything needed here, but it’s much harder for any business started in the Fediverse today.
Policy
Another relatively grey area here would be the setting of policy for a US Government-run instance. Dealing with hate speech, CSAM, trolling, harassment, and other nastiness is a job and a half for ordinary instance admins, but I would imagine that this could be compounded further by hosting a government server with potentially millions of followers.
How does a government handle that kind of thing without violating the First Amendment? Does moderation even count as violating free speech, as some people believe? Is there perhaps a threshold for what’s tolerated in civil discussion?
I’m not a lawyer, and don’t have a complete answer. They might be able to get away with something similar to the Mastodon Server Covenant, in which ground rules for participation are set. Alternatively, maybe only allowing inbound federation from other government servers is an answer. I don’t know.
Tooling
One final consideration: departments and organizations are unlikely to get very far if they only have a default web interface to rely on. The Fediverse needs tools like Buffer, Fedica, and Mixpost for teams to come together and coordinate their presence in this new space. As the ecosystem evolves, we’ll likely need alternative tools and frontends to deal with emerging challenges.
It’s Still Worth Trying
I’ll be the first to admit that, looking at everything above, there’s a lot of unanswered questions. People asked why President Biden and the White House opted in to using Threads with ActivityPub federation, rather than stand up their own server. For the time being, the cost of setup, onboarding, and training is cheaper. They’re also making a smart bet by migrating to where a lot of people are, in the hopes that they will be heard by the greatest amount of potential followers.
As the Fediverse continues to grow, and both the protocol and platforms continue to evolve, my hope is that government entities might see the Fediverse as viable. One day, we may see a lot of municipal entities and departments setting up their base of operations right here on the network. I think it’s important that we continue thinking about how to get there.
In our report yesterday about President Biden and the White House opting in to ActivityPub federation, there were a number of responses from people wishing that the White House (and other organizations) would simply self-host their own server to be a part of the network. I agree with this sentiment, and have been thinking about the requirements that would make this kind of thing possible.
Here are my thoughts, based on my limited experience working for both tech startups and government.
Why Would Anyone Want This?
There are a number of people in the Fediverse that would like all forms of government to stay the heck away from the network, citing the problems of bringing the military-industrial-complex and surveillance capitalism to our cozy little space on the Internet. Depending on which government we’re talking about, what their policies are, and how they interact with the network, this isn’t necessarily an unreasonable reaction.
However, there are a number of benefits that bringing government to self-hosted infrastructure might bring:
Government Officials – Communicating with and representing their constituents.
Service Notifications – Are there outages on certain train lines? Are roads closed down? Has a natural disaster occurred?
Bureau Interactions – interacting with municipal services, civic organizations, and emergency / non-emergency services for a variety of jurisdictions.
Department Information – easy promotion and access to studies from, say, the Department of Labor, or the Department of Energy.
Legislature – coverage of meeting notes, policies passed, votes on the House or Senate floor.
As of today, these things primarily exist within the domain of corporate social media. You’re more likely to see a smattering of accounts across Twitter, Facebook, and Threads, and those accounts might be pretty limited in what they’re able to actually accomplish, since they’re not even running on government infrastructure.
The fact of the matter is, being able to directly access all of the things listed above could be a boon to users of the Fediverse. Rather than trying to rely on a Facebook page or Twitter account to get necessary information, it could be seen from verified accounts on your timeline, with receipts, and would be accessible to journalists, researchers, developers, and citizens alike.
Technical and Organizational Hurdles
There are a number of hoops to jump through, so let’s talk about them. Before diving in: I’m aware of the effort being done by the European Union as well as some EU governments. I think those are great, and give us some kind of playbook to look to for examples. These musings are more focused on the United States.
Funding
The first headache with any government project is setting aside the funds and people to work on it. A political figure could introduce a bill with provisions to set aside a budget for such a program, but then there are questions pertaining to who actually carries out this effort. How much of the work is being contracted out to another business or agency? What’s the criteria for “winning” the contract, and who carries out what tasks?
Procurement
Then there’s the choice of software itself: the platform and its dependencies need to be audited, examined, and vouched for. Off the top of my head, relatively few Fediverse platforms actually fulfill this expectation: I believe that Mastodon may be one of the few that has actually gone through this process, but there may be significant differences between a security audit by a compliance group, and a security audit by a government.
Aside from choosing an official platform to stake operations on, there’s also the matter of finding an ideal third-party vendor. Currently, managed Fediverse hosting services are still in their infancy, and I’m not sure they’re up to scratch for what a government entity demands: comprehensive compliance requirements, service-level agreements, user training and onboarding materials, and promises pertaining to security upgrades and threat mitigations.
There may also be requirements for custom development, for example, integrating federal single sign-on, such as ID.me or something similar. There would also need to be a deployment strategy for various users, departments, and bureaus. It may be possible for an existing government IT provider to adopt Mastodon or another platform and develop everything needed here, but it’s much harder for any business started in the Fediverse today.
Policy
Another relatively grey area here would be the setting of policy for a US Government-run instance. Dealing with hate speech, CSAM, trolling, harassment, and other nastiness is a job and a half for ordinary instance admins, but I would imagine that this could be compounded further by hosting a government server with potentially millions of followers.
How does a government handle that kind of thing without violating the First Amendment? Does moderation even count as violating free speech, as some people believe? Is there perhaps a threshold for what’s tolerated in civil discussion?
I’m not a lawyer, and don’t have a complete answer. They might be able to get away with something similar to the Mastodon Server Covenant, in which ground rules for participation are set. Alternatively, maybe only allowing inbound federation from other government servers is an answer. I don’t know.
Tooling
One final consideration: departments and organizations are unlikely to get very far if they only have a default web interface to rely on. The Fediverse needs tools like Buffer, Fedica, and Mixpost for teams to come together and coordinate their presence in this new space. As the ecosystem evolves, we’ll likely need alternative tools and frontends to deal with emerging challenges.
It’s Still Worth Trying
I’ll be the first to admit that, looking at everything above, there’s a lot of unanswered questions. People asked why President Biden and the White House opted in to using Threads with ActivityPub federation, rather than stand up their own server. For the time being, the cost of setup, onboarding, and training is cheaper. They’re also making a smart bet by migrating to where a lot of people are, in the hopes that they will be heard by the greatest amount of potential followers.
As the Fediverse continues to grow, and both the protocol and platforms continue to evolve, my hope is that government entities might see the Fediverse as viable. One day, we may see a lot of municipal entities and departments setting up their base of operations right here on the network. I think it’s important that we continue thinking about how to get there.
In our report yesterday about President Biden and the White House opting in to ActivityPub federation, there were a number of responses from people wishing that the White House (and other organization
io penso che tutti gli enti pubblici dovrebbero togliersi da tutte le piattaforme privative e usare esclusivamente il fediverso come sistema di comunicazione diretta, oltre ad offrire il servizio ai cittadini, con tutte le restrizioni che comporta.
Allo stesso modo esorterei tutti i politici a non usare le piattaforme privative per fare annunci istituzionali o politici.
E inviterei gli stessi partiti ad aprire i loro server e a togliersi dalle varie piattaforme privative.
❄️ freezr ❄️
in reply to Poliverso - notizie dal fediverso • • •io penso che tutti gli enti pubblici dovrebbero togliersi da tutte le piattaforme privative e usare esclusivamente il fediverso come sistema di comunicazione diretta, oltre ad offrire il servizio ai cittadini, con tutte le restrizioni che comporta.
Allo stesso modo esorterei tutti i politici a non usare le piattaforme privative per fare annunci istituzionali o politici.
E inviterei gli stessi partiti ad aprire i loro server e a togliersi dalle varie piattaforme privative.
Poliverso - notizie dal fediverso likes this.