fuck authn, fuck authz
fuck authn, fuck authz
Good breakdown by @yossarian.net about that
Good breakdown by @yossarian.net about that
it’s a simple rule that vastly simplifies just about any authz/authn conversation around agents
it also provides clear guidance for how an agent fits into an organization (socially speaking)
As it should be!!
In the end, the dev still 100% responsible for shipping code. If they ship a regression: that was the DEV's decision. AI doesn't "decide" anything - it's a tool!
it’s a simple rule that vastly simplifies just about any authz/authn conversation around agents
it also provides clear guidance for how an agent fits into an organization (socially speaking)
Kyle Simpson on local-first identity, encryption, passkeys and authn.
www.localfirst.fm/17
Kyle Simpson on local-first identity, encryption, passkeys and authn.
www.localfirst.fm/17
Who is doing interesting work in this regard?
Who is doing interesting work in this regard?
- Race condition in system that updates DNS records for DynamoDB instances causes deletion of key records
- DynamoDB becomes unavailable
- Tons of services relying on DynamoDB start to also go down (EC2, network load balancing, Lambda, ECS, EKS, Fargate, Connect, STS, IAM authn)
- Race condition in system that updates DNS records for DynamoDB instances causes deletion of key records
- DynamoDB becomes unavailable
- Tons of services relying on DynamoDB start to also go down (EC2, network load balancing, Lambda, ECS, EKS, Fargate, Connect, STS, IAM authn)
I love the UX, such an improvement.
Do y'all have a magical password manager that works without 15 taps in mobile apps?
Or are you self-defeating by not using the built-in (Chrome or iCloud) authenticator? Is this a Linux desktop issue?
- Firehose: full Merkle Search Tree updates, cryptographic guarantees, big/slow
- Jetstream: contents, no MST diffs, faster but no authn (trusts firehose to check authn)
- Turbostream: Jetstream, but "hydrated" by filling in refs to users/other records
#atproto
it's jetstream but a bunch of linked data is pre-hydrated, so you don't need to do a bunch of xrpc calls when processing events!
user profile info is attached, parent posts are included with replies, embedded records from quote posts...
- Firehose: full Merkle Search Tree updates, cryptographic guarantees, big/slow
- Jetstream: contents, no MST diffs, faster but no authn (trusts firehose to check authn)
- Turbostream: Jetstream, but "hydrated" by filling in refs to users/other records
#atproto
Exposed by the @ngrok.com Kubernetes Operator.
Such a pleasant experience.
zitadel.rawkode.academy
Exposed by the @ngrok.com Kubernetes Operator.
Such a pleasant experience.
zitadel.rawkode.academy