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.

Didn't realize the default quickslice railway template was broken 😭, but it should be fixed now if you trying it out. Also don't forget to redeploy after generating a public domain or the OAuth callback doesn't get registered properly.

Just submitted a talk along the lines of "AT Protocol on BEAM" for the Vancouver Code Beam. Gotta spread the word!

@j4ck.xyz basically recreated @grain.social in very little time with the quickslice mcp #getsliced

in case you missed it, @zzstoatzz.io's status.zzstoatzz.io now runs on a quickslice zzstoatzz-quickslice-status.fly.dev

Tools is exactly what I’m trying to get at with @slices.network but for AT. I’m thinking about spinning up tools.slices.network that showcases one off mini apps built on different quickslices. Form to create a @grain.social gallery, teal fm feed, tangled search, etc.

quickslice is like tap but instead you’re at the bar with At The Drive-In on full blast

very awesome write up on quickslice, check it out!

If want to play around with a @teal.fm GraphQL API, you can check out the quickslice instance here fmteal.slices.network. The dashboard for a quickslice instance shows a few simple stats about the AppView and the latest jetstream activity.

Now that there's quickslice, the hosted slices.network experience in it's current form will go away soon. Probably going to turn it into more of a landing page for slices related resources/content but haven't figured all that out yet. Trying to reduce the number of things I need to maintain 😵‍💫

If you give quickslice a try let me know how it goes. Documentation could be improved especially around setting the domain authority (ie social.grain), importing a lexicon set, and how primary vs external collections work. At some point you have to press the ship button and this is where it's at!

My crazy idea to cram all of the AT Protocol into a single deployable container. Works with SQLite, Postgres and potentially more data stores in the future. Steps are literally deploy container -> import your lexicons -> backfill -> build your app with the GraphQL APIs. quickslice.slices.network

I've been playing around with this in an astro app and it's pretty nice! Relay has always had the best dx for @graphql.org and it's nice to be able to use the compiler without going all in. The graphql codegen scene for ts has been all over the place and this was desperately needed.

Can confirm, I've been experimenting a lot with AT dev on BEAM using @gleam.run. I've been working on some lower level AT utilities like a jetstream consumer and a lexicon validation library, and also a total rewrite of @slices.network. Felt daunting a few months ago but making a lot of progress.

got sidetracked and created this package for @gleam.run to render open graph images from lustre elements inspired by takumi/satori. uses a NIF via rustler to bind to takumi but if there is a better solution native to erlang, let me know! github.com/bigmoves/og_...

Working on an mcp integration with @slices.network so you can just ask the LLM questions about your AppView ie what lexicons it indexes, what queries are available, and even the ability to execute queries via GraphQL. I asked claude to give me a yearly wrapped of plays for @baileytownsend.dev

@teal.fm noticing tracks submitted with multi-scrobbler include duration as null. The fm.teal.alpha.feed.play lexicon doesn't specify duration as nullable so technically validation should fail on these. Not sure if that data isn't available for the tack or an issue with multi-scrobbler.

workshop idea submitted for #ATmostphereConf ✨

gleam tangled takeover happening now ⭐️ #atproto

fun new #atproto app, congrats @danabra.mov for launching!

it's almost 2026 and claude still thinks it's 2024

Also want to say thanks to Bluesky for generously supporting @slices.network with some grant funding ☺️ Working on a containerized auto-indexing “AppView in a box” sort of thing I’m hoping will make it easier to get started with #atproto. More updates soon!

@tangled.org spotted, knots mentioned #eurosky

appreciate @gleam.run's dedication to semantic versioning. just release your v1 already k thanks

classic

getting ready for @eurosky.social next week ✨ @slices.network @grain.social #atprotocol

👀 didn't know you could use details/summary in readmes til now, also @plyr.fm is v cool