I get this with videoconferencing too (webex, teams), where the app starts downloading and the ability to do what you want (use the browser) is hidden or delayed until you've failed.
I wonder how many people installed the app thinking it was the only option now. I assume a lot of people. Or how to increase your install numbers with that one weird trick.
Very sneaky.
This is the dark side of the "update culture" --- forcing you to take all the things you don't want along with the bug fixes. Aided by dire security warnings of not updating, it's a perfect way to achieve control over your userbase.
If you can get the switch vendor to release a GPL archive (which is often a struggle in of itself) I have never seen them release the source code to manage the switch ASIC. That's always built as an out-of-tree module which is not released as part of the GPL archive.
Many switches are not even running Linux, it's quite typical to see eCos, VxWorks, or an RTOS (e.g. ThreadX) on a switch.
tl;dr - even if the switch runs Linux (many don't), it is very unlikely you will have the datasheet and/or reference implementation for managing the switch ASIC
Open source is the only equipment you can trust to not adopt this model as it’s much more profitable than shipping a box once every five years.
You're right Ubiquiti did it though and I believe their devices are priced even higher. (Edit: note the post next to mine says you can opt out of this.)
I agree replacing the stock firmware with an open-source aftermarket one like OpenWRT is the way to go but there's still the moral dilemma of supporting such practices with your wallet.
I was also thinking if this could be an attempt to thwart the second-hand market for their devices? Is the binding to the online account permanent, or maybe it requires unbinding the previous account first?
Is there additional telemetry that cannot be disabled?
If Ubiquiti staff has the non-existent procedures and corporate security for this to happen, they surely don't care about your privacy or security.
Not cool to do that :(.
I wouldn't mind going back to where I started and using Tomato again, so I was curious what major thing(s) they've done in the last 10 years and why you would chose Tomato over dd-wrt or openwrt.
As far as I know the choice is constrained by the SoC in the device you have (or are planning to get): generally, Tomato has better support for Broadcom devices, and OpenWRT works better on Atheros. DD-WRT should be more balanced in this aspect. (And predictably, open-source support for MediaTek devices is the most patchy.)
I haven't really used Tomato. Between DD-WRT and OpenWRT, the former is arguably easier to set up (through the GUI), while the latter can offer more functionality (with no hardcoded settings and a huge repository of installable packages). OpenWRT has higher memory and storage requirements though.
Could you clarify what you're claiming here? The obvious interpretation seems far fetched.
Buy router, plug it in, change password and rarely any setting required for average user.
Not worth the monthly fees and data collection on users (name, email, location, credit card,...)
How generous, for a device that people buy (not rent) from them, and pay actual money for (not receive for free).
And apparently Netgear didn't even feel the need to bother including any contrived excuse as to why this is being introduced. What a time to be alive.