You could say that decentralized systems are thus passed to centralized systems by value, and not by reference.
I'll show myself out. 😅
Joking aside, it's a pretty decent read: https://www.thediff.co/p/the-promise-and-paradox-of-decentralization
I imagine when the branding is complete we'll get the following gem:
<meta property="og:title" content="Meta">
<meta property="og:site_name" content="Meta">
<meta property="og:url" content="https://meta.com">
The first time I open TWDNE I get: https://t.co/aNHXf7MfgI
Yeah, thanks for that. 🧐
If the ethical framework for Delphi #AI is actively reinforced from a highly constrained set of inputs, then isn't bias inherently being placed into the system, thereby easily predicting the outputs?
Isn't this just doubling down on using training models over backpropagation?
Recently unredacted documents from #Google's antitrust case outline "Project NERA", the strategic precursor to their Privacy Sandbox initiative.
Full document here: https://storage.courtlistener.com/recap/gov.uscourts.nysd.564903/gov.uscourts.nysd.564903.152.0_1.pdf
@abeorch @humanetech IMO if they opt to export only the user's toots, and implement a Read-Only flag on toot replies, that would solve half the problem.
Afterwards when importing, any children or parents of a user's toots in a thread would simply display the username (without a hyperlink) and the comment text (in a grayed-out fashion) so that the context of the thread isn't lost — and at the same time NOT initiating mass federation requests over the network.
@humanetech I would argue that Mastodon does not "support" moving accounts, for the simple reason that any import/export/migration feature that does not include user-generated content is inherently broken.
Transferring followers is transferring metadata. Moving toots is what constitutes as migration IMHO.
Mastodon's developers have said that moving toots would be too much of a database-intensive task, and would also break comment threads. Fair enough, but it's still broken.
Ouch. The dissonance that exists between Dev and Ops is sometimes surprisingly understated.
via: https://nadh.in/blog/javascript-ecosystem-software-development-are-a-hot-mess/
Sometimes I do browse comments, but mostly I just want to see what's trending/interesting on the Hacker News front page without straining my eyes.
On that note, I whipped up Haychen; that loads the top 25 stories with far less clutter.
Also, a phonetic pun of HN. 😄
@stampirl Well that's why I linked an (open-source) extension in the original toot.
It adds a button to Firefox's tab bar that you can use to quickly toggle the 'resist.Fingerprinting' setting OFF when faced with the Cloudflare portal, an ON again once you've gotten past.
Doesn't fix the problem, but makes it super easy to toggle the setting just when you need to (for login/portal pages of sites that a strict WAF setting), without having to "give up" any privacy all-around.
@stampirl Yeah, until Cloudflare fixes it.
It's a known issue affecting many sites (GitLab, for example) that use Cloudflare's WAF to issue a browser-based challenge to visitors.
You can read more about the issue here: https://community.cloudflare.com/t/firefox-resistfingerprinting-vs-cloudflare-challenge/306354
Getting infinite-looped on any of #Cloudflare's "Checking your browser" challenge portals when using #Firefox?
It's due to the 'privacy.resistFingerprinting' boolean in 'about:config'. Toggle that, and you'll get in.
An extension to make this easier is https://github.com/Aaron-P/ToggleResistFingerprinting
https://www.nomadproject.io/docs/nomad-vs-kubernetes
Shots fired. But in truth, the simplicity of any one of their products in (and interoperability with the rest of) the HashiStack makes a compelling case.
https://www.jonstokes.com/p/why-a-chinese-invasion-of-taiwan
The use of tactical scorched-earth scenarios to destroy fabs and/or IP holdings actually seems practical, but I'd wager TSMC will be looking to decentralize their factory locations into and including the Western Hemisphere long before that.
https://www.innoq.com/de/blog/nginx-ssi-env/
Usually today's static site methodology would opt for injection via client-side routing, but good old SSI provides an interesting (read: secure) way to hardcode ENV variables into something like NGINX; although I'd personally use Varnish (ESI) instead.
https://www.roundcrisis.com/2021/09/28/bytesize-architecture-sessions/
This seems like a really good extension of a typical stand-up for things like knowledge transfer between departments that should understand DevOps/SysOps choices, and the moving parts involved.
I've always been a fan of Hot/Warm DR setups, and corresponding Cloud Native environments that offer agility and modern security architecture choices, such as zero-trust networking.
SysAdmin. WebDev. This. That.
Honor is what no man can give you, and none can take away.