@atpassport.net
Handle Manager for atproto.
atprotoのハンドル管理アプリ
For apps not yet supported, use our Chrome/Firefox extensions.
未対応のアプリは、Chrome/Firefoxの機能拡張からご利用いただけます。
https://atpassport.net/
Developed by @usounds.work
@atpassport.netI use Wxt, so the effort is minimal. My only hurdle right now is the Apple Developer Program fee!
@atelier-fan.comReposted by @atpassport.net【ATelier 改善報告 9/26】
・@passport でログインできるように
・Blogger（Google Takeout）から引っ越しできるように
・取り込みで本文の最初の画像もその位置に残るように
・画像の縦横が 5 種類に。高精細でも選べます
・高精細のGPT Image 2を新しいモデルに
・長いプロンプトを送れるように
・貼り付けた文の改行が消える不具合を修正
・ハッシュタグを空白区切りで続けて入力できるように
@atpassport.netThe experience varies by browser, and I can see how that’s confusing. With Chrome (no extension needed) or Firefox with the extension, you can pick your account without being redirected to @passport.
bsky.app/profile/atpa...
@atpassport.netIt turned out to be the same header issue, so the assertion is working perfectly now!
@postgame.atReposted by @atpassport.net✨ A handful of updates as we head into the weekend: - You can add extra details to the games in your library like platform, format, a custom note, and more - Logged out users will see a new landing page that gives an overview of the site and features - You can log in with @atpassport.net Enjoy!
@atpassport.netI actually just tested declarativeNetRequest on Firefox MV3, and it successfully injected the header and returned 200 OK!
@atpassport.netAh, makes sense! I'll definitely give that idea a try. Thanks!
@atpassport.net- Assertion: The extension doesn't call the server at all—it just creates the token locally and returns it. So yes, Chrome FedCM and Firefox extension currently hit completely different paths due to prototyping debt.
@atpassport.netTo answer directly: it's actually both! - Accounts: The extension calls an internal API (/api/user/handles) instead of /api/fedcm/accounts, because extension fetch() cannot set native FedCM headers like Sec-Fetch-Dest: webidentity.
@atpassport.netSo I'm planning to do a refactor on my end first to align everything with the Accounts Push specification. Once that foundation is in place, I’d absolutely love your contributions and feedback! I'll keep you posted as I make progress.
@atpassport.netI relied a bit too heavily on AI for the quick prototype, so while it successfully intercepts navigator.credentials.get, behind the scenes it’s cutting corners and not actually speaking the proper FedCM API/endpoints at all. To put it bluntly, it's kind of a mess!
@atpassport.netThat’s awesome to hear, and yes, it’s completely open source! You can find the code here:
github.com/usounds/atpa...
Full disclosure, though: the current implementation is honestly in pretty rough shape right now! 😅
@rocksky.appReposted by @atpassport.netYou can now sign in to @rocksky.app with @atpassport.net
@atpassport.netDo you mean a browser extension that polyfills this API so people can test it out? If so, definitely! I'm actually building a Firefox extension right now, so that sounds like a super fun experiment 🙌
@atpassport.netYes, I'm intercepting FedCM for atpassport.net. You can get the extension below: 👇
addons.mozilla.org/en-US/firefo...
@holybea.blueReposted by @atpassport.netTOKIMEKIをatpassportに対応してみた！
@atpassport.netThe @passport Firefox extension has been updated to support in-app handle input assist! Under the hood, this is powered by FedCM. Please note that for this feature to work, individual apps will need to add support for @passport's FedCM. 🛠️ Developers, we'd love for you to check it out!
@atpassport.net@passport のFirefox拡張機能がアップデート！ アプリ内での「ハンドル入力アシスト」に対応しました✨ 内部的にはFedCMの仕組みで実現しています。そのため、この機能を利用するには各クライアントアプリ側でも @passport のFedCM対応が必要になります🛠️ 開発者の皆さま、ぜひ対応をご検討ください！
@studynext.appReposted by @atpassport.net@atpassport.net を使ったログインに対応しました!
@atpassport.netSpot on. It’s definitely different from the decentralized approach you all are building, but yes, I'm just utilizing the Fields API in a centralized way for this experiment.
