home.social

Search

72 results for “bsdphk”

  1. @bsdphk Wonder if this will affect #Fastly's use of Varnish, or perhaps they are big enough to simply pay the licensing fees?

  2. RE: fosstodon.org/@bsdphk/11641975

    Back in the 1980s when I was but a larval programmer my father, who worked on the railways, heard about , and tried to encourage me to give it a whirl, as it would surely be what everyone used in the future. There was even a compiler available for CP/M that I could have used at home. I took one look at it and decided that writing Z80 assembler was easier and therefore better. It was, of course, only easier because I already knew it. And so I have never used Ada.

  3. '“We’re gonna remake our airspace,” Duffy continued. “And we’re gonna do it quickly, and we have the support of the Congress, I think right now, to say, you know what, we’re using like 1960s, World War II technology in much of the components of the airspace. We’re gonna upgrade it.”' #fearofflying @bsdphk yahoo.com/news/musk-cost-cutte

  4. Varnish Cache project to change its name to Vinyl Cache with after the next release (after today's 8.0.0, in March), per @bsdphk:

    We have tried to negotiate with Varnish Software for many months about this issue, but their IP-Lawyers still insist that Varnish Software owns the Varnish Cache name, and at most we have being offered a strictly limited, subject to their veto, permission for the FOSS project to use the “Varnish Cache” name.

    We cannot live with that: We are independent FOSS project with our own name.

    So we will change the name of the project.

    The new association and the new project will be named “The Vinyl Cache Project”, and this release 8.0.0, will be the last under the “Varnish Cache” name. The next release, in March will be under the new name, and will include compatibility scripts, to make the transition as smooth as possible for everybody.

    fosstodon.org/@bsdphk/11520890

    #VarnishCache #VinylCache

  5. @slink @jandi @overunderlay @esoteric_programmer @bsdphk awww thank you Nils! ❤️​

    You have no idea how grateful I am for #VarnishCache. It's a real gem, protecting my site against the Mastodon stampede. Nothing else worked before.

    Bravissimo for the great work on it 🙌​

  6. @jandi thank you for letting me know about the two LEGENDS responsible for #VarnishCache (aka my favorite discovery in this 7-month self-hosting journey) 🙌✨❤️

    @overunderlay @esoteric_programmer @bsdphk @slink

  7. Unless you need ultra-low latency, a nothingburger: When retrieving @bsdphk 's benchtime I discovered MarkMail.org died; wanted to evaluate claims made in an article linked by @fanf for not relying on vDSO for POSIX #clock_gettime in contemporary #Linux and #FreeBSD .. It could be rewritten from its very brief functional description in my PhD thesis: "The benchtime program computes the mean [delta] over 2M samples where the ... function has returned an updated value."
    hmpcabral.com/2026/04/26/the-f

  8. Unless you need ultra-low latency, a nothingburger: When retrieving @bsdphk 's benchtime I discovered MarkMail.org died; wanted to evaluate claims made in an article linked by @fanf for not relying on vDSO for POSIX #clock_gettime in contemporary #Linux and #FreeBSD .. It could be rewritten from its very brief functional description in my PhD thesis: "The benchtime program computes the mean [delta] over 2M samples where the ... function has returned an updated value."
    hmpcabral.com/2026/04/26/the-f

  9. Unless you need ultra-low latency, a nothingburger: When retrieving @bsdphk 's benchtime I discovered MarkMail.org died; wanted to evaluate claims made in an article linked by @fanf for not relying on vDSO for POSIX #clock_gettime in contemporary #Linux and #FreeBSD .. It could be rewritten from its very brief functional description in my PhD thesis: "The benchtime program computes the mean [delta] over 2M samples where the ... function has returned an updated value."
    hmpcabral.com/2026/04/26/the-f

  10. Unless you need ultra-low latency, a nothingburger: When retrieving @bsdphk 's benchtime I discovered MarkMail.org died; wanted to evaluate claims made in an article linked by @fanf for not relying on vDSO for POSIX #clock_gettime in contemporary #Linux and #FreeBSD .. It could be rewritten from its very brief functional description in my PhD thesis: "The benchtime program computes the mean [delta] over 2M samples where the ... function has returned an updated value."
    hmpcabral.com/2026/04/26/the-f

  11. Unless you need ultra-low latency, a nothingburger: When retrieving @bsdphk 's benchtime I discovered MarkMail.org died; wanted to evaluate claims made in an article linked by @fanf for not relying on vDSO for POSIX #clock_gettime in contemporary #Linux and #FreeBSD .. It could be rewritten from its very brief functional description in my PhD thesis: "The benchtime program computes the mean [delta] over 2M samples where the ... function has returned an updated value."
    hmpcabral.com/2026/04/26/the-f

  12. Dette glimrende indlæg mindede mig om det lige så glimrende forslag fra @bsdphk om at værdiansætte boliger via ‘Texas shoot-out clause’ - det kunne selvsagt også bruges til værdiansættelse af virksomheder man gerne vil arvebeskatte.

    jyllands-posten.dk/debat/kroni #dkpol #dkøko

  13. just had a "@bsdphk told us so" moment when @pid_eins said in his talk something along the lines of "now that they are JSON, i can finally understand what my bus calls do when looking at strace output"

  14. just had a "@bsdphk told us so" moment when @pid_eins said in his #varlink talk something along the lines of "now that they are JSON, i can finally understand what my bus calls do when looking at strace output"
    #allsystemsgo #ASG2024

  15. just had a "@bsdphk told us so" moment when @pid_eins said in his #varlink talk something along the lines of "now that they are JSON, i can finally understand what my bus calls do when looking at strace output"
    #allsystemsgo #ASG2024

  16. just had a "@bsdphk told us so" moment when @pid_eins said in his #varlink talk something along the lines of "now that they are JSON, i can finally understand what my bus calls do when looking at strace output"
    #allsystemsgo #ASG2024

  17. just had a "@bsdphk told us so" moment when @pid_eins said in his #varlink talk something along the lines of "now that they are JSON, i can finally understand what my bus calls do when looking at strace output"
    #allsystemsgo #ASG2024

  18. @spz @vriesk @bsdphk At least this will safe #WindowsEmbedded from obscurity, they will be able to provide their customers with some insurance.

  19. @SteveBellovin @hpk

    Not to #bikeshed but...

    In my experience asking "whom?" only works if the person you ask have a competent(-ish) threat-model, which no normal people do.

    The implicit focus on intentionality also downplays the much more frequent accidental loss of control.

    At least for me, it works better to ask what outcomes we are trying to avoid, and work through both the intentional, incidental and accidental scenarios that lead there.

  20. @SteveBellovin @hpk

    Not to but...

    In my experience asking "whom?" only works if the person you ask have a competent(-ish) threat-model, which no normal people do.

    The implicit focus on intentionality also downplays the much more frequent accidental loss of control.

    At least for me, it works better to ask what outcomes we are trying to avoid, and work through both the intentional, incidental and accidental scenarios that lead there.

  21. @SteveBellovin @hpk

    Not to #bikeshed but...

    In my experience asking "whom?" only works if the person you ask have a competent(-ish) threat-model, which no normal people do.

    The implicit focus on intentionality also downplays the much more frequent accidental loss of control.

    At least for me, it works better to ask what outcomes we are trying to avoid, and work through both the intentional, incidental and accidental scenarios that lead there.

  22. @SteveBellovin @hpk

    Not to #bikeshed but...

    In my experience asking "whom?" only works if the person you ask have a competent(-ish) threat-model, which no normal people do.

    The implicit focus on intentionality also downplays the much more frequent accidental loss of control.

    At least for me, it works better to ask what outcomes we are trying to avoid, and work through both the intentional, incidental and accidental scenarios that lead there.