haha 😄 all good. thanks for the PRs will try to take a look later today

I'd want the option to never open a new tab lol. just one tab per pane

interesting, i'll take a look into this. this is a PDS you run right? not something like selfhosted.social?

thanks! was this earlier today? if so try upgrading to 0.1.12, i just cut a release that should fix the issue with non bsky PDS

should work now with custom PDS on 0.1.12

Yeah pckt may be a good default. A standard/default defined by standard.site would be useful

Yeah there's definitely room for that. It would just depend which schema the app serving/rendering the publication is expecting. I haven't actually looked around for a "standard" one. Did you have any in mind?

yeah might be mostly doable already. I haven't tried it because i don't have any custom pubs myself

But if its a standard.site.publication record in your PDS, it should pull it in as an option. It would publish unformatted text, but could be changed to publish generic markdown for the rich content

this is a direction I'm looking into with bsky.app/profile/did:...

ahh, I see a broke auth for non bsky PDSs in a recent change. will fix that later today, thanks for the heads up 🙂

working towards this with github.com/treethought/...

❤️ lemme know if you have any issues or feedback!

bsky.social is the pds entryway for PDS hosted by bluesky. It's basically a gateway or proxy to individual PDS's docs.bsky.app/docs/advance...

let me know if you try it out and have any feedback! I have some bigger updates coming to it as well within a few days 🙂

wow had not heard of this one. loving it so far, thanks for the share!

its not necessarily that you can make every chat msg a bsky post (but you could make a UI to mimic that). It's that chat msgs and posts and any other "record" used in an ATproto app is just a public item in your PDS. apps can freely chose which types (lexicons) to use when talking to your PDS

dude, yes this is awesome!

wow. top notch door