Twitter had what, 160 or 280 char limit per message? 50k*280 is 14MB. What's to imagine here?
The AT protocol is the most obtuse crock of shit
231–240 of 493 posts
Re: The AT protocol is the most obtuse crock of shit
#232Earlier quoted context omitted.
> "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.
Does that makes it more difficult to implement the right to be forgotten and block spam and trolls?
Re: The AT protocol is the most obtuse crock of shit
#233Okay 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…
Can you elaborate on this point? There's multiple mature solutions in this space like OpenAPI+Json Schema, GraphQL, gRPC. All try to solve the same problems to varying degrees and provide similar benefits like generated static typed and runtime validation. Was there something unique for you that made these tools not appropriate and prevented you from building upon an existing ecosystem?
Re: The AT protocol is the most obtuse crock of shit
#234It says To use the Mastodon web application, please enable JavaScript. Alternatively, try one of the native apps for Mastodon for your platform. Good job, Mastodon. (No, I am not the same guys that complain they don't see javascript games or utilities without javascript. But I think I should be able to see a text on the Internet?)
Re: The AT protocol is the most obtuse crock of shit
#235Okay 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…
Re: The AT protocol is the most obtuse crock of shit
#236Earlier quoted context omitted.
I’m curious about this. So email that I’ve sent, let’s say from a gmail account to an iCloud account, isn’t guaranteed to be verifiable years later because of dkim key rotation? That’s not great. I wonder if the receiver could append a signed message upon receipt with something like “the sender’s identity was valid upon receipt”.
> I wonder if the receiver could append a signed message upon receipt with something like “the sender’s identity was valid upon receipt”. That's exactly what does happen, if you view the raw message in GMail/iCloud, you should see DMARC pass/fail header added by the receiving server (iCloud in your example). (Well not exactly , it's not signed, but I'm not sure that's necessary? Headers are applied in order, like a w…
I’m also curious how this plays into the original comment about dkim/spf/dmarc not being sufficient due to key rotation still factors into the conversation after having discussed this?
Re: The AT protocol is the most obtuse crock of shit
#237Earlier quoted context omitted.
The tone of that whole thread in combination with posts like > Imagine if I had to store the 50k+ tweets I've made on Twitter on my device, and upload ALL of them to a new server whenever a community server went down. doesn't make this person seem particularly competent. I'm getting a vague feeling that this is normal discourse on Mastodon though, and that not using social media much shifts your personal overton wind…
Yea I was like, 50K tweets converted to bytes is like… well it’s one second to upload on my home internet connection. After that, it just felt like rant.
Re: The AT protocol is the most obtuse crock of shit
#238Okay 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…
Some of this seems very familiar, in a good way, which makes me very interested in Bluesky and the AT protocol. I worked with XRIs and was on the XDI TC. I also was on the fringes of some of the early DID spec work, and experimented with Telehash for while. I know Jeremie Miller is on the board, is Telehash or something similar being used within Bluesky? Also, I'm sure you get this a lot, but I'd love a BlueSky invit…
Re: The AT protocol is the most obtuse crock of shit
#239Earlier quoted context omitted.
ActivityStreams just requires an object to have a unique URI. ActivityPub says it "should" be a https URI. However, since this URI is expected to be both unique and unchanging (if you put up the same content with a different id, it's a different object), you can choose to use it as the input to a hash function and put the posts in a content-addressable store. Mastodon will already check the local server first if you…
one important difference is: > expected Because the URI is only _expected_ to be immutable, not required, servers consuming these objects need to consider the case where the expectation is broken. For example, imagine the serving host has a bug and returns the wrong content for a URI. At scale this is guaranteed to happen. Because it can happen, downstream servers need to consider this case and build infrastructure t…
Posts are explicitly not immutable, so they do need to be revalidated, and that's fine.
For a social network immutable content is a bad thing. People want to be able to edit, and delete, for all kinds of legitimate reasons, and while you can't protect yourself against people keeping copies you can at least make the defaults better.