home.social

Search

297 results for “nlnetlabs”

  1. @nlnetlabs @fedora First discovery is that we do not have even library in Fedora yet. That man openssl-quic can already provide client connection API, but server API is not yet available via releases. There is openssl+quic fork, which is unlikely to ever be in Fedora. We could end with unbound linked to openssl, but libngtcp2 linked to gnutls. Definitely not as straight forward as I have expected.

  2. #programmation #eroom #décroissance

    Avec l'augmentation du prix des mémoires (quand on en trouve !), on est obligés d'être plus frugal : blog.nlnetlabs.nl/smaller-fast

    Fini de se vautrer dans la RAM comme si elle était infinie.

  3. Cascade is de nieuwe DNSSEC-handtekeningsoplossing van NLnet Labs die OpenDNSSEC moet vervangen.
    Op de NLUUG voorjaarsconferentie van 7 mei 2026 zal Jan-Piet Mens (@jpmens) Cascade aan ons voorstellen, enkele functies bespreken en natuurlijk demonstreren hoe je een zone ermee ondertekent.

    Kijk voor het hele programma op nluug.nl/evenementen/nluug/voo
    Schrijf je in voor deze dag en zie je op de voorjaarsconferentie!

    #NLUUG is dé vereniging voor (professionele) gebruikers van UNIX/Linux, #OpenSource, #OpenSystemen en #OpenStandaarden in NL.

  4. Back from and straight into building High Availability with multiple active nodes for our CA software Krill. github.com/NLnetLabs/krill/iss

  5. We're excited to hear real world experiences running NSD with AF_XDP enabled. Please share your performance numbers and hardware specs! #XFP #EBPF #DNS #OpenSource
    social.nlnetlabs.nl/@nlnetlabs

  6. @drk is giving a talk on Rotonda, our #bgp collector/monitor/alerter, right now at #NLNOG day.

  7. At , @maarten and @romdalf organised a session about how regulating software for the European market could impact . A series of lightning talks is followed by a panel discussion covering the , the and the possible effects of them. You can now watch the recording of this session.
    fosdem.org/2023/schedule/event

  8. I was also involved in bringing the #CyberResilienceAct to #FOSDEM this year:

    fosdem.org/2023/schedule/event

    First, introductory lightning talks by the @EU_Commission introducing the audience to the proposals for a CRA and new #ProductLiabilityDirective. I'll share a @nlnetlabs perspective on the CRA.

    This introduction is then followed by a panel led by Red Hat's @romdalf
    (w/ @gijs and other great panelists) to hear different perspectives on the proposals.

    Looking forward to it!

  9. Another little research project we're still tinkering with after the Hackathon is Encrypted Client Hello () for our connectbyname library. We'll be taking these experiences forward in our comprehensive tooling for . github.com/NLnetLabs/connectby

  10. Question in relation to our signing project Nameshed: does anyone have operational experiences with for interfacing with HSMs, as an alternative to PKCS#11? We'd love to hear from you. — Boosts appreciated 💚

  11. Awesome to see the switchover from #DNSSEC records signed by the old key to those signed by the new key. #KeyRoll #KSKRoll #KSKRollover (See live(ish) graph at nlnetlabs.nl )

  12. While Willem was chairing the working group at , the crew back in the office was hard at work with fancy new `dnsi` features. blog.nlnetlabs.nl/newsletter-m

  13. @nlnet @NGIZero @nlnetlabs Welcome! And thanks for funding the #OpenWebCalendar
    Thanks to your funding, the project now has a #documentation website in German, Spanish and English: open-web-calendar.quelltext.eu
    🧡

  14. The initial deployment of the Stable Cascade (SC) on the AI Horde supported just text2image workflows, but that was just a subset of what this model can do. We still needed to onboard the rest of its capabilities.

    One such capability was the “image variations” option, which allows you to send an image to the model, and get a variation of that image, perhaps with extra stuff added in, using the unClip technology. This required quite a bit of work on hordelib so that it uses a completely different ComfyUI workflow but ultimately this was not so much harder than just adding the img2img capabilities to SC.

    The larger difficulty came when I wanted to add the feature to remix multiple images together. The problem being that until now the AI Horde only supported sending a single source image and a single source mask, so a varying amount of images was not possible at all.

    So to support this, I needed to touch all areas of the AI Horde. The AI Horde had to accept and upload each of them on my R2 bucket and provide individual download links. The SDK had to know to expect and provide methods to download those images in parallel to avoid delays, to the reGen worker had to be able to receive those images and send them to hordelib which should know how to dynamically adjust a comfyUI pipeline on-the-fly to add as many extra nodes as required.

    So after 2 weeks of developing and testing, we finally have this feature available. If your Horde front-end supports the “remix” feature. You can send up to 1-6 images to this workflow along with a prompt, and it will try its best to “squash” them all together into one composition. Note that the more images you send, and the larger the prompt, the harder it will be for the model to “retain” all of them in the composition. But it will try its best.

    As an example, here’s how the model remixes my own avatar. You’ll notice that the result can understand the general concepts of the image, but can’t follow it exactly as it’s not doing img2img. The blur is probably caused by the need to upscale my original image, which is something I’d like to fix on the next pass.

    Original AvatarRemix Avatar

    Likewise, this is the Haidra logo

    Original LogoRemix Logo

    And finally, here’s a remix of both logo and avatar together

    Pretty neat, huh?

    This ability to send extra source images also lays the groundwork for the Horde to support things like InstantID, which I hope I’ll be able to work on supporting soon enough.

    https://dbzer0.com/blog/image-remix-on-the-ai-horde/

    #aiHorde #nlnetTask #stableCascade

  15. The initial deployment of the Stable Cascade (SC) on the AI Horde supported just text2image workflows, but that was just a subset of what this model can do. We still needed to onboard the rest of its capabilities.

    One such capability was the “image variations” option, which allows you to send an image to the model, and get a variation of that image, perhaps with extra stuff added in, using the unClip technology. This required quite a bit of work on hordelib so that it uses a completely different ComfyUI workflow but ultimately this was not so much harder than just adding the img2img capabilities to SC.

    The larger difficulty came when I wanted to add the feature to remix multiple images together. The problem being that until now the AI Horde only supported sending a single source image and a single source mask, so a varying amount of images was not possible at all.

    So to support this, I needed to touch all areas of the AI Horde. The AI Horde had to accept and upload each of them on my R2 bucket and provide individual download links. The SDK had to know to expect and provide methods to download those images in parallel to avoid delays, to the reGen worker had to be able to receive those images and send them to hordelib which should know how to dynamically adjust a comfyUI pipeline on-the-fly to add as many extra nodes as required.

    So after 2 weeks of developing and testing, we finally have this feature available. If your Horde front-end supports the “remix” feature. You can send up to 1-6 images to this workflow along with a prompt, and it will try its best to “squash” them all together into one composition. Note that the more images you send, and the larger the prompt, the harder it will be for the model to “retain” all of them in the composition. But it will try its best.

    As an example, here’s how the model remixes my own avatar. You’ll notice that the result can understand the general concepts of the image, but can’t follow it exactly as it’s not doing img2img. The blur is probably caused by the need to upscale my original image, which is something I’d like to fix on the next pass.

    Original AvatarRemix Avatar

    Likewise, this is the Haidra logo

    Original LogoRemix Logo

    And finally, here’s a remix of both logo and avatar together

    Pretty neat, huh?

    This ability to send extra source images also lays the groundwork for the Horde to support things like InstantID, which I hope I’ll be able to work on supporting soon enough.

    https://dbzer0.com/blog/image-remix-on-the-ai-horde/

    #aiHorde #nlnetTask #stableCascade

  16. The initial deployment of the Stable Cascade (SC) on the AI Horde supported just text2image workflows, but that was just a subset of what this model can do. We still needed to onboard the rest of its capabilities.

    One such capability was the “image variations” option, which allows you to send an image to the model, and get a variation of that image, perhaps with extra stuff added in, using the unClip technology. This required quite a bit of work on hordelib so that it uses a completely different ComfyUI workflow but ultimately this was not so much harder than just adding the img2img capabilities to SC.

    The larger difficulty came when I wanted to add the feature to remix multiple images together. The problem being that until now the AI Horde only supported sending a single source image and a single source mask, so a varying amount of images was not possible at all.

    So to support this, I needed to touch all areas of the AI Horde. The AI Horde had to accept and upload each of them on my R2 bucket and provide individual download links. The SDK had to know to expect and provide methods to download those images in parallel to avoid delays, to the reGen worker had to be able to receive those images and send them to hordelib which should know how to dynamically adjust a comfyUI pipeline on-the-fly to add as many extra nodes as required.

    So after 2 weeks of developing and testing, we finally have this feature available. If your Horde front-end supports the “remix” feature. You can send up to 1-6 images to this workflow along with a prompt, and it will try its best to “squash” them all together into one composition. Note that the more images you send, and the larger the prompt, the harder it will be for the model to “retain” all of them in the composition. But it will try its best.

    As an example, here’s how the model remixes my own avatar. You’ll notice that the result can understand the general concepts of the image, but can’t follow it exactly as it’s not doing img2img. The blur is probably caused by the need to upscale my original image, which is something I’d like to fix on the next pass.

    Original AvatarRemix Avatar

    Likewise, this is the Haidra logo

    Original LogoRemix Logo

    And finally, here’s a remix of both logo and avatar together

    Pretty neat, huh?

    This ability to send extra source images also lays the groundwork for the Horde to support things like InstantID, which I hope I’ll be able to work on supporting soon enough.

    https://dbzer0.com/blog/image-remix-on-the-ai-horde/

    #aiHorde #nlnetTask #stableCascade

  17. The initial deployment of the Stable Cascade (SC) on the AI Horde supported just text2image workflows, but that was just a subset of what this model can do. We still needed to onboard the rest of its capabilities.

    One such capability was the “image variations” option, which allows you to send an image to the model, and get a variation of that image, perhaps with extra stuff added in, using the unClip technology. This required quite a bit of work on hordelib so that it uses a completely different ComfyUI workflow but ultimately this was not so much harder than just adding the img2img capabilities to SC.

    The larger difficulty came when I wanted to add the feature to remix multiple images together. The problem being that until now the AI Horde only supported sending a single source image and a single source mask, so a varying amount of images was not possible at all.

    So to support this, I needed to touch all areas of the AI Horde. The AI Horde had to accept and upload each of them on my R2 bucket and provide individual download links. The SDK had to know to expect and provide methods to download those images in parallel to avoid delays, to the reGen worker had to be able to receive those images and send them to hordelib which should know how to dynamically adjust a comfyUI pipeline on-the-fly to add as many extra nodes as required.

    So after 2 weeks of developing and testing, we finally have this feature available. If your Horde front-end supports the “remix” feature. You can send up to 1-6 images to this workflow along with a prompt, and it will try its best to “squash” them all together into one composition. Note that the more images you send, and the larger the prompt, the harder it will be for the model to “retain” all of them in the composition. But it will try its best.

    As an example, here’s how the model remixes my own avatar. You’ll notice that the result can understand the general concepts of the image, but can’t follow it exactly as it’s not doing img2img. The blur is probably caused by the need to upscale my original image, which is something I’d like to fix on the next pass.

    Original AvatarRemix Avatar

    Likewise, this is the Haidra logo

    Original LogoRemix Logo

    And finally, here’s a remix of both logo and avatar together

    Pretty neat, huh?

    This ability to send extra source images also lays the groundwork for the Horde to support things like InstantID, which I hope I’ll be able to work on supporting soon enough.

    https://dbzer0.com/blog/image-remix-on-the-ai-horde/

    #aiHorde #nlnetTask #stableCascade

  18. Nice – :MW: MOULE WORLD is in the Phonebook of the Internet, listed 5 websites before the website of the Moulin Rouge!

    If there's any DNS errors, you can try visiting a website by its IPv4 address.

    nlnetlabs.nl/news/2025/Apr/01/

    #MouleWorld #PhoneBookOfTheInternet #NLnet

  19. Looking forward to present @nlnetlabs’ research on TLD operations in the #DNSSEC and Security Workshop at #ICANN84, starting today at 13:15 hrs UTC.

  20. @jpmens I was there for the announcement and previously had the opportunity to submit some requirement/ideas for #Nameshed.
    Nameshed seems well-designed, uses an efficient programming language (#Rust ) and builds on the experience from #OpenDNSSEC and the tooling from other Rust-based software from @nlnetlabs
    I will regret #OpenDNSSEC that served me well but I am waiting to get my hands on #Nameshed first release.
    I already felt this way: m.youtube.com/watch?v=Cl7xQ8i3 ;-)