The article is about talking to modems right?
The AT protocol is the most obtuse crock of shit
141–150 of 493 posts
Re: The AT protocol is the most obtuse crock of shit
#142Earlier quoted context omitted.
Hi, original author here. Some comments: > We sign the records so that authenticity can be determined without polling the home server, and we use a repository structure rather than signing individual records so that we can establish whether a record has been deleted (signature revocation). Why do you need an entirely separate protocol to do this? Email had this exact same problem, yet was able to build protocols on t…
> I have 55k tweets, that would be a nightmare to host locally) theyre tweets, how much could they cost? @ 280 bytes each, that's like 15MB. double it for cryptographic signatures and reply-to metadata. is that really too much to ask for the capacity to transfer to another host at anytime? (also, leaving aside the fact that 55k tweets puts you in the 0.1% of most prodigious users)
> double it for cryptographic signatures and reply-to metadata
Ah, email, where a message of 114 characters with no formatting ends up over 9KB due to authentication and signatures, spam analysis stuff, delivery path information and other metadata. Sigh. Although I doubt this will end up as large as email, the lesson is that metadata can end up surprisingly large.
In this instance, I think 1–2KB is probably more realistic than the half kilobyte of “double it”.
Re: The AT protocol is the most obtuse crock of shit
#143It seems like blue sky is fun right now because it’s exclusive. There doesn’t seem to be anything fundamental to the technology that differentiates the experience from Twitter.
Re: The AT protocol is the most obtuse crock of shit
#144It says
To use the Mastodon web application, please enable JavaScript. Alternatively, try one of the native apps for Mastodon for your platform.
Re: The AT protocol is the most obtuse crock of shit
#145It seems to me that a lot of the problems discussed in this thread (it's using a new protocol that doesn't work with existing tools, it uses crypto, handles auth in the protocol, server can goes down) are just frustrations that don't have to do with the core innovation that Bluesky promises to deliver, and are instead confusing the AT protocol to be another ActivityPub-related protocol, rather than something complete…
> are just frustrations that don't have to do with the core innovation that Bluesky promises to deliver, and are instead confusing the AT protocol to be another ActivityPub-related protocol, rather than something completely different. AtProto is designed to be a federated protocol. The issue I have is that it is not interoperable with the major standard used on the federated internet right now: ActivityPub. You can b…
My experience with mastodon is that both explore and the feed are miles behind the experience I have on twitter to discover content I care about. No offense but everybody that switched from twitter to mastodon that I know went back. In the end I dont care what protocol you use but mastodon experience really isn't great IMO so I tend to be willing to give Bluesky a shot before I judge.
Re: The AT protocol is the most obtuse crock of shit
#146It's not that bad. ATZ and ATDT are the main two you have to remember. Wait, is that not what we're talking about? So, it has a confusing name too?
+++ATH0 I hope I have just disconnected someone browsing this page with a dialup modem.
It only works if you're sending it, so you have to put it in a ping payload, to make a "ping of death".
This only works because Hayes patented the idea of the escape code being +++ followed by a delay, so to evade the patent, most other modem OEMs removed the delay requirement.
Re: The AT protocol is the most obtuse crock of shit
#147Anyone else read "AT protocol" and thought of old modems?
Yes, me. But old modems? Two months ago I was integrating a 5G modem into a bare metal embedded application. AT is also used for the WiFi and Bluetooth chips/modems we use. AT commands on two- or four-wire RS232. Not everything is Linux and PCI/USB.
Same here, had a client ask for an AT command set to have a brand new nRF52 talking with a Cortex-M3 running some other legacy code.
Re: The AT protocol is the most obtuse crock of shit
#148Okay 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…
Hi, original author here. Some comments: > We sign the records so that authenticity can be determined without polling the home server, and we use a repository structure rather than signing individual records so that we can establish whether a record has been deleted (signature revocation). Why do you need an entirely separate protocol to do this? Email had this exact same problem, yet was able to build protocols on t…
[flagged]
Re: The AT protocol is the most obtuse crock of shit
#149Earlier quoted context omitted.
Having done a decent bit of hacking around ActivityPub, when I read the (thin, which 'pfraze and others have copped to) documentation I immediately went "oh, this is going to be way more scalable than ActivityPub once it's done." It's not all roses. I'm not sold on lexicons and xrpc, but that's probably because I am up to my eyeballs in JSON Schema and OpenAPI on a daily basis and my experience and my existing toolki…
> "oh, this is going to be way more scalable than ActivityPub once it's done." Can you elaborate on this?
I think this is referring to the content-hashed user posts. Using this model one can pull content from _anywhere_ without having to worry about MITM forgeries etc. This opens up the structure of the network, basically decentralizing it even _more_.
Correct me if I'm wrong on this though.
Re: The AT protocol is the most obtuse crock of shit
#150It seems to me that a lot of the problems discussed in this thread (it's using a new protocol that doesn't work with existing tools, it uses crypto, handles auth in the protocol, server can goes down) are just frustrations that don't have to do with the core innovation that Bluesky promises to deliver, and are instead confusing the AT protocol to be another ActivityPub-related protocol, rather than something complete…
> are just frustrations that don't have to do with the core innovation that Bluesky promises to deliver, and are instead confusing the AT protocol to be another ActivityPub-related protocol, rather than something completely different. AtProto is designed to be a federated protocol. The issue I have is that it is not interoperable with the major standard used on the federated internet right now: ActivityPub. You can b…
[flagged]