moshyfawn

moshyfawn

@moshyfawn.dev

Software engineer with quirks. Give me all the new shiny tech and I'll have all the fuel needed to create any project! Building @atplay.blue

340 followers488 following680 posts

moshyfawn
@moshyfawn.dev

Has anyone experimenting with permissioned spaces alpha run into putRecord silently updating the record without returning InvalidSwap? space.putRecord seems to behave different between updating a public and space records

github.comHow to do a conditional write in spaces? · bluesky-social atproto · Discussion #5432Im trying out spaces alpha with a simple sync engine for notes that can be updated from more than one device. I currently have it working on the public API where a conditional write with com.atprot...
moshyfawn
@moshyfawn.dev

The hosted alpha PDS might not want to expose the app password flow, but you can’t stop me from hitting the xrpc endpoint directly 🤪

moshyfawn
@moshyfawn.dev

With ats:// out of scope (which is a better layered design for this, I believe), are there any ongoing efforts one could follow today? It is kinda cool that running your own PDS does meaningfully negate the need for the encryption layer already due to trust boundaries.

daniel holmgren 🫠@dholms.at

so excited to get this in folks' hands and to see what people build with it! it’s been a lot of work getting here & i'm proud of where it's at check it out, bang on it, break it, see where it doesn't work. let's make sure this is something we're all excited about & can take pride in building on

atproto.comThe Atproto Spaces Alpha is LiveAtproto Spaces, formerly known as “the permissioned data protocol,” is a new extension to atproto that enables non-public data. The alpha is now officially open. Here’s how to develop with it and what to expect as we work towards the full release.
View full thread
moshyfawn
@moshyfawn.dev

I’m happy with how OAuth is supported (even on mobile albeit with a wackier UX than desktop). The app password option is also there (see the ™️ comment above for more context).

moshyfawn
@moshyfawn.dev

I might write up a post about it when I’m back. But for now, most of the relevant links are in the plugin’s listing, so feel free to snoop around and let me know what you think 😊

moshyfawn
@moshyfawn.dev

It supports both private and public notes via opaque records and @standard.site publications respectively. And yea, while opaque records are frowned upon, it’s secure enough for me and “you don’t fucking control me”™️

moshyfawn
@moshyfawn.dev

Your Fable can generate entire functioning video games in one prompt. My Fable can't even generate a release date. We are not the same.

moshyfawn
@moshyfawn.dev

When Trezy is #LookingForWork - grab ‘im! Or consider sponsoring his open source work and the tremendous effort he’s put into the future of decentralized gaming and its tooling 🙏

Trezy@trezy.codes

Hey y'all, I'm looking for some work to bridge the gap while I continue working on @cartridge.dev and @happyview.dev. If you have contract work for #atproto projects (planning, code, architecture), I'd be delighted to help. DM me with details. #atproto #OpenToWork #LookingForWork

moshyfawn
@moshyfawn.dev

@github.com quietly working on stacked PRs **in private** while the rest of the system feels like it’s in shambles wasn’t on my bingo card 🤔 The site itself is a lovely set of @astro.build Starlight pages too - more from that team, please!

moshyfawn
@moshyfawn.dev

I made the process of getting to #AtmosphereConf so needlessly stressful by forgetting I’m flying a day earlier than I thought. Had to scramble to get a few things and plans in order but looks like im all set to land in Vancouver tonight 😮‍💨

moshyfawn
@moshyfawn.dev

Found this room(y) on the first floor of the residence I’m staying at. Now I know I’m in the right place 😊 5am EDT - I’m cooked but happy I made it!

moshyfawn
@moshyfawn.dev

@youandme.at is such a great idea! Already got mine installed as a PWA on my phone - gotta catch 'em all ✨ One thing I ran into: can't scan the dark mode QR code across a few different lighting conditions, whether from a laptop screen or my phone.

moshyfawn
@moshyfawn.dev

That's so neat - I've been seeing the discourse around automated PDS activity management for spam bots, and I just got "targeted" myself. By the time I went to report and block it, the operation failed because it had already been blocked and deleted. Super neat 🚀

moshyfawn
@moshyfawn.dev

When something like npmx.dev that genuinely touches and potentially drastically changes so many areas of a developer’s life, I always wonder how much the ripples of celebration touch the day to day lives of “blue collar workers”, devs and execs outside of the community.

moshyfawn
@moshyfawn.dev

Do you get taken aback by an influx of otherwise dull LinkedIn posts talking about this new thing. Do workspaces update their onboarding docs with it as the starting point? Does your mentor introduce you to it as your first packages browser?

moshyfawn
@moshyfawn.dev

I remember my ecosystem intro months (weirdly) fondly and most of what I’ve learned at the time was quite boring, battle tested. I wonder how it is these days, with AI, thoughtful and shiny solutions.. I felt overwhelmed at the time; is today’s landscape easier or harder to navigate?

