Grapevine: Difference between revisions
(Add “Accelerationism” and “Cancel”) |
(Change category to SI29, and move it to the bottom to avoid line-break at the beginning of the file.) |
||
| Line 1: | Line 1: | ||
This page will hold '''G(l)oss(ary)ips''' shared during the XPUB 2026 [[SI29: Gossiping at the Intersection of Crafts and Resistances]]. | This page will hold '''G(l)oss(ary)ips''' shared during the XPUB 2026 [[SI29: Gossiping at the Intersection of Crafts and Resistances]]. | ||
| Line 11: | Line 9: | ||
== Cancel == | == Cancel == | ||
{{:Cancel}} | {{:Cancel}} | ||
[[Category: SI29]] | |||
Revision as of 16:07, 7 January 2026
This page will hold G(l)oss(ary)ips shared during the XPUB 2026 SI29: Gossiping at the Intersection of Crafts and Resistances.
Gossip
<what's new :)>
Accelerationism
Speeding up the spreading of gossip, especially if venomous, to accelerate the collapse of hierarchical, unequal, unfair systems.
Negative connotations of gossiping can be weaponized against the very information infrastructure that discriminates it.
Cancel
How does the definition of “cancelling” and “deleting” change in a distributed, decentralized, nonhierarchical knowledge infrastructure?
For example, in peer-to-peer protocols the most that can be done is requesting to delete something from a node/peer, but there can be no way to ensure that any cached version of that something is still stored.
Especially to counter authoritarianism, this becomes a powerful resistance to censorship, as it becomes virtually impossible to erase all sources of some specific information.
In VCSs like git, removing something from a repository means adding a removal operation, yet the file is (almost) irreversibly engraved in the history of the repository, thus impossible to erase.