Never play the "who's dumber" game with private companies you'll always lose. If it happens twice you should switch on your common sense and stop using the service, or at the very least change your behaviour/don't be surprised if you get banned.
> which any engineer worth their salt should’ve predicted - this is not rocket science
There are probably tons of other issues you don't know about. Making it work offline would probably increase the attack surface, &c.
Any engineer worth their salt knows that they have 100 things to work on and this guy's corner case didn't make the cut. Easier for them to ban him and work on a new feature that generates revenue for thousands of users.
My point is that this isn’t some minor bug that you can leave in the backlog because it’s just a minor inconvenience. This is a major dealbreaker that should’ve been thought of when designing the service in the first place.
> which any engineer worth their salt should’ve predicted - this is not rocket science
There are probably tons of other issues you don't know about. Making it work offline would probably increase the attack surface, &c.