Cryptography nerd

Fediverse accounts;
Natanael@slrpnk.net (main)
Natanael@infosec.pub
Natanael@lemmy.zip

Lemmy moderation account: @TrustedThirdParty@infosec.pub - !crypto@infosec.pub

@Natanael_L@mastodon.social

Bluesky: natanael.bsky.social

  • 0 Posts
  • 20 Comments
Joined 5 months ago
cake
Cake day: January 18th, 2025

help-circle

  • You could import fabric physics and just have it lie there, but that’s going to be a bigger hit on performance than you possibly can imagine and it will move weirdly (in large part becomes we’re not modeling wind, just fabric in a vacuum) and the model features it will lie on top of won’t deform accurately from the simulated weight, etc…












  • It’s kinda comparable in terms, but because both licenses have comparable copyleft “no rights may be removed and no terms added” restrictions they conflict and can’t be merged.

    CDDL came after GPL, and I’m not convinced by the arguments for why it was used (to make some kind of development with commercial modules easier, but this could’ve been done with GPL + exceptions)

    That license plus patents (which only are freely licensed to the CDDL implementation specifically) means you can’t just rewrite it for Linux either. You’d have to wait for the patents to expire and then do clean room reverse engineering.





  • If you’ve already noticed incoming traffic is weird, you try to look for what distinguishes the sources you don’t want. You write rules looking at the behaviors like user agent, order of requests, IP ranges, etc, and put it in your web server and tells it to check if the incoming request matches the rules as a session starts.

    Unless you’re a high value target for them, they won’t put endless resources into making their systems mimic regular clients. They might keep changing IP ranges, but that usually happens ~weekly and you can just check the logs and ban new ranges within minutes. Changing client behavior to blend in is harder at scale - bots simply won’t look for the same things as humans in the same ways, they’re too consistent, even when they try to be random they’re too consistently random.

    When enough rules match, you throw in either a redirect or an internal URL rewrite rule for that session to point them to something different.



  • The steam controller didn’t really fail, but the patent fight was a mess that took way too long (much too late disqualified patent over paddle buttons). That sucked a lot of energy out of the project. Don’t forget the steam deck kept those touch pads (although with a different design)!

    Steam Link IMHO also wasn’t bad, but there didn’t seem to be much interest in it then. (interestingly enough I think it could be recreated today in a Chromecast-like form factor)

    Stream machines was definitely a big mess however, there just wasn’t enough interest, too limited compatibility, the machines just wasn’t versatile enough for average Joe to pay for one.


  • Natanael@infosec.pubtolinuxmemes@lemmy.worldWhats his problem?
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    edit-2
    4 months ago

    “yes”? He’s definitely not building any significant fraction himself, but if he didn’t care for these things he wouldn’t let the company put so much resources into them.

    Credit for the things built goes to the people building them. Credit for it being possible to build goes to the people who founded and funded the teams