GreenFediverse: Difference between revisions
m
text-corrections
m (text-corrections) |
|||
Line 7: | Line 7: | ||
==A brief history== | ==A brief history== | ||
Why not being the first | Why not being the first decentralized social network that runs on renewable energy? Sounds utopian, but we do it anyway! | ||
The project emerged from discussions in Fediverse in 2019. The discussions focused on digitization, climate change, the environmental sustainability of social networks, data centers and their energy consumption. It all started in March 2019 with the mastodon-account [https://chaos.social/@greenfediverse GreenFediverse]. In the beginning the community around the project created some manually edited lists: [https://lite.framacalc.org/greenfediverse-instances old instances list] and a [https://lite.framacalc.org/green-webhosting green webhoster list]. In 2020 [https://mastodon.social/@attac_hl @attac_hl] worked on the technical realization of a [https://greenfediverse.frama.io/green-instances/ new green instances list] and combined the databases from [https://sp3r4z.fr/mastodon/ Mastostats] and | The project emerged from discussions in Fediverse in 2019. The discussions focused on digitization, climate change, the environmental sustainability of social networks, data centers and their energy consumption. It all started in March 2019 with the mastodon-account [https://chaos.social/@greenfediverse GreenFediverse]. In the beginning the community around the project created some manually edited lists: [https://lite.framacalc.org/greenfediverse-instances old instances list] and a [https://lite.framacalc.org/green-webhosting green webhoster list]. In 2020 [https://mastodon.social/@attac_hl @attac_hl] worked on the technical realization of a [https://greenfediverse.frama.io/green-instances/ new green instances list] and combined the databases from [https://sp3r4z.fr/mastodon/ Mastostats] and The [https://www.thegreenwebfoundation.org/green-web-feed/ GreenWebFoundation]. In 2021 [https://digitalcourage.social/@aligyie @aligyie], created a [https://lite.framacalc.org/green-webhost-ranking green webhost ranking]. Since the beginning, the project has been managed by [https://chaos.social/@moagee @moagee]. Moagee and a friend are currently developing the list, researching and filling the database. | ||
==Why are we doing this?== | ==Why are we doing this?== | ||
Line 32: | Line 32: | ||
====1. Collision of open databases: There are two open databases we work with==== | ====1. Collision of open databases: There are two open databases we work with==== | ||
<u>Database 1:</u> [https://www.thegreenwebfoundation.org/ The GreenWebFoundation]'s open database, the "Green Web API" [https://github.com/thegreenwebfoundation ( | <u>Database 1:</u> [https://www.thegreenwebfoundation.org/ The GreenWebFoundation]'s open database, the "Green Web API" [https://github.com/thegreenwebfoundation (GitHub]) works in such a way that it outputs the "green" status of a website. This is done by The GreenWebFoundation first using various machine-verifiable methods to determine the domain names, IP addresses or the [[wikipedia:Autonomous_system_(Internet)|autonomous system number]]. In addition, the GreenWebFoundation has built an independent certificate database, where operators of websites or web hosts, which can not be automated-machine recorded, can register - take a look at the [https://www.thegreenwebfoundation.org/what-you-need-to-register/ registration-process]. There, a "proof" in the form of a certificate can then be provided, i.e. a [https://api.thegreenwebfoundation.org/greencheckimage/joinfediverse.wiki?nocache=true badge] can be acquired. These registered servers and services can then be labeled, i.e. provided with the information that they operate with renewable energy or not. Website addresses can be queried in the front end via a "[https://www.thegreenwebfoundation.org/green-web-check/ Green Web Check]" search mask or via the API. Whether a "green" entry exists here, the API then outputs a status result with "green" or "gray". More information about the functionality of this API can be found [https://www.thegreenwebfoundation.org/news/introducing-the-green-web-foundation-partner-api/ here]. "The Green Web Foundation is a recognized not-for-profit organization registered in the Netherlands, that is run by a small group of dedicated volunteers located in Germany and The Netherlands." "Our strategy is simple: we use the existing protocols of the internet to understand where infrastructure is run, when we speak to the people running it to see how they power it. We then make these answers easy to look up, providing free online tools, APIs and open datasets, and helping people incorporate this information into their own services and analysis."[https://www.thegreenwebfoundation.org/our-story/ <nowiki>[citation]</nowiki>] | ||
<u>Database 2:</u> Another database we use is that of [https://the-federation.info/ the-federation], (they are also on [https://socialhome.network/u/thefederation Socialhome] and [https://github.com/thefederationinfo/the-federation.info | <u>Database 2:</u> Another database we use is that of [https://the-federation.info/ the-federation], (they are also on [https://socialhome.network/u/thefederation Socialhome] and [https://github.com/thefederationinfo/the-federation.info GitHub]). Using the API, which is also open, we get a list of all connected and [https://the-federation.info/info here registered] instances of the Fediverse. A single instance offer us more information with the "/nodeinfo/2.0", (e.g. https://chaos.social/nodeinfo/2.0). Here we get, for example, what kind of "software" (Mastodon, PeerTube, etc.) is used on an instance. | ||
<u>Then the magic begins: The Data-Collider:</u> | <u>Then the magic begins: The Data-Collider:</u> | ||
Line 44: | Line 44: | ||
While building up our own database we would like to get more knowledge by critical research and make it available to everyone. This relates very specifically to knowledge about the energy use of server operators. Through our script we already receive a first status of all registered Fediverse instances from the GreenWebFoundation. However, since we had to realize that not all companies and server operators are transparent with a statement about the use of renewable energy and partly even do greenwashing, we would like to complement this status with a qualitative and transparent research. This information collected by the community is for each server operator, technically all domain names, AS numbers or IP addresses are collected and added to the list. | While building up our own database we would like to get more knowledge by critical research and make it available to everyone. This relates very specifically to knowledge about the energy use of server operators. Through our script we already receive a first status of all registered Fediverse instances from the GreenWebFoundation. However, since we had to realize that not all companies and server operators are transparent with a statement about the use of renewable energy and partly even do greenwashing, we would like to complement this status with a qualitative and transparent research. This information collected by the community is for each server operator, technically all domain names, AS numbers or IP addresses are collected and added to the list. | ||
For this purpose [https://digitalcourage.social/@aligyie nieebel] already collected a lot of information and put it together in a | For this purpose [https://digitalcourage.social/@aligyie nieebel] already collected a lot of information and put it together in a self-made [https://lite.framacalc.org/green-webhost-ranking ranking]. After research and investigation, we will have a lot of information that we systematically add to the database. We collect these information about single hosting services and data centers and their use of renewable energy in separate .md or .html - files. In these text files the collective research is structured and written in text, where we will offer links to information pages and certificate-files. | ||
So we have several options to work with: | So we have several options to work with: | ||
"[https://codeberg.org/GreenFediverse/green-instances/src/branch/master/additional-info additional infos]" means we make our research transparent in a structured way. For every webhoster we create a separate .md file. You should use this | "[https://codeberg.org/GreenFediverse/green-instances/src/branch/master/additional-info additional infos]" means we make our research transparent in a structured way. For every webhoster we create a separate .md file. You should use this style-sheet and take a look at the entries we already filled. It should look like this:<syntaxhighlight> | ||
**Hosting Provider:** | **Hosting Provider:** | ||
Line 78: | Line 78: | ||
"FlokiNET": "flokinet" | "FlokiNET": "flokinet" | ||
</syntaxhighlight>"[https://codeberg.org/GreenFediverse/green-instances/src/branch/master/rejectlist rejectlist]" means that a downgrade of a "green" status comes into play here. Servers marked as "rejected" are those that, according to our research, contradict the status of the GreenWebFoundation. Here we also work with | </syntaxhighlight>"[https://codeberg.org/GreenFediverse/green-instances/src/branch/master/rejectlist rejectlist]" means that a downgrade of a "green" status comes into play here. Servers marked as "rejected" are those that, according to our research, contradict the status of the GreenWebFoundation. Here we also work with separate .md files. Same as above, we have to set the entry we want to reject in the table.js. Currently it looks like this:<syntaxhighlight> | ||
const REJECT_LIST = { | const REJECT_LIST = { | ||
"Amazon EU (Ireland)": "amazon", | "Amazon EU (Ireland)": "amazon", | ||
Line 93: | Line 93: | ||
Server operators who claim to use renewable energies, but at the same time and by other means invest in fossil energies, cannot in our view make an ecologically sustainable contribution and are destroying their acquired status themselves - we do this in order to bring more reality, transparency and quality into play. In simpler terms, we unfortunately have to remain suspicious of all the greenwashing and marketing promises. Finally, we refrain from an exact and hardly realizable rating, because a lot of factors have to be considered and cannot be read out technically yet. But what we can do is document our research process transparently. We have written down our experiences in a [https://greenfediverse.codeberg.page/green-instances/header/research.html best practices guide]. | Server operators who claim to use renewable energies, but at the same time and by other means invest in fossil energies, cannot in our view make an ecologically sustainable contribution and are destroying their acquired status themselves - we do this in order to bring more reality, transparency and quality into play. In simpler terms, we unfortunately have to remain suspicious of all the greenwashing and marketing promises. Finally, we refrain from an exact and hardly realizable rating, because a lot of factors have to be considered and cannot be read out technically yet. But what we can do is document our research process transparently. We have written down our experiences in a [https://greenfediverse.codeberg.page/green-instances/header/research.html best practices guide]. | ||
"[https://codeberg.org/GreenFediverse/green-instances/src/branch/master/acceptlist acceptlist]" means that we set a gray status to a green status by ourself. We just need to put our wished entry (instances | "[https://codeberg.org/GreenFediverse/green-instances/src/branch/master/acceptlist acceptlist]" means that we set a gray status to a green status by ourself. We just need to put our wished entry (instances address like "chaos.social") to the instances.md. Currently it looks like this:<syntaxhighlight> | ||
social.vikings.net | social.vikings.net | ||
music.selea.se | music.selea.se | ||
Line 100: | Line 100: | ||
blogs.linux.pizza | blogs.linux.pizza | ||
blogi.arjoranta.fi | blogi.arjoranta.fi | ||
</syntaxhighlight>But don't forget to add and document your research to the "additional-info" section, otherwise someone will set your green status back to gray, because there is no transparent research and proof. If a instance (server/data center) is marked as gray, this means that there were no result from | </syntaxhighlight>But don't forget to add and document your research to the "additional-info" section, otherwise someone will set your green status back to gray, because there is no transparent research and proof. If a instance (server/data center) is marked as gray, this means that there were no result from The GreenWebFoundation API, technically it is a "0". When a instance is green, technically a "+1" was coming from the GWF. By the way, there is no -1 for a not green status, just "+1" and "0". At the moment, only single instances (not the entire webhoster) can be set to green. If you can't find your instance, you should visit https://the-federation.info/info and register your instance, because we fetch all instances via their API database. If you are registered there, but the The GreenWebFoundation won't give you a result for your instance, then the accept-list is the way. | ||
== Register Fediverse Instances == | == Register Fediverse Instances == | ||
Line 113: | Line 113: | ||
In this case, you should also register your instance with [https://the-federation.info/info The-Federation.info] first. If your instance then appears in our [https://greenfediverse.codeberg.page/Green-instances/ GreenInstancesList], you can try to submit a proof through the GreenWebFoundation. We do not have any experience with this. | In this case, you should also register your instance with [https://the-federation.info/info The-Federation.info] first. If your instance then appears in our [https://greenfediverse.codeberg.page/Green-instances/ GreenInstancesList], you can try to submit a proof through the GreenWebFoundation. We do not have any experience with this. | ||
But you can then register your instance with us. First create an account at [https://codeberg.org/ Codeberg.org] for the access to our repository (it is a non-profit association from | But you can then register your instance with us. First create an account at [https://codeberg.org/ Codeberg.org] for the access to our repository (it is a non-profit association from Berlin, you can follow them [https://mastodon.technology/@codeberg here]). | ||
Then you have to make a few entries: | Then you have to make a few entries: | ||
Line 119: | Line 119: | ||
1. in the acceptlist in the [https://codeberg.org/GreenFediverse/green-instances/src/branch/master/acceptlist/instances.json instances.json]. This will mark your instance as "green". | 1. in the acceptlist in the [https://codeberg.org/GreenFediverse/green-instances/src/branch/master/acceptlist/instances.json instances.json]. This will mark your instance as "green". | ||
2. if you want to add further information, i.e. " | 2. if you want to add further information, i.e. "additional infos" for a certificate or explanation, then you should make an entry in the [https://codeberg.org/GreenFediverse/green-instances/src/branch/master/table.js table.js], under "const ADDITIONAL_INFO_LIST = {" | ||
3. you also have to create your own additional-info file in this [https://codeberg.org/GreenFediverse/green-instances/src/branch/master/additional-info folder]. Please make sure that the filenames match everywhere. | 3. you also have to create your own additional-info file in this [https://codeberg.org/GreenFediverse/green-instances/src/branch/master/additional-info folder]. Please make sure that the filenames match everywhere. |