I would ask for more consistent access to typescript internals.
(also in vscode, btw!)
it feels like adding plugins (for example, for .vue support!) is needlessly complicated, particularly when native <> js boundaries are concerned with tsgo
roe.dev/ama
#ama
in a sense!
I no longer do external consultancy, as I work at @Vercel, but I'm happy to take a brief look or provide a sanity check if I can 🙏
roe.dev/ama
#ama
by this, I mean:
I've been using a cms for a long time to store things like:
⚪ #ama questions people ask
⚪ talks I'm planning to give (or have given!)
⚪ my current location (which I track and expose publicly 👀)
...and so on
👉 but atproto means your pds = your data
so … why not use it as a cms?
there are some new lexicons in my pds
@nicr.dev has been verified by @danielroe.dev. ✅
it’s a good thing bluesky doesn’t render
<danielroe.dev is typing>
underneath posts i’m replying to
if you'd like to do something like this for yourself, let me know 🙏
I'm thinking of building an orm/cms library so you can easily use your own pds as a cms for any project