home.social

Search

1000 results for “DrHyde”

  1. I'm so glad that #ChinaPost so thoughtfully did a careful safety inspection on this #postcard 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 #MaoTseTungThought corrupted.

    #Chinese #PostCrossing #WorldAltTextChampionshipEntry

  2. I'm so glad that #ChinaPost so thoughtfully did a careful safety inspection on this #postcard 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 #MaoTseTungThought corrupted.

    #Chinese #PostCrossing #WorldAltTextChampionshipEntry

  3. I'm so glad that #ChinaPost so thoughtfully did a careful safety inspection on this #postcard 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 #MaoTseTungThought corrupted.

    #Chinese #PostCrossing #WorldAltTextChampionshipEntry

  4. I'm so glad that #ChinaPost so thoughtfully did a careful safety inspection on this #postcard 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 #MaoTseTungThought corrupted.

    #Chinese #PostCrossing #WorldAltTextChampionshipEntry

  5. 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

  6. 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

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

  8. 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

  9. 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

  10. @ChuckMcManis @lcamtuf are the crowd working from the C source (in which case these bugs are really really stupid) or are they writing code /de novo/ based on a spec? If the latter then these bugs are understandable, provided that they are dealt with when reported.

    The real problem here though is Ubuntu, just changing stuff for teh lolz.

  11. @ChuckMcManis @lcamtuf are the #uutils crowd working from the C source (in which case these bugs are really really stupid) or are they writing code /de novo/ based on a spec? If the latter then these bugs are understandable, provided that they are dealt with when reported.

    The real problem here though is Ubuntu, just changing stuff for teh lolz.

  12. @ChuckMcManis @lcamtuf are the #uutils crowd working from the C source (in which case these bugs are really really stupid) or are they writing code /de novo/ based on a spec? If the latter then these bugs are understandable, provided that they are dealt with when reported.

    The real problem here though is Ubuntu, just changing stuff for teh lolz.

  13. @ChuckMcManis @lcamtuf are the #uutils crowd working from the C source (in which case these bugs are really really stupid) or are they writing code /de novo/ based on a spec? If the latter then these bugs are understandable, provided that they are dealt with when reported.

    The real problem here though is Ubuntu, just changing stuff for teh lolz.

  14. @ChuckMcManis @lcamtuf are the #uutils crowd working from the C source (in which case these bugs are really really stupid) or are they writing code /de novo/ based on a spec? If the latter then these bugs are understandable, provided that they are dealt with when reported.

    The real problem here though is Ubuntu, just changing stuff for teh lolz.

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

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

    #wizard #emoji

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

    #wizard #emoji

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

    #wizard #emoji

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

    #wizard #emoji

  20. And after a heroic evening of saving the polar bears and poor people, time to go to bed, with the latest podcast from the #LatinMassSociety!

  21. And after a heroic evening of saving the polar bears and poor people, time to go to bed, with the latest podcast from the !

  22. And after a heroic evening of saving the polar bears and poor people, time to go to bed, with the latest podcast from the #LatinMassSociety!

  23. And after a heroic evening of saving the polar bears and poor people, time to go to bed, with the latest podcast from the #LatinMassSociety!

  24. And after a heroic evening of saving the polar bears and poor people, time to go to bed, with the latest podcast from the #LatinMassSociety!

  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 , 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

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

  29. 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