We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
End of support for OS X 10.4 and 10.5
Why pull support and remove functionality? Why not just drop support -- just stop updating the app but still allow basic functionality? There are still a lot of legacy machines that are still in use ...
@JoshK: thanks for being the man to share the reasoning. I get that and see a possible easy way to leave legacy support....
A few old servers, old existing s/w, serve the fixed size (&declining) "original" mode users, the clients would just need to address some form of subnet address which I'm sure a bit of network whizzadry can do - at worst we all move to legacydropbox.com or whatever.
The trick is to gateway between data on these servers and the newstyle supporting new clients - and I can see that is another layer of the version resolution handling that already exists from client A overlapping client B updates - just here A is legacy land and B is main land. I guess that depends on your architecture and hits your 32 - 64 bit ident thunking issue.
Can that not just be all 32 bits codes are treated as 64 bits by with leading zeros and reserving these for files used by the merry band of those with a foot in legacy land.
I'm sure my thoughts are somewhat simplistic and there may be a bit of work but not insuperable. Maybe it could be crowdsource funded...?
As you say, other breakers may roll up in future - but all it needs is a "gateway" solution and, we hope, that can continue.
If not how aboput spinning-off legacydropbox.com with some old servers and code and you are done? keeps the size down and leaves any new to old world issues up to us users... At least there is a future for those that need it then.
