https://aboutmako.makopool.com
Currently (at least on this account) focused on protocol and UX. Radical extensibility agenda.
alt for foodposts: https://bsky.app/profile/makoconstruct-food.bsky.social
Passed comment on a potential `$extensions` field for atproto objects. I think it's necessary (though not sufficient) to escape the need for the mutation of lexicon types and actually decentralize the evolution of the protocol.
Passed comment on a potential `$extensions` field for atproto objects. I think it's necessary (though not sufficient) to escape the need for the mutation of lexicon types and actually decentralize the evolution of the protocol.
github.com/makoConstruc...
github.com/makoConstruc...
hackmd.io/@xZDxp0NgTQe...)
Privacy-preserving real identity systems are totally possible, and it's disturbing that no one is talking about that given what's currently going on (age verification discourse, llm spam apocalypse, generally languishing democracies)
hackmd.io/@xZDxp0NgTQe...)
Privacy-preserving real identity systems are totally possible, and it's disturbing that no one is talking about that given what's currently going on (age verification discourse, llm spam apocalypse, generally languishing democracies)
www.youtube.com/watch?v=984r...
www.youtube.com/watch?v=984r...
Galled that flutter/android never established a standard way of getting the screen size in mms,
Galled that flutter/android never established a standard way of getting the screen size in mms,
infinite TPS globally (while any individual actor is 900tps), so it has that crucial but currently very rare quality that it wouldn't just become prohibitively expensive and choke if it saw global adoption.
infinite TPS globally (while any individual actor is 900tps), so it has that crucial but currently very rare quality that it wouldn't just become prohibitively expensive and choke if it saw global adoption.
Apparently 40x faster than merkle stuff. I can now see why. But I look forward to forgetting why and just using someone else's implementation cause it's a lot
Apparently 40x faster than merkle stuff. I can now see why. But I look forward to forgetting why and just using someone else's implementation cause it's a lot
- freeourfeeds.com announces campaign for an independent governance organisation for ATProto
- Mark Cuban looking to fund a TikTok alternative on ATProto
- A deep dive explainer on Lexicons, and why they matter
Read at […]
- freeourfeeds.com announces campaign for an independent governance organisation for ATProto
- Mark Cuban looking to fund a TikTok alternative on ATProto
- A deep dive explainer on Lexicons, and why they matter
Read at […]
A technical deep-dive, since people have been asking me for my thoughts. I'll expand a bit on some of the key points here in a thread. 🧵
A technical deep-dive, since people have been asking me for my thoughts. I'll expand a bit on some of the key points here in a thread. 🧵
the first is a high-level introduction to "causal logs" - how and why replicating operation-based CRDTs means storing them in a partially-ordered dependency graph.
the first is a high-level introduction to "causal logs" - how and why replicating operation-based CRDTs means storing them in a partially-ordered dependency graph.
I feel like they *shouldn't be*? Like from what I can gather, "specialist" graph dbs never needed to be a thing,
I feel like they *shouldn't be*? Like from what I can gather, "specialist" graph dbs never needed to be a thing,
*has a bit of a cry about IPLD::dag-cbor only allowing keys to be strings*
... You know what? I don't accept this.
If you're going to introduce a special type for binary-encoding CIDs in values, you should also allow that type when CIDs are used as keys,
*has a bit of a cry about IPLD::dag-cbor only allowing keys to be strings*
... You know what? I don't accept this.
If you're going to introduce a special type for binary-encoding CIDs in values, you should also allow that type when CIDs are used as keys,