Difference between revisions of "Fediverse"
m (Fix template usage) |
|||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 11: | Line 11: | ||
== ArchiveTeam and the Fediverse == | == ArchiveTeam and the Fediverse == | ||
In May 2019, AT (or at any rate, what was seen from the outside as AT-as-a-unitary-actor) archived a Mastodon server called {{URL|https://berries.space}}, which caused blowback<ref>https://fanlore.org/wiki/Berries.space</ref><ref>https://wilkie.how/posts/social-archival</ref><ref>https://bune.city/2019/05/archive-team-and-the-fediverse/</ref><ref>https://twitter.com/textfiles/status/1133235657340530693</ref>. Subsequently AT | In May 2019, AT (or at any rate, what was seen from the outside as AT-as-a-unitary-actor) archived a Mastodon server called {{URL|https://berries.space/|berries.space}}, which caused blowback<ref>{{URL|https://fanlore.org/wiki/Berries.space}}</ref><ref>{{URL|https://wilkie.how/posts/social-archival}}</ref><ref>{{URL|https://bune.city/2019/05/archive-team-and-the-fediverse/}}</ref><ref>{{URL|https://twitter.com/textfiles/status/1133235657340530693}}</ref>. Subsequently AT adopted a policy of not archiving Fediverse instances unless we get permission from the owners. This held until AT's de facto current leadership [https://wiki.archiveteam.org/index.php?title=Mastodon&diff=50243&oldid=49446 signaled that it is no longer a thing] in 2023, but since then we haven't archived any Fediverse instances anyway due to its (i.e. Mastodon instances') heavy use of Javascript - and the expected post-buyout exodus from Twitter not really happening, making this less of a priority than we might've thought. | ||
== JavaScript Workarounds == | |||
Most Fediverse instances use [[Mastodon]], which requires JavaScript, which calls Mastodon APIs to retrieve data. | |||
[https://github.com/jwilk/zygolophodon zygolophodon] is a command-line client for the Mastodon APIs, and a [https://github.com/jwilk/zygolophodon/pull/3 patchset] for it is aiming to add an option to output URLs for archiving, including JavaScript based pages, the API requests they make and RSS URLs as well as outlink URLs. Not production ready yet and only intended for targeted archiving. | |||
The [https://threadtree.xyz/ ThreadTree] service is a thread "unroller" for Mastodon URLs that outputs plain HTML with no JavaScript requirement. Currently it has some [https://github.com/Two9A/ThreadTree/issues issues] that make it suboptimal for archiving, but it can still work OKish. | |||
== References == | == References == | ||
<references /> | <references /> | ||
Latest revision as of 03:31, 28 November 2024
| Fediverse | |
| Status | Special case |
| Archiving status | Special case |
| Archiving type | Unknown |
| IRC channel | #fedisperse (on hackint) |
The Fediverse is a network of interoperating servers used for web publishing. Due to the federation, instances are constantly joining the network or disappearing.
The main protocol used in the fediverse is ActivityPub. Many software platforms exist; the most widely used ones as of early 2019 are Mastodon, Pleroma, PeerTube, Friendica, GNU social, and WriteFreely[1].
ArchiveTeam and the Fediverse
In May 2019, AT (or at any rate, what was seen from the outside as AT-as-a-unitary-actor) archived a Mastodon server called berries.space[IA•Wcite•.today•MemWeb], which caused blowback[2][3][4][5]. Subsequently AT adopted a policy of not archiving Fediverse instances unless we get permission from the owners. This held until AT's de facto current leadership signaled that it is no longer a thing in 2023, but since then we haven't archived any Fediverse instances anyway due to its (i.e. Mastodon instances') heavy use of Javascript - and the expected post-buyout exodus from Twitter not really happening, making this less of a priority than we might've thought.
JavaScript Workarounds
Most Fediverse instances use Mastodon, which requires JavaScript, which calls Mastodon APIs to retrieve data.
zygolophodon is a command-line client for the Mastodon APIs, and a patchset for it is aiming to add an option to output URLs for archiving, including JavaScript based pages, the API requests they make and RSS URLs as well as outlink URLs. Not production ready yet and only intended for targeted archiving.
The ThreadTree service is a thread "unroller" for Mastodon URLs that outputs plain HTML with no JavaScript requirement. Currently it has some issues that make it suboptimal for archiving, but it can still work OKish.
References
- ↑ https://web.archive.org/web/20190312111429/https://fediverse.network/
- ↑ https://fanlore.org/wiki/Berries.space[IA•Wcite•.today•MemWeb]
- ↑ https://wilkie.how/posts/social-archival[IA•Wcite•.today•MemWeb]
- ↑ https://bune.city/2019/05/archive-team-and-the-fediverse/[IA•Wcite•.today•MemWeb]
- ↑ https://twitter.com/textfiles/status/1133235657340530693[IA•Wcite•.today•MemWeb]