I keep building lots of atproto tools, and they all use app passwords, cos most have unattended modes, but *damn* if that isn’t scary as hell.
blinkers.dev gets me most of the way, but it’s still not great to have to run an additional server to do this (especially for the less technically inclined)
1 Boost
0 Likes
I’m definitely interested in @thisismissem.social@bsky.brid.gy’s excellent recent proposal, but I don’t know if it’d cover very long lived/unattended processes (like servers), and wouldn’t be able to constrain to specific rkeys, or parts of records anyway.
[Spec Change Request] Support ...
@tranquil.farm & @jaz.sh@bsky.brid.gy (vlpds 😍) have you considered how even tighter scopes might work for app passwords?
eg: auth that allows writing @marque.at@bsky.brid.gy DNS records for just one subdomain (or just certain record types)