I’m also on Mastodon as https://hachyderm.io/@BoydStephenSmithJr .

  • 1 Post
  • 56 Comments
Joined 2 years ago
cake
Cake day: October 2nd, 2023

help-circle

  • bss03@infosec.pubtoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    23 hours ago

    No, I think more MS users = MS shady shit. So, to discourage MS shady shit, I encourage people to not use MS software. I also think that people who are worried about abuse by priests should not tithe or otherwise donate to Catholic churches (belief matters less than action here; and it’s less reasonable to swap out belief system, I guess.)

    That’s why your analogy seems backwards to me.

    Doesn’t matter anyway. I guess I just don’t get it. Have a nice day.





  • I’m been using Linux full time since 2004, and while I think it is good to let people know it is there, I don’t recommend it to people I’m not willing to personally support. But, I also let them know I just can’t help with Windows problems either, and they should address their complaints to their OS vendor.

    I file Debian bugs if I have a problem with my OS, and have received fixes that way. This is better support that I ever received from MS during my first 2 decades of using MS OSes.





  • Yeah, we’d have to shift tactics. But, without IP law protections, the hacker community would double down on reverse engineering and binary patching. Debian etc. would still be available, but you’d also see spins on Adobe, Apple, Microsoft, and Google software based on decompiling, patching, and rebuilding, or just game genie / PC game cracks binary patching based on offset and signature.

    The DMCA would dissolve and encrypted data that was expected to be decrypted on the fly (“streaming only”) would just be published fully decrypted.

    It would be a revolutionary shift, but I’m not convinced it would be worse.

    What would be worse is keeping IP law, but only having it enforced by million dollar yearly budget teams of lawyers and not protecting creators from having their works fed to “AI” and regurgitated as slop.





    1. No, we can test groksponk without flibbertygibbet. But, when rolling to production, flubbertygibbet will need to be in place before grokspunk due to how the gonksponk end-user documentation is written (at least, for now).

    2. Oh, sorry, “doohicky” is how me and my team call them. They are actually <link to ISO specification for purchase>, specifically chapter 4, section 2 (in my 2012 copy it is titled “Hippydip Operations and Serialization”). Hopefully that connects well with the existing goober documentation, but let me know if you need further details/clarification.


  • On average a communication has more readers than writers, so it is better for writer(s) to use effort in order to save effort on the behalf of the reader(s).

    This was especially true in the days of mailing lists and me having to beat TOFU users about the head with a clue-by-4. But, it remains true today. The median communication might be 1 to 1, but it’s much more frequent for additional readers to be added that additional writers, so maximum effort with writing is still true.

    But, man, it is annoys the heck out of me when I compose informative, contexual email/SMS with several open-ended questions and get back: “yes”.


  • While I don’t doubt this, I’m also sure that tarrifs will also affect the pricing/availability of utility (non-status symbol) mobile devices.

    We are going to have to deal with this for 4 years (unless some Rs will vote the remove in 2) and recovery won’t be immediate. I hope my current mobile lasts that long, but I usually only get about 3 years out of a battery. Replacement parts will be hit by tarrifs, too.