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/)G
Posts
1
Comments
50
Joined
3 yr. ago

  • What you need here is not the stability in memory (i.e. of pointers, which you lose when you recreate an object) but instead just the stability of an identifier (e.g. the index into a list).

  • FYI there is an open source reimplementation of Flash from scratch called Ruffle that should solve all the security issues that Flash had. It runs on WASM so it's compatible with modern browsers. The New York Times is using it to bring back some old interactive/animated pages that relied on Flash.

  • You keep the recovery codes unexposed to the internet or obfuscated in some way, unlike your usual password.

    How is a strong password I used exclusively for Bitwarden "exposed to the internet"? I do see the value of this for people that don't care about security and reuse the same password everywhere. In that case you would need something like phishing to expose the 2FA code or the recovery code, just a leak of the email-password combination from another website would not be enough. But what's the point if I'm already using a unique strong password specifically for Bitwarden?

  • yes, that's the whole point, to recover your account if you lose your MFA device. what are you even trying to say?

    If you can login without the second factor then what's the point?

  • The fact that no widely used LLM is open source is not a good reason to change its meaning.

  • From the wikipedia link you posted:

    Account recovery typically bypasses mobile-phone two-factor authentication

    It also lists more advantages than disadvantages.

  • Why can't I keep my password in a secure location then?

  • Sounds like a second password then.

  • It's not open-source, stop spreading disinformation. The core of the product are the model weights and no source is provided for them, making them irreproducible. This is as open source as distributing a single exe file because after all you can read the assembly code, no?

  • Insanity is when you lose or can't access your 2FA device and you're locked out of your account.

  • Not really, portals give you shortcuts in 3D space, they don't allow you to interact with a whole different dimension. If you have Minecraft there's a really nice custom map called "The Hypercube" which sorts of emulates a 4th dimension, it felt much more confusing than Portal (2) for me.

  • 50 years ago people thought everyone would be able to program using BASIC, now you think everyone will be able to program using AI. It seems nothing has changed in 50 years.

  • Sorry, by looking more into it I realized webview is actually a different thing than what I was thinking about.

  • This would be so good. As someone who fully switched to Firefox on Android I hate that chrome webview is a thing.

    Why does that bother you? There's also a Firefox Webview you can use system-wide. I think only Google apps insists on opening Chrome's webview.

  • Do you apply the same reasoning for software that use javascript, the JVM, the CLR or some other kind of VM?

  • These are server CPUs, not something you wanna put in your laptop or desktop.

  • What? You can easily escape from it if there are better alternatives you can use.

    So there is no general escape hatch.

    Pointing at one language and saying it is not easy to code like it is another language is a pointless argument.

    I'm not arguing that it is easier to code in C# than in Rust, just that this particular escape hatch is possible in C# and not in Rust. It's just an observation.

    They all differ for good reasons and as long as you can solve similar problems in both, even if in different ways then what does it matter that you cannot do it in the same way?

    It does not really matter, but does it have to?

  • This is a kind of stupid example, but imagine you have to implement some external trait (e.g. in order to work with some dependency) with the following shape:

     rs
        
    trait Foo {
        fn foo(&self, i: usize) -> &Bar;
    }
    
      

    Which is not too unreasonable, for example it's very similar to the stdlib's Index. In order to implement this trait you must return a reference, you can't return e.g. a Cow or an Arc. The fact that it takes a parameter means there might not even be one single value it has to return, so you can't even cache that inside of self with e.g. LazyLock.

    Of course I'm not saying I would try to reach for an escape hatch if I had to do something like this. I would first try to see if this is an intrinsic problem in my code, or if maybe I can change the crate I'm working with to be more permissible. That is, I would try to look for proper solutions first, though Cow might not always work for that.

  • You dont write code like this in rust.

    I perfectly agree, that would be horrible code! I would generally try to restructure my code, making it better fit the actual lifetimes of the data I'm working with. The point in the article is that you can't really escape from this. I'm not arguing this is a real problem, and I don't think the article is neither, just pointing out that this is something you can easily do in C# and not in Rust. It's just a difference between the two languages.