Synthesizing Social Media/First Breakout Session: Difference between revisions

Revision as of 17:10, 12 November 2022

Possible Topics

Patching on top of masto

First pass

Using the profile tags to be able to assign prefixes to a digital object
- So say i have paper:paper url in my profile
Then being able to refer to that object using @jonny:paper in a post
And then posts beneath that use that as the subject when resolving [ [Semantic::wikilinks] ]

Second pass

Metadata tag in masto profile that links to a wiki page
- wiki:https://synthesis-infrastuctures.wiki/Jonny_Saunders
Page has a series of Property:Tag annotatations that link a short tag to a further page or URL. The linked page could have additional metadata like DOIs, authors, etc.
- [[Tag::shortname::Longer Page Name]]


Posting a thread with the first post using a syntax like @jonny:wiki:shortname then treats posts underneath that as having that as the subject, and a bot then scoops those up and puts them in the page enabling the use of semantic wikilinks, etc.
A bot then is monitoring opt-in accounts for these kinds of threads and exporting them to the relevant wiki page as subpages containing the threads.
Like the WikiBot, additional Wikilinks within the thread also embed a link to the thread (probably want to have the thread be its own page then, and have some syntax for declaring a title)
The bot could also have interoperable export formats out to Braid, etc.

TODO during the workshop

Deploy a glitch-soc instance in the synthesis-infrastructures domain to test
Write the above bot and make relevant wiki components :)

Further integration into client

UX elements to be able to select and resolve tags for a given author within the instance that has enabled this syntax.
An overlay could search for linked wikis and work backwards - so given a DOI, find the page with the [[Has DOI::...]] page and then overlay the threads underneath it.

Use cases

Shorthand identifiers using profile metadata (as above)
Using semantic links in streams headed by shorthand identifiers
Attention data on reading: taking eg. zotero and converting that to a post stream or something

@@ Line 8: / Line 8: @@
 == Patching on top of masto ==
+=== First pass ===
 * Using the profile tags to be able to assign prefixes to a digital object
@@ Line 13: / Line 15: @@
 * Then being able to refer to that object using @jonny:paper in a post
 * And then posts beneath that use that as the subject when resolving [ [Semantic::wikilinks] ]
+=== Second pass ===
+* Metadata tag in masto profile that links to a wiki page
+** <code>wiki:https://synthesis-infrastuctures.wiki/Jonny_Saunders</code>
+* Page has a series of [[Property:Tag]] annotatations that link a short tag to a further page or URL. The linked page could have additional metadata like DOIs, authors, etc.
+** <code><nowiki>[[Tag::shortname::Longer Page Name]]</nowiki><code>
+* Posting a thread with the first post using a syntax like <code>@jonny:wiki:shortname</code> then treats posts underneath that as having that as the subject, and a bot then scoops those up and puts them in the page enabling the use of semantic wikilinks, etc.
+* A bot then is monitoring opt-in accounts for these kinds of threads and exporting them to the relevant wiki page as subpages containing the threads.
+** Like the [[WikiBot]], additional [[Wikilinks]] within the thread also embed a link to the thread (probably want to have the thread be its own page then, and have some syntax for declaring a title)
+* The bot could also have interoperable export formats out to [[Braid]], etc.
+==== TODO during the workshop ====
+* Deploy a glitch-soc instance in the synthesis-infrastructures domain to test
+* Write the above bot and make relevant wiki components :)
+==== Further integration into client ====
+* UX elements to be able to select and resolve tags for a given author within the instance that has enabled this syntax.
+* An overlay could search for linked wikis and work backwards - so given a DOI, find the page with the <nowiki>[[Has DOI::...]]</nowiki> page and then overlay the threads underneath it.
 == Use cases ==