The upcoming release of ATStudio will support creating and sharing collections across the #atprotocol by storing them in your PDS 💽
Easy access to apps and bespoke toolkits will be a collective social effort 🌎♻️ #atproto
The upcoming release of ATStudio will support creating and sharing collections across the #atprotocol by storing them in your PDS 💽
Easy access to apps and bespoke toolkits will be a collective social effort 🌎♻️ #atproto
try the beta: at-studio.dev
#atprotocol #atproto
try the beta: at-studio.dev
#atprotocol #atproto
The storage update 💼
- Save XRPC requests in request collections
- Save recent history + reload past requests
- Persist request tabs between page load
Try the beta: at-studio.dev
#atprotocol #atproto #bsky #webdev
The storage update 💼
- Save XRPC requests in request collections
- Save recent history + reload past requests
- Persist request tabs between page load
Try the beta: at-studio.dev
#atprotocol #atproto #bsky #webdev
You can quickly import custom and unpublished Lexicons using the new file import option.
Of course, you can always provide bespoke Lexicons by hand using the `lexicons` input parameter.
You can quickly import custom and unpublished Lexicons using the new file import option.
Of course, you can always provide bespoke Lexicons by hand using the `lexicons` input parameter.
You may want to interface with an application or feature set that doesn't have direct integration with ATStudio.
The PDS import option allows you to import any Lexicon records that are published by a target PDS.
You may want to interface with an application or feature set that doesn't have direct integration with ATStudio.
The PDS import option allows you to import any Lexicon records that are published by a target PDS.
Use the app import dropdown to source Lexicons published by an app.
Your studio client will receive up-to-date Lexicon data directly from the source.
Initial direct integrations include @bsky.app @lexicon.community @statusphere.xyz @stream.place
Use the app import dropdown to source Lexicons published by an app.
Your studio client will receive up-to-date Lexicon data directly from the source.
Initial direct integrations include @bsky.app @lexicon.community @statusphere.xyz @stream.place
Importing Lexicons just got WAY easier.
Source schemas from applications, PDSes, or bring your own custom Lexicons.
Try the beta: at-studio.dev
#atprotocol #atproto #bsky #webdev
Importing Lexicons just got WAY easier.
Source schemas from applications, PDSes, or bring your own custom Lexicons.
Try the beta: at-studio.dev
#atprotocol #atproto #bsky #webdev
Now with unauthenticated user support.
This move should help lower the barrier of entry for developers who are new to #atproto 🌿🧑💻
try the beta: at-studio.dev
#atprotocol #bsky #webdev
Now with unauthenticated user support.
This move should help lower the barrier of entry for developers who are new to #atproto 🌿🧑💻
try the beta: at-studio.dev
#atprotocol #bsky #webdev
@stream.place is up next!
@stream.place is up next!
2.0 brings the ability to use ATStudio with your own self hosted Personal Data Server 📁🔐
Testing has been done with a self hosted PDS without issue, but please, come along and help experiment with this new feature.
2.0 brings the ability to use ATStudio with your own self hosted Personal Data Server 📁🔐
Testing has been done with a self hosted PDS without issue, but please, come along and help experiment with this new feature.
In addition to SDK method calls, you can now make raw XRPC requests using ATStudio.
Modify host/NSID, customize parameters, attach OAuth session, and bring your own custom Lexicons.
You can also import Lexicons from popular apps! @bsky.app is supported but more support is on the way.
In addition to SDK method calls, you can now make raw XRPC requests using ATStudio.
Modify host/NSID, customize parameters, attach OAuth session, and bring your own custom Lexicons.
You can also import Lexicons from popular apps! @bsky.app is supported but more support is on the way.
Try the beta: at-studio.dev
Execute XRPC and SDK requests on #atproto. It's like Postman/Paw, but for your favorite protocol.
#atprotocol #bsky #webdev 🧵👇
Try the beta: at-studio.dev
Execute XRPC and SDK requests on #atproto. It's like Postman/Paw, but for your favorite protocol.
#atprotocol #bsky #webdev 🧵👇
Text formatting and styling has been improved for better readability, and nested data is properly parsed for better usability.
Check out the before/after 👇
Text formatting and styling has been improved for better readability, and nested data is properly parsed for better usability.
Check out the before/after 👇
tooltipdev.github.io/at-studio/
"bsky OAuth Playground" is now "@ATStudio"
Changelog:
- Rename application/repo
- UI improvements/fixes
- Improve "About" section
- devx QoL
Hotfixes:
- Fix issue with data table parsing
#atprotocol #atproto
tooltipdev.github.io/at-studio/
"bsky OAuth Playground" is now "@ATStudio"
Changelog:
- Rename application/repo
- UI improvements/fixes
- Improve "About" section
- devx QoL
Hotfixes:
- Fix issue with data table parsing
#atprotocol #atproto
tooltipdev.github.io/bsky-oauth-p...
Changelog:
- local devx overhaul
- deployment QoL improvements
Hotfixes:
- Fr is no longer the default locale
#atproto #atprotocol #bsky #webdev
tooltipdev.github.io/bsky-oauth-p...
Changelog:
- local devx overhaul
- deployment QoL improvements
Hotfixes:
- Fr is no longer the default locale
#atproto #atprotocol #bsky #webdev
This tool allows you to quickly interface with the protocol to evaluate potential code paths, or to debug existing flows.
Almost all SDK methods are currently supported, and raw Lexicon support is on the way.
Thanks for reading along!
This tool allows you to quickly interface with the protocol to evaluate potential code paths, or to debug existing flows.
Almost all SDK methods are currently supported, and raw Lexicon support is on the way.
Thanks for reading along!
Select the `getFeed` SDK method and supply the feed `uri` value.
Select the `getFeed` SDK method and supply the feed `uri` value.
You will want to gather the `uri` of the feed you'd like to read from.
We will use the `getSuggestedFeeds` SDK method to gather a list of feeds to read posts from, but you can bring your own `uri` value.
You will want to gather the `uri` of the feed you'd like to read from.
We will use the `getSuggestedFeeds` SDK method to gather a list of feeds to read posts from, but you can bring your own `uri` value.
At least it gives us application level ability to check for "expected" record types.
Not sure if this is desirable; we could argue that Lexicon SHOULD be extensible and fully interoperable.
At least it gives us application level ability to check for "expected" record types.
Not sure if this is desirable; we could argue that Lexicon SHOULD be extensible and fully interoperable.
- Runtime validation for #ATProtocol Lexicons
- Convert Lexicon JSON to Zod schemas
- Validate Lexicon input, output, records, etc
- Extensible and customizable
www.npmjs.com/package/lexi...
github.com/tooltipdev/l...
#atproto #bsky #webdev
- Runtime validation for #ATProtocol Lexicons
- Convert Lexicon JSON to Zod schemas
- Validate Lexicon input, output, records, etc
- Extensible and customizable
www.npmjs.com/package/lexi...
github.com/tooltipdev/l...
#atproto #bsky #webdev
tooltipdev.github.io/bsky-oauth-p...
This client-side app lets you easily interact with the ATProtocol via its browser SDK.
Authenticate with your @bsky.app account via OAuth to begin experimenting with the protocol.
#bsky #atprotocol #atproto #webdev #oauth
tooltipdev.github.io/bsky-oauth-p...
This client-side app lets you easily interact with the ATProtocol via its browser SDK.
Authenticate with your @bsky.app account via OAuth to begin experimenting with the protocol.
#bsky #atprotocol #atproto #webdev #oauth