Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)RE
Posts
0
Comments
304
Joined
2 yr. ago

  • Future software is going to be written by AI

    Of course, if you look far enough into the future. Look far enough and the whole concept of "software" itself could become obsolete.

    The main disagreements are about how close that future is (years, decades, etc), and whether just expanding upon current approaches to AI will get us there, or we will need a completely different approach.

  • This is also the kind of task you would expect it to be great at - tutorial-friendly project for which there are tons of examples and articles written online, that guide the reader from start to finish.

    The kind of thing you would get a YouTube tutorial for in 2016 with title like "make [thing] in 10 minutes!". (see https://www.google.com/search?q=flappy+bird+in+10+minutes)

    Other things like that include TODO lists (which is even used as a task for framework comparisons), tile-based platformer games, wordle clones, flappy bird clones, chess (including online play and basic bots), URL shorteners, Twitter clones, blogging CMSs, recipe books and other basic CRUD apps.

    I wasn't able to find a list of tasks in the linked paper, but based on the gomoku one, I suspect a lot of it will be things like these.

  • It would be fine if the footage was end-to-end encrypted, meaning you need to transfer the encryption/decryption keys from device (e.g. a phone) to camera, and then manually between all devices that should have access to the decrypted footage.

    Camera would only ever send out encrypted footage, and thus it would be insufficient to have access to the cloud account if you want to view the footage - you would need both access to the account (to obtain the encrypted data) and the decryption key (to actually decrypt it). The decryption key must never reach any 3rd party servers and can only be manually transferred between devices that should have access.

    There are still possible attack vectors, like malicious firmware updates, or the viewer client app updates, but those are very difficult to exploit, and pretty much exist in most "secure" software today (including from companies like Google, Apple, Meta, etc.). They could be mitigated by hardware design (do the encryption in hardware, camera's software never has access to decrypted footage) and open source viewer clients that the user controls, but I would consider a camera sufficiently secure (for non-sensitive locations) without those.

  • It's just inherently suspicious, because there is no valid technical reason to do it that way (things just end up being more complicated, more expensive, etc., for no benefit, not to mention the brand damage), unless you have some future plans for it that will involve crypto/NFT crap. The fact that MrBeast has a history with NFTs also doesn't help.

    Or course it's still pure speculation.

    Have they explained why they chose to use it in some plausible way?

  • So basically admitting you don't know the actual history? Maybe start with reading a Wikipedia page or something.

    None of that excuses US war crimes in Vietnam, but it does show how a potential future with a hypothetical peace treaty could look like.

  • Not like that, lol

    Just saying, instead of this monstrosity

     
        
    CreateOrderRequest(user,
                       productDetails,
                       pricingCalculator,
                       order => order.internalNumber)
    
      

    Just use

     
        
    CreateOrderRequest(
        user,
        ...
    
      

    Putting the first argument on a separate line.

    Same if you have an if using a bunch of and (one condition per line, first one on a new line instead of same line as the if) and similar situations.

  • And you know how the Vietnam war ended, right?

    There was a peace agreement between the north and the south, and then a few years later North Vietnam broke it and invaded again, taking over all of the country.

  • Can you post any source at all that would back your claims? Or any technical details at all?

    Neither the actual proposal https://github.com/RupertBenWiser/Web-Environment-Integrity/blob/main/explainer.md#what-information-is-in-the-signed-attestation, nor the article itself seem to show that there would be a difference when it comes to privacy.

    The entire problem with this proposal is that it limits client choice, similar to how Google Play integrity API on Android restricts some apps from running on rooted/unlocked phones.

    That same problem obviously also exists in Apple's implementation.

  • Yes, people using it as the main messaging app is still preferable to the situation in the US where people on different mobile platforms can't message each other without bullshit compatibility issues and bubble colors.

    At least here it doesn't matter what platform you're on - including desktops and the web - and as a result nobody cares.

    Of course, the same is true for almost every other messaging service too, and there are better ones out there.

  • So you have zero evidence that this is actually happening?

    If it gives you video from the same channel instantly after blocking, that means nothing, these changes take a while to propagate, YouTube is a distributed system. Give it a few minutes to rebuild the feed and then try.

    How are people upvoting this crap?

  • That ship has sailed a long time ago. Tons of cars on the roads now have built-in cameras. Cameras that are ultimately under centralized control of the car manufacturer.

    And then there are all the outdoor cameras that homes and businesses have.

  • Seatbelts I don't really care about, because with that people mostly just affect themselves (or others in the same car), but for other infractions it makes sense.

    The real issue is whether you can trust that the data will only be used for its intended purpose, as right now there are basically no good mechanisms to prevent misuse.

    If we had cameras where you could somehow guarantee that - no access for reason other than stated, only when flagged or otherwise by court order, all access to footage logged with the audit log being publicly available, independent system flagging suspicious accesses to any footage, etc. - it wouldn't be too bad.

    Compared to all the private cameras that exist in cars these days...