And parents are held responsible if they give it to kids
Imo, only if it can be proven that the parent is being willfully negligent regarding the safety the child.
Also, if a product that claimed to be safe, but actually wasn't, was purchased and given to the child, then this responsibility should fall on the producer only.
Yes, but it shouldn’t be legalized for the wrong reasons.
This is kind of an interesting thought, imo. If one agrees with the resultant policy, does the rationale used to get there matter? Perhaps it does in principle, but I wonder if it matters in practice. The end result is the same.
[…] ivermectin, hydroxychloroquine […]
I'll be honest, I don't really understand this one. I'd guess that this is likely some hold over grudge from COVID, but I don't really understand why it's still a concern to get, presumably, more open access to those drugs. Aren't we long past that conversation? Feels like beating a dead horse.
[…] raw milk […]
I'd support raw milk being legal for consumers to purchase so long as the manufacturers of said raw milk could be held to account for harm caused to a consumer who purchased it under the belief that it was safe — likely, this would also mean that, if it isn't safe, the product containing raw milk must otherwise display explicit warnings. I think a person should be allowed to take take their own risks.
[…] psychedelics […]
I'm glad that it seems like the war on drugs is showing cracks. I completely support a move to legalize psychedelics.
From what I can see, "Hot" seems like a boosted "New" — it favors new posts, and ranks them by activity [1.1], whereas, from what I understand, "Active", is more like the classic forum format where a comment bumps it back up to the top, but ranked also based on score [1.2].
References
[…] Hot: Like active, but uses time when the post was published […]
[…] Active (default): Calculates a rank based on the score and time of the latest comment, with decay over time […]
At least with Windows, most people know what its normally like at home, but thats less true for Linux.
Yeah, that's a fair point that they wouldn't have a comparison, so they wouldn't know if it's always like that. One could perhaps make an educated guess, depending on circumstance, but, without any first-hand experience or exposure, it would be just that: a guess.
Hm, but I'm not sure people would attribute that to the design of the underlying OS itself rather than just the employer. Like do those people with restrictions on Windows blame Microsoft? It'd be the same as someone blaming the Linux maintainers for employer placed restrictions on an OS running Linux. Don't get me wrong, I'm sure someone would still do that, but I'm not convinced that the majority would think that way — I think most people would be able to make the distinction.
I still expect it to be done in the open, one of the things Munich got right was upstreaming all their changes, which meant that even when it was cancelled, nothing was lost. Maintaining out of tree changes is just way to much work
Would you be able to cite a source for this Munich program? I'd like to read more about it.
Only the end-users would have rights to the source under GPL, and its unlikely that someone is going to risk their job by releasing the code.
Fair point. So I suppose that would be the employees using the distribution rather than the entire populace.
I swear I've only seen meta posts talking about all the cats. I haven't seen a single non-meta cat post.
Update (2024-11-23T01:52Z): It turns out that, to see the cats, one must sort by "Hot" [1]. I was sorting by "All" + "Active", but, to see the cats, I must sort "All" + "Hot".
References
[...] Active prioritizes many comments iirc, but on most of these posts I see few if any comments. Using Hot though, they can dominate a feed due to being highly upvoted.
References
"Tiny Machinery" (tinymachinery). Instagram. Published: 2023-02-17T15:38:08.000Z. Accessed: 2024-11-13T23:21Z. .https://www.instagram.com/p/CoxNDm5NnO_/.
Gotta get that KYC!
This is a bug in KDE Plasma [1.1][2]. It appears that it might be fixed in KDE Plasma v6.2 [1.2][3].
I have noticed this behavior with Element and Signal while playing Deadlock. The game will have a pretty severe stutter, ie the frame-rate will substantially dip, for half a second or so at the exact moment that a message is received. It seems to happen with every message. Do note that these are only messages that would result in a system notification. All other messages that are silent, ie they have no pop-up notification, do not result in any stutter.
References
it’s a bug in KDE Plasma
[the bug] might be fixed [in KDE Plasma] 6.2
There are some remaining code paths that can block direct scanout - namely effects that haven't been fixed, or that may need to block direct scanout in some situations. There's a new API in 6.2 that effects can use though, https://invent.kde.org/plasma/kwin/-/merge_requests/6203, which blocks direct scanout only when really necessary. It's implemented for all built in effects, and external javascript effects automatically make use of this API too.
Could you elaborate on what you mean?