3/
If you cannot get (most) regular people to write JSON-LD, JSON, or even HTML —
But, you might be able to get them (regular people) to write something similar to Markdown and INI —
Then, are there ways you could (explicitly or implicitly) encode JSON-LD type information, such as ActivityPub, into a Markdown-like or INI-like file — in a way where they (regular people) would likely include it?
I suspect — probably yes.
#ActivityPub #FediDev #FediDevs #FediUX #Fediverse #FediverseUX
2/
I spend time thinking about how this (the importance of files and file data-formats) intersects with user-experience (UX).
For example, what types of files could you get regular people to create?
I don't think you can get regular people en masse to write JSON (including JSON-LD).
I think even getting them (regular people) to write HTML is difficult.
Something similar to Markdown probably has the best chance or success. Maybe something similar to INI, too.
3/
If you cannot get (most) regular people to write JSON-LD, JSON, or even HTML —
But, you might be able to get them (regular people) to write something similar to Markdown and INI —
Then, are there ways you could (explicitly or implicitly) encode JSON-LD type information, such as ActivityPub, into a Markdown-like or INI-like file — in a way where they (regular people) would likely include it?
I suspect — probably yes.
#ActivityPub #FediDev #FediDevs #FediUX #Fediverse #FediverseUX
@reiver i think notion might be a slightly better fit to the underlying AS data model than obsidian or hedgedoc, but i love the idea of a "direct WYSIWIG" AP client that writes to collections in a "files metaphor". C2S could enable this a bit, making one or more outboxes just the thing you upload these documents to...
@reiver in my opinion, regular people will never write markdown. Regular people need an UI where they can select formatting options (or type information) like in MS Word.
