

A bit ironic to see a community on this open platform shilling for the closed, invasive platform known as Discord.


A bit ironic to see a community on this open platform shilling for the closed, invasive platform known as Discord.


I expected that astute readers would notice the opportunity on their own. :)
Perhaps the defenestration could be an escalating affair: Use a ground floor window the first time. Add a floor for each subsequent offence. Add a floor for each co-conspirator supporting the mass surveillance attempt.


I propose that any government official seeking (more) mass surveillance be immediately told “no”, thrown out of office, and prosecuted.
I wish they hadn’t put a close-up shot of the antagonist on the store page. It kind of undermines the suspense.
Yeah, but before you get excited, know that planet is rife with dihydrogen oxide.


already commented by iknewitwhenisawit
I don’t see any such comment. I guess federation could be lagging.


Rampage (1986) comes to mind, but (minor) enemies are present and I don’t think it applies damage in layers.


They infest humans, too.


A You Should Know post is generally expected to offer little-known information, mainly the kind that can significantly improve many people’s quality of life. What you have posted here is widely known and trivial, and therefore fails both criteria.
It would be a better fit in Today I learned. (But not much better, because pointing out the existence of an old, well-documented, basic software feature is not the least bit interesting.)


a lot of the rule changes on the road to 5e (especially to magic) are tied to in-universe events that wouldn’t have happened yet.
Feel like sharing some examples?


The article talks about cattle, but these things infest humans, too.


Weird. I don’t know how that happened. I wonder if I hit a glitch in Lemmy’s web UI.


- He described new C “guards” and scoped locks inspired by Rust
In other words, the improved safety will sometimes come from Rust code, and sometimes from C code. The important point being that safer practices are becoming more common now that Rust has called attention to them.


The word naphtha comes from Latin through Ancient Greek (νάφθα), derived from Middle Persian naft (“wet”, “naphtha”), the latter meaning of which was an assimilation from the Akkadian 𒉌𒆳𒊏 napṭu (see Semitic relatives such as Arabic نَفْط nafṭ [“petroleum”], Syriac ܢܰܦܬܳܐ naftā, and Hebrew נֵפְט neft, meaning petroleum)


This is extremely dangerous command! If anything goes wrong for whatever reason and the variable $tempdir is empty at the time of this command, then it would delete everything.
And this danger is not merely theoretical. Steam for Linux did it in 2015.
https://github.com/valvesoftware/steam-for-linux/issues/3671


The go env -w command can make most go environment variable settings persistent for the current user. Alternatively, you could set the environment variable in your shell’s login script.
Be sure to read go’s docs for individual environment variables, because go doesn’t respect all methods of setting them in every case. (For example, it ignores certain approaches to disabling its telemetry. How convenient for Google.)


Matrix is… really crashed and often breaks.
Matrix is a protocol. It’s not possible to crash it.
I did find that certain Matrix implementations had a habit of breaking when encryption was used, until about a year ago. From what I’ve seen, recent versions appear to have fixed it. Element X is worth a try.
Back to your original question: Matrix apparently supports whatever UnifiedPush distributor you choose, such as ntfy.
This is someone’s personal fork of Cantata. (The original is no longer receiving updates.)
What makes this one more useful or trustworthy than the 183 other forks? Why did the person behind this one strip/avoid the upstream reference, which GitHub normally applies to forks?