boltless

@boltless.me

I do #rust #swiftui #reactnative #golang #lua #janet or anything I need to make my life better. I use #neovim btw. Developer at @tangled.org GitHub: https://github.com/boltlessengineer Tangled: https://tangled.org/boltless.me Blog: https://boltless.me

from the policy: "A project that implements a protocol incompatible with the AT Protocol must use its own distinct name." so uhhh, incompatible with what, exactly?

there are so many posts I should write and my writing speed is so slow 😭 - how to setup air-gapped tangled infra for local development (replacing old nixos-vm one) - my military service journey (it's been more than a year now..) - atproto COB situation <- I should finish this before IETF...

I'm listing out all hurdles I faced while using @htmx.org because just saying "Our application is too complex for HTMX" doesn't help much. At what level of complexity does an application start choosing JS frameworks over HTMX?

I should write a new blog post about Tangled's COB situation. It's one of the fields atproto hasn't solved yet (even with permissioned space) and I think there are few more services that can benefit from this architecture other than Tangled.

boltless@boltless.me · 3w ago

two types of applications I haven't seen in #atproto even with upcoming permissioned space. 1. collaborative space where space does actually own the contributed data - Tangled should solve this. 2. federated space like wikipedia. - similar to case 1, but with distributed ownership over the data.

people love the For You feed, and it shows in the numbers. it generates around 4% of post views inside feeds on Bluesky. that's amazing especially because it's operated by one dev, @spacecowboy17.bsky.social given its popularity, we've decided to give it a bump in visibility on the feeds page.

Screenshot showing how the For You feed may appear at the top of the Feeds page in the Bluesky app.

two types of applications I haven't seen in #atproto even with upcoming permissioned space. 1. collaborative space where space does actually own the contributed data - Tangled should solve this. 2. federated space like wikipedia. - similar to case 1, but with distributed ownership over the data.