982
edits
Discord Messages: Difference between revisions
→23-01-31: new section
No edit summary |
(→23-01-31: new section) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 717: | Line 717: | ||
|Text=in thinking about some of the problems from this weekend like the (affectionately titled) [[The Google Docs Problem]] and various other interface problems with the wiki, where it'll always be easier for people to interact with a system from something they're more used to using, I've been thinking about a more generalized kind of bridging where one can set a [[Context of Interoperability]] where for a given workshop, time period, project, etc. people can plug their tools together and work in a shared space without needing to make all of them anew - so for the simple example of this discord and this wiki, it should be possible to reuse this space to eg. connect to a different (or multiple) wikis, and vice versa to have a different discord connect to it. Along those lines, being able to have a synchronizing eg. git repository of the pages on the wiki so that people could edit them in obsidian or logseq or whatever their tool of choice is... this feels like an incredibly generic idea, so I feel like there must already be a ton of work on it, but it feels like it starts by just making a framework for bridging where the n-to-n problem is simplified by having a set of tools for auth and format translation and modeling documents and messages... I'm going to start sketching one piece of that with the [[Mediawiki-Git Bridge]], but I'm curious to hear if anyone either has any ideas, prior experience, or unmet needs that I might be orbiting around here | |Text=in thinking about some of the problems from this weekend like the (affectionately titled) [[The Google Docs Problem]] and various other interface problems with the wiki, where it'll always be easier for people to interact with a system from something they're more used to using, I've been thinking about a more generalized kind of bridging where one can set a [[Context of Interoperability]] where for a given workshop, time period, project, etc. people can plug their tools together and work in a shared space without needing to make all of them anew - so for the simple example of this discord and this wiki, it should be possible to reuse this space to eg. connect to a different (or multiple) wikis, and vice versa to have a different discord connect to it. Along those lines, being able to have a synchronizing eg. git repository of the pages on the wiki so that people could edit them in obsidian or logseq or whatever their tool of choice is... this feels like an incredibly generic idea, so I feel like there must already be a ton of work on it, but it feels like it starts by just making a framework for bridging where the n-to-n problem is simplified by having a set of tools for auth and format translation and modeling documents and messages... I'm going to start sketching one piece of that with the [[Mediawiki-Git Bridge]], but I'm curious to hear if anyone either has any ideas, prior experience, or unmet needs that I might be orbiting around here | ||
|Link=https://discord.com/channels/1029514961782849607/1034992937391632444/1041814238362079242 | |Link=https://discord.com/channels/1029514961782849607/1034992937391632444/1041814238362079242 | ||
}}{{Message | |||
|Author=sneakers-the-rat | |||
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024 | |||
|Date Sent=22-11-14 23:15:29 | |||
|Channel=bridges | |||
|Text=This project, [[Git-Mediawiki]] looks pretty good: https://github.com/Git-Mediawiki/Git-Mediawiki | |||
I'm gonna see if i can get a further translating layer between wiki markup and markdown going, thank god for [[Pandoc]] | |||
|Link=https://discord.com/channels/1029514961782849607/1041814238362079242/1041853913479000245 | |||
}} | |||
== 22-11-15 == | |||
{{Message | |||
|Author=sneakers-the-rat | |||
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024 | |||
|Date Sent=22-11-15 08:38:56 | |||
|Channel=synthbots | |||
|Text=<@743886679554654299> brilliant idea for a [[Local Algorithm]] [[Parametrization]] along the lines of using the [[Medium as Storage]] and parametrization from a conversation I was having just now | |||
|Link=https://discord.com/channels/1029514961782849607/1041519468121161798/1041995710901526608 | |||
}}{{Message | |||
|Author=petermr | |||
|Avatar= | |||
|Date Sent=22-11-15 10:44:45 | |||
|Channel=semantic-climate | |||
|Text=We have been developing code for extraction of "claims" from IPCC [[executive summary]]s . <@322545403876868096> <@499904513038090240> So far we have the following design: | |||
* exec summary for chapter => 15-20 paras | |||
* bold leading sentence for each para => leading_claim | |||
* subsequent sentences => supporting_claims | |||
* annotation (high|medium|robust|low) (evidence|agreement|confidence) | |||
I will continue | |||
|Link=https://discord.com/channels/1029514961782849607/1040060354161557574/1042027374377709578 | |||
}}{{Message | |||
|Author=petermr | |||
|Avatar= | |||
|Date Sent=22-11-15 10:57:35 | |||
|Channel=general-brainstorming | |||
|Text=Thanks for [[Glamorous Toolkit]] . Watched the video and understood most of it. Impressive, and maybe the future, but not quite what I wanted now - it requires a fluency with creating new types of object on the fly and so a change in orientation. I want something that I can tag the methods with (say) 'PDF conversion', 'prototype`, etc. I don't mind dumping that as static docs and navigating with Obsidian. | |||
|Link=https://discord.com/channels/1029514961782849607/1034992937391632444/1042030600359510026 | |||
}} | |||
== 22-11-23 == | |||
{{Message | |||
|Author=Wutbot | |||
|Avatar=https://cdn.discordapp.com/avatars/709165833888464966/d959819a9a72aa307c6ef1b91d7f94a2.png?size=1024 | |||
|Date Sent=22-11-23 18:59:16 | |||
|Channel=discourse-modeling | |||
|Text=[[claim]] claims and questions dominate in natural conversation; the imbalance of sources & evidence is quite stark. This aligns with my mental model of *conversational charity*, where we assume our interlocutors *could* ground their statements in evidence if pressed, but skip this step in the interest of time. | |||
|Link=https://discord.com/channels/1029514961782849607/1038988750677606432/1045050924466458725 | |||
}} | |||
== 22-12-20 == | |||
{{Message | |||
|Author=sneakers-the-rat | |||
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024 | |||
|Date Sent=22-12-20 10:34:44 | |||
|Channel=synthesizing-social-media | |||
|Text=check this out. [[DIY Algorithms]]. instead of adding accounts to lists and autopopulating, you can directly add posts themselves. so then you can rig up whatever the frick algorithm you want to masto: | |||
https://social.coop/@jonny/109545449455062668 | |||
https://github.com/sneakers-the-rat/mastodon/tree/feature/postlists | |||
|Link=https://discord.com/channels/1029514961782849607/1038983225348993184/1054708427399626872 | |||
}} | |||
== 23-01-31 == | |||
{{Message | |||
|Author=bengo | |||
|Avatar=https://cdn.discordapp.com/avatars/602622661125996545/f01c2d17587b5d9b1542dcf40c7c2e33.png?size=1024 | |||
|Date Sent=23-01-31 16:02:30 | |||
|Channel=computable-graphs | |||
|Text=I've also recently been using logseq. I like how it just writes to markdown. I've been wanting to parse that markdown, look for we--known #hashtags and [[wikitags]], and build an rdf dataset. It looks like SBML is kinda like XML, so maybe something similar is possible there. Have you done anything more with logseq since this post in November? | |||
|Link=https://discord.com/channels/1029514961782849607/1038983137222467604/1070011203939749958 | |||
}} | }} | ||