home.social

#reproducible — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #reproducible, aggregated by home.social.

fetched live
  1. Hi All Nix, Guix users

    I want a better term to address , , etc
    Coz whenever I mention something about Nix's benefits etc , I also mean guix, lix too
    So I'm hunting for a better term to address things in common.
    Coz Nix(and it's family is),
    , , , , , , pure , , etc etc

    The terms I came up with are
    eng, eng, Pure Functional Eng.
    🧵

  2. Hi All Nix, Guix users

    I want a better term to address #nix, #guix, #lix etc
    Coz whenever I mention something about Nix's benefits etc , I also mean guix, lix too
    So I'm hunting for a better term to address things in common.
    Coz Nix(and it's family is),
    #Declarative, #idempotent, #bit2bit #reproducible, #Immutable, #hermetic, #provenant, pure #functional, #incremental, #Atomic etc etc

    The terms I came up with are
    #Congruent eng, #Invariant eng, Pure Functional Eng.
    🧵

    #nixos #guixos

  3. Hi All Nix, Guix users

    I want a better term to address #nix, #guix, #lix etc
    Coz whenever I mention something about Nix's benefits etc , I also mean guix, lix too
    So I'm hunting for a better term to address things in common.
    Coz Nix(and it's family is),
    #Declarative, #idempotent, #bit2bit #reproducible, #Immutable, #hermetic, #provenant, pure #functional, #incremental, #Atomic etc etc

    The terms I came up with are
    #Congruent eng, #Invariant eng, Pure Functional Eng.
    🧵

    #nixos #guixos

  4. Hi All Nix, Guix users

    I want a better term to address #nix, #guix, #lix etc
    Coz whenever I mention something about Nix's benefits etc , I also mean guix, lix too
    So I'm hunting for a better term to address things in common.
    Coz Nix(and it's family is),
    #Declarative, #idempotent, #bit2bit #reproducible, #Immutable, #hermetic, #provenant, pure #functional, #incremental, #Atomic etc etc

    The terms I came up with are
    #Congruent eng, #Invariant eng, Pure Functional Eng.
    🧵

    #nixos #guixos

  5. Hi All Nix, Guix users

    I want a better term to address #nix, #guix, #lix etc
    Coz whenever I mention something about Nix's benefits etc , I also mean guix, lix too
    So I'm hunting for a better term to address things in common.
    Coz Nix(and it's family is),
    #Declarative, #idempotent, #bit2bit #reproducible, #Immutable, #hermetic, #provenant, pure #functional, #incremental, #Atomic etc etc

    The terms I came up with are
    #Congruent eng, #Invariant eng, Pure Functional Eng.
    🧵

    #nixos #guixos

  6. 📢 Next up at R-Ladies Rome!
    Typst for Efficient Typesetting with Derek Sollberger (@Princeton)
    Discover how Typst + Quarto, publication-quality PDFs—without the complexity of LaTeX.
    📅 Registration: luma.com/k9bw4g7e
    #RLadiesRome #RStats #Typst #Quarto #Reproducible

  7. 📢 Next up at R-Ladies Rome!
    Typst for Efficient Typesetting with Derek Sollberger (@Princeton)
    Discover how Typst + Quarto, publication-quality PDFs—without the complexity of LaTeX.
    📅 Registration: luma.com/k9bw4g7e

  8. 📢 Next up at R-Ladies Rome!
    Typst for Efficient Typesetting with Derek Sollberger (@Princeton)
    Discover how Typst + Quarto, publication-quality PDFs—without the complexity of LaTeX.
    📅 Registration: luma.com/k9bw4g7e
    #RLadiesRome #RStats #Typst #Quarto #Reproducible

  9. 📢 Next up at R-Ladies Rome!
    Typst for Efficient Typesetting with Derek Sollberger (@Princeton)
    Discover how Typst + Quarto, publication-quality PDFs—without the complexity of LaTeX.
    📅 Registration: luma.com/k9bw4g7e
    #RLadiesRome #RStats #Typst #Quarto #Reproducible

  10. 📢 Next up at R-Ladies Rome!
    Typst for Efficient Typesetting with Derek Sollberger (@Princeton)
    Discover how Typst + Quarto, publication-quality PDFs—without the complexity of LaTeX.
    📅 Registration: luma.com/k9bw4g7e
    #RLadiesRome #RStats #Typst #Quarto #Reproducible

  11. What's in the box:

    QKD Engine - BB84, CV-QKD, and DI-QKD ready. Physical-layer key distribution that detects eavesdroppers in real-time via QBER monitoring. Eavesdrop? We measure it.

    Hardened Debian - Minimal attack surface. Kernel locked. Audit-ready. Runs on secure enclave with measured boot.

    10G Fiber NIC - Low-latency quantum-safe key exchange at wire speed. Plug into existing dark fiber or dedicated QKD links.

    QRNG Core - Hardware quantum random number generator feeding /dev/random. Real entropy from vacuum fluctuations. No pseudo-random guesswork.

    REST & gRPC APIs - Expose QRNG streams and QKD key material to your apps. Consume fresh quantum keys via simple GET requests. Integrate in minutes.

    Port Knocking + SPA - Single Packet Authorization with port knocking closes all public ports until a cryptographically signed knock sequence unlocks access. Invisible unless you know the knock.

    Post-Quantum Crypto Stack - liboqs, OpenSSL 3.x with QKD engine, hybrid PQC+QKD modes. Future-proofed.

    Small business? Enterprise edge?
    Deploy one. Deploy a mesh. The Black Box auto-discovers peers, negotiates QKD sessions, and delivers fresh symmetric keys for IPsec, TLS, or your own crypto.

    Compliance-ready. Information-theoretic security. No backdoors. No math to factor. Just physics.

    Random Oracle not included—but with this box, you generate your own.

    $2499. Debian's first quantum edge. Deploy today. Secure forever.
    #reproducible builds #rolling keys #bb84 #shor #dh..qdh? #device independent #pki #oqc ready #compliance #hybrid PQC key exchange #qssh

    github.com/QuantumUPB/qssh

  12. What's in the box:

    QKD Engine - BB84, CV-QKD, and DI-QKD ready. Physical-layer key distribution that detects eavesdroppers in real-time via QBER monitoring. Eavesdrop? We measure it.

    Hardened Debian - Minimal attack surface. Kernel locked. Audit-ready. Runs on secure enclave with measured boot.

    10G Fiber NIC - Low-latency quantum-safe key exchange at wire speed. Plug into existing dark fiber or dedicated QKD links.

    QRNG Core - Hardware quantum random number generator feeding /dev/random. Real entropy from vacuum fluctuations. No pseudo-random guesswork.

    REST & gRPC APIs - Expose QRNG streams and QKD key material to your apps. Consume fresh quantum keys via simple GET requests. Integrate in minutes.

    Port Knocking + SPA - Single Packet Authorization with port knocking closes all public ports until a cryptographically signed knock sequence unlocks access. Invisible unless you know the knock.

    Post-Quantum Crypto Stack - liboqs, OpenSSL 3.x with QKD engine, hybrid PQC+QKD modes. Future-proofed.

    Small business? Enterprise edge?
    Deploy one. Deploy a mesh. The Black Box auto-discovers peers, negotiates QKD sessions, and delivers fresh symmetric keys for IPsec, TLS, or your own crypto.

    Compliance-ready. Information-theoretic security. No backdoors. No math to factor. Just physics.

    Random Oracle not included—but with this box, you generate your own.

    $2499. Debian's first quantum edge. Deploy today. Secure forever.
    #reproducible builds #rolling keys #bb84 #shor #dh..qdh? #device independent #pki #oqc ready #compliance #hybrid PQC key exchange #qssh

    github.com/QuantumUPB/qssh

  13. What's in the box:

    QKD Engine - BB84, CV-QKD, and DI-QKD ready. Physical-layer key distribution that detects eavesdroppers in real-time via QBER monitoring. Eavesdrop? We measure it.

    Hardened Debian - Minimal attack surface. Kernel locked. Audit-ready. Runs on secure enclave with measured boot.

    10G Fiber NIC - Low-latency quantum-safe key exchange at wire speed. Plug into existing dark fiber or dedicated QKD links.

    QRNG Core - Hardware quantum random number generator feeding /dev/random. Real entropy from vacuum fluctuations. No pseudo-random guesswork.

    REST & gRPC APIs - Expose QRNG streams and QKD key material to your apps. Consume fresh quantum keys via simple GET requests. Integrate in minutes.

    Port Knocking + SPA - Single Packet Authorization with port knocking closes all public ports until a cryptographically signed knock sequence unlocks access. Invisible unless you know the knock.

    Post-Quantum Crypto Stack - liboqs, OpenSSL 3.x with QKD engine, hybrid PQC+QKD modes. Future-proofed.

    Small business? Enterprise edge?
    Deploy one. Deploy a mesh. The Black Box auto-discovers peers, negotiates QKD sessions, and delivers fresh symmetric keys for IPsec, TLS, or your own crypto.

    Compliance-ready. Information-theoretic security. No backdoors. No math to factor. Just physics.

    Random Oracle not included—but with this box, you generate your own.

    $2499. Debian's first quantum edge. Deploy today. Secure forever.
    #reproducible builds #rolling keys #bb84 #shor #dh..qdh? #device independent #pki #oqc ready #compliance #hybrid PQC key exchange #qssh

    github.com/QuantumUPB/qssh

  14. What's in the box:

    QKD Engine - BB84, CV-QKD, and DI-QKD ready. Physical-layer key distribution that detects eavesdroppers in real-time via QBER monitoring. Eavesdrop? We measure it.

    Hardened Debian - Minimal attack surface. Kernel locked. Audit-ready. Runs on secure enclave with measured boot.

    10G Fiber NIC - Low-latency quantum-safe key exchange at wire speed. Plug into existing dark fiber or dedicated QKD links.

    QRNG Core - Hardware quantum random number generator feeding /dev/random. Real entropy from vacuum fluctuations. No pseudo-random guesswork.

    REST & gRPC APIs - Expose QRNG streams and QKD key material to your apps. Consume fresh quantum keys via simple GET requests. Integrate in minutes.

    Port Knocking + SPA - Single Packet Authorization with port knocking closes all public ports until a cryptographically signed knock sequence unlocks access. Invisible unless you know the knock.

    Post-Quantum Crypto Stack - liboqs, OpenSSL 3.x with QKD engine, hybrid PQC+QKD modes. Future-proofed.

    Small business? Enterprise edge?
    Deploy one. Deploy a mesh. The Black Box auto-discovers peers, negotiates QKD sessions, and delivers fresh symmetric keys for IPsec, TLS, or your own crypto.

    Compliance-ready. Information-theoretic security. No backdoors. No math to factor. Just physics.

    Random Oracle not included—but with this box, you generate your own.

    $2499. Debian's first quantum edge. Deploy today. Secure forever.
    #reproducible builds #rolling keys #bb84 #shor #dh..qdh? #device independent #pki #oqc ready #compliance #hybrid PQC key exchange #qssh

    github.com/QuantumUPB/qssh

  15. Just finished listening to the first episode of @Felienne and Hanna Schraffenberger’s #podcast CS off course:

    rss.com/podcasts/computer-scie

    What stuck most: how tools for building #software are designed to build but not to keep track of the thought process.
    This would also be a way to make CS output truly #reproducible. I love the idea of having an atlas type annotation tool. Testing would be more involved, metrics for #reproducibility of #researchsoftware are still illdefined.

  16. Just finished listening to the first episode of @Felienne and Hanna Schraffenberger’s #podcast CS off course:

    rss.com/podcasts/computer-scie

    What stuck most: how tools for building #software are designed to build but not to keep track of the thought process.
    This would also be a way to make CS output truly #reproducible. I love the idea of having an atlas type annotation tool. Testing would be more involved, metrics for #reproducibility of #researchsoftware are still illdefined.

  17. Just finished listening to the first episode of @Felienne and Hanna Schraffenberger’s #podcast CS off course:

    rss.com/podcasts/computer-scie

    What stuck most: how tools for building #software are designed to build but not to keep track of the thought process.
    This would also be a way to make CS output truly #reproducible. I love the idea of having an atlas type annotation tool. Testing would be more involved, metrics for #reproducibility of #researchsoftware are still illdefined.

  18. Just finished listening to the first episode of @Felienne and Hanna Schraffenberger’s #podcast CS off course:

    rss.com/podcasts/computer-scie

    What stuck most: how tools for building #software are designed to build but not to keep track of the thought process.
    This would also be a way to make CS output truly #reproducible. I love the idea of having an atlas type annotation tool. Testing would be more involved, metrics for #reproducibility of #researchsoftware are still illdefined.

  19. Just finished listening to the first episode of @Felienne and Hanna Schraffenberger’s #podcast CS off course:

    rss.com/podcasts/computer-scie

    What stuck most: how tools for building #software are designed to build but not to keep track of the thought process.
    This would also be a way to make CS output truly #reproducible. I love the idea of having an atlas type annotation tool. Testing would be more involved, metrics for #reproducibility of #researchsoftware are still illdefined.

  20. Bugs were squashed and #reproducible (?) pizza was baked in Darmstadt at the #NixOS 26.05 bug squashing party. Doesn't that look delicious?

  21. Bugs were squashed and #reproducible (?) pizza was baked in Darmstadt at the #NixOS 26.05 bug squashing party. Doesn't that look delicious?

  22. Bugs were squashed and #reproducible (?) pizza was baked in Darmstadt at the #NixOS 26.05 bug squashing party. Doesn't that look delicious?

  23. Bugs were squashed and #reproducible (?) pizza was baked in Darmstadt at the #NixOS 26.05 bug squashing party. Doesn't that look delicious?

  24. Bugs were squashed and #reproducible (?) pizza was baked in Darmstadt at the #NixOS 26.05 bug squashing party. Doesn't that look delicious?

  25. I've just updated the Reproducible project template repo based on a few small #reproducible research websites I've needed to create. This workflow is now my default for doing talks and workshops, quicker than PowerPoint with many benefits! Details: robinlovelace.net/reproducible

  26. I've just updated the Reproducible project template repo based on a few small research websites I've needed to create. This workflow is now my default for doing talks and workshops, quicker than PowerPoint with many benefits! Details: robinlovelace.net/reproducible

  27. I've just updated the Reproducible project template repo based on a few small #reproducible research websites I've needed to create. This workflow is now my default for doing talks and workshops, quicker than PowerPoint with many benefits! Details: robinlovelace.net/reproducible

  28. I've just updated the Reproducible project template repo based on a few small #reproducible research websites I've needed to create. This workflow is now my default for doing talks and workshops, quicker than PowerPoint with many benefits! Details: robinlovelace.net/reproducible

  29. I've just updated the Reproducible project template repo based on a few small #reproducible research websites I've needed to create. This workflow is now my default for doing talks and workshops, quicker than PowerPoint with many benefits! Details: robinlovelace.net/reproducible

  30. Listening to Bernhard M. Wiedemann talking at #oSC26 about:

    What happened with #reproducible #builds in @opensuse and #SLES

    events.opensuse.org/conference

    Once upon a time the syslog-ng project also did a couple of changes to allow reproducible builds (no timestamp or git hash).

  31. Listening to Bernhard M. Wiedemann talking at about:

    What happened with in @opensuse and

    events.opensuse.org/conference

    Once upon a time the syslog-ng project also did a couple of changes to allow reproducible builds (no timestamp or git hash).

  32. Listening to Bernhard M. Wiedemann talking at #oSC26 about:

    What happened with #reproducible #builds in @opensuse and #SLES

    events.opensuse.org/conference

    Once upon a time the syslog-ng project also did a couple of changes to allow reproducible builds (no timestamp or git hash).

  33. Listening to Bernhard M. Wiedemann talking at #oSC26 about:

    What happened with #reproducible #builds in @opensuse and #SLES

    events.opensuse.org/conference

    Once upon a time the syslog-ng project also did a couple of changes to allow reproducible builds (no timestamp or git hash).

  34. Listening to Bernhard M. Wiedemann talking at #oSC26 about:

    What happened with #reproducible #builds in @opensuse and #SLES

    events.opensuse.org/conference

    Once upon a time the syslog-ng project also did a couple of changes to allow reproducible builds (no timestamp or git hash).

  35. 📣 The Turing Way’s June Community Forum!

    Join our second Community Forum of 2026:
    🗓 25th June 2026
    ⏰ 5:00 PM (UK), 6:00 PM (Central Europe), 12:00 PM (Eastern US), 9:00 AM (Western US)

    🔍 What to expect:
    - Insights from our working groups and projects
    - Highlights from our steering committee
    - A focused discussion on our work with JupyterHub

    👉 Register here: forms.gle/GapNn9Vx8aMz8o6A7

    Let’s come together to share, learn, and shape what’s next 🚀

    #openscience #openresearch #reproducible

  36. 📣 The Turing Way’s June Community Forum!

    Join our second Community Forum of 2026:
    🗓 25th June 2026
    ⏰ 5:00 PM (UK), 6:00 PM (Central Europe), 12:00 PM (Eastern US), 9:00 AM (Western US)

    🔍 What to expect:
    - Insights from our working groups and projects
    - Highlights from our steering committee
    - A focused discussion on our work with JupyterHub

    👉 Register here: forms.gle/GapNn9Vx8aMz8o6A7

    Let’s come together to share, learn, and shape what’s next 🚀

  37. 📣 The Turing Way’s June Community Forum!

    Join our second Community Forum of 2026:
    🗓 25th June 2026
    ⏰ 5:00 PM (UK), 6:00 PM (Central Europe), 12:00 PM (Eastern US), 9:00 AM (Western US)

    🔍 What to expect:
    - Insights from our working groups and projects
    - Highlights from our steering committee
    - A focused discussion on our work with JupyterHub

    👉 Register here: forms.gle/GapNn9Vx8aMz8o6A7

    Let’s come together to share, learn, and shape what’s next 🚀

    #openscience #openresearch #reproducible

  38. 📣 The Turing Way’s June Community Forum!

    Join our second Community Forum of 2026:
    🗓 25th June 2026
    ⏰ 5:00 PM (UK), 6:00 PM (Central Europe), 12:00 PM (Eastern US), 9:00 AM (Western US)

    🔍 What to expect:
    - Insights from our working groups and projects
    - Highlights from our steering committee
    - A focused discussion on our work with JupyterHub

    👉 Register here: forms.gle/GapNn9Vx8aMz8o6A7

    Let’s come together to share, learn, and shape what’s next 🚀

    #openscience #openresearch #reproducible

  39. 📣 The Turing Way’s June Community Forum!

    Join our second Community Forum of 2026:
    🗓 25th June 2026
    ⏰ 5:00 PM (UK), 6:00 PM (Central Europe), 12:00 PM (Eastern US), 9:00 AM (Western US)

    🔍 What to expect:
    - Insights from our working groups and projects
    - Highlights from our steering committee
    - A focused discussion on our work with JupyterHub

    👉 Register here: forms.gle/GapNn9Vx8aMz8o6A7

    Let’s come together to share, learn, and shape what’s next 🚀

    #openscience #openresearch #reproducible

  40. Great to be in #Estonia again! I'm here for the #MobileTartu conference and will be teaching Data Science for Transport Planning. For anyone unable to make it in person but interested in the topic, you can follow the #openaccess materials here: tdscience.github.io/tartu26/ #reproducible #datascience

  41. Great to be in again! I'm here for the conference and will be teaching Data Science for Transport Planning. For anyone unable to make it in person but interested in the topic, you can follow the materials here: tdscience.github.io/tartu26/

  42. Great to be in #Estonia again! I'm here for the #MobileTartu conference and will be teaching Data Science for Transport Planning. For anyone unable to make it in person but interested in the topic, you can follow the #openaccess materials here: tdscience.github.io/tartu26/ #reproducible #datascience

  43. Great to be in #Estonia again! I'm here for the #MobileTartu conference and will be teaching Data Science for Transport Planning. For anyone unable to make it in person but interested in the topic, you can follow the #openaccess materials here: tdscience.github.io/tartu26/ #reproducible #datascience

  44. Great to be in #Estonia again! I'm here for the #MobileTartu conference and will be teaching Data Science for Transport Planning. For anyone unable to make it in person but interested in the topic, you can follow the #openaccess materials here: tdscience.github.io/tartu26/ #reproducible #datascience

  45. Learn how to use Go Modules for effective dependency management, version control, and reproducible builds in Go projects. Master best practices for initializing, managing, and securing Go modules in modern development workflows.

    #Go Modules #dependency management #semantic versioning #Go 1.22 #reproducible builds

    dasroot.net/posts/2026/02/go-m

  46. Learn how to use Go Modules for effective dependency management, version control, and reproducible builds in Go projects. Master best practices for initializing, managing, and securing Go modules in modern development workflows.

    #Go Modules #dependency management #semantic versioning #Go 1.22 #reproducible builds

    dasroot.net/posts/2026/02/go-m

  47. Learn how to use Go Modules for effective dependency management, version control, and reproducible builds in Go projects. Master best practices for initializing, managing, and securing Go modules in modern development workflows.

    #Go Modules #dependency management #semantic versioning #Go 1.22 #reproducible builds

    dasroot.net/posts/2026/02/go-m

  48. Learn how to use Go Modules for effective dependency management, version control, and reproducible builds in Go projects. Master best practices for initializing, managing, and securing Go modules in modern development workflows.

    #Go Modules #dependency management #semantic versioning #Go 1.22 #reproducible builds

    dasroot.net/posts/2026/02/go-m

  49. Learn how to use Go Modules for effective dependency management, version control, and reproducible builds in Go projects. Master best practices for initializing, managing, and securing Go modules in modern development workflows.

    Modules management versioning 1.22 builds

    dasroot.net/posts/2026/02/go-m

  50. Dear opensource developers,

    I added an "adoption" list to the repro-env README, if you publish pre-compiled binaries and you successfully adopted it to allow anyone to reproduce them from source code to prove the absense of a build server compromise, you are very welcome to add yourself to the list. 😺

    github.com/kpcyrd/repro-env#ad

    #reproducible #reproduciblebuilds #supplychainsecurity #rust

  51. Dear opensource developers,

    I added an "adoption" list to the repro-env README, if you publish pre-compiled binaries and you successfully adopted it to allow anyone to reproduce them from source code to prove the absense of a build server compromise, you are very welcome to add yourself to the list. 😺

    github.com/kpcyrd/repro-env#ad

    #reproducible #reproduciblebuilds #supplychainsecurity #rust

  52. Dear opensource developers,

    I added an "adoption" list to the repro-env README, if you publish pre-compiled binaries and you successfully adopted it to allow anyone to reproduce them from source code to prove the absense of a build server compromise, you are very welcome to add yourself to the list. 😺

    github.com/kpcyrd/repro-env#ad

    #reproducible #reproduciblebuilds #supplychainsecurity #rust

  53. Dear opensource developers,

    I added an "adoption" list to the repro-env README, if you publish pre-compiled binaries and you successfully adopted it to allow anyone to reproduce them from source code to prove the absense of a build server compromise, you are very welcome to add yourself to the list. 😺

    github.com/kpcyrd/repro-env#ad

    #reproducible #reproduciblebuilds #supplychainsecurity #rust

  54. Dear opensource developers,

    I added an "adoption" list to the repro-env README, if you publish pre-compiled binaries and you successfully adopted it to allow anyone to reproduce them from source code to prove the absense of a build server compromise, you are very welcome to add yourself to the list. 😺

    github.com/kpcyrd/repro-env#ad

    #reproducible #reproduciblebuilds #supplychainsecurity #rust