Discord Messages: Difference between revisions

1,684 bytes added ,  22:50, 3 November 2022
no edit summary
No edit summary
No edit summary
Line 142: Line 142:
|Text=this is almost exactly the idea with the [[WikiBot]] that pushes to a [[Semantic Wiki]], and good to have a name in [[Gradual Enrichment]]. looking forward to digging though the references and finishing that piece^ tomorrow. (and finishing the n-back linking syntax so I can just directly include the piece in the annotation that is this message). thanks for sharing 🙂
|Text=this is almost exactly the idea with the [[WikiBot]] that pushes to a [[Semantic Wiki]], and good to have a name in [[Gradual Enrichment]]. looking forward to digging though the references and finishing that piece^ tomorrow. (and finishing the n-back linking syntax so I can just directly include the piece in the annotation that is this message). thanks for sharing 🙂
|Link=https://discord.com/channels/1029514961782849607/1035691728356790322/1037689452157481071
|Link=https://discord.com/channels/1029514961782849607/1035691728356790322/1037689452157481071
}}{{Message
|Author=sneakers-the-rat
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
|Date Sent=22-11-03 22:51:30
|Channel=In terms of overlap with my own
|Text=[[Project Ideas#Linked Data Publishing On Activitypub]]
ooh I'm very interested in this. so are you thinking a [[Twitter#Bridge]] -> [[ActivityPub#Bridge]] where one could use markup within the twitter post to declare [[Linked Data#Markup Syntax]] and then post to AP? I have thought about this kind of thing before, like using a bot command syntax to declare prefixes by doing something like
```
@ bot prefix
foaf: https:// (ontology URL)
```
or
```
@ bot alias
term: foaf.LongerNameForTerm
```
so that one could do maybe a semantic wikilink like `[ [term::value] ]` either within the tweet or as a reply to it (so the tweet itself doesn't become cluttered/it can become organized post -hoc?).
I've also thought about a bridge (I called [[Threadodo]] ) that implements that kind of command syntax to be able to directly archive threads to [[Zenodo]] along with structured information about the author, but this seems more interesting.
I can help try and clear some of the groundwork out of the way to make it easier for you and other interested participants to experiment. I have asked around fedi a bunch for a very minimal AP server implementation, and I could try and find one (or we could try and prototype one) if you want to experiment with that :), and I can also document and show you a tweepy-based bot that has an extensible command/parsing system too
|Link=https://discord.com/channels/1029514961782849607/1037786518800039978/1037861609885925467
}}
}}