Looking for a response from Evernote team, or a link to one, not people speculating unless they have something useful to add.
TL;DR Legacy seems to stop working in a manner that indicates (1) issues on the server happening for many users on the same day, but (2) specific and "sticky" per client machine, with only some machines permanently breaking and others being fine with the same version/account/OS/network/...
What can possibly cause such specific symptoms? I have some speculations below, can you please fix or just announce what's going on?
Long details:
I have 3 computers all running Windows 10, same network, ~same everything, and same 6.25 legacy (literally from the same installer on a usb stick). A few months ago, machine #1 legacy stopped syncing (password error, and connection error on logging out), I went here/to reddit and there were tons of people complaining about legacy breaking on the same day. However, machines #2-3 kept syncing fine.
A few days back, machine #2 stopped syncing with the same symptoms. Again, bunch of people complain on the same day. And again, machine #3 is still syncing fine! And on the forums some people claim 6.25 works, I assume they are also lucky.
Clearly this is not a local issue cause a bunch of users all break on the same day and there aren't many complaints on different days.
At the same time, the broken-ness seems to be "sticky" per machine, surviving reinstall.
I uninstalled on #2, nuked the DB and any registry settings left behind, reinstalled, and it won't even start - says immediately it's not online and cannot connect.
Also machine #1 is also still broken, for months now.
So, some machine ID (based on hardware/Windows install/IP/...) is probably involved?
What can possibly cause such specific symptoms? As it happens, I work in distributed systems for a big tech co and I've been scratching my head. The only thing I can think of is that there's legacy-specific load-balancing somewhere based on machine ID, and as that legacy infrastructure is decommissioned in steps, the old machine IDs do not get re-assigned. So, they talk to dead instances while some "lucky" machines talk to the remaining live instances.
If so, can you please fix this?
Otherwise, it's really hard to come up with a charitable explanation here. If you are disabling legacy, disable legacy and announce it loud and clear. Are you trying to just create chaos and FUD among legacy users to have people upgrade?