moshyfawn
@moshyfawn.dev

npmx.dev is a much needed breath of fresh air in the packages registry space, baked by a battle tested set of maintainers and an incredibly passionate community along side of atproto builders. If you like to bet on alpha software from time to time - npmx has all the green flags you need 😉

npmx.devnpmx - Package Browser for the npm Registrya fast, modern browser for the npm registry. Search, browse, and explore packages with a modern interface.
npmx@npmx.dev

npmx is now in alpha: this is our story, as told by our team and friends

npmx.devAnnouncing npmx: a fast, modern browser for the npm registryToday we're releasing the alpha of npmx.dev – a fast, modern browser for the npm registry, built in the open by a growing community.
moshyfawn
@moshyfawn.dev

Welp, I’ve circled back to ElysiaJS - there’s still nothing else that integrates as fully with Bun. I ended up fixing my main issue with Tailwind and Kita by dissecting both their processes and writing a plugin that ties together runtime templates with Tailwind’s parser.

github.comGitHub - Moshyfawn/tailwind-serve: Compile and serve Tailwind CSS at server startup - no build pipeline neededCompile and serve Tailwind CSS at server startup - no build pipeline needed - Moshyfawn/tailwind-serve
moshyfawn@moshyfawn.dev

Maybe I’m simply spoiled by meta frameworks, but I’m gonna try migrating the frontend to SolidStart. I’ll need client interactivity soon anyway, and SolidJS has the Bun adapter plus Zero sync engine plugin I want to explore for something else.

moshyfawn
@moshyfawn.dev

SolidStart v2 bun compatibility is in a weird limbo - it only works about half the time, and Solid v2 still isn’t fully compatible with SolidStart v2.

moshyfawn
@moshyfawn.dev

I’ve also reconsidered what the @atplay.blue client actually needs in terms of interactivity, and a static frontend should do the job for quite a while, especially with modern HTML features like view transitions.

moshyfawn
@moshyfawn.dev

Welp, I’ve circled back to ElysiaJS - there’s still nothing else that integrates as fully with Bun. I ended up fixing my main issue with Tailwind and Kita by dissecting both their processes and writing a plugin that ties together runtime templates with Tailwind’s parser.

github.comGitHub - Moshyfawn/tailwind-serve: Compile and serve Tailwind CSS at server startup - no build pipeline neededCompile and serve Tailwind CSS at server startup - no build pipeline needed - Moshyfawn/tailwind-serve
moshyfawn@moshyfawn.dev

Maybe I’m simply spoiled by meta frameworks, but I’m gonna try migrating the frontend to SolidStart. I’ll need client interactivity soon anyway, and SolidJS has the Bun adapter plus Zero sync engine plugin I want to explore for something else.

moshyfawn
@moshyfawn.dev

Welp, it turns out Solid's (or Vinxi's ?) SSR workers still run in NodeJS so utilizing Bun's SQL or S3 pieces won't work still. Uh.. back to the drawing board.

moshyfawn@moshyfawn.dev

Maybe I’m simply spoiled by meta frameworks, but I’m gonna try migrating the frontend to SolidStart. I’ll need client interactivity soon anyway, and SolidJS has the Bun adapter plus Zero sync engine plugin I want to explore for something else.

View full thread
moshyfawn
@moshyfawn.dev

Welp, it turns out Solid's (or Vinxi's ?) SSR workers still run in NodeJS so utilizing Bun's SQL or S3 pieces won't work still. Uh.. back to the drawing board.

moshyfawn@moshyfawn.dev

Maybe I’m simply spoiled by meta frameworks, but I’m gonna try migrating the frontend to SolidStart. I’ll need client interactivity soon anyway, and SolidJS has the Bun adapter plus Zero sync engine plugin I want to explore for something else.

moshyfawn
@moshyfawn.dev

SolidStart is weird - it has all the polish of a modern framework, yet it feels tied down by legacy baggage like Vite v6, which comes from its dependency on Vinxi, and that in turn has some half-baked parts like incomplete Bun support - partly because of Vite v6 lacking their environments support..

moshyfawn
@moshyfawn.dev

Like I've got a custom `vite-env-bun` plugin in the project now that intercepts Bun module requests and "translates" them to Bun's runtime properties because Vite v6 workers run in Node specifically.

moshyfawn
@moshyfawn.dev

The project's not even released yet, I've already chased down patches I need to apply 🫠 The cost of bleeding edge tech, maybe? ```json "patchedDependencies": { "@solidjs/meta@0.29.4": "patches/@solidjs%2Fmeta@0.29.4.patch", "@bomb.sh/tab@0.0.13": "patches/@bomb.sh%2Ftab@0.0.13.patch" } ```