stream.place down?

@teal.fm if you ever do a search input for plays "Thee Oh Sees" is a pretty good test artist to see if you return both osees and the oh sees and thee oh sees

new @tangled.org account switcher is so nice

atproto engineer showing up in job listings when?

teal-relay-production.up.railway.app got the graphql teal fm demo back up and running but with duckdb + lex-gql had to go back to drawing board because there's over 600,000 scrobbles now and queries were slow 🫨

@zzstoatzz.io and I were talking earlier about setting up some kind of regular hang for atproto hackers and the like. Let us know if you’re interested! Could be a place to share a new project, talk about patterns/pain points, etc

welll shoot guess I should use duckdb

on a kick to simplify and extracted my ideas for what a lexicon graphql mapping looks like from quickslice into a separate standalone .js library. very poc stage with some stuff likely to change but i've got a basic statusphere example working with tap. tangled.org/chadtmiller....

tapping in

making progress on pds.js tangled.org/chadtmiller...., there's something to be said about starting with the simplest possible implementation and working your way up from there. the core logic, at least, is zero dep, with a hexagonal architecture that allows different functionality via ports/adapters

is the atproto based npm alternative still alive?

we should just commit our prompts, that’s the real code these days

hear me out, a PDS proxy/mirror that copies my data to all the different PDS implementations and allows me log in with all the available auth patterns

what if i put a pds on pdsjs.dev so if you mistype pdsls.dev you get a pds.js pds.

added this lil scopes table and better scopes support to pds.js we're at 5,324 lines and ~27.5 KB gzipped deployed

a cool feature of the comment model in @grain.social is being able to comment on a particular photo in a gallery, something a lot of other social apps don’t have @goose.art 📸

If anyone wants to try the next version of @grain.social, kind of just letting it simmer on next.grain.social for a bit. it's basically peak quickslice, all views are hydrated via graphql (favs, comments, follows, etc). no complicated lexicon view defs. notifications, create moderation reports, etc

pds.js oauth coming in hot bringing back the single .js zero deps besides cloudflare worker stuff still ironing out stuff (and very basic scopes support) but it works on @pdsls.dev

pretty awesome, pds.js already getting used for hacking on new patterns

things you say when working on a PDS

anyone working on a custom PDS have trouble with the bsky cdn loading blobs? @mk.gg are you able to create a bsky post with images yet with your custom pds and see them load correctly?

i think i waited too long to give cloudflare workers/R2 a try, the tooling anyways is really nice to work with, and easy to mock locally

serious question: is anyone hiring? open to connecting. 10+ years of full stack experience plus 1 year of unhinged ai/atproto hacking

it would be cool to do a gallery show with all the different PDS homepages. #atmosphereconf idea

what have i done

inspired by cirrus, had this idea the other day that maybe you could do a plain js PDS with zero dependencies (i don't want all the hono, third party atproto lib stuff). a few thousand lines of js later and here were are! bsky.app/profile/chad...

pushed a change to quickslice-client-js this morning and now you can be logged into multiple apps on the same domain ie my tools.slices.network setup all scoped to their respective oauth scopes. pretty rad. build your own atproto app universe with quickslice(s).

was listening to KXLU FM on radio.garden today and really wanted to scrobble some tracks to @teal.fm so I made this new tooooool tools.slices.network/teal-scrobble

really enjoying tools.slices.network experiments. write directly to an html file, no build tools, deploy to CDN. it's great for lexicon exploration because you don't have to commit to a domain, just use your subdomain. in a few hours i made a fully functional AT bug app! tangled.org/slices.netwo...

there's already been some exploration in this space with constellation backed components, but playing around with the same idea for quickslice based web-components. as long as you have an instance deployed with the correct domain authority/namespace and lexicon set, anyone can host their own.

wow this worked?? quickslice is in the atmosphere now I guess @atcr.io

really need a jsDelivr for @tangled.org

@baileytownsend.dev found an interesting problem! I was noticing that your profile doesn't sync in quickslice based on the current app.bsky.actor.profile lexicon description constraints. popped your record into tools.slices.network/lexicon-validator and sure enough it fails! lol

made this while I was drinking coffee this morning tools.slices.network/tangled-repos originally made this a while back with some earlier versions of slices but moving it's proper home in the tools library

exactly

I pushed out a fix for this and it seems to be working so far. If you’re running a quickslice instance just redeploy or set your version to 0.17.4. Check the bug tracker for the latest updates 🐛 tools.slices.network/bugs. You can now leave comments/attachments as well.

my take on the internet handle scandal is that we need more atproto apps! appviews are complicated but they don’t have to be. this is sounding like a slices ad. have you tried slices?

quickslicers! tracking this issue where you get an error if you try to create a mutation after being logged in for a while. hopefully have a fix ready soon tools.slices.network/bugs?ns=netw...

i feel like it's hard to talk about the elephant in the room sometimes (LLMs, claude code, etc). i've been using it pretty heavily this past year. i put in my time writing code manually. life is short. ai tools allow me experiment and build the things i want to build faster so i can do other stuff

starting to feel the same way about writing frontend apps, if you're going to vibe why do it in an html file? news.ycombinator.com/item?id=4620...

you might think I'm crazy but I can't explain how quickly you can build an #atproto app with quickslice and graphql. no codegen, no custom indexes, no view defs, just join and ship!

playing around with cross-lexicon interactions outside of bluesky, create a tangled issue from a 🐛 bug. You can try it now 👉 tools.slices.network/bugs You can imagine an #atproto tool like linear interacting with all kinds of apps in the AT ecosystem.

@tangled.org is there a way to link to a tangled issue via rkey? The incremental counts makes it hard to link from externally ie "https://tangled.org/slices.network/tools/issues/2" vs "https://tangled.org/slices.network/tools/issues/3ma7bagaxtv22" because that number isn't stored anywhere.

it's a two tool kinda day 🔧 : tools.slices.network/bugs 🐛 a bug tracker for the atmosphere. i literally went from lexicon design to ship in about 2 hours using quickslice. feel free to report bugs for atmosphere apps! the idea is that it's a place outside of code land for anyone to use

new tool drop: tools.slices.network/lexicon-vali... a lexicon validator, created with the same validation library that runs in quickslice (gleam compiles to erlang and js ✨) great for debugging schema/record validation issues or even for learning how lexicon validation works!

so much fun deploying html straight to a CDN and see it live instantly. easy to forget how simple the internet is sometimes when you're buried in build tools and deployment pipelines

made this teal.fm plays feed in a few minutes with quickslice mcp via fmteal.slices.network tools.slices.network/teal-plays

just published the first slices tool! obviously it's gonna be statusphere but more soon. excited to tinker and build on a network of slices via quickslice in the Atmosphere (without React)! tools.slices.network/statusphere tangled.org/slices.netwo...

the best part of quickslice imo is the integrated oauth proxy and the ability to register oauth clients. it frees you up to deploy your quickslice in one place and your frontend apps anywhere and not worry about the AT metadata.json. you can also have multiple sessions across multiple clients

I feel like I'm seeing more design systems adopt web components now? Is that accurate? I wish there was a solid web component alternative to projects like base-ui.com or shadcn.