bairun ツ
@bairun.xyz
working on a open, public, decentralized data protocol • https://bairun.xyz
Here’s an updated link bsky.app/profile/bair.... Not sure when it got changed
Here's an updated link github.com/graphprotoco...
December 5, 2024 at 5:10 PM
Here’s an updated link bsky.app/profile/bair.... Not sure when it got changed
Rite of passage for new CS2 players
December 2, 2024 at 4:30 PM
Rite of passage for new CS2 players
I was an alpha user as well but bounced away because of how much they pivoted to documents vs notes so excited to check this out
November 28, 2024 at 3:19 PM
I was an alpha user as well but bounced away because of how much they pivoted to documents vs notes so excited to check this out
Designing for maximally composable data and behaviors for highly dynamic data is actually a very complex problem. Interestingly, some video game engines use this exact tagging approach to compose data and behaviors for in-game objects
en.wikipedia.org/wiki/Entity_...
en.wikipedia.org/wiki/Entity_...
Entity component system - Wikipedia
en.wikipedia.org
November 27, 2024 at 7:57 PM
Designing for maximally composable data and behaviors for highly dynamic data is actually a very complex problem. Interestingly, some video game engines use this exact tagging approach to compose data and behaviors for in-game objects
en.wikipedia.org/wiki/Entity_...
en.wikipedia.org/wiki/Entity_...
Consuming type-aware data is now possible for any use-case, without the complexity and rigidness of schemas and tables. It's all data pipelines, so a developer or end-user can decide what behaviors to layer on top of the type information. Or ignore it completely. 4/x
November 27, 2024 at 7:57 PM
Consuming type-aware data is now possible for any use-case, without the complexity and rigidness of schemas and tables. It's all data pipelines, so a developer or end-user can decide what behaviors to layer on top of the type information. Or ignore it completely. 4/x
Consumers can decide how to consume entities based on the types that it has. If an entity is a Programmer and knows Rust I might show a different UI than if they know Python. You could make a feed of all the Programmers that are also Photographers. There's a lot of us 👋🏼. 3/x
November 27, 2024 at 7:57 PM
Consumers can decide how to consume entities based on the types that it has. If an entity is a Programmer and knows Rust I might show a different UI than if they know Python. You could make a feed of all the Programmers that are also Photographers. There's a lot of us 👋🏼. 3/x
Types in GRC-20 work like tags. A type describes which properties might exist on an entity of the given type. Types on entities are composable, so an entity might be more than one type at once. For example, an entity might be a Programmer and a Photographer. 2/x
November 27, 2024 at 7:57 PM
Types in GRC-20 work like tags. A type describes which properties might exist on an entity of the given type. Types on entities are composable, so an entity might be more than one type at once. For example, an entity might be a Programmer and a Photographer. 2/x
Main thing will be monetization pathways. Can a business monetize on atproto better than it could on a centralized thing? My guess is no.
November 26, 2024 at 5:54 PM
Main thing will be monetization pathways. Can a business monetize on atproto better than it could on a centralized thing? My guess is no.
Works great for me the last few months
November 26, 2024 at 4:14 PM
Works great for me the last few months
Call it “Random thoughts on SQLite internals.” Turn it into a bullet list.
November 24, 2024 at 3:42 AM
Call it “Random thoughts on SQLite internals.” Turn it into a bullet list.
unique insights can be the moat*
November 23, 2024 at 7:09 PM
unique insights can be the moat*
data harvesting tools. Maybe bsky the company has the best data science team with the best insights they can sell to people and that’s their monetization. At that point it’s Web 2.0 monetization with extra decentralization steps.
November 23, 2024 at 7:09 PM
data harvesting tools. Maybe bsky the company has the best data science team with the best insights they can sell to people and that’s their monetization. At that point it’s Web 2.0 monetization with extra decentralization steps.
Eventually the people undercutting competitors will have to make money somehow, but there’s no obvious way to do it that competitors can’t just replicate. Data science teams will probably be the money makers, because unique insights can be the most. So any products built on open data just become…
November 23, 2024 at 7:09 PM
Eventually the people undercutting competitors will have to make money somehow, but there’s no obvious way to do it that competitors can’t just replicate. Data science teams will probably be the money makers, because unique insights can be the most. So any products built on open data just become…
That’s the biggest problem with an open, decentralized platform in general. Monetization. Anybody can undercut your pricing or provide the same service service in a better way because the data is open. The only moat is the product, which is great for consumers but a tough position for businesses.
November 23, 2024 at 7:09 PM
That’s the biggest problem with an open, decentralized platform in general. Monetization. Anybody can undercut your pricing or provide the same service service in a better way because the data is open. The only moat is the product, which is great for consumers but a tough position for businesses.
Like everything there’s tradeoffs for this model, namely developer tooling for graphs vs tables. I’ll talk about how we’re solving this with schemas and types soon.
November 22, 2024 at 6:52 PM
Like everything there’s tradeoffs for this model, namely developer tooling for graphs vs tables. I’ll talk about how we’re solving this with schemas and types soon.
We think this model is incredibly powerful for composability and extensibility over public, open, decentralized data. It’s effectively a giant knowledge graph with subgraphs for each community composed into a global mega-graph. This is working today with a small set of alpha users.
November 22, 2024 at 6:52 PM
We think this model is incredibly powerful for composability and extensibility over public, open, decentralized data. It’s effectively a giant knowledge graph with subgraphs for each community composed into a global mega-graph. This is working today with a small set of alpha users.
Community A and Individual B can add data to the same node permissionlessly, but they can’t change the data from other communities unless they are a member. This enables different groups to add their own views and perspectives to the same data. Maximum composability over the same data.
November 22, 2024 at 6:52 PM
Community A and Individual B can add data to the same node permissionlessly, but they can’t change the data from other communities unless they are a member. This enables different groups to add their own views and perspectives to the same data. Maximum composability over the same data.
Where this gets interesting is that you can layer a permissions and scoping model over the data. Each piece of data in the graph is scoped to an id which represents an individual or community.
November 22, 2024 at 6:52 PM
Where this gets interesting is that you can layer a permissions and scoping model over the data. Each piece of data in the graph is scoped to an id which represents an individual or community.
Interoperability in this graph model just comes down to using the same node id. Extending the node is just adding new properties or edges to it. No need to run migrations to merge it into your database schema.
November 22, 2024 at 6:52 PM
Interoperability in this graph model just comes down to using the same node id. Extending the node is just adding new properties or edges to it. No need to run migrations to merge it into your database schema.
In a classic schema-first, row-based model, interoperability over the same data sets is much more complex. You end up needing a lot of tooling to merge someone else’s representation of a row with yours. You need to write migrations to add/remove columns in your db or change column types.
November 22, 2024 at 6:52 PM
In a classic schema-first, row-based model, interoperability over the same data sets is much more complex. You end up needing a lot of tooling to merge someone else’s representation of a row with yours. You need to write migrations to add/remove columns in your db or change column types.
You can add as many properties as you want to represent this node. Additional, you can add edges. Edges represent relationships between Nodes. Byron is Married to Jess. Married to is an Edge, and in our model it’s actually a Node, too. So you can add data to it like “Marriage date.”
November 22, 2024 at 6:52 PM
You can add as many properties as you want to represent this node. Additional, you can add edges. Edges represent relationships between Nodes. Byron is Married to Jess. Married to is an Edge, and in our model it’s actually a Node, too. So you can add data to it like “Marriage date.”