oh, and you'll see I have website card embeds, too. rich text and tags are forthcoming. follow me if you'd liek to see more experiments. I'm enjoying the protocol, and have lots of publication plans in the future

okay, I could go into much more detail if I felt like it... but really I just wanted to send out the full demonstration, recursive screenshots and all

messages seemed straightforward at first... until I wrestled with the union types on the in the lexicon. luckily, by composing cleanly and accepting 'any' on my client's create record endpoint, I could use a generic constraint to specify the embeds

from a technical POV, the 🧵 must start with a valid session token, which will be used in all the requests to the api. I embed the Session in a Client, which will request a new token when necessary (eg expiration)

moreover I can, using the same tools I'm building locally, segue between long-form and short-form composition without any change in focus. I suspect many people already do this, composing in text then pasting snippets in posts, but I never got the hang of it personally

the cool thing about doing a series of posts this way from a static file, rather than from a client app, is that I'm able to put more *effort* into the writing process. By composing like I would any other document, I can hone the writing better for my purpose

the key constraint here is that I'm writing the tool using the Go standard library only. No third party dependencies. This allows me to work with atproto directly as a protocol rather than as an SDK

okay, I could go into much more detail if I felt like it... but really I just wanted to send out the full demonstration, recursive screenshots and all

messages seemed straightforward at first... until I wrestled with the union types on the in the lexicon. luckily, by composing cleanly and accepting 'any' on my client's create record endpoint, I could use a generic constraint to specify the embeds

from a technical POV, the 🧵 must start with a valid session token, which will be used in all the requests to the api. I embed the Session in a Client, which will request a new token when necessary (eg expiration)

moreover I can, using the same tools I'm building locally, segue between long-form and short-form composition without any change in focus. I suspect many people already do this, composing in text then pasting snippets in posts, but I never got the hang of it personally

the cool thing about doing a series of posts this way from a static file, rather than from a client app, is that I'm able to put more *effort* into the writing process. By composing like I would any other document, I can hone the writing better for my purpose

the key constraint here is that I'm writing the tool using the Go standard library only. No third party dependencies. This allows me to work with atproto directly as a protocol rather than as an SDK

also using website embeds

now with image attachments

and here's the second reply

here's the first reply