• 1 Post
  • 320 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2023

help-circle

  • The rules text says it creates an area of darkness, and with your interpretation, it doesn’t, which means your interpretation is wrong. Yes, the ability could be written more clearly, but the logic for a reasonable way for it to function follows pretty cleanly. Your interpretation is not RAW or RAI.

    There’s a reply on RPG StackExchange that covers a similar line of logic to what I wrote above.

    Remember that Fifth Edition D&D is intentionally not written with the same exacting precision as games like M:tG. The game doesn’t have an explicit definition of magical darkness, but it’s pretty clear that the intent is for magical to trump mundane (when it comes to sources of light and darkness). Even the Specific Beats General section says that most of the exceptions to general rules are due to magic.


  • If you have normal darkness everywhere, there isn’t a reason to use it, but you don’t always have darkness everywhere. In fact, you generally don’t.

    Not all monsters with darkvision have access to light sources. Even if they do, they may need an action to use it or may be out of range. A torch or the light cantrip only has a 40’ range. If you collaborate on positioning with the caster, you can basically set yourself up to have advantage every turn thanks to the darkness, since as a ranged attacker you don’t have to stay within 40’ of your enemies.

    Also, Gloom Stalkers can’t see through Darkness like Warlocks can, so this effect is useful to them in a way that the Darkness spell isn’t.

    That all said, Tricksy wouldn’t do anything if it didn’t block nonmagical illumination, so it’s reasonable to run it as though it does. Sure, it still wouldn’t block even a cantrip, but it would block torches, lanterns, the sun, etc…

    And running it as though it doesn’t block nonmagical darkness results in nonsensical behavior. You’re in a torchlit chamber and use the ability - now there’s a cube of darkness, blocking the light of all four nonmagical torches. If you move one of those torches away and back, why would it suddenly pierce the magical darkness? If it wouldn’t, why would a new nonmagical light source?


  • Thanks for clarifying! I’ve heard nothing but praise for Kagi from its users so that’s what I was assuming, but Searxng has also been great so I wouldn’t have been too surprised if you’d compared them and found its results to be on par or better.

    By the way, if you’re self hosting Searxng, you can use add your own index. Searxng supports YaCy, which is an actively developed, open source search index and crawler that can be operated standalone or as part of a decentralized (P2P) network. Here are the Searxng docs for that engine. I can’t speak to its quality as I still haven’t set it up, though.




  • “But tante, then we will never have Open Source AI”. Exactly. That’s how reality works. If you can’t fulfil the criteria of a category you are not in that category. The fix is not to change the criteria. That’s playing pigeon chess.

    This is a bad take. If your criteria aren’t grounded in reality, they aren’t useful, so of course you should change the criteria.

    It’s also a missed opportunity to point to an AI model that did things right and that would qualify as “open source AI” even if that definition were not watered down. For example, OLMo (which I just learned about) says that they provide full insight into the training data as well as “full model weights, training code, training logs, training metrics in the form of Weights & Biases logs, and inference code.” Their most complex models are 7B models, which is enough to be relevant.

    Saying “Meta and Alphabet will never release Open Source AI that meets the proposed definition” is fine. Saying “we’ll never have Open Source AI, period, that meets the proposed definition” means your proposed definition needs rewritten.




  • Your Passkeys have to be stored in something, but you don’t have to store them all in the same thing.

    If you store them with Microsoft’s Windows Hello, Apple Keychain, or Google Password Manager, all of which are closed source, then you have to trust MS/Apple/Google. However, Keychain is end to end encrypted (according to Apple) and Windows Hello is currently not synced to the cloud, so if you trust those claims, you don’t need to trust that they won’t misuse your data. I don’t know if Google’s offering is end to end encrypted, but I wouldn’t trust it either way.

    You can also store Passkeys in a password manager. Bitwarden is open source (though they did recently introduce a proprietary, source available SDK), as is KeepassXC. 1Password isn’t open source but can store Passkeys as well.

    And finally, you can store Passkeys in a compatible security key, like the YubiKey 5 series keys, which can each store 100 Passkeys. This makes them basically immune to being stolen. Note that if your primary interest in Passkeys is in the phishing resistance (basically nearly perfect immunity to MitM attacks) then you can get that same benefit by using WebAuthn as a second factor. However, my experience has been that Passkey support is broader.

    Revoking keys involves logging into the particular service and revoking them, just like changing your password. There isn’t a centralized way to do it as far as I’m aware. Each Passkey is only used for a single service, after all. However, in the same way that some password managers will offer to automatically change your passwords, they might develop a similar for passkeys.





  • For starters, it was never “open source”…

    From your link:

    Instead, as Winamp CEO Alexandre Saboundjian said, “Winamp will remain the owner of the software and will decide on the innovations made in the official version.” The sort-of open-source version is going by the name FreeLLama.

    While Winamp hasn’t said yet what license it will use for this forthcoming version, it cannot be open source with that level of corporate control.

    If I upload the source code for my project on Github/Forgejo/Gitlab/Gitea and license it under and open source license, allowing you to fork it and do whatever you want (so long as you follow the terms of my copyleft license), and I diligently ensure that code is uploaded to my repository before being deployed, but I ignore all issues, feature requests, PRs, etc., is my project open source?

    Yes.

    Likewise, if Winamp had been licensed under an open source license, it would have been open source, regardless of how much control they kept over the official distribution.

    Winamp wasn’t open source because its license, the WCL, wasn’t open source.



  • Do you memorize all of your passwords? If so, I take that to mean that you don’t use a password manager. Password managers - really, any app with 2FA - have this problem, too. But if you use a password manager and store your 2FA methods in it, then you only need to be able to regain access to your password manager.

    If you use a cross-platform password manager with Passkey support, like Bitwarden, you can use it on any of your devices. In the event that you lose all of your devices, if you don’t have an Emergency Contact set up, you will need your password and one of the following to gain access to your account:

    • Access to your 2FA method
    • Access to your Recovery Code
    • If you’re in an enterprise using Duo 2FA, access to a Duo bypass code (contact your Duo admin to request this)

    If you use security keys for 2FA, then you should have at least two - one that you keep with you and a backup that you keep in a safe place, like at home in a lockbox.

    If you use a TOTP app to log in, or if you use security keys and want another backup, then making sure you’ll have access to the Recovery Code should be your priority. You can write it down and keep it in a few different places - at home, in your car, in your locker at work, etc… You can share it with someone you trust in person or over an encrypted channel (like Signal). You can store it on a flash drive, encrypted by a second password (which can be much easier than your primary password) or even unencrypted, if you generally keep the drive somewhere safe, disconnected from your computer. As long as you remember your password and can access your recovery code, you’ll also be able to regain access to your account, including all of your passkeys.

    Emergency Access requires someone else to have access to their Bitwarden account, but assuming you don’t both lose access, it’s a pretty solid solution. When they request access, Bitwarden will send you an email allowing you to accept or reject their request. If you accept or don’t respond within the allotted “Wait Time” (which you configure: 1 day minimum, 90 days maximum) then they’ll be granted access. You also get a choice (when setting this up) to let them takeover the account (resetting your master password) or to just get read-only access.

    Maybe you don’t like Bitwarden and want to use some other app, like 1Password, Dashlane, Roboforms, etc… Whatever your choice, familiarize yourself with how to restore access to your account in an emergency. Then you only need to worry about that and not about how to get access to your passkeys that are on your Windows laptop or only synced to your Apple devices.


  • But that is exactly what he recommends, using a password manager - with one time email authentication for the first login as an extra step, right?

    Nope.

    Using a cross-platform password manager with synced passkeys is different and much more secure than using a password manager with email TOTPs or sign-in links with emails that aren’t end-to-end encrypted.

    And password manager adoption is much higher than PGP keyserver adoption, and if you can’t discover someone’s public key you can’t use it to encrypt a message to them, so sending end-to-end encrypted emails with TOTPs/sign-on links isn’t a practical option.

    According to Statista, 34% of Americans used password managers in 2023 (a huge increase from 21% in 2022), so it’s not even like the best case scenario is rare.


  • The author mentions it: the QR code approach for cross device sign in. I don’t think it’s cumbersome, i think it’s actually a great and foolproof way to sign in. I have yet to find a website which implements it though.

    The site doesn’t need to implement this; the browser handles that part.

    I confirmed this works and logged into Github using Google Chrome on my work computer using a passkey stored in Bitwarden earlier today. I had to enable Bluetooth for Chrome, since I’d had it disabled, but then everything else was seamless.