Also Nine Sols. It's becoming increasingly popular as games are moving the complexity/flashiness of interactions with enemies to the enemy's side. Rather than learn and perform complex combos like Devil May Cry, the enemies now are the ones with very flashy movesets and now you simply parry/dodge.

From a personal use perspective yes, the big issue here is enterprise and existing contracts as surely most companies will have signed zero retention.

I've seen a few organizations consider moving from ADO to GitHub (only repos and CI/CD pipelines) due to the new fancy AI features, but this frequent downtime has been a constant in meetings.

ADO may be stuck in time but at least it works.

I do see one Googler in the Twitter chain saying "Sorry. This will be fixed." but I wonder how these Google projects get insights from customers if they can't get through the AI support barrier to a proper human.

Or is the current expectation that everyone needs to shout on Twitter to get their Google problems solved?

VSCode just released their Agents Mode, this is pretty much the same thing. Surprised they decided to do a split like this all of a sudden.

I feel the same way, it's all very terrible and I'm glad you felt the same and made an alternative.

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.

Thanks! Yeah basically I did this also for the waifu, so she has a qr extension easy access, I haven't user qr-cli I will check it

Reminds me of Telegram that forces you to pay premium to login to a new device depending on the country. Login, not registration. This is all due to the cost of SMSes of course.

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.

sms are free, at least rcs

RCS is not SMS. RCS does have a fallback to SMS in some rare inter-carrier cases, but it won't fall back if you're stuck on 2G or anything.

SMS also isn't free. Many contracts contain "free" texting, but that's just SMS being packaged into the subscription price.

Carriers charge each other for (excess) SMS exchanges, so SMS simply cannot be entirely free.

Keep in mind they're deprecating it because xAI is doing so upstream.

https://docs.x.ai/developers/migration/may-15-retirement

The obsidian vault is to already have the chosen plugin pre-selected and is part of the social engineering effort, that's not the main problem.

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.

The pop-ups and "social engineering" in question are things that any users in HN likely already accepted, which is to enable community plugins. These community plugins are the backbone of Obsidian and where a lot of the meat is behind its fame come from.

There's no protections beyond that, community plugins can do whatever they want. Thankfully, the vast majority of them are open-source.

I'm gonna push back against the "backbone of Obsidian" part. I'll argue that vanilla Obsidian is plenty powerful enough.

I know many people swore / swear by the datatables plugin, but now that Bases in core, you can get pretty far without it, no?

I agree with you that vanilla Obsidian is plenty powerful, but it's exactly like Vim's case. It's good enough on its own, but there's always more.

There's countless articles and videos about various community plugins and even curated selections of them depending on your use case for Obsidian.

I can't do without the livesync plugin. And also copilot (connected to a locally hosted LLM of course) and readitlater.

As someone who doesn't use shared vaults - would the warning popup, 'to enable the "Installed community plugins" synchronization feature', not be on a per shared vault basis? Is trusting a single shared vault for plugin sync going to mean I sync my plugins for every shared vault?

IMO that's an issue in and of itself, but it doesn't read that way in the (very unclear) original article.