#WorkingInPublic in the [[Agora]] this weekend, some improvements so far:
1. The Agora graph in e.g. https://anagora.org/nodes now works and doesn't escape its container.
2. Better (hopefully) header and footers. Not super huge but I like the difference.
3. New/refreshed search providers; added [[bing]] and [[marginalia]], ditched searx (broken as it was) and twitter (I don't like where twitter is going currently)
Some planning as it's on one of my workspaces as of [[2023-03-18]]
Flancia is about #WorkingInPublic
ok so re-reading #IPFS paper and there are a few things I think in retrospect are undesirable about the #MerkelDAG spec. it's hard to parse them out as separable ideas because they depend on one another, but the main thing I think is how it conflates the structure of a metadata graph, the content of the graph, and the notion of authorship/identity.
In (basic) IPFS, each node contains some data and some links. the data is some unspecified binary blob, the links are all references to hashes of other nodes, and then the hash of all that identifies the node. There are some abstractions like flattened trees that can represent n-depth links, but that's the gist. I'm refreshing myself, so correct me where I'm wrong.
This makes traversing the graph expensive from a naive (cacheless) state- you have to fetch each node and parse its links serially, and since there isn't a notion of authorship except when used to sign a node, you might have to do the resolution process across a lot of the network instead of being able to say "ah ok this is from this identity so I should ask their neighborhood first"
Since the links are untyped, and because of the need for serial resolution, you can't really "plan" queries and move the query logic to the "edges" (in a networking, rather than graph parlance) of the network - the network resolution logic handles all that.
This structure also makes it so you can't "talk about" a node. A node contains its links. The links are directional, so I could make some statement about a node by pointing to it, but I can't, as a third party make a link under my identity, separate from the author and content of the node, that points from some object to another. That makes the network more like a hard drive than a social space.
Further, since links aren't typed, you have to move that metadata inside the node, and since "keys" for identifying different fields in the node aren't themselves links, you can't have any notion of "schema" where a term can be reused. So there isn't really a facility for being able to do graph queries like "find me this type of data whose field has this value" which restricts a whole huge range of possibilities too long to list here. This also makes knowing what the binary data inside a node is. #IPLD and #Multiformats are intended to solve, post-hoc.
I'll stop there for now, and save what I think could be a different model for later, but I am thinking along the lines of merging with #LinkedData #Triplets , encoding the notion of authorship into links (so that links can have an "utterance" rather than "fact" ontological status), a notion of container/contained for explicit block formation and metadata separation, and formalizing the notion of orthogonal Merkel DAGs to change the points where the content addressing happens to be able to have "graph subunits" that allow for cycles at a "complete" scope but for the purposes of hashing have no cycles. very much #WIP, still at conceptual stage haven't started writing spec yet.
#ipfs #merkeldag #ipld #multiformats #linkeddata #triplets #wip #longpost #p2p #workinginpublic
OK I'm starting my #p2p #LinkedData reading list to get started drafting a protocol and I'm checking out #IPLD - lots of really good ideas here, and plenty to learn from. It has a bit of a different focus than what I have planned, but some stuff i like and some stuff I can learn from:
I depart from a lot of their design decisions, and it's also clear that this is something that evolved in the process of developing IPFS (they say as much) to fill gaps as they were emerging, rather than a foundational part of the ecosystem. In particular I think the blockchain brain ties them to this notion of immutability, append-only stuff which (imperfectly) trades off with needs for privacy and careful scoping/permissions, valuing verifiability and structuredness above ease of expression, and etc. Regardless, interesting to see a bit of the way they think, particularly since they're a bunch of years ahead of me in dealing with the practicalities of implementation.
I'm gonna try and do this project in public, writing as I go on here rather than limiting to an end piece, so if u want to avoid future posts like this from me in the future u can mute the #Longpost and #WorkingInPublic hashtags which will be sort of wandering like this.
#p2p #linkeddata #ipld #ipfs #longpost #workinginpublic #protocols
Held a good #WorkingInPublic session with @changbai and @flancian. Thank you!
#workingInPublic on Jitsi now: https://meet.jit.si/celeste-summit
Join to talk and see me writing text.
I'm enjoying John's process videos like this one testing o-ring fitment and compression when under pressure.
#machining #WorkingInPublic
https://youtu.be/nc8_S0gkAVs
Anybody up for a #workingInPublic session for Merveilles in Jitsi tomorrow or the day after it?
#WorkingInPublic on the [[Agora]] tonight.
This is an example of Transclusion in the Agora, as per the pattern by Nelson (1980) and Sutherland (1963).
This all as an exercise of #WorkingInPublic, done with [[loving kindness]] :)
An [[Agora]], late [[2022]].
I accidentally committed the unfinished command and test last night, complete with dd() statement 😅.
#latenightcoding #workinginpublic #professional
#WorkingInPublic in [[hypatia]]
as of [[2022-11-20]] we are truly living in the future... as long as you don't want a wildcard cert :)
this screenshot contains a mistake ;)
as of [[2022-11-20]] we are truly living in the future... as long as you don't want a wildcard cert :)
this screenshot contains a mistake ;)
we
@SocialCoop [[working in public]] #WorkingInPublic
Thank you for the opportunity of being an instance admin, it's a privilege.
AMA / let me know if you need anything!