Because it does not remove a spectator, it ends the entire match. Please read the article.
421 karma · joined October 5, 2018
It's been 7 years and we still don't have feature parity with what UIKit got in less than 3-4 years of its life.
That's a problem with DMCA in that it's applicable in an immediate and unilateral manner and any decision to resist comes after the takedown. DMCA is the problem in this context, not "copyright" itself.
ADO may be stuck in time but at least it works.
Or is the current expectation that everyone needs to shout on Twitter to get their Google problems solved?
That said, exactly due to this problem I just use qr-cli whenever I've needed QR codes as it's pretty quick and handy.
There's countless articles and videos about various community plugins and even curated selections of them depending on your use case for Obsidian.
You can bypass this if you have a passkey, but phone and password isn't enough. No idea why they opted to do that, it's not like passkeys are indicative of any device binding.
The issue to solve is payments, Portugal for instance has its Multibanco payment scheme, but it's only used in Portugal. I assume eventually it'll be cobranded with Wero like it happened to Netherlands' iDEAL and eventually fully replaced.
The issue is that this could happen to anyone who just searches the malicious plugin's name and installs it. Worse if it's a popular one that gets compromised.
There's no protections beyond that, community plugins can do whatever they want. Thankfully, the vast majority of them are open-source.
Many of the european countries have their own "Pix", but there's no European-wide alternative. The ECB wants to make one (tentatively titled "digital euro"), but it's going to take a long time to come out.
Here's a charitable take, assuming there's no messed up internal politics in a company going on: Because not everyone at a company is working at the same speed.
If you have developers who are now sitting around doing almost nothing because the stakeholders and product teams aren't using AI yet, then you have a bottleneck. Even before LLMs, if you had an excess of developers to the speed the teams they depend on deliver, you'd lay them off all the same.
There's two ways to go about this: The company either lays off engineers and delivers at the same speed as it did before, trading personnel cost for tokens (Showing it's a company that doesn't want to grow or is currently unable to), or alternatively the company keeps things as is and forces the rest of the departments to grow with the new added velocity from the engineering teams.
This isn't about being right or wrong but about what the publishers will do when they see their games are again getting cracked day one, and if it'll be a catalyst to again return to getting either less PC releases or at least delayed releases compared to consoles.
I will hope that does not happen.
Juniors don't have that skillset yet, but they're being pushed to use AI because their peers are using it. Where do you draw the line?
What will happen when the current senior developers start retiring? What will happen when a new technology shows up that LLMs don't have human-written code to be trained on? Will pure LLM reasoning and generated agent skills be enough to bridge the gap?
It's all very interesting questions about the future of the development process.
There's a lot of useful use cases for OpenClaw but I wish I had the guts.
It's also a lot more comfortable for one-hand typing since you can do multiple swipes per word.
Funny that looking at their "number of touches" and "distance covered" checker, I've tried a few words and thinking in my head how it'd be in Nintype and it would score far better than Keybee.
Unfortunately I haven't seen anyone since Nintype (and the older Keymonk) to give it an attempt.