I use the same tool. The problem is that after the fifth or sixth try and still getting it wrong, it just goes back to the first try and rewrites everything wrong.
Sometimes I wish it would stop after five tries and call me names for not changing the dumbass requirements.
Most IoT devices that died did so because the vendor went out of business and had to shut off the servers. Most lived in hope that a last minute investment would keep them afloat. In a few other cases, it was the middleware software provider (like Google IoT) that shut down and bricked a device.
This legislation might apply to a big company that decides to discontinue a product line and could then send notices out, but most startups won't know (or admit defeat) till the last possible moment. By then it's too late.
I used to work with big companies collecting IoT data. 90% were collecting telemetry without knowing why. Or having business goals they could easily achieve in other ways, without hoovering everything and violating our privacy.
The rest were doing it so they could sell it to data brokers and make money.
None of them were trying to push privacy as a competitive advantage.
Still locked out, but posted a comment upthread that you may want to consider.
Just had a thought... here's a prime example of one of the stated advantages of the Fediverse. If you get locked out of one account, you can move to another instance.
Question is: do you get to carry over your profile, subscriptions, followers, comments, saves, up/down votes? Or do you have to start from scratch.
Because if it's scratch, somebody should change the "Fediverse Promise" so users know what to expect.
I'm guessing I know the answer, but this could be something Voyager could handle. Maybe even for a sustainable fee 🤔
Also, if you logout, you can't log back in. Sounds like it's getting blocked at the server end.
If you right-click and View Source, it all fits on one screen.