If you keep thinking "wow, Christine keeps being right in retrospect"
-
wrote for 21 dage siden sidst redigeret af
If you keep thinking "wow, Christine keeps being right in retrospect"
You can get in early on smug correctness by paying attention: the work we are doing at @spritely is the future
-
If you keep thinking "wow, Christine keeps being right in retrospect"
You can get in early on smug correctness by paying attention: the work we are doing at @spritely is the future
-
If you keep thinking "wow, Christine keeps being right in retrospect"
You can get in early on smug correctness by paying attention: the work we are doing at @spritely is the future
wrote for 21 dage siden sidst redigeret af -
wrote for 21 dage siden sidst redigeret af
-
-
C cwebber@social.coop shared this topic for 21 dage siden
-
wrote for 21 dage siden sidst redigeret af
@laurenshof @spritely Depends on what layer you're talking about. On the social layer you can extrapolate from a combination of https://gitlab.com/-/snippets/2535398 and https://codeberg.org/spritely/ocappub/src/branch/master/README.org
But in general Spritely is building infrastructure where things are consent-based and don't just necessarily resemble the web 2.0 social network era
-
@laurenshof @spritely Depends on what layer you're talking about. On the social layer you can extrapolate from a combination of https://gitlab.com/-/snippets/2535398 and https://codeberg.org/spritely/ocappub/src/branch/master/README.org
But in general Spritely is building infrastructure where things are consent-based and don't just necessarily resemble the web 2.0 social network era
wrote for 21 dage siden sidst redigeret afYeah, I've read both articles, and I understand that Spritely is aiming for a different network topology than the web2.0 shaped ones. But the articles dont make it clear yet to me what the rough topology would instead be.
My (extremely limited!) understanding is that the ocaps stuff mainly governs interactions between users and how set/control/define visibility access on posts. But are these users on servers, in a somewhat comparible manner to current fedi?
-
Yeah, I've read both articles, and I understand that Spritely is aiming for a different network topology than the web2.0 shaped ones. But the articles dont make it clear yet to me what the rough topology would instead be.
My (extremely limited!) understanding is that the ocaps stuff mainly governs interactions between users and how set/control/define visibility access on posts. But are these users on servers, in a somewhat comparible manner to current fedi?
wrote for 21 dage siden sidst redigeret af@laurenshof @spritely It's not instance-oriented in the way the fediverse is, and with OCapN, is more p2p
-
If you keep thinking "wow, Christine keeps being right in retrospect"
You can get in early on smug correctness by paying attention: the work we are doing at @spritely is the future
wrote for 19 dage siden sidst redigeret af@cwebber @spritely I found myself thinking "hmm, Bluesky technically didn't remove that persons content but they said virtually shadowban them for 99.99% of people using their network as It's virtually completely centralized, and ActivityPub handles the decentralized part better but it is still brittle, we need to bypass the server model entirely."
...and now it clicked as to why you're investing in Spritely.
-
@cwebber @spritely I found myself thinking "hmm, Bluesky technically didn't remove that persons content but they said virtually shadowban them for 99.99% of people using their network as It's virtually completely centralized, and ActivityPub handles the decentralized part better but it is still brittle, we need to bypass the server model entirely."
...and now it clicked as to why you're investing in Spritely.
️
