I think this is a little hyperbolic. The product may drop features, increase prices, and squeeze its free tier users. Everything enshittifies. But the idea that password export might disappear or be degraded? Nah. You'll be able to jump ship any time you want.

>You'll be able to jump ship any time you want.

Famous last words...

I mean, LastPass was a train wreck after their breach, but they didn't go as far as trying to stop me from exporting my vault when I switched to BW.

The idea of BW doing a rug pull and suddenly removing the ability to export your vault I think would trigger a class-action lawsuit.

I don't know why this is framed as "jumping ship" ... of course you can stop using it any time (and use your periodic export to go elsewhere).

The real issue is potential data loss. Remember LastPass? Bought by someone and downhill it went, with multiple security incidents.

Never underestimate the lengths companies will go to, to enshittify their product to squeeze customers for money.

Name one major password manager that blocks or paywalls export.

The iOS "passwords" app didn't support exporting for a while, though they eventually added it.

Usually when this type of thing happens, all the major players decide to do it at the same time.

- Authy

- Google Authenticator

Not password managers of course, but thanks for reminding me that I should figure out how to ditch Authy.

https://github.com/BrenoFariasdaSilva/Authy-iOS-MiTM is going to be my project for the afternoon.

I had to migrate from Authy because it doesn't work on Graphene OS. Migrated to Ente Auth and couldn't be happier.

Ente Auth

is a good alter. Works perfect for me.

Google Authenticator has an export-as-QR-code function that several other authenticator apps can parse. Is it the best/most convenient implementation? Obviously not, but you can absolutely export the codes.

Notably not password managers.

Comment you're replying to should've specified afterwards. Feature that were never there is very different than pay walling a such essential feature.

How you use the tool matters, yes. But the freedom to demonstrate and understand this weakness with watermarks is much more important to exercise than saying "shhhhh don't tell people about this".

The takeaway should be that watermarks aren't very reliable and you should keep your guard up anyway.

I think we can find out a way where these watermark, becomes too difficult to remove

Checking openrouter (it's not available yet) and, uh, what's up with the spike in Qwen usage from early april here? https://openrouter.ai/qwen

Is this normal humans kicking the tires on a new model, or a few whales doing serious benchmarks?

Qwen 3.6 Plus released and they offered it for free

personally seen a lot of people switch to Kimi and Qwen after Opus 4.7. Kimi 2.6 feels like Opus 4.6 which, to me, was a great model for 98% of coding tasks

Frontier: Need it done quick and I'm willing to pay.

Open-weight: Good enough for the majority of tasks, and I'm willing to spend a bit more time and effort steering towards my desired result.

I've realized that in most of my workflows, I really don't need frontier-tier intelligence

95% of the work most of us do is mostly just plumbing - connecting X and Y together. A ton of grunt work - writing basic loops, fetch statements, importing libraries. You really don't need PhD level intelligence to handle these

The only time you need Opus 4.7+ tier intelligence is when you're quashing a nasty bug or refactoring something complex

Your soul is nourished by navigating congested traffic and searching for mundane stuff on the internet? That's not how mine works.

I have a Dell U3225QE with a built-in KVM and 2 macs.

One connects with Thunderbolt only. The other connects with Display Port for video and USB-C for the rest of the built-in dock.

It's OK most of the time with the nipple switch. My one piece of advice is *avoid HDMI*. I learned after getting this monitor that the HDMI protocol is a petulant unstable little shit that does not tolerate renegotiation well. Get yourself a USB-C to DisplayPort cable.

I have had exact opposite experience WRT display technologies. I normally use USB-C <-> DP, but they are far more finicky than HDMI. I only use the former because the hub I have for my Mac doesn’t do 4K@120 Hz over HDMI.

EDIT: sorry, the reason is because the monitor has HDMI 2.0, so it can’t do 4K@120 Hz over HDMI. Otherwise, I’d use the Mac’s native HDMI port and be done with it.

I think you might be confusing Umami with Plausible? Plausible is a total mess of heavy-idling containers and ClickHouse. I dropped switched to Umami and have had no performance issues of any kind. It's running on ~12 year old shitbox. I do only deal with ~10K events per day max though.

> Go is absolutely an easier/simpler language than JS/TS.

You're suggesting that a language with concurrency is simpler/easier than a language that does not have concurrency.

Does the event loop not exist? Go has parallelism where JS does not. Both are able to run concurrent actions (async in JS).

I was really into Andy's blog when it first came out, but he might be doing the same motivated reasoning he complains about everyone else doing.

https://blog.andymasley.com/p/data-centers-heat-exhaust-is-n...

> The one remaining question: why the clean step change?

In the middle of this piece, he runs into a critical flaw in his reasoning and just shrugs it off.

This is a weird take but I think I like it?

Indeed. _everyone_ has noticed it. Nobody really has any plan to fix it. IMO the urbanism movement comes closest to having some practical plans.