Live data from Hacker News

The AT protocol is the most obtuse crock of shit

urbanists.social

311–320 of 493 posts

Re: The AT protocol is the most obtuse crock of shit

#311

Earlier quoted context omitted.

Maybe they could call it the Strudel protocol?

"Rocambole" would be even easier to search for

Ok, If I make a protocol I will call it "rocambole" but I will be thinking of the sand leek rather than the victorian fictional adventurer.

Re: The AT protocol is the most obtuse crock of shit

#312
post #162

Earlier quoted context omitted.

If they'd proposed (or even just implemented) improvements that at least suggested they'd considered existing options and wanted to try to maximise the ability to do interop (even with proxies), I'd have been more sympathetic. But AT to mean seems to be a big ball of Not Invented Here that makes me worry that either they didn't care and try, or that they choice to make interop worse for a non-technical reason.

During this stage of discovery I'm completely comfortable with ground up rethinks. I don't feel we have the correct solution and there is no commercial reason to ge this thing shipped. Now is the time to explore all the possibilities. Once we have explored the problem space we should graft the best bits together for a final solution, if needed. I'm not sure I see the value of standardizing on a single protocol. Multi…

Ground up rethinks that takes into account whether or not there's an actual reason to make a change is good. Ground up rethinks that throws things away for the sake of throwing them away even what they end up doing would layer cleanly are not. They're at best lazy. At worst intentional attempts at diluting effort. I'm hoping they've only been lazy.

Re: The AT protocol is the most obtuse crock of shit

#314
post #54

Okay well. I work on Bluesky and helped build the AT Protocol. I'm sorry Sam differs with us on this, and I'm glad that Activity Pub is already there for him. However, Sam doesn't understand the ATProto very well and I want to clear it up a bit. Before I do, let me just say: Bluesky and the AT Proto are in beta. The stuff that seems incomplete or poorly documented is incomplete and poorly documented. Everything has m…

Not having read the article, I got pretty far into your second paragraph before realizing you all aren't talking about configuring a modem over a serial link. It's funny because the "Hayes AT command set" protocol is also an obtuse crock. I was really hoping you were going to open my mind with some deep wisdom straight out of 1981.

> Hayes AT command set" protocol is also an obtuse crock.

I will nake sure to reuse this name if I ever find myself developing an Obtuse crock.

Re: The AT protocol is the most obtuse crock of shit

#315

Earlier quoted context omitted.

I have not looked much at AT, but it seems it solves many of the same problems as Matrix. Instead of redoing all the Crypto and everything, why not build on martrix. There were other Twitter like things on Matrix before. As far as I'm aware its developed on Matrix and had some connection with it, so this isn't a case of not knowing about it so there is likely some engineering reasons why this was not done. Would be i…

