home.social

Search

495 results for “zeab”

  1. #openssh now defaults to #mlkem768x25519 algorithm for keys. In other words, welcome to quantum resistance being a thing. 😎

    Congrats to the team on this release!

    openssh.com/txt/release-10.0

  2. now defaults to algorithm for keys. In other words, welcome to quantum resistance being a thing. 😎

    Congrats to the team on this release!

    openssh.com/txt/release-10.0

  3. #openssh now defaults to #mlkem768x25519 algorithm for keys. In other words, welcome to quantum resistance being a thing. 😎

    Congrats to the team on this release!

    openssh.com/txt/release-10.0

  4. #openssh now defaults to #mlkem768x25519 algorithm for keys. In other words, welcome to quantum resistance being a thing. 😎

    Congrats to the team on this release!

    openssh.com/txt/release-10.0

  5. #openssh now defaults to #mlkem768x25519 algorithm for keys. In other words, welcome to quantum resistance being a thing. 😎

    Congrats to the team on this release!

    openssh.com/txt/release-10.0

  6. Ok #TrustedDocuments is effectively #jsonrpc but in #GraphQL. 😄 Though, because you know of the query for the client, you can have the query planner in graphql optimized for those type. Helping considerably in speed, but also execution and security.

    Little to say, I like it. 😅

  7. Ok #TrustedDocuments is effectively #jsonrpc but in #GraphQL. 😄 Though, because you know of the query for the client, you can have the query planner in graphql optimized for those type. Helping considerably in speed, but also execution and security.

    Little to say, I like it. 😅

  8. Ok #TrustedDocuments is effectively #jsonrpc but in #GraphQL. 😄 Though, because you know of the query for the client, you can have the query planner in graphql optimized for those type. Helping considerably in speed, but also execution and security.

    Little to say, I like it. 😅

  9. Ok #TrustedDocuments is effectively #jsonrpc but in #GraphQL. 😄 Though, because you know of the query for the client, you can have the query planner in graphql optimized for those type. Helping considerably in speed, but also execution and security.

    Little to say, I like it. 😅

  10. @alxlg your most welcome!

    I by no means only use #docker. Far from it. 😎 But it does have a lot of capabilities now. Very much thanks to the outstanding work done on #podman and #buildah.

    Heck, yesterday a colleague found out "they" copied #skopeo for image mirroring with "imagetools". The cli design is really noisy, but it does work. 😅

    docs.docker.com/reference/cli/

  11. @alxlg your most welcome!

    I by no means only use #docker. Far from it. 😎 But it does have a lot of capabilities now. Very much thanks to the outstanding work done on #podman and #buildah.

    Heck, yesterday a colleague found out "they" copied #skopeo for image mirroring with "imagetools". The cli design is really noisy, but it does work. 😅

    docs.docker.com/reference/cli/

  12. @alxlg your most welcome!

    I by no means only use #docker. Far from it. 😎 But it does have a lot of capabilities now. Very much thanks to the outstanding work done on #podman and #buildah.

    Heck, yesterday a colleague found out "they" copied #skopeo for image mirroring with "imagetools". The cli design is really noisy, but it does work. 😅

    docs.docker.com/reference/cli/

  13. @alxlg your most welcome!

    I by no means only use #docker. Far from it. 😎 But it does have a lot of capabilities now. Very much thanks to the outstanding work done on #podman and #buildah.

    Heck, yesterday a colleague found out "they" copied #skopeo for image mirroring with "imagetools". The cli design is really noisy, but it does work. 😅

    docs.docker.com/reference/cli/

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

    discourse.ubuntu.com/t/multipa

  15. #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

  16. #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

  17. #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

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

  19. Discovered recently #oras for #OCI artifact handling.

    I thought the normal way for these uploads was setting the metadata manually to the container registry. 😅

    Meaning... I'm using this now. 😁

    oras.land/

  20. Discovered recently #oras for #OCI artifact handling.

    I thought the normal way for these uploads was setting the metadata manually to the container registry. 😅

    Meaning... I'm using this now. 😁

    oras.land/

  21. Discovered recently #oras for #OCI artifact handling.

    I thought the normal way for these uploads was setting the metadata manually to the container registry. 😅

    Meaning... I'm using this now. 😁

    oras.land/

  22. Discovered recently #oras for #OCI artifact handling.

    I thought the normal way for these uploads was setting the metadata manually to the container registry. 😅

    Meaning... I'm using this now. 😁

    oras.land/

  23. Absolutely bonkers reception for the new #framework releases.

    Now to figure if I want a #thelio still or go all in one these crazy things. 😁

    @frameworkcomputer fosstodon.org/@frameworkcomput

  24. Absolutely bonkers reception for the new #framework releases.

    Now to figure if I want a #thelio still or go all in one these crazy things. 😁

    @frameworkcomputer fosstodon.org/@frameworkcomput

  25. Absolutely bonkers reception for the new #framework releases.

    Now to figure if I want a #thelio still or go all in one these crazy things. 😁

    @frameworkcomputer fosstodon.org/@frameworkcomput

  26. Absolutely bonkers reception for the new #framework releases.

    Now to figure if I want a #thelio still or go all in one these crazy things. 😁

    @frameworkcomputer fosstodon.org/@frameworkcomput

  27. Logical replication in is the secret sauce of data prowess. 😅 The WAL can be the difference between distress or just stress. 🤣

    usage for their search instance is prime example. Replicate and go. A whole lot saner than the full ETL path. 🫠

    paradedb.com/blog/etl_vs_logic

  28. Discovered and absolutely mind shattering. 🤯 I seen companies fall because of getting to get the sync right with . 🫠

    Seeing paradedb is replica away from giving those gains... Like, it's getting considerably hard recommending anything other than it, and of course. 😅

    paradedb.com/

  29. @markus I'm sorry for be the bearer of bad news friend, but here 😭: community.fly.io/t/sunsetting-

    On the plus side, #litefs is still being developed. Just not as a service anymore and more as utility. 🫠

  30. @markus I'm sorry for be the bearer of bad news friend, but here 😭: community.fly.io/t/sunsetting-

    On the plus side, #litefs is still being developed. Just not as a service anymore and more as utility. 🫠