In mercurial, you can do anonymous branches. Think multiple heads not dependent on being latest. your can do this when you are doing random pet peeve tasks. Collect work in different heads. When you done, you merge them back into something of order with no conflict. 🤯
This is immensely powerful when you working on older revision to work on different ideas without effecting the main head.
The new #TwitterNotes is another proprietary garden. Owning and controlling your content in their social network.
Own your social network. Own your words. Move to #ActivityPub.
Even when you in an instance not hosted by you, you can still migrate to others. You can carry your data with you. No company holds you here. It's you that are the sayer of what you do.
Don't let yourself be silence by what a company let's you do.
It's not like I don't understand the orchestrator. I very much do. Enough to have written my own scheduler 🕞 for it. But dammit do I hate how much you have to do to get the smallest goals done.
Meanwhile in nomad, you get to actually work on the job. 🤯 Not the orchestrator. Cluster management is almost nonexistent. Even self hosted.
I did not know there was a single column 🛣️ view available in #mastodon web ui. It feels weird not seeing the columns. Interesting enough, I can't really navigate by using j/k hotkeys. Yet I can with the multicolumn view 🙃.
Was a nice 30 second experiment. Going back...
Got access to #neondatabase. Love typing out psql -h pg.neon.tech to log in to the database. Absolutely love it. Definitely going to need to learn how they did this. Makes it real easy to play with.
Still haven't the time spin up my own instance of neon, but will soon. I think this is exactly what the community needed to start doing fancy things on #serverless. All while not being gated by the big corps.
Now hold on! Before you eyeroll it out, take a look.
A lot of alternatives fall down the trap of more complexity to make. #just does not. It focuses on being expressive as a command runner and only that. Using similar syntax to make. Enough so, you may end up hating make even more.
So after a few weeks now with #logseq, I can safely say I have become dependent on it. I now have to keep it open at all times to jot random stuff.
Has anyone out there used #topicbox? Especially as an alternative to the Google groups.
It feels like a product with potential. Running a mailing list server can be a hurdle. Not to mention how many are still stuck with web ui from the 90s. Topicbox looks and feels reasonable for this age. And of course, email very much the core of its conversations.
Even with multi read replicas on #litestream. Your system most likely doesn't need strong consistency.
You can get by with having one writer. Publish events to some message broker. So the writer can do what it was destined to do.
Leaving the rest of the app to keep turning. Updating once the read replicas synced from those writes.
Yeah... for read heavy, #sqlite is now my preferred choice.
#litestream has changed my thinking on how to deal with such systems. Even with multiple replicas. You can get around by how you handle writes in such a system.
It's such intuitive pattern. Feels like next couple of years, n-tier apps are going to fundamentally change from alternatives like this.
A meticulous developer who happens to do a lot infrastructure and platform engineering.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.