It's possible to get unauthenticated streams if you know the media paths. Media collections, at least in my experience, usually adhere to a few common organization schemes. This would allow someone with a list of common titles, which are available in various public databases, to leak data by brute force from a public facing Jellyfin instance quite efficiently.
Discounting this as merely "suboptimal behavior" sounds like a mistake.
In what I wrote above, I wasn't referring to NixOS or Guix. I was thinking of the other ones (SteamOS, Fedora Silverblue, OpenSuSE Aeon, Vanilla OS, etc.) -- In fact, I think it's a bit misleading to lump them together in the same category of "atomic" or "immutable". This term has come to mean way too many different things.
I'm not sure what you mean by "invented", but as far as I know the Chinese lab leak theory is still widely accepted as credible and supported by many facts.
Ok but why would anyone care if they aren't calling for a shutdown of growth-of-function research? There's nothing essentially qualitatively different about China that make them more evil or less competent. Hence the comment about racism. Even if they did intend it as a weapon, they certainly could not have predicted how badly we would bungle the response. The complete lack of serious protest against growth-of-function research has led me to conclude this is almost pure racism/fearmongering/arrogance/special interests driving this narrative.
This is just naked propaganda and there's zero substance to it. just "covid=china=bad".
For you and me, not a problem. My wife is a medical professional and would have no clue what to do with a TGZ file.
Also, the fact that they don't mention this difference- the UI is so poorly done that you can only tell that TGZ can go an order of magnitude larger after selecting it in one drop-down and then looking at the other drop down- is a sign of how Google wants to make this as difficult as possible.
I'm always surprised when people speak highly of Apple devices here. While they do have certain advantages, there are some issues that should be dealbreakers for tech literate people. (in my own, possibly biased opinion at least)
In case of Macbooks, it's the fact that they refuse to provide an official GPU driver for Linux and general poor support for things outside the walled garden. The Asahi stuff is cool and all, but come on, is a 3.4 trillion dollar company really going to just stand there and watch some volunteers struggling to provide support for their undocumented hardware without doing anything substantial to help? That sounds straight up insulting to me, especially for such a premium product.
For iphones, it's the fact that you are not allowed to run your own code on YOUR OWN DEVICE without paying the Apple troll toll and passing the honestly ridiculous Apple Store requirements.
And of course, in both cases, they actively sabotage third party repairs of their devices.
> there are some issues that should be dealbreakers for tech literate people. (in my own, possibly biased opinion at least)
I know you admit right after that your opinion is biased, but it's almost ludicrous to assert that all the programmers and engineers using Macs and iPhones by choice must just not be tech literate.
> In case of Macbooks, it's the fact that they refuse to provide an official GPU driver for Linux
MBPs are so much better than any other laptop that, with a few caveats[1], running Linux in a VM on a top-of-the-line MBP is a much nicer experience than using Linux natively on any other laptop. So while it'd be nice if there were more first-party support for Linux, it's certainly not a deal-breaker for "tech-literate" people. (Not to mention the fact that there are "tech-literate" people who use macOS and not Linux, so it wouldn't matter to them at all).
> general poor support for things outside the walled garden
macOS isn't a walled garden, so I don't know what you mean. You can download any software you want from anywhere you want and run it on your laptop, and Apple doesn't do anything to try to prevent this.
> The Asahi stuff is cool and all, but come on, is a 3.4 trillion dollar company really going to just stand there and watch some volunteers struggling to provide support for their undocumented hardware without doing anything substantial to help? That sounds straight up insulting to me, especially for such a premium product.
Now it's unclear whether your point is "I don't understand why people use Macs because there are objective drawbacks" or "I don't think people should use Macs because Apple does stuff that I find annoying". You're blending the two here but they are meaningfully separate points. I've discussed the practical point already above, but as for the stuff you subjectively find annoying: surely the only real answer is that lots of other people just subjectively don't care as much as you.
> For iphones, it's the fact that you are not allowed to run your own code on YOUR OWN DEVICE without paying the Apple troll toll and passing the honestly ridiculous Apple Store requirements.
I don't care about this at all. I've never wanted to run my own code on my own iOS device except when I was working on iOS apps and had an Apple developer account through work. I, like the vast majority of people, use my phone as a browsing/messaging/media consumption device, not as a general-purpose computer.
If Apple tried to prevent me from running my own code on my own MacBook, it would be a deal-breaker, but as I already said above, they don't.
In conclusion I think you've confused "tech-literate person" and "geek who wants to be able to tweak/configure everything". Indeed there is a large overlap between those sets, but they're not quite the same thing.
Not having a built-in syncing mechanism is the #1 reson I'm looking to move away from KeepassXC as soon as possible. Making users kludge together their own makeshift sync methods using file shares and dropbox is honestly comical when syncing is probably one of the main features people think of when talking about password managers.
I'd never use anything less than completely open source and self-hostable for this purpose! Which is why I'm having trouble with finding a viable alternative to KeepassXC. I intended to go with Bitwarden+Vaultwarden, but that sounds a lot less appealing now.
