Gregory's Server@trwnh 1.) love this, looking forward to the blog post. 2.) i'm not 100% convinced of the analogy of open-world : closed world :: AP : "one" "social" "network" , but it resonates a lot with my thinking on platforms lately. i think the fediverse thinks of itself as ONE OPEN platform, rather than multiple overlapping platforms (that could include closed platforms, too, in every sense of closed including the economic!) with no global guarantees, periodt.
|
7 comments
 @trwnh ...and yet somehow many people DO implicitly or perhaps even unwittingly expect the "identity layer" for all of this to somehow be easier to harmonize than the content itself, w/E2EE and moderation/blocking guarantees universally applicable, and even expects the many shades of grey between public and private to be "standardizable" [sic] across all form factors and platforms. so yeah, maybe the singular framing of "the fediverse" is the problem, but also a bit of economic fingers-in-ears @trwnh all of which is just to posit that maybe the "social" part allows a certain "closed world" assumption to creep in (and a lot of scope creep!) because identity is infrastructure and people think it's easy to "standardize" social norms globally. anyways, send me the blog post when you push it, or before!  @by_caballero the blog post is basically just gonna be this thread but formatted in html with headings, so you're not missing much lol. maybe will be up by tomorrow, still need to decide on the uri, probably gonna create an /unstable directory for things that might get moved out later @by_caballero yeah i'm not saying AP is "open-world" but rather it straddles the line AS2 requiring the AS2 context is a bit weird from an LD perspective because it introduces weird "supremacy" conflicts especially with the "MUST NOT override" requirement i've thought that perhaps jsonld context should only ever be a "progressive enhancement" to json, and that new apis or interchange formats should instead use *expanded* form, and processors should expand any compacted json(ld) before using it @trwnh oh interesting i didn't realize that you meant openworld/closedwforld that literally in the RDF sense, i thought you meant more in the protocol-design sense (of like "drop all unfamiliar properties" as is conventional for all JSON protocols versus "here is how you cautiously parse or preserve for others what you don't know") |
@trwnh I use the word platform because everything with an interoperable inbox is a "messaging platform" and everything which has the concept of a thread is a forum platform and everything with listenable content is an "audio platform" and anything with public, readable content is a "publishing platform" but no one assumes you have to be all those things to be an AP implementation...