home.social

Search

495 results for “zeab”

  1. The #canonical #craft ecosystem is interesting. Learning from #nix 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 #snapcraft is likely it. But #debcraft is a new one to target debs directly. Or say #imagecraft 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

  2. The #canonical #craft ecosystem is interesting. Learning from #nix 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 #snapcraft is likely it. But #debcraft is a new one to target debs directly. Or say #imagecraft 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

  3. The #canonical #craft ecosystem is interesting. Learning from #nix 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 #snapcraft is likely it. But #debcraft is a new one to target debs directly. Or say #imagecraft 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. The #canonical #craft ecosystem is interesting. Learning from #nix 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 #snapcraft is likely it. But #debcraft is a new one to target debs directly. Or say #imagecraft 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

  5. 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

  6. #Fastmail has now an #mcp server.

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

    So no #Google or ai vendor training on your data. 😎

    fastmail.com/blog/an-mcp-serve

  7. #Fastmail has now an #mcp server.

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

    So no #Google or ai vendor training on your data. 😎

    fastmail.com/blog/an-mcp-serve

  8. #Fastmail has now an #mcp server.

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

    So no #Google or ai vendor training on your data. 😎

    fastmail.com/blog/an-mcp-serve

  9. #Fastmail has now an #mcp server.

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

    So no #Google or ai vendor training on your data. 😎

    fastmail.com/blog/an-mcp-serve

  10. Ok, this is unexpected. 13 pro with ram! Even first marketing. 🤯

    Granted, you should not buy anything with ram or CPU or disk drives until the ai bubble pops. 😅 Still exciting to see.

    frame.work/laptop13pro

  11. is such an elegant solution to expiration. 😅

    Handling distributed TLS expiration is not exactly a solved problem. So many incidents due to it. Even with notary just being an intermediary, worlds better than managing it all. 🫠

    discourse.charmhub.io/t/beyond

  12. 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

  13. 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

  14. And #discourse post speaks exactly towards why closed source move from #cal makes no sense.

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

    blog.discourse.org/2026/04/dis

  15. And #discourse post speaks exactly towards why closed source move from #cal makes no sense.

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

    blog.discourse.org/2026/04/dis

  16. And #discourse post speaks exactly towards why closed source move from #cal makes no sense.

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

    blog.discourse.org/2026/04/dis

  17. And #discourse post speaks exactly towards why closed source move from #cal makes no sense.

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

    blog.discourse.org/2026/04/dis

  18. 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

  19. So let's get this straight. #cal is moving proprietary because ai is finding bugs. Bugs also can be patched by ai as well. And they think #opensource 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

  20. So let's get this straight. #cal is moving proprietary because ai is finding bugs. Bugs also can be patched by ai as well. And they think #opensource 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

  21. So let's get this straight. #cal is moving proprietary because ai is finding bugs. Bugs also can be patched by ai as well. And they think #opensource 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

  22. So let's get this straight. #cal is moving proprietary because ai is finding bugs. Bugs also can be patched by ai as well. And they think #opensource 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

  23. 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. 😅

  24. But you may wonder... why not 'just' use the docker-language-server for #hcl? 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. 😅

  25. But you may wonder... why not 'just' use the docker-language-server for #hcl? 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. 😅

  26. But you may wonder... why not 'just' use the docker-language-server for #hcl? 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. 😅

  27. But you may wonder... why not 'just' use the docker-language-server for #hcl? 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. 😅

  28. 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

  29. 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 #HCL one. So I can get the #docker bake set up "JUST right" on #helix with docker-language-server. So I can fix the annoyance of #terraform #LSP 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

  30. 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 #HCL one. So I can get the #docker bake set up "JUST right" on #helix with docker-language-server. So I can fix the annoyance of #terraform #LSP 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