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/)C
Posts
30
Comments
158
Joined
3 yr. ago

  • Itch.io has begun restoring NSFW content, but only if it’s free

    Jump
  • The problem is the payment processor. There's only so many of them that customers actually choose to use.

  • How about some Yubikeys or smart cards instead of something that requires me to scan my retina and share it with Sam Altman

  • Right. Zero trust means at the very least you need to add AuthN and AuthZ to every endpoint with no exceptions for internal IP addresses.

  • Encryption at rest just means the data itself is encrypted when stored on disk and the key is somewhere. It doesn't dictate that the key is not visible to the server.

    Encryption in transit refers to an encrypted channel from client to server.

    E2E encryption usually refers to encryption from one entity to another where any intermediary servers do not have the ability to decrypt

    Source: too many years doing application security at my job

  • Yeah this isn't even human readable even when it's in YAML. What am I going to do? Read the floats and understand that the person looked left?

  • The point seems to be able to handle a UPS failure

  • WiFi is on all three bands. It's not so much what's newer vs older. Newer devices tend to support 2.4, 5, and 6 and switch between them based on quality of signal and support by the WiFi network. Higher frequencies like 5 and 6GHz are generally better because there's less interference.

    Cheaper devices tend to only support 2.4GHz

  • Fascinating. Just based on your comment and nothing else, sounds like it could be something like a CPU Enclave like Intel SGX. Basically a remote client can validate that an application runs in a secure part of a remote cloud computer. The stated goal of SGX is that you only have to trust Intel and if you trust Intel and say run program X in the enclave, then only that part of the CPU can access the data, not the applications running in the non-secure enclave.

    Now that brushes over some things like you still need to trust the client and IIRC in a WhatsApp situation, you don't really know what enclave does, but the communications between the enclave and the host OS are heavily restricted. LLMs also require lots of CPU and are usually run on GPUs, so not sure how that works yet.

  • I think #1 is suggesting to move the neutral over to another hot phase and change the outlet to a 240v nema 6/three prong (I think) with two hots and a ground instead of the 4 prong.

    The 240v at the same amps gives you higher watts so faster charging without an expensive new conductor. I'm

  • Maybe that's intentional to keep you from wanting to stay there a long time and negotiate.

  • They used a protocol called WebRTC that allows for establishing direct P2P connections to establish a connection to the Facebook app running on your phone. The FB app knew your identity so it was able to link your in browser actions with your FB identity.

  • Sounds a lot like getting used to time zones. Just get used to it being 3pm there when it's 6pm here

  • It makes some things hard and some things easier. For example, you can more easily defend against DoS attacks because there's just more targets.

    But decentralized makes it easier for bot manipulation because you can hide your actions across multiple users on different instances and those instances can't easily identify bot signatures like IP addresses to ban many accounts.

  • Google is doing this because they have incentives to do so. They want to block malicious actors like attack their platforms.

    Other companies want to lock down their own apps because they don't think users should be permitted to do anything other than use their apps exactly as they want.

    I don't like it as a user, but I also see the reason why companies want this by being on the security side of software.

  • This is the future of the Big Tech Internet if we're not careful. Attestation to be able to use communications and other websites.

  • I used to work in Amazon (left after 10 years because it wore me down), but it wasn't that compartmentalized.

    I'm sure there were some teams that were like that but I could easily find another team, open a ticket, get a response and see their on calls investigate the issue. It was often times possible to look at their service metrics and source code to see if I could find the problem myself.

    Support just can't share that info because they don't know what is considered a trade secret or internal detail vs what is public.

  • No, it's electrical code. Standard outlets can't be used to supply power because it means you have a plug that has exposed wires commonly called suicide wires. While these balconey top solar likely use grid following so it has to detect a grid voltage, the electrical code doesn't consider it AFAIK. This rule is for safety and because it would only power half your house because there's only one leg per 110 outlet.

  • You might behind a shared IP with NAT or CG-NAT that shares that limit with others, or might be fetching files from raw.githubusercontent.com as part of an update system that doesn't have access to browser credentials, or Git cloning over https:// to avoid having to unlock your SSH key every time, or cloning a Git repo with submodules that separately issue requests. An hour is a long time. Imagine if you let uBlock Origin update filter lists, then you git clone something with a few modules, and so does your coworker and now you're blocked for an entire hour.