Bombos
@bombostrue.bsky.social did:plc:fgwsjuwe4qluvsya7bhg4jdz
Forget AI, Bombos does it! More work done with the same amount of people. https://bombos.ai/en
No Bluesky desde
- Seguidores
- 46
- Seguindo
- 98
- Posts
- 119
- Dias nos rankings
- 0
Resumo
Bombos (@bombostrue.bsky.social) é um usuário do Bluesky desde 28 setembro 2026. Tem 46 seguidores, segue 98 contas e publicou 119 posts.
Aparições nos rankings
Os melhores dias em que posts desta conta entraram na lista diária do Debya.
Esta conta ainda não apareceu em um ranking diário.
Posts curtidos recentemente
Curtidas públicas da rede Bluesky.
One #native #passkey experience. Every moment that matters. What if AI agents could act on your behalf, with your passkey approval? 🔐 Native authentication 🤖 Human-in-the-loop approval 🛡️ Just-in-time authorization Built with #Keycloak and the Agent-Native Authorization (ANA) framework Demo 👇
Ver postAgent guardrails question: max tool calls per task, a token budget per run, or a human approval on anything that writes. Which one do you actually have in prod?
Ver postagent learning through governance https://cubething.dev/blog/agent-learning-through-governance
Ver post"SPIFFE confirms the presence of agents and prevents spoofing. That's it," says Karthik Karunanithi, a solution architect at IBM. Workload identity is the gate check. Deciding what an authenticated agent may access or change takes a separate authorization and policy layer on top.
Ver postScoped, revocable credentials is the right primitive. The hard part is not issuance, it is the audit trail: who authorized what, and can the agent edit its own log. If the same principal writes and grades the record, revocation is theater.
Ver post
Contas que bloqueia
No Bluesky, bloqueios são registros públicos.
Esta conta não bloqueia ninguém.