it's hard to see it as anything other than bullying when they so extensively strawman you, refusing to engage with the criticism in any way.
it's hard to see it as anything other than bullying when they so extensively strawman you, refusing to engage with the criticism in any way.
53, not really technical. Great at his job... as a religious master.
Learning to be a developer? He already thinks he's one.
Why?
Because he can vibecode with Cursor and get ChatGPT to teach him Python
53, not really technical. Great at his job... as a religious master.
Learning to be a developer? He already thinks he's one.
Why?
Because he can vibecode with Cursor and get ChatGPT to teach him Python
you can use the rest of the tools (the identity part, notably), you don't need to use records / sync protocol, and you'll still be pretty much atproto
you can use the rest of the tools (the identity part, notably), you don't need to use records / sync protocol, and you'll still be pretty much atproto
so i have to assume that people who are fine with not doing authenticated transfer either do not care, or do not understand the protocol.
so i have to assume that people who are fine with not doing authenticated transfer either do not care, or do not understand the protocol.
you can invent your own new kinds of instances that communicate on the protocol as your app requires.
you can invent your own new kinds of instances that communicate on the protocol as your app requires.
labelers also do this through the signatures on subscribeLabels! i.e. there are avenues for other forms of data to be on protocol!
labelers also do this through the signatures on subscribeLabels! i.e. there are avenues for other forms of data to be on protocol!
the question is never whether something "does atproto", it's whether it's *idiomatic* atproto. that doesn't necessarily mean records!
the question is never whether something "does atproto", it's whether it's *idiomatic* atproto. that doesn't necessarily mean records!