![](/static/61a827a1/assets/icons/icon-96x96.png)
![](https://lemmy.blahaj.zone/pictrs/image/5825d3d0-d996-4356-afe6-f16b094d6d17.webp)
Which is easily disproved as people started having long covid long before we had vaccines.
Which is easily disproved as people started having long covid long before we had vaccines.
I have read them. While Vaxry makes his points in typical Vaxry fashion he’s not wrong IMHO.
I think it’s ridiculous and unprecedented to demand that other open source projects adhere to the rules of another project. If more projects would do that then where will it end? The big COC wars where camps of open source projects are split and fractured along opinions of how one should moderate their own communities? This is not the way to work together with others.
The demand was not about Vaxry’s own behaviour outside freedesktop, but about his community. I disagree that behaviour there reflects on freedesktop itself. Hell, I think a lot of people who use Hyprland couldn’t even explain what freedesktop is and does.
So in my opinion Vaxry was right to refuse the demand, and right to publish the email conversation about it. Openness in open source about these sorts of things is important. His hostility in writing about it is something else altogether. Feel free to judge him on that, but it doesn’t retroactively excuse freedesktop’s behaviour.
Last part isn’t true, he was banned for refusing to give his own community a COC that was compatible with the freedesktop one. Which is quite an overreach IMHO.
If this means I can deny WhatsApp access to my regular contacts and still have a decent user experience I’m all for it.
The inherent flaw is Qualcomm actually having to properly support one of their chipsets directly to customers for once, something they’re apparently really bad at. This box has had some pretty bad press already, mostly due to the software being abysmal.
FS 2020 reportedly already used 2 PB of data as it’s base. Good luck downloading that!
Object storage (the S3 API stuff) is the most logical answer here, it’s much simpler and thus more reliable than solutions like Gluster, and the abstraction actually matches your use case. Otherwise something like an NFS share from a central fileserver works too.
But I agree with the other comment that you’re trying to do kubernetes on hard mode and most likely with a worse result.
btop has GPU stats in recent versions.
Firefox has been able to block all third-party / cross-site cookies for ages. It’s just not the default because it breaks some sites. But dive into the settings and you can easily set it to block all cross-site cookies, or even all cookies if you prefer.
Oh I agree with your post, but I was responding to Valmond who used different criteria.
You can have all three of those, but you won’t get great performance. The Samsung QVO SATA drives are a great example. I wouldn’t use those for an OS drive but they’re fantastic for NAS or media use.
If everything went fine during production you’re probably right. But there have definitely been batches of hard disks with production flaws which caused all drives from that batch to fail in a similar way.
This used to be the norm, not a weird thing that noone has thought of before. If you do this your kernel will be a lot smaller, boot faster, and be a bit more secure. Once you’re booted it won’t make any meaningful speed difference though.
Yes, please. Would be nice to have a life again.