This has been discussed on 𝕏 / Reddit
Posts by chrisb --yolo
More often than not, in a community where reputation has been established, the claim of "bikeshedding" is used as a tool to shut down decent by those with influence that want to control the narrative.
Will someone please build a new modern development experience for non Apple mobile?
The entire Google/Android stack is embarrassing! Surpassed only by the extremely convoluted Play Store. 🤯
If you care about privacy in this digital world you need to learn about Third Party Doctrine and Bailment. Thankfully, @naomibrockwell.bsky.social puts the cookies on the lower shelf for you.
www.youtube.com/watch?v=iakg...
I think this is my least favorite thing about Bluesky. Someone quotes a post which starts a thread. Later on the author of the original post deletes it. Now, I have this comment about a video that I no longer can access.
Only Satoshi would not admit to being Satoshi
We may never know, but if I had to put all my chips on one square, this is where I'd place them.
Been thinking about this a bit. What's missing is a PDS secure inbox—one where apps can send encrypted "offers" that call apps can receives and establishes the call.
Turns out this has a ton of overlap with solving open DMs on atproto. WebRTC "offer" is just a special type of content sent via DM.
What's missing in AT Protocol to make this a reality is an open standard secured inbox.
That is, an inbox that can functions like your existing email provider, but receives E2E encrypted messages based on public keys stored in your PDS.
This is super interesting! And, I wonder if this the peanut butter my chocolate has been looking for?
atmosphere-mail solves delivering email to legacy behemoths (ie. gmail). I also want to solve the problem of a secure inbox for your atproto messages (DMs or email). 🍫+🥜🧈
bsky.app/profile/bosc...
I'm curious, how are you handling auth for this bi-directional sync?
How the 🇺🇸 government leapfrogs over your fourth amendment rights.
h/t @naomibrockwell.bsky.social
www.youtube.com/watch?v=hPAL...
Why
make 2>&1 | stash tee
is better than
make 2>&1 | tee build.log
github.com/vrypan/stash...
x402 has a new home in the Linux Foundation
"The new Foundation will serve as the neutral home for x402, a universal standard for payments that embeds payments directly into web interactions, enabling AI agents, APIs, and apps to transact value as seamlessly"
www.linuxfoundation.org/x402foundation
love this!
have you given any thought to layering a local first auth layer onto the PDS?
I've been experimenting with an "app key pair" that borrows the OAuth scope syntax for defining level of access, but I know others have pondered UCANs.
regulatory capture, there is no incentive to make their service better
Define local 😅 j/k
Does it come with a plane ticket? My week opened up, I’m sure @bmann.ca will let me sleep on his couch.
hey chat do you agree with this recommendation? (spoiler alert, claude did the recommending)
I 💯 agree that notifications could be a 3rd party service. I have long held this is the true grip Apple/Google have on the mobile market (as much as the app store).
I also think it is a huge privacy loss vector.
Wonder if the @grapheneos.org community is working on this?
bsky.app/search?q=fro...
How would you design it without depending on an external server?
just own it 😅
bsky.app/profile/bosc...
big fan of Signal, but it is a centralized service frequently at risk of being disallowed by some countries. Also, with E2EE DM built on AT Protocol, users can custody their own identity key pairs if they wish, which isn't possible with Signal.
it is today
it won't be when transit is dominated by self-driving electric vehicles that leverage the 25x more roads than rail
You should all read what moxie wrote about how Confer works. Outside of the TEE being compromised, not sure how FB would get access to your data. They could--as @matthewdgreen.bsky.social--mentioned change how things work and most user probbably wouldn't notice or care.
confer.to/blog/2026/01...
The lesson in this article is simple.
Do not trust ANY company to protect your private communications. The protocol itself must ensure this, and must be geographically distributed so no one legal jurisdiction can override it.
This is why we should push to adopt a standard for AT Protocol DMs.
AT Protocol's crypto roots run deep. Instead of reflexively hating this fact, it's OK to evaluate technology on its merits.
bsky.app/profile/atpr...
since you lose your privacy the moment you use money, does anything else even matter?
Working on it...seriously!
The problem with spam calls is not your ☎️ phone number ☎️ like many who don't understand the problem claim. The problem is how apps handle new inbound requests from people you don't know. (It applies to all communication apps)
More 👇
bsky.app/profile/bosc...
I use a bot plugin to solve those for me so I never see them
I feel like we have jumped straight to the blunt instruments used to fight email spam without first experimenting with the rich set of signals that AT Protocol gives us.