robin

joined 8 years ago
[–] robin@mastodon.social 8 points 6 months ago (1 children)

@JustinH @mariafarrell @fediverse Thank you! Yes — "this chaotic-seeming thing is good, actually" is a tough message :)

[–] robin@mastodon.social 1 points 9 months ago

@poVoq Look, no offence but I'm almost at three decades working on web standards. I lost interest in people picking sides for one tech just for the sake of it a long time ago. Happy to discuss if you have better than vague and inaccurate analogies to unrelated tech or "seems to be" aspersions about documented architectures, but if not I'll just get back to my weekend!

[–] robin@mastodon.social 1 points 9 months ago (2 children)

@poVoq Cloud providers aren't commodified, they're not interoperable. You're comparing a protocol with specific design to enable commodification with proprietary platforms. If you don't understand the properties of ATProto that target that, your critiques are going to go well wide.

[–] robin@mastodon.social 1 points 9 months ago (1 children)

@poVoq For instance, I think it would make *a lot* of sense to manage PDS infra with coops the way it's done in plenty of places for energy provision. Things become a lot harder to manage when the people who are good at providing a commodity *also* have to be good at CoMo. For completely different topics. In completely different languages. Etc. Decoupling really helps here.

[–] robin@mastodon.social 1 points 9 months ago (3 children)

@poVoq I used to think that treating the server as a cityish thing made best sense. But cities are dense, they are used for everything including many things we often don't think about (see Jacobs, etc.). The mapping doesn't work very well, except perhaps for people who are very much in one community rather than overlapping ones.

The ATProto approach is credible exit and all the properties that make servers into commodities. It means that you have better flexibility in dealing with infra.

[–] robin@mastodon.social 1 points 9 months ago (8 children)

@poVoq Except that there is no *necessary* requirement to reproduce the constraints of IRL infrastructure specifically at that location. A good question is why pick a server instead of, say, people who use the same undersea cable? Typically that's because cables are a commodity whereas servers provide a single point of capture. But there are two options: make the server democratic or make the server a commodity (a real one, with no power and near-zero switching costs).

[–] robin@mastodon.social 1 points 9 months ago (10 children)

@maegul @poVoq I'm well aware of democratic work at the instance level, I just don't think that it's the right granularity and I don't see how it doesn't get captured. I'm interested in solutions that work even for people who use Gmail.

I don't understand the Bluesky comment, it doesn't sound related to anything I've said or even to reality?