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/)HE
Posts
3
Comments
995
Joined
2 yr. ago

  • “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.

  • We’re in danger of becoming a fascist state? We just had a four year period of having a Democrat as president, with the Democrats also having a two year period at the start of that where they controlled both the Senate and the House. Are you telling me that the Democrats did nothing in that time to counter the threat of the US falling under fascist rule?

    If the Democratic elected officials didn’t consider that to be important, why should we?

  • the law has already made it clear you cannot copyright the output of an LLM.

    That’s true in this context and often true generally, but it’s not completely true. The Copyright Office has made it clear that the use of AI tools has to be evaluated on a case-by-case basis, to determine if a work is the result of human creativity. Refer to https://www.copyright.gov/ai/ai_policy_guidance.pdf for more details.

    For example, they state that the selection and arrangement of AI outputs may be sufficient for a work to be copyrightable. And that’s without doing any post-processing of the AI’s outputs.

    They don’t talk about situations like this, but I suspect that, if given a prompt like “Rewrite this paragraph from third person to first person,” where the paragraph in question is copyrighted, the output would maintain the same copyright as the input (particularly if performed faithfully and without hallucinations). Such a revision could be made with non-LLM technology, after all.

  • Do you only experience the 5-10 second buffering issue on mobile? If not, then you might be able to fix the issue by tuning your NextCloud instance - upping the memory limit, disabling debug mode and dropping log level back to warn if you ever changed it, enabling memory caching, etc..

    Check out https://docs.nextcloud.com/server/latest/admin_manual/installation/server_tuning.html and https://docs.nextcloud.com/server/latest/admin_manual/installation/php_configuration.html#ini-values for docs on the above.

  • https://www.apple.com/airpods-pro/hearing-health/ says it has received FDA authorization, but doesn’t mention receiving approval from any other country’s regulatory body. It doesn’t say it’s US exclusive, though:

    The Hearing Test and Hearing Aid features are expected to be available fall 2024. The Hearing Aid feature has received FDA authorization. Both features will be supported on AirPods Pro 2 with the latest firmware paired with a compatible iPhone or iPad with iOS 18 or iPadOS 18 and later and are intended for people 18 years old or older. The Hearing Aid feature will also be supported on a compatible Mac with macOS Sequoia and later. It is intended for people with perceived mild to moderate hearing loss.

    The Hearing Protection feature, on the other hand, is explicitly listed as being exclusive to the US and Canada.

  • 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.

  • Nah, the idea is that anyone not buying it thinks it looks like drugs, not to convince the people buying that they’re buying drugs.

    You could also call it “Spice” and make it a blend of different spices, salt, etc..

    Either way, all you need is a bunch of people who are all in on the same joke.

  • 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.

  • a talking collar isn’t likely to help … if the cat is even willing to wear the thing at all.

    “Realistically,” Quagliozzi says, “that collar would just be saying ‘get this fucking collar off me’ all the time.”