home.social

Search

243 results for “DrHyde”

  1. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  2. Grargh! hates extensions. And can't be configured to specifically use instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

  3. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  4. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  5. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  6. Oh how wonderful! I got a feature request for Number::Phone, asking me to add support for the format which is standardised in ITU-T . The request is in Github issue 164!

    github.com/DrHyde/perl-modules

  7. Re earlier toot ... as soon as I'd finished dealing with 's PRs, I wanted to use the script to view other peoples' PRs against my code (there are only two that I've not dealt with because I'm a good boy, although one has been festering for 7 years because I'm a bad boy), and then to see all my PRs against other peoples' code that are still open. And so the script got just a teensy bit bigger.

    github.com/DrHyde/shellscripts

  8. @DrHyde On behalf of us all, I apologise for our failure. You are right, that is very lax from us.

    I, of course, will be indulging in lots of during the coming weeks.

  9. @DrHyde @bmop So glad to see you’ve joined the Odyssey! We’re particularly proud of this collection of #opera collabs with @bmop because they’re all #worldpremiere recordings.

  10. Re earlier toot (fosstodon.org/@DrHyde/11517952) the release was further delayed by being bastards and breaking my CI by not letting me grab their data from within workflows, so I had to work around that. So that's more crawling horrors accreted onto the 20 years old that builds it all. Yay! But we have a release! The only changes are data updates and a tweak to cope with the 's new weirdness.

    @perl

  11. CW: letter to promote the fedi / shout-out for transit/ cycling/ walking/ neighbourhood accounts

    @unchartedworlds @futurebird
    Cool. I'll hold off on that, then.

    The travel / transit account I follow is really only @notjustbikes

    For topic-specific things I like following hashtags since I then get to see people that I would not normally pick up.

    I can recommend the hashtags: #CrossBorderRail
    #BikeTooter
    #WalkableCities
    #LowCar - actually, rather use #CarFree

    @jmax @DrHyde @craiglambie42 @gbargoud

  12. RE: mastodon.social/@simple_sabota

    Implausible ways seem to also work. See any infrastructure or housing development in the UK for examples.

  13. Outgoing as an unofficlal swap with a @postcrossing chum today. had "mad skills yo", and took an absolutely ridiculous 96 5-fers in 485 first class matches.

  14. Well fuck, I've started getting junk mail advertising life insurance, will writing, and funeral plans.

  15. Noooooo!!!!!!! is down!!!!!!

    I hope this means that the head 9front honcho is doing the yearly on-stage presentation about shiny new things we'll be able to buy later today!

  16. I'm so glad that so thoughtfully did a careful safety inspection on this that I got from a random stranger via @postcrossing. I can now rest assured that I won't get a paper cut from it, or have the purity of my corrupted.

  17. A very nice pair of pieces for all my chums to read today. The first summarises bugs in some code: seclists.org/oss-sec/2026/q2/3. The Rust code in question replaces older code which only didn't have those bugs because it had had 30 years of bug reports and patches. The second article dives into some common patterns patterns in the bugs. Those patterns will occur in code written in *every* language, so the lessons to be taken will apply to *you*: corrode.dev/blog/bugs-rust-won

  18. A very nice pair of pieces for all my #programmer chums to read today. The first summarises bugs in some #Rust code: seclists.org/oss-sec/2026/q2/3. The Rust code in question replaces older #C code which only didn't have those bugs because it had had 30 years of bug reports and patches. The second article dives into some common patterns patterns in the bugs. Those patterns will occur in code written in *every* language, so the lessons to be taken will apply to *you*: corrode.dev/blog/bugs-rust-won

    #bugs

  19. A very nice pair of pieces for all my #programmer chums to read today. The first summarises bugs in some #Rust code: seclists.org/oss-sec/2026/q2/3. The Rust code in question replaces older #C code which only didn't have those bugs because it had had 30 years of bug reports and patches. The second article dives into some common patterns patterns in the bugs. Those patterns will occur in code written in *every* language, so the lessons to be taken will apply to *you*: corrode.dev/blog/bugs-rust-won

    #bugs

  20. A very nice pair of pieces for all my #programmer chums to read today. The first summarises bugs in some #Rust code: seclists.org/oss-sec/2026/q2/3. The Rust code in question replaces older #C code which only didn't have those bugs because it had had 30 years of bug reports and patches. The second article dives into some common patterns patterns in the bugs. Those patterns will occur in code written in *every* language, so the lessons to be taken will apply to *you*: corrode.dev/blog/bugs-rust-won

    #bugs

  21. A very nice pair of pieces for all my #programmer chums to read today. The first summarises bugs in some #Rust code: seclists.org/oss-sec/2026/q2/3. The Rust code in question replaces older #C code which only didn't have those bugs because it had had 30 years of bug reports and patches. The second article dives into some common patterns patterns in the bugs. Those patterns will occur in code written in *every* language, so the lessons to be taken will apply to *you*: corrode.dev/blog/bugs-rust-won

    #bugs

  22. Important news! I can now type 🧙 on my keyboard.

  23. After my recent playing around with #Copilot, I thought I'd take a look at my Github billing report to see how much I'd used. I have, this month, used US$5.80 worth of Copilot ... and US$870 of actions.

    Most of those computrons got burned when #Dependabot pushed branches and then when it created pull requests so that it could whine at me about point releases of stuff like #CrossPlatformActions (github.com/cross-platform-acti).

    1/n

  24. After my recent playing around with , I thought I'd take a look at my Github billing report to see how much I'd used. I have, this month, used US$5.80 worth of Copilot ... and US$870 of actions.

    Most of those computrons got burned when pushed branches and then when it created pull requests so that it could whine at me about point releases of stuff like (github.com/cross-platform-acti).

    1/n

  25. After my recent playing around with #Copilot, I thought I'd take a look at my Github billing report to see how much I'd used. I have, this month, used US$5.80 worth of Copilot ... and US$870 of actions.

    Most of those computrons got burned when #Dependabot pushed branches and then when it created pull requests so that it could whine at me about point releases of stuff like #CrossPlatformActions (github.com/cross-platform-acti).

    1/n

  26. After my recent playing around with #Copilot, I thought I'd take a look at my Github billing report to see how much I'd used. I have, this month, used US$5.80 worth of Copilot ... and US$870 of actions.

    Most of those computrons got burned when #Dependabot pushed branches and then when it created pull requests so that it could whine at me about point releases of stuff like #CrossPlatformActions (github.com/cross-platform-acti).

    1/n

  27. After my recent playing around with #Copilot, I thought I'd take a look at my Github billing report to see how much I'd used. I have, this month, used US$5.80 worth of Copilot ... and US$870 of actions.

    Most of those computrons got burned when #Dependabot pushed branches and then when it created pull requests so that it could whine at me about point releases of stuff like #CrossPlatformActions (github.com/cross-platform-acti).

    1/n

  28. @manwar Test2 is great, but whenever I see something using yath on one of my testing machines it seems to be incredibly slow. Don't know why, and have better things to do than investigate, but that's put me off using it.