What have we done? We used βaskβ as a noun so often in the past 15 years that LLMs think itβs OK.
What have we done? We used βaskβ as a noun so often in the past 15 years that LLMs think itβs OK.
Cursed video game idea. The council of brainworms.
As I age, I get more and more parenthetical in my written communication (and therefore more verbose).
I find myself annoying. π€
Congrats! I love to see this kind of change (in general; not specifically for you). I'd love to chat with you in the new capacity at some point. I'm building some weird stuff I think you'll like :) Will you be at AtmosphereConf?
atproto lexicons are basically a perfect match for vibecoding. sonnet 4.6 is surprisingly solid at handling the record structure and blob logic once you dump the schema in
atproto + the create post permission-set + image blobs + your own freq include for creating relevant records
lexicon.garden/scope-builde...
Also as a musician very interested to see what you're working on.
@bmann.ca FYI I just deployed the ability to do AT proto auth from a legacy irc client on freeq. /login bmann.ca
Doing it in a decoupled way so you can have AT proto DID as the anchor identity and add 3rd party identities without changing the server software. github, google, SAML, etc
Thanks!
AT proto people, given that I want to be able to 1) log in via bluesky 2) post media to the repo as the place e.g. images in chat get uploaded and rendered from and 3) potentially cross-post to bluesky to/from Freeq/irc, what's the right way to think about scoping permissions?
The only diagrams I speak are dots+lines & byte layouts
three replies from "Endless Screaming" to me and Joshua Erlich. the posts are "AAAAAHHHH"s of varying lengths
finally, a streamlined social media experience
It may be that we in fact regenerate entire applications much like infrastructure-as-code - see @chadfowler.com's writing
Interesting post. It reminds me a bit of notation.dev which essentially had a quasi runtime, like how you describe, to provide type constraints over the infra layer. The one question I have is how seperable architecture and implementation are in practice.
Thank you so much!
lol
Thank you! Safe travels (wow) and looking forward to hearing from you!
I haven't but this is a cool direction. Would love to see your take on this.
I've been going broad, fast, and messy so far just to get something working and semi-compelling to use. It started as a lark and took on a life of its own.
Do you mean because BlueSky is centralized and that's where the DID comes from?
There's a Tauri build too. And don't miss the client SDK.
Yes! There are iOS and android apps in the repo also. Everything needs work
What do you think is the best way to do it? I enabled things like cross-posting with Bluesky + media uploads to the repo for e.g. dragging images into a channel.
It does this because it uses this for media storage (e.g. /media command). Could make it optional or I might just be ignorant of a better way?
I was on IRC before I was on the web. Bringing ATproto to IRC is amazing.
Hmmβ¦.bug
The 90s are so back. Showing the kids what they missed
You canβt do AT auth with a legacy client though I know now how I can enable that
Freeq'ing awesome. π»
You canβt do AT auth with a legacy client though I know now how I can enable that