Ty for the shout out!
Thanks for giving it a try!
The lexicon requirement is built into the XRPC library, but I'll fork it and make some modifications.
Shooting for a release this week which will include publishing request collections to your PDS and importing other ppl collections.
I'll try to fit that mod in!
Thanks! It went well.
Advice fwiw
- Don't over prepare
- practice fundamentals as much or more than DSA
- Practice problem solving skills and verbalize EVERYTHING don't memorize shit
- Cramming does NOTHING just do a solid focused hour a day CONSISTENTLY and DO NOT STOP
- TAKE BREAKS
I have to take a technical coding interview in a few minutes.
I've been in the industry for 10+ years, and I've built companies from 0 - acquisition, but I still get nervous during these things.
I will do my best, but I won't fault myself if I don't make it.
All I can do is improve every day.
Importing and exporting XRPC request collections is complete ✅
Only remaining work for the next release is some UI stuff #atproto
DID web will have to do though I'd argue this issue is more to do with app developers and libraries only supporting "blessed" did methods.
I want many PLC instances but that would create a mastodon type situation #atproto
It's here! ATStudio 2.3.0 💫
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
I published the first XRPC request collection just now‼️
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
Great! I'll add did web support for importing.
Super quality work 👍
It's so crazy, I was looking at the glama page for the atproto docs MCP earlier today. I didn't realize it was your work!
I'll experiment with it soon for sure 👏
ATStudio is your new XRPC client 👀
It's like paw/postman, but for #atproto
Get started now:
at-studio.dev
congrats on the new release
XRPC request collections are SUPER easy with ATStudio ♻️
try the beta: at-studio.dev
#atprotocol #atproto
Release day bros 👋🍻
Additional Updates:
SDK mode has been removed to reduce app complexity and development overhead. You should use XRPC request collections in place of SDK calls.
The UI has received upgrades including a cleaned up XRPC interface and additional panel view controls.
Request Collections:
Create XRPC request collections to easily reuse your favorite #atprotocol features and apps.
You can expect to see multiple forms of sharing collections in the next update.
Request history:
Your recent request history will now be saved and available in the new History sidebar. Both errors and successful requests will be stored.
Request Tabs:
ATStudio will now remember your tabs between page load, so you can pick up right where you left off!
It's here! ATStudio 2.3.0 💫
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
Shameless plug; if you need to easily make XRPC requests you can use this tool I'm working on:
at-studio.dev
Many features in the works!
Quickly approaching rc for ATStudio 2.3.0 #atproto
#atprotocol is much more than a micro blogging platform, but it's up to developers and entrepreneurs to extend the user base with novel products and bridges to/from existing systems and platforms.
I think the next ATStudio update will make people really excited #atproto 🫶
Damn y'all are blowing up my notifications, but I'm out in the streets today ✊
Tysm for the support 💕
Be safe out there! #resist
The beauty of mixing and matching Lexicon sources is that you can test new feature sets by swapping sources.
Imports also take priority by order of import, so you can "override" imports from other sources 🧠
Utilizing unpublished @stream.place features via a combination of imported apps + custom Lexicons 💥🔓🔧
Dude! The support is massively appreciated 🙏👍🤙
Side note; I noticed some Lexicons like `place.stream.live.getLiveUsers` aren't published, so they weren't importing.
Do you plan on publishing them for service discovery?
Thanks again!
Custom Lexicon Import:
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.
PDS Import:
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.
