home.social
  1. standards are how to federate widely.

    I'm a fan of . Extensively versatile protocol. Without the baggage of gotchas from . 🫠

    But won't be adopted by corps. They already built their custom version on top of IMAP. 😅

    Still. Email works. 😎

    buttondown.com/blog/future-of-

  2. And... officially has a split product with db and og. It could work.

    But honestly.. I'm kind of liking obsidian now. 🫠 Sure it does 0.1 of what logseq can do. At the same, maybe that's ok? 😅

    Like if you enrich frontmatter, use tags, and follow principles, obsidian can do a lot.

    You don't need an everything tool. Just enough flexibility to shape your needs. 😉

    logseq.io/page/b2ad9ce1-9cb7-4

  3. The ecosystem is interesting. Learning from to produce a concise artifacts.

    What makes it different is targets are based on which craft you use. Like if you want an app, then is likely it. But is a new one to target debs directly. Or say which creates an os image.

    In nix you target all the things with the same language. But I think this approach of target based tooling makes sense as well. 😅

    discourse.ubuntu.com/t/what-ma

  4. has now an server.

    If you use with locally, you got yourself a fully private access to your emails. Benefits of ai without snooping. 😅

    So no or ai vendor training on your data. 😎

    fastmail.com/blog/an-mcp-serve

  5. So the team at created a new ai agent tool called . 😵‍💫 Did not see that coming. 😅

    My question is more of how does it impact the new thunderbird pro effort the same team is trying to release. 🤔

    thunderbolt.io/announcing-thun

  6. And post speaks exactly towards why closed source move from makes no sense.

    Simply put, it's not security and it's not ai. 😅

    blog.discourse.org/2026/04/dis

  7. So let's get this straight. is moving proprietary because ai is finding bugs. Bugs also can be patched by ai as well. And they think is the problem?! 🤣

    Mind you, ai will STILL find bugs on. 😅 AI is a lot of things, but these excuses are getting ridiculous. 🫠

    cal.com/blog/cal-com-goes-clos

  8. But you may wonder... why not 'just' use the docker-language-server for ? Good question. You see~ if that's done, then I don't get all my terraform files working as intended.

    But I could simply leave as is. Then using the docker-language-server solely when the file is loaded, but then falling back to switching the language to hcl when I want the rest of the grammar.

    That's where the annoyance came from. 😅

  9. Without a doubt, I'm "trying to change a lightbulb."

    All I wanted was to start up a server. 🫠

    I'm now researching creating a grammar for docker-bake. Forking one. So I can get the bake set up "JUST right" on with docker-language-server. So I can fix the annoyance of being used incorrectly. Then refactor a dockerfile. So I can then upload into a registry cleanly.

    So I can finally host the darn thing. 🤣

    youtube.com/watch?v=5W4NFcamRhM

  10. One of the main reasons I want to use 26.04 is for the desktop. 😅 All that package handling. 😇

    I didn't need more reasons for the release. 😁

    phoronix.com/review/ubuntu-260

  11. I left for .

    The tool continues to work. Yet, I know focus is on database version. Meaning current stable is a bit lacking. 🫠

    What's interesting is how difficult finding an outliner as good as logseq. There's really none.

    Venturing out isn't THAT bad... Let's see in 3 months. 😅

  12. I've been slowly moving to . Though now, quite quickly thanks to this article. 😅 Especially when using , the advantage is quite apparent. 😉

    chrisdown.name/2026/03/24/zswa

  13. Ok. This the moment I stop using and maybe , for . 😎

    The implement of without me doing a single thing... Simply start the server... I don't think I need another dns authoritative server. 😉

    Excellent work from !

    blog.dnsimple.com/2026/02/erld

  14. Started to use from and I'm SO with this. 😎

    I don't run . Yes. I still prefer or . I like the distros and usually deviate their base to be anything anyhow. 😏

    But that does not mean I like missing declaration magic. System manager lets me still do all the crazy things I normally do. Plus I get some guard on my system settings. 😅

    system-manager.net/main/

  15. Oh no, got acquired by . Something had to give. I think the tools astral made are truly great changing for . But now with this acquisition... Color me surprised if does more of the plans astral had. 🫠

    astral.sh/blog/openai

  16. I haven't been tracking, but date time library is GA. 😍

    It's a must have!

    I can remember many failures in js world attributed to date usage. So much pain... Made me hate js almost instantly when I learned of date. 😅

    Now safari is left to fix. 🫠

    piccalil.li/blog/date-is-out-a

  17. All these quality of life improvements in . 😍 Congrats to the whole team for 1.3.

    The native notification on command finish! I've had a plugin for I don't know how many years for this... I'm going to need to test this magic. 😎

    ghostty.org/docs/install/relea

  18. 2 is out and it is impressive! 😁 Great work team. Going to ride through in some personal projects to test out.

    I been moving to flake parts all my things, but still. Would like these dev shell benefits. 😎

    devenv.sh/blog/2026/03/05/deve

  19. On no. There's even more ways I'll be putting the into what I do. 😂 Basically now has a new ASGI called .

    I don't think I can ignore this amazingness. 😁

    hornbeam.dev/

  20. Forget is locked down as hard as fort knox.

    Read through their specs documentation. It's an absolutely stellar pattern to follow. Write your requirements and track design of your requirements.

    immensely valuable advice on how to build software in general. 😅

    kiro.dev/docs/specs/

  21. v2 is official. I'm so on this. 😅 I found writing in honestly fun thanks to bubbly tea.

    charm.land/blog/v2/

  22. Interesting to see combinator conditions on for CLI.

    This is something that's hard to do in any CLI library. Easier with typed languages, but still can be complex. Very cool to see with and their approach leveraging the type system. 😎

    optique.dev/why

  23. So I started to look over again for self hosting . , , and are the simplest. All focused.

    Yet still, Pocket ID is by far the easiest to run. Strictly Unix like focused on doing one thing. But doing one thing really well. 😎

    pocket-id.org/

  24. Rest in piece . It set the stage to what is better . Now the market is littered with options. 😎

    heroku.com/blog/an-update-on-h

  25. now has with its own webpage. You want to learn how to develop software like a boss? Go there! 😎
    tigerstyle.dev/

  26. Been reading a bit more on from and Sandboxes.
    The gist is trying to isolate as much as possible. So you can run insecure workloads on these environments. Which is usually agentic by default.

    Though, for secure workloads, they still make no sense. 😅

  27. I must say and , are like catnip. 😅 You can do SO much with those two.

    Case in point, . A new framework for targeting mobile and desktop apps. All with go, templ, and . 🫡

    irgo.dev/

  28. I haven't seen many users yet on for . Nice of trying things for the rest of us. 😅

    For migrations like this, spinning up a read replica is key. Use it to do what you need. Primary then gets no impact while migrating.
    buttondown.com/blog/2026-01-14

  29. I think a lot of the cloud providers get lost in well... the cloud. 😅

    You can do what does with /#incus system containers. It has all the ec2 magic there as well.

    App containers help packaging software. But inhibit developing the software itself.

    fly.io/blog/code-and-let-live/

  30. Who hasn't bought? 😅
    now part of the ever expanding buyouts.
    🫠
    confluent.io/blog/ibm-to-acqui

  31. This is interesting. has moved to .

    I really think for open source software, they should be in open source . Basically, use to share, not . 😉

    ziglang.org/news/migrating-fro

  32. now makes have some formatting when an output response. 😍

    I use hurl both home and at work. And while you can use to format, it is really nice not to have to look for another tool when I'm troubleshooting tests. 😎

    hurl.dev/blog/2025/11/26/hurl-

  33. BRB, going to implement cluster time. 😎 brilliance is like on every post they do. I learn so much just from reading their posts. Let alone going over there code. This is what resilient db looks like.

    tigerbeetle.com/blog/2021-08-3

  34. And further sprinkles here is the license on . So whole rugpull scenario gets MUCH harder.

    Which btw, is also hosted on their own server. 😁 The further I go on Garage, the more I'm really falling in love with this option.

    Consistency controls was first requirement. Development continuity is the big second. 😎

    git.deuxfleurs.fr/Deuxfleurs/g

  35. And in a twist of design, here's doing durable execution directly with and an event bus framework in called .

    So just in case you all in go, this may be the way to go instead of . 😅

    threedots.tech/post/sqlite-dur

  36. 0.5 is even more reason just to pick . You can get pretty far with litestream and have it fully manageable for duplication.

    Lower the N tier of your app. 😉

    fly.io/blog/litestream-v050-is

  37. Profile control in is kind of outstanding. I have this very problem with monorepo dev work. Not all the time you need to load everything under the sun. 😅

    Going to see how to fit on these very repos. 😁

    devenv.sh/blog/2025/09/17/deve

  38. Here I go again. Diving deep into modern design.

    feature introduction for materialized views in their fork looks interesting, to say the least. 😅

    turso.tech/blog/introducing-re

  39. Another project for in . Hold up! It's a fork of . Using instead of . 😅

    The difference here is how much datastar use (). It's EVERYWHERE. Very potent stuff.

    Hadn't yet tried datastar, but maybe soon with this. 😁

    starhtml.com/

  40. Starting to learn how to use with for . It's an itch I had.

    Been meaning to build up everything with pyinfra. But I need tests. In world, I had tests for everything using Molecule. It worked well enough, but was quite complex.

    However, with pyinfra, the tests can be isolated integration test containers! 😎

    Now I can go crazy with the amount of tests for every operation done. 😆

  41. Found out about and kind of in love. It's simple enough. No fluff and can do operations with keybindings. Absolute joy. 😄

    Honestly, I don't know why I haven't been trying file managers. I'm like 99.9999% in the terminal. 😅

  42. On , the complexity is on knative rollout. But if you strip down to nothing, it becomes easier. knative serving CRDs with , and you get something that work for requests cross nodes easy. pro and con are, you now have a whole bloody k8s cluster. 🤣 Heavy at start, but light in maintaining after. Especially if this is a or single node /#k3s setup. 😅

  43. is such an important tool. Especially when working with c libraries. Great work on getting actually function for it. 😅
    mitchellh.com/writing/ghostty-

  44. Found out about a new secret handling standard called .

    Has some nice simplicity with . And integrates with . 😎

    I have workloads doing this stuff all over the place. So it's definitely nice maybe not reinventing the same wheel for the 42nd time. 🫠

    secretspec.dev/

  45. I didn't see this coming. Apparently from is yo try to do local cloud. Though I'm curious why not do this from . It's already doing this exact same work and it works pretty well. 😅

    discourse.ubuntu.com/t/multipa

  46. I've gotten in this habit of building all software to be . And I mean ALL software. 😅

    Functional languages make this easier. But they still don't capture state of systems you rely on. Like time or random number generators. 🫠 The things that truly break apart. 🙃

    Abstracting non deterministic properties to calls you inject can make a world of difference. It helps then being able to evaluate why you get an error for api outside of your control. And yes time is an api. 😏

  47. I been looking at and this is complex. 🤔 The command runner has so many abilities. And verbose too. 🫠

    I don't think I'll use for myself, but I can see utility for shared tasks.

    For me is enough. Not too complex. Has a syntax. And NOT . 😅

    taskfile.dev/usage/

  48. Kind of wild gets a description from guides posts.

    Not always should you reach for microservices (read never). 😅 But when your company is knee deep, it does help to have some common way for services. Plus dapr follows erlang patterns. 😎

    aws.amazon.com/blogs/opensourc

  49. now does compaction. Using s3 condition writes. 😎

    is good, but complex when not in infra. Especially for . Too many moving parts. 😅

    Very happy litestream is getting some love. Makes even more of a no brainer choice. 😏
    fly.io/blog/litestream-revampe