AT proto has some significant similarities to Matrix: * Both are work by self-authenticating git-style replication of Merkle trees/DAGs * Both define strict data schemas for extensible sets of events (Matrix uses JSON schema - https://github.com/matrix-org/matrix-spec/tree/main/data/eve... and OpenAPI; AT uses Lexicons) * Both use HTTPS for client-server and server-server traffic by default. * Both are focused on dec…

> Both define strict data schemas for extensible sets of events (Matrix uses JSON schema

Matrix uses JSONSchema to define event schemas, but how can they be considered strict if the Matrix spec doesn't specify that any of them have to be validated apart from the PDU fields and a sprinkling of authorization events?

> Matrix has an open governance model with >50% of spec proposals coming from the wider community these days.

Do you have a percentage for the proportion of spec proposals from the wider community making it into spec releases?

Re: The AT protocol is the most obtuse crock of shit

#316

Earlier quoted context omitted.

My reaction whenever I see such headline is always "there must be an engineer out there who worked on this, I wonder how they feel about this". I had the same reaction today, opened comments and you were at the top. I love HN sometimes.

A few years ago I had to work with an obscure 90's era embedded microcontroller with a proprietary language and IDE, and a serial adapter based programmer and debugger. The IDE sucked, and programming would fail 9 times out of 10, but at least the debugger was solid. By complete chance, I happened to interview someone that had, "wrote the debugger for that obscure microcontroller back in the 90's," tucked away in the…

Was it some MCU from Rabbit Semiconductor?

Re: The AT protocol is the most obtuse crock of shit

#317
post #54

Okay well. I work on Bluesky and helped build the AT Protocol. I'm sorry Sam differs with us on this, and I'm glad that Activity Pub is already there for him. However, Sam doesn't understand the ATProto very well and I want to clear it up a bit. Before I do, let me just say: Bluesky and the AT Proto are in beta. The stuff that seems incomplete or poorly documented is incomplete and poorly documented. Everything has m…

Not having read the article, I got pretty far into your second paragraph before realizing you all aren't talking about configuring a modem over a serial link. It's funny because the "Hayes AT command set" protocol is also an obtuse crock. I was really hoping you were going to open my mind with some deep wisdom straight out of 1981.

> the "Hayes AT command set" protocol is also an obtuse crock

Yeah, but it's an obtuse crock that you can literally still here in your memories. How many protocols can say that? It has a special place in my heart, I think.

Re: The AT protocol is the most obtuse crock of shit

#318
post #198

Earlier quoted context omitted.

In this hypothetical minimalist Twitter clone in the 2009 spirit, images are elsewhere. We have a widely used hypertext protocol that lets you reference media objects from anywhere, so let’s use that. Client apps can individually solve the image upload usability question in ways that fit their user base. Yes, there will be broken links. But IMO that’s better than having all your data in one centralized location where…

Deep linking Flickr's content without showing Flickr's adverts gets you blacklisted so quick.

2010 was a more optimistic time. The integration described in that old TechCrunch post was clearly designed together with Flickr.

Re: The AT protocol is the most obtuse crock of shit

#319
post #54

Okay well. I work on Bluesky and helped build the AT Protocol. I'm sorry Sam differs with us on this, and I'm glad that Activity Pub is already there for him. However, Sam doesn't understand the ATProto very well and I want to clear it up a bit. Before I do, let me just say: Bluesky and the AT Proto are in beta. The stuff that seems incomplete or poorly documented is incomplete and poorly documented. Everything has m…

> ATProto doesn't use crypto in the coin sense. It uses cryptography. The underlying premise is actually pretty similar to git.

It's annoying how the word blockchain got associated with the worst of cryptocurrency excesses, isn't it ?

Also :

https://medium.com/@shemnon/is-a-git-repository-a-blockchain...

Re: The AT protocol is the most obtuse crock of shit

#320
post #54

Okay well. I work on Bluesky and helped build the AT Protocol. I'm sorry Sam differs with us on this, and I'm glad that Activity Pub is already there for him. However, Sam doesn't understand the ATProto very well and I want to clear it up a bit. Before I do, let me just say: Bluesky and the AT Proto are in beta. The stuff that seems incomplete or poorly documented is incomplete and poorly documented. Everything has m…

Reading this I hear someone passionate about technology for the sake of technology. Which is cool, I totally get the desire to build things oneself, but it doesn't really address the substantive questions people are asking about AT: An open protocol exists that broadly does what you want to do. That protocol is stable and widely used. That in itself, regardless of the quality of the protocol, already represents an OK…

I run a single user ActivityPub instance with a minimal following and small number of people across multiple instances that I follow. From a user perspective ActivityPub is fine I have no complaints.

However from an Ops perspective ActivityPub is incredibly chatty. If this had to scale to a larger instance the costs would spiral fast. Operationally and cost efficiency wise ATProto is a better looking protocol already. From a single individual user this won't necessarily be obvious right off the bat. But it will tend to manifest in either overworked operations people or slow janky instance performance.

While it's certainly a reasonable question whether the world needs another federated social protocol or not ATProto definitely solves real problems with the ActivityPub protocol.

Post reply on HN