“Siri” actually does a lot locally, and I assume Google assistant does too.
On what basis? It's Google, so I would assume any and all data that you could possibly input into their apps and services to be used against you.
"Problemlos" würde ich #NewPipe jetzt nicht nennen. Der PII-Mißbrauch durch Google ist zwar weniger heftig, da zumindest client-seitig kein tracking mehr stattfindet, auf Server-Seite jedoch sehr wohl präsent und weiterhin kritisch.
Wer statt Youtube links proxies von #invidious oder #piped verwenden möchte, soll sich redirect add-ons wie #LibRedirect zulegen. Direkt proxy links zu posten finde ich fragwürdig. Das sollte jeder selbst für sich entscheiden.
That and @kubikpixel@chaos.social explicitly tagged this community in their post which Lemmy interprets as posting to the community.
Though they may have also mistaken this community's handle ("@newpipe@lemmy.ml") for being the NewPipe account. Mastodon makes it extremely ambiguous: https://github.com/LemmyNet/lemmy/issues/4339
I don't have a Messiah.
That could be Cloudflare or any number of DNS providers out there.
I can highly recommend desec.io for this purpose.
But I could easily see
nixpkgsimplement functions that allownixos-rebuild switchto use either live patching method, or even implementing one specifically for NixOS.
Sadly, I could not. Live patching requires extensive knowledge of the previous system state and that is the antithesis to NixOS where any system state is fully independent of any other possible system state.
nixos-rebuild switch isn't very magical at all once you understand this principle.
Live patching is also not really something you want to use or use frequently. It's more intended for "this super critical box can only be taken down next Saturday but there's a fix for a 0-day in the kernel today that we need ASAP". If it's at all possible to simply reboot, simply reboot (or kexec).
They did follow that. You can read their disclosure timeline in their report.
Problem is that the devs of glibc aren't the only people interested in getting glibc patched but us distro maintainers too.
What I would have preferred would be an early private disclosure to the upstream maintainers and then a public but intentionally unspecific disclosure with just the severity to give us distro people some time to prepare a swift rollout when the full disclosure happens and the patch becomes public.
Alternatively, what would be even better would have been to actually ship the patch in a release but not disclose its severity (or even try to hide it by making it seem like a refactor or non-security relevant bugfix) until a week or two later; ensuring that any half-decent distro release process and user upgrade cycle will have the patch before its severity is disclosed. That's how the Linux kernel does it AFAIK and it's the most reasonable approach I've seen.
Though in the past decade or so, the lines have been blurred between a "dumb" editor and a full-on IDE with the advent of LSP, DAP and the like.
If you literally followed all the stuff from the bible, you could end up being punished for even just casually saying the name of another god according to Exodus 23:13 KJV.
Following a text literally is not the same as following the actual teachings of a religion.
Any "Bible" most of us can read is a revision of a translation of a translation with the additional problem of being coloured by the opinion of whoever had control over subsequent versions. You cannot take it literally. Like, at all.
If you as a translator, publisher, king or whoever had influence over a major revision of "the bible" started out with a phrase to the effect of "you shouldn't follow other religions' teachings" and had a particular pet peeve for people speaking of other gods, you could easily arrive at a wording forbidding the "mention of the name of other gods". I'm not knowledgeable about this in the slightest and cannot make any solid assertions here (though if you look at i.e. the older Wycliff version it sounds a lot less specific) but rather want this to serve as an example for just how much room there is for error in such historical documents.
There is no authoritative and exact source on the beliefs of Christianism as many assume the bible to be.
I feel sorry you had to put up with this person but I found your replies to be quite insightful :)
If they ignore the New testament, that would basically make them Jewish
I think that was the joke.
It's used in many cases where the machine may not be on the LAN and LAN is a technical term. "Internal" is not and to me signifies that it's "not public" aswell as probably managed by someone, well, internally at the entity you're with.