I’d honestly even consider it a good idea for Russia to get the FSF to fight this considering it’s a blatant violation of the GPL.
How is telling someone that you won’t accept their contributions anymore a violation of the GPL?
I’d honestly even consider it a good idea for Russia to get the FSF to fight this considering it’s a blatant violation of the GPL.
How is telling someone that you won’t accept their contributions anymore a violation of the GPL?
Literally none of those freedoms were impacted. Everyone is still free to use the program as they wish, fork it, make changes, etc… Linux doesn’t have a new license that says “anyone but Russians” can use it.
he then followed up by gloating about Russian maintainers
How did he gloat? He explained the change. If your complaint is that he was abrasive, I feel like you’re not familiar with Linus.
Ok, lots of Russian trolls out and about.
It's entirely clear why the change was done, it's not getting
reverted, and using multiple random anonymous accounts to try to
"grass root" it by Russian troll factories isn't going to change
anything.
And FYI for the actual innocent bystanders who aren't troll farm
accounts - the "various compliance requirements" are not just a US
thing.
If you haven't heard of Russian sanctions yet, you should try to read
the news some day. And by "news", I don't mean Russian
state-sponsored spam.
As to sending me a revert patch - please use whatever mush you call
brains. I'm Finnish. Did you think I'd be *supporting* Russian
aggression? Apparently it's not just lack of real news, it's lack of
history knowledge too.
Sounds a lot more like he’s frustrated than delighted to me.
Calling your former volunteer contributors bots
He didn’t call the contributors bots.
He called the people submitting reverts and complaining about those maintainers, who weren’t contributors themselves, “troll farm accounts.”
and state assets because of their home country
When did he call anyone a state asset? To be clear, being a troll or a paid actor doesn’t make you someone’s property.
He also explained that this was a legal matter:
> Again -- are you under any sort of NDA not to even refer to a list of
> these countries?
No, but I'm not a lawyer, so I'm not going to go into the details that
I - and other maintainers - were told by lawyers.
I'm also not going to start discussing legal issues with random
internet people who I seriously suspect are paid actors and/or have
been riled up by them.
First, you’re acting like the decision was made by Linus or another member of the team and that they weren’t following the law.
Second, even if that weren’t the case, it’s still completely free. Unless you can name one of the following freedoms that was impacted by those actions:
What “not at all free dogmas” are you referencing, and why is “free” in scare quotes?
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.
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.
Do any of the iOS or Android apps support passkeys? I looked into this a couple days ago and didn’t find any that did. (KeePassXC does.)
You have your link formatted backwards. It should be Vaultwarden, with the link in the parentheses.
Up until a year ago, the README explicitly said they didn’t claim to be an open source project: https://github.com/jgraph/drawio/commit/8906f90ac0cc50a0c6da77c28cf9b2b2339277b1#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L10
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.”
You could’ve scrolled down to the bottom, clicked on “Links,” then clicked on the repo link
The repo has instructions to install a Snap or build from source. If you build from source, it looks like you should download an archive from the releases page rather than just pulling from master.
The unicode standard has stated that U+2019 is the preferred character for apostrophes since at least the late 90s.
And it’s not like using a curved apostrophe in typesetting was novel even then.
as opposed to U+2019 being posthumously appropriated
U+0027 was also an ASCII character. The death of ASCII as a common format is the only one I can think of… what death are you referring to here?
From https://en.m.wikipedia.org/wiki/Right_single_quotation_mark
The Unicode character ’ (U+2019 right single quotation mark) is used for both a typographic apostrophe and a single right (closing) quotation mark.[1] This is due to the many fonts and character sets (such as CP1252) that unified the characters into a single code point, and the difficulty of software distinguishing which character is intended by a user’s typing.[2] There are arguments that the typographic apostrophe should be a different code point, U+02BC modifier letter apostrophe.[3]
In other words, U+2019 is the typographic apostrophe character. It’s also the right single quote character. There are people who think that the typographic apostrophe character should be something else (and having read their arguments, I agree), but in practice, it isn’t, and certainly wasn’t back in the 90s / early 2000s.
Can you elaborate on why this is mildly infuriating?
You probably just need Google One and Youtube Premium, which includes Youtube Music Premium.
Of course, if you don’t care about YouTube Premium, you could instead get a family subscription to a different music streaming service - Spotify, Tidal, and Apple Music are all leagues better than Youtube Music, in my opinion.
I don’t personally recommend Google for anything, to be clear.
Open-Webui published a docker image that has a bundled Ollama that you can use, too: ghcr.io/open-webui/open-webui:cuda
. More info at https://docs.openwebui.com/getting-started/#installing-open-webui-with-bundled-ollama-support
For the purposes of this project, you could at least reproduce them by running wget
and downloading them from the original projects.
Expecting everything for free with no ads is just greedy.
In this case you’re not paying to not have ads. You’ll still get ads; they just won’t be personalized.
Personalized ads are more valuable to advertisers, so it still makes sense for them to charge a bit for it, but it’s not something I’ve seen before.
I’m guessing they charge a decent amount more than the difference, though - and probably even more than they make from personalized ads per person. On that note, I really wish ad free subscriptions were closer to the revenue providers get from serving ads - if they were, I’d be more willing to pay for them than just running an adblocker all the time. YouTube Premium, for example, costs 14 USD monthly, but annual ad revenue per non premium user was 1.21 USD.
Right? It’s weird how so many people upset about the situation in this thread are incapable of explaining why it’s a problem without lying.
Like, I get that it sucks to be removed as a maintainer because of something outside your control. But being, or continuing to be, a maintainer of a project isn’t a right that’s integral to that project being free.