I’m a staff software engineer at Sunrun, the USA’s largest residential solar installer.

I mostly work with kotlin, but also java, python, ruby, javascript, typescript. My hobby is picking up new hobbies. Currently bird photography and camping.

  • 0 Posts
  • 28 Comments
Joined 3 years ago
cake
Cake day: June 6th, 2023

help-circle

  • the amount of people that do not understand how big of an improvement passkeys are is really saddening. They think that somehow these tech companies are utilizing this in some nefarious way, rather than the very very simple explanation that … tech companies don’t want to be responsible for more breaches.

    Passkeys are so simple and such a huge improvement that it’s literally all upsides and no downsides. Either you use their passkey managers like you would their password managers and it’s safer for them, or you use your own password manager with passkeys in it and it’s still safer for them.


  • You have a vast misunderstanding of why passkeys aren’t transferrable or usable outside of those providers. It had nothing to do with lock-in, but because every implementation was different. And no, you do not ‘depend on the site’ to let you use that option instead of a major provider. There’s a standard now and everyone is following it. If you can use a passkey you can use your password manager to manage that passkey.






  • It blocks access to the link on your site. For example, on programming.dev people have uploaded CSAM. The links are immediately blocked (e.g. no one can get to them except an instance owner actually looking in the pictrs database) and then in the CF dashboard you get a notification with the link to the webpage it occurred on.

    CSAM blocking works based on a known agreed upon, shared hash list which is created by a consortium of large tech giants. If novel CSAM is uploaded to your instance, then yes, it will fail to catch that. db0’s plugin might catch it though. LLM blocking doesn’t have the benefit of a bunch of multi billion dollar companies trying to stop it, in fact they’re doing the exact opposite, so yes LLM blocking sucks.

    For your edit, I would expect you to have an email set up that you would get the notice from. You are not responsible for this kind of stuff until you have been notified, pretty much globally, so pay attention to your email.










  • that is most definitely not the process. You have to explicitly go into Steam’s settings > Compatibility > “Enable Steam Play for all other titles” (what in the world, it’s called Steam Play, not Proton?) and then additionally select which Proton version you want. If you don’t know this, or don’t google it with the right keywords, you won’t understand why literally 90% of your library isn’t available (in my case it was 99% of my library, I think I only had 3 games available on linux natively). Also if you select the wrong Proton version some games won’t run, so you have to know that and switch it for those games only.