Garden and Stream: Difference between revisions
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
http://meatballwiki.org/wiki/ThreadMode | http://meatballwiki.org/wiki/ThreadMode | ||
|Link=https://discord.com/channels/1029514961782849607/1038112016038101062/1038196314409803826 | |Link=https://discord.com/channels/1029514961782849607/1038112016038101062/1038196314409803826 | ||
}}{{Message | |||
|Author=sneakers-the-rat | |||
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024 | |||
|Date Sent=22-11-14 04:21:58 | |||
|Channel=libraries-and-manual-curation | |||
|Text=encouraging the use of the thread for the sake of people's notifications as we enter slow-mode. | |||
sidebar: this to me is one of the more interesting uses of this kind of wiki-bot, in a more long-lived chat and communication medium (glad 2 have <@708787219992805407> here for the long-timescales perspective btw). in both this and any future workshops, being able to plug in something like a wikibot that can let different threads get tagged to common concepts through time to different/overlapping discord servers and output to potentially multiple overlapping wikis is v interesting to me. | |||
I'm gonna continue to make it easier to deploy because i feel like the [[Garden and Stream]] metaphor is one that can unfold on multiple timescales, and it would be cool to build out the ability to make that easier: how cool would it be if you didn't have to decide on a chat/document medium or have to make a new set at the start of an organizing project since it was arbitrary anyway and your infra supported use and crossposting across many media. | |||
Eg. the very understanding surfacing of [[The Google Docs Problem]] because of [[Mediawiki]]'s lack of [[Synchronous Editing]] [[Live Editing]] and the need to remember to link out to external services rather than that being a natural expectation of a multimodal group and having systems that explicitly support that is illustrative to me. Maybe one description is being able to deploy a [[Context of Interoperability]] [[Interoperability]]: during this time period I am intending these documents/discord servers/hashtags/social media accounts/etc. to be able to crosspost between each other so that everyone needs to to as little as possible to make their workflows align | |||
|Link=https://discord.com/channels/1029514961782849607/1041565762546053190/1041568655948922910 | |||
}} | }} | ||
Latest revision as of 04:22, 14 November 2022
From the essay "The Garden and the Stream: A Technopastoral" (https://hapgood.us/2015/10/17/the-garden-and-the-stream-a-technopastoral/amp/)
Related to DocumentMode and ThreadMode
Discord
the idea is exactly to merge the Garden and Stream we have here, or as olde wiki culture called it, DocumentMode and ThreadMode in a process of Gradual Enrichment http://meatballwiki.org/wiki/DocumentMode http://meatballwiki.org/wiki/ThreadMode
encouraging the use of the thread for the sake of people's notifications as we enter slow-mode.
sidebar: this to me is one of the more interesting uses of this kind of wiki-bot, in a more long-lived chat and communication medium (glad 2 have <@708787219992805407> here for the long-timescales perspective btw). in both this and any future workshops, being able to plug in something like a wikibot that can let different threads get tagged to common concepts through time to different/overlapping discord servers and output to potentially multiple overlapping wikis is v interesting to me.
I'm gonna continue to make it easier to deploy because i feel like the Garden and Stream metaphor is one that can unfold on multiple timescales, and it would be cool to build out the ability to make that easier: how cool would it be if you didn't have to decide on a chat/document medium or have to make a new set at the start of an organizing project since it was arbitrary anyway and your infra supported use and crossposting across many media.
Eg. the very understanding surfacing of The Google Docs Problem because of Mediawiki's lack of Synchronous Editing Live Editing and the need to remember to link out to external services rather than that being a natural expectation of a multimodal group and having systems that explicitly support that is illustrative to me. Maybe one description is being able to deploy a Context of Interoperability Interoperability: during this time period I am intending these documents/discord servers/hashtags/social media accounts/etc. to be able to crosspost between each other so that everyone needs to to as little as possible to make their workflows align