Post

getting a bsky app to work with granular permissions is a lot of trial and error - `app.bsky.authFullApp` doesnt include chat and cant be set to `aud=*` - `chat.bsky.authFullChatClient` in the scope builder has the wrong `aud` - video upload doesnt work (part of `app.bsky.authFullApp` but wrong aud)

12/6/26, 3:54 pm0 reposts20 likes

xan

@xan.lol

13 June

the aud situation is very annoying github.com/bluesky-soci...

github.comInclude scope doesn't allow wildcard audience (aud=*) · Issue #4490 · bluesky-social/atprotoDescribe the bug When using a permission set for example include:app.bsky.authFullApp in client metadata with aud=* it gets ignored. To Reproduce Steps to reproduce the behavior: Have a client that...

flo-bit

@flo-bit.dev

13 June

indeed, i left a comment, without that `aud=*` i dont really see granular permissions working out for a bsky fork/app

Jim Ray

@jimray.bsky.team

12 June

Mind opening an issue and tagging lil ole me? github.com/bluesky-soci...

github.comIssues · bluesky-social/atproto-websiteContribute to bluesky-social/atproto-website development by creating an account on GitHub.

flo-bit

@flo-bit.dev

12 June

...probably more to come thats just after an hour or two of testing

flo-bit

@flo-bit.dev

12 June

@jimray.bsky.team a feature request for the scope builder: if i check e.g. `app.bsky.authFullApp` it'd be great if the other permission sets that i dont need anymore because they're already included could be greyed out or smth (also a permission set for video would be great)

Tamme Schichler

@tamme.schichler.de

12 June

I don't know if this is related to my recent comments, but: Very appreciated that you're looking into this. I'm aware that the Bluesky permission sets aren't exactly granular, but looking forward to seeing what'll work.