Synthesizing Social Media/First Breakout Session: Difference between revisions

From Synthesis Infrastructures
No edit summary
Line 43: Line 43:
* [[Attention]] data on reading: taking eg. zotero and converting that to a post stream or something
* [[Attention]] data on reading: taking eg. zotero and converting that to a post stream or something


One of the common norms that have developed on academic social media (Twitter/Mastodon) is announcement/summary threads of one’s paper.
<nowiki>https://hci.social/web/@Mor/109309396530932422</nowiki>
(others of interest: job market announcements, taking PhD announcements)
Imagine if you could create for yourself a unique, short, readable identifier for a paper, and add that in your post thread about your paper announcement.
Possible syntax:
@mor:crisis-informatics //user namespace
<nowiki>#</nowiki>cscw22:crisis-informatics //conference namespace
Things you could do as a result:
- put all your different paper threads on your webpage and associated with each paper
- collect all the paper announcements for a conference
- people could reference your identifier in their conversations, and a bot could post the paper announcement thread as a reply (<nowiki>https://hci.social/web/@lewischuang/109331737391363720</nowiki>)
- you could collect all discussion around your paper in a separate place, or a bot could post pingbacks on the original paper announcement thread
[[Category:Conversation]]
[[Category:Conversation]]

Revision as of 17:10, 12 November 2022

Back up to Synthesizing Social Media

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
  • 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


One of the common norms that have developed on academic social media (Twitter/Mastodon) is announcement/summary threads of one’s paper.

https://hci.social/web/@Mor/109309396530932422

(others of interest: job market announcements, taking PhD announcements)

Imagine if you could create for yourself a unique, short, readable identifier for a paper, and add that in your post thread about your paper announcement.

Possible syntax:

@mor:crisis-informatics //user namespace

#cscw22:crisis-informatics //conference namespace

Things you could do as a result:

- put all your different paper threads on your webpage and associated with each paper

- collect all the paper announcements for a conference

- people could reference your identifier in their conversations, and a bot could post the paper announcement thread as a reply (https://hci.social/web/@lewischuang/109331737391363720)

- you could collect all discussion around your paper in a separate place, or a bot could post pingbacks on the original paper announcement thread