Jaz

Hi protocol friends! I've been cooking up a Very Large PDS (vlpds) implementation capable of scaling up to billions of accounts and down to just one. It uses Object Storage as its only state, supports HA operation, live scaling up and down, is feature-complete with the reference PDS, and is FOSS.

Main account migrated to the streamplace.com VLPDS. Is this thing on?

five nines and flat lines

its not possible to watch this video without smiling really wide

don't make me tap the sign thepope.dev/posts/2026-1...

Some days I just wish I was a cat.

free foot pics because you made a fridge whose door falls off, oldest trick in the book

the story goes like this

the new job at eMudhra is not going well, my bad

Claude: "No! That's too far! I will not use leaked certs to impersonate Sony! Go buy a new cable!" Astra:

🚨 Six WebPKI Intermediate CAs are compromised. This is bigger than Heartbleed, but a client-side issue. Anything that verifies certificates against public roots, like most TLS clients, is/was affected. Details, live test, patched versions and workarounds at emudhra.we-have-a-problem.com Act now.

THIS IS NOT A DRILL. If you package/distribute/maintain root stores or chain verifiers, act immediately. If you know how to remove trust in a root, consider doing it now. Otherwise, prepare to update systems as patches/mitigations come. Go users, update to Go 1.27.3 or Go 1.26.10.

👩🏽‍🔬 Go 1.27.3 and 1.26.10 are released! 🔐 Security: Includes 1 security fixes to the standard library. 🗣 Announcement: https://groups.google.com/g/golang-announce/c/66pojueaQek/m/tmWX2Pq9AgAJ 📦 Download: https://go.dev/dl/#go1.27.3 #golang

you should update to go 1.27.3 asap

You should take this update. bsky.app/profile/gola...

for the curious, my compute node went from an amd epyc 7302P to a 7713 so from 16->64 cores and from zen2 to zen3 architecture yay

This is Pele, my new rendering library for diagrams and charts, compatible with the latest Mermaid syntax. - 100-500× faster than mermaid.js - 6× smaller bundle - No dependencies - Easy to theme - Responsive to device width - Open source (MIT) Try it at pele.run

This is a great post about how we ran massive bloom filters at scale for Bluesky's AppView, check it out!

Been sitting on this draft for a very long time!

Hello friends! Life update: after 1.5 years, I've decided it's time to move on from Bluesky and start the next chapter. Today's my last day! It has been an absolute honor and pleasure to work with such a talented, fun team on a critical mission. I'm so proud of them and excited to see what's next

support trans rights

“Better HTTP/1 connection reuse” by Nicholas Husin and Damien Neil — https://go.dev/blog/http-connection-reuse #golang

interviewer: can you explain this gap in your resume? sre: look, you can’t have consistency, availability, AND partition resistance,

linux solved github.com/haileyok/Mag...

my new record is out on lauren records. it’s called grimdark. i’m really proud of it. the album art was made by sebastian kim bateman. jack shirley mixed & mastered it. cleo mckenzie directed it. lauren records put it out. neat stuff ^_^

Oh yeah vlPDS now has full support for the atproto spaces alpha btw with tooling for users to manage their space data and operators to see the infrastructure-relevant info about spaces sync for their vlPDS instance. vlpds.jazco.dev/docs/spaces

I truly believe that Object Storage is the only real datastore and everything else should be cache and compute on top of it. Databases are fake, Object Storage is the last database. All your systems should be built on top of it and use NVME and RAM as caches and local compute.

If you need low latency, simply support shard replicas and accept writes as durable when a quorum of replicas have written the write into memory and let them slowly flush to object storage in efficient batches that amortize operation costs. That's durable enough for pretty much anything.

Of course for ^ to be durable you want your replicas to be on different physical nodes and maybe different racks but yeah. Horizontally scalable DBs use RAM as a cache and NVME as durable storage with writes durable at R=2 nodes reporting in-memory writes. Now we have RAM -> NVME -> Object Storage.

This is nice because it allows single node operation and also allows recovery and seamless handoff by pulling from object storage instead of having to do heavy node-to-node reads to catch up or onboard a new node. Your durability is also a lot higher and you can run your local NVME hot.

There are numerous elevators

Okay so I've built a new Atlas, this time it lets you explore the conversations on Bluesky over the past 7 days graphically. It should update every ~6 hours and help you navigate the information environment that exists on here. I've learned a LOT about what people do here today... atlas.jazco.dev

Projects like this are fun because I always end up with more questions than I had when I started, such as: - What is "Feral Flannel Friday"? - What is "Drag'n Wash" and why is there backlash about it? (the summary helped answer this one) - Who is making Hazbin Hotel Omegaverse art? - Furry pilot?