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/)BJ
Posts
0
Comments
275
Joined
2 yr. ago

  • stainless has ~10x the thermal conductivity of borosilicate glass

    Glass has double the heat capacity, and I would assume greater mass due to thicker construction. So unless you are preheating fully to boiling temps first every time, there will be more heat loss to the glass over the course of ~1-3 minutes

  • Abolishing the monarchy would involve rewriting the constitution - if that was happening every province would want to slip in their own terms - Quebec would want specific French language rights and autonomy and if Quebec got their way Alberta would want something similar. We successfully altered the constitution back in 1982 - it took 2 years and the country almost blew up over it.

    Basically it would be a total shit show. Considering the impact the monarchy has on our day to day life (basically zero) it's easier to just let sleeping dogs lie

  • It's really not that complicated. At a high level:

    • $5/mo for having the service turned on
    • $5/mo for every TB storage above and beyond the first 1TB
    • $1 for every TB of data transfer beyond the first 1TB in a month

    And then divide those numbers because it's actually billed by the hour

  • That assumes that an adversary has control of the browser

    No it doesn't, if they intercept an encrypted password over HTTPS they can resend the request from their own browser to get access to your account

    The big reason you don't want to send passwords over https is that some organizations have custom certs setup

    What is the problem with that? The password is secure and only shared between you and the site you are intending to communicate with. Even if you sent an encrypted password, they wrote the client side code used to generate it, so they can revert it back to its plaintext state server side anyways

    It is better to just not send the password at all.

    How would you verify it then?

    If not sending plaintext passwords was best practice then why do no sites follow this? You are literally posting to a site (Lemmy) that sends plaintext passwords in its request bodies to log-in

  • Client side verification is just security by obscurity, which gains you very little.

    If someone is capable of MITM attacking a user and fetching a password mid-transit to the server over HTTPS, they are surely capable of popping open devtools and reverse engineering your cryptographic code to either a) uncover the original password, or b) just using the encrypted credentials directly to authenticate with your server without ever having known the password in the first place

  • The word ‘decipher’ is doing a lot of heavy lifting. I’m wondering if they socially engineered or just found it written somewhere in the house?

    You can plausibly brute force up to 4, maybe 5 words of a seed phrase. It takes longer than a normal password because every seed phrase is technically valid, so the only way to know if your brute force is successful is to generate thousands of addresses at each of the different derivation paths you may expect funds to exist at.

    The same seed phrase is used for Bitcoin, Ethereum, Monero, etc, but each currency uses the seed phrase to generate addresses in a slightly different standard. Additionally, each wallet uses a slightly different variation of that. Within each wallet is a notion of accounts, and within each account you could have dozens of addresses. You need to generate each of those addresses, and scan each cryptocurrencies blockchain to see if those addresses have ever been used.

    Realistically one of three things happened: his seed phrase was written down and they found it, it was password protected or on a drive with weak AES encryption and they cracked THAT instead, or finally, he used a hardware wallet and they exploited a firmware vulnerability to lift the PIN and transfer out funds and/or read the seed from the device

  • You are acting like someone checked off a "log passwords" box, as if that's a thing that even exists

    Someone configured a logger to write HTTP bodies and headers, not realizing they needed to build a custom handler to iterate through every body and header anonymizing any fields that may plausibly contain sensitive information. It's something that literally every dev has done at some point before they knew better.

  • COVID has long lasting effects across your entire body, it impacts your immune and cardiovascular systems for years after you get it.

    Risks of heart attack, stroke, etc are increased 2.5x in the year after infection, increasing exponentially with the number of times you have been infected. In fact, the risk of pretty much ANY health problem skyrockets following a COVID infection.

  • I haven't used dual shock so I can't speak to that, but as far as Xbox 1/S controllers, there is no 1st party support - literally all the drivers are from some non-MS affiliated GitHub page. 360 controllers required the xpad driver as well - that isn't 1st party support. Yes they work out of the box with steam if you are using a wired connection, but that's because it's going through steaminput (not 1st party either), and making the controls of the submarine dependent on being launched through steam is even more absurd. Gen 2 series 1/S controllers didn't work via Bluetooth for a long time after they (silently) launched on most LTS Linux OSs due to the kernel missing requisite BLE functionality