masterspace

I don't necessarily disagree.

Though it does raise concerns about government identity systems and fascist governments...

I grew up thinking that was a ridiculous anachronism, but looking at how far the US has fallen, I do understand the concern.

Imho the best option is just OS level enforcement. You buy a device, you set up accounts on them, some can be kid accounts, those ones have their web fetches always include their restrictions.

This is horseshit.

It is worth remembering that many of those who champion Digital Sovereignty today were silent back in 2006, when the open ISO/IEC ODF standard — the pillar of Digital Sovereignty — was announced: not only did they not listen to us during all these years, but in some cases they greeted us with a condescending smile.

If we can speak of Digital Sovereignty in Europe today, it is thanks to The Document Foundation and LibreOffice community members at large, who kept the flag of open-source office suites flying when everyone was predicting their demise, and who continued to develop the only truly open and standard format that guarantees Digital Sovereignty, as it provides full user control over content.

The answer to this, is "thank you for your service". It is / was genuinely valuable. That being said, arguments about what people said or agreed with in the past is irrelevant to discussions about how to move forward.

The basic premise of this kind of arguing is a smell that you don't actually have a real argument to lean on. It's like credential dropping, it's a heuristic that hints at what could be a likelier truth than another, based purely on debate metadata, but that's it, and by their nature / definition, heuristics are constantly wrong.

Insisting on a white knight campaign to make a file format standard when you are not the standard file saving platform is Quixotic. It does not make you an ally of Microsoft to meet users where they're at.

The EU government mandating a certain file format might actually move the needle, a niche documenting software's defaults will not. This is why Microsoft's famous playbook was "Embrace, Extend, Extinguish", not "try and force a niche number of users into making this a thing somehow" (of course, Microsoft has also tried and failed the latter playbook numerous times).

Social media needs regulation for everyone, and I'm deeply concerned about the impact of ID verification on the open web, but at the same time, given the clear harms, it's hard to argue with people attempting some form of regulation, even if limited and imperfect.

No, as someone who has grown up and seen the change, it is vastly different.

I mean sort of, but it's a parenting issue in the way that smoking was for our grandparents, but in some ways, much worse.

With smoking back in the day, our grandparents were addicted to it, and inadvertently modelled that behaviour for our parents (or for other people's kids who thought they looked cool), leading way more of our parents generation to smoke, even though they started growing up being aware of the risks and the impact it was having on their parents.

Social media is operating like that, but one difference is that smoking mostly cost people money... It did also cost them time, but most of that time was paid in years of their lives at the end. Social media is costing everyone their time constantly, day in - day out, and sapping their attention, focus, and willpower... Leaving social media addicted parents even less bandwidth to try and make sure their kids grow up different then smoking parents.

You asked if you were wrong about what is a third party launcher, and they are pointing out that you were.

Your point of view does not matter when it comes to the definition of 'first party', 'third party', etc, because that is not how those words are defined.

Whether or not you like games insisting on you using the game developer or publisher's launcher is separate question from what is or is not a first vs third party launcher.

Somewhere between 4 porn sites and 30 million porn sites is quite the hedged bet.

I feel confident saying that there's at least 6 of them.

I was basing my assessment on the content of the article.

We're a small company so I do the opposite and am avoiding any co-authored tag being applied to the code I publish.

I review and test my code before it's published to make sure that it works and that it's the right solution to the problem, and I'm the one responsible for fixing it if it goes wrong late at night in prod.

That was the case when I was using Intellisense and codegen tools and that's still the case now.

That makes me the author.

Anything else is a lie, a violation of engineering ethics, and is flat out not SOC2, nor regulatorily compliant for anything that matters.

That used to be the case, largely because we used to be really bad at converting AC to DC (and vice versa) so would incur a ton of efficiency loss at the conversion step.

But for the actual on the wire transmission part, high voltage DC is inherently more efficient at long distances because you don't get drift between the voltage and current phase (which reduces its effectiveness).

These days though we are far better at converting DC to AC (and vice versa) so high voltage DC systems are overall more efficient (plus let you connect distribution systems without synchronizing them, or connect ones that operate on different frequencies like 50Hz vs 60Hz).

Their downside is that conversion equipment is still more complicated and slightly more prone to failure then AC systems.

The US has already literary intentionally tried to starve the people of Cuba for decades and it's accomplished nothing.

America's cruelty in service of America's incompetence really exposes what a sad, atrophied husk it's become.

All empires collapse, at least others have managed to do so with dignity.