After about a year here, I’ve decided to migrate this “Journal” miniblog from micro.blog to Leaflet , a new blogging service built on top of Bluesky’s AT Protocol. I wrote about this in my first post on Leaflet here . I’m leaving this site up for now, but I’ve imported all existing posts from here to there, and eventually I’ll add a redirect to the new…
You know that feeling when you’re trying to find a post (skeet) that you’ve seen some time ago, and you can’t find it? It happens to me all the time. Let’s say someone from the Bluesky dev team wrote some piece of technical detail, or some ATProto developer from the community posted about their project - I know more or less what I’m looking for, but not enough to find…
Since last autumn, I’ve mostly been focused on database and server stuff ( the Postgres migration ) and Ruby coding (e.g. the firehose consumer optimizations . I also have a couple of JavaScript projects, mainly Skythread – I’ve been collecting a todo list of things to fix and add there, but I somehow couldn’t get myself to switch contexts and take a look at that project again.…
A couple of months ago, I wrote about the tests I’ve done on how I can speed up my code for processing the Bluesky firehose, using my Skyfall Ruby gem. The limits I’ve reached then were around: 4k events/s with full post processing that it normally does (saving all posts, matching posts to feeds etc.) 5k events/s if using Jetstream – but I noted that it seemed suspiciously like that…
As the final phase of my database experiments , I’ve been playing recently with optimizing the speed of processing in the firehose process. The Bluesky firehose is a streaming API that sends you every single thing happening on the network in real time – every post, like, follow, everything (encoded in a binary format called CBOR ). And my firehose process is a client connecting to that…
I’m a very picky person when it comes to buying things… especially Apple hardware. I can’t count the number of Apple devices I tried out and sent back, because something wasn’t right. Because there are always tradeoffs, and I don’t like tradeoffs, I want it to be just perfect 😅 So since I really needed a new MacBook (I’ve been using an M1, which would be fine if I…
2024 was a pretty intense year for me in terms of coding… and a pretty not-intense one for anything else 🫣 I was so completely absorbed with building my Bluesky-related projects. It gives me a lot of satisfaction to be able to work on things which are based on my own ideas and needs, which give me fun problems to solve, let me learn a lot, and which seem to be helping a lot of other people . I…
I think I’ve finally made some good progress with my Postgres database. Things are working pretty well now, and I still have a few fixes in the queue. It’s not all finished yet, but I feel like I’m coming out of the woods now. For those out of the loop: I have a server which streams and saves all posts from the Bluesky firehose, and uses this data to run several feeds on Bluesky…
who dis
test 123
just setting up my mcroblog