In actuality there are several forks, and the original Crosspoint Reader really got the ball rolling, but now seems to get stuck in discussions. The forks (especially the one I linked) has progressed much further and has better KOReader sync (as in actually syncs to the correct XPath position instead of some close-enough position), bionic reading, streamlined UI, etc. Give that one a shot!
Is it cheating, though? I find it is more like bringing the games difficulty down to an acceptable level. I enjoy puzzle games, but often the puzzles boil down to combining everything in your inventory with everything in the game world (in LucasArts terms). That can simply be unfun for some of us in a game we otherwise enjoy. A variant of this is that I would e.g. enjoy open world-ish action combat fantasy games, but I really do not find the Souls like loop of git gud compelling at all, so I... basically don't play these games. But AA or AAA fantasy action games with this kind of presentation are (at the moment) basically only Souls like, so... yeah, great. At least for puzzle games I can "cheat" if one of the puzzles is simply illogical for my way of thinking, so I can skip over that part and go back to enjoying the rest of the game...
I remember a different app thats was used on e.g. festivals where the local broadcast cells where overwhelmed when a quite rural area suddenly had to server 50000 to 100000 additional people and 3g and 4G basically stopped working. I think it was called Firechat or something.
That seems to me to be a direct result of too many actors involved in the creation of the Deutschlandticket actually ebing against this ticket, and so those in favor tried to appease them and created this absolut disaster of a booking process. There is no other reason for this otherwise, and it would be trivial to sort this out by e.g. having a validity period of 31 days, or always going until the end of the month and costing only a percentage. But that would be too easy.
I was with you until this point, but 1.2 is bigger than 1.10, because 1.2 is a shortened version of writing 1.20 _unless_ you explicitely want these to be version numbers or something like that. The normal expectation would be to treat numbers as, well, mathematical numbers, and not SemVer, especially if we only have one decimal point, don't you think?
Thanks. We do not serve video, so it is indeed not that comparable. But we do have hosted web applications (SAP CRM), and syncing of offline applications for field staff (technicians) (and that can be quite a lot of data). It seems that our use cases mean either low latency and low bandwidth (non-technical users and their web apps, where "stuff is broken" if it is slow, but they might be already used to that from other areas of their online lifes) OR any latency and high bandwidth (sync doesn't really care if the packages come in with ultra low latency, as long as it syncs). Might work out indeed.
UIh, any specific issues? My company will be rolling out SAP from Germany to ZA soonish, and so far we have not yet had a chance to actually really test the connection. Self-hosted data center here, so probably not that comparable. Just overall crappy connection?
In actuality there are several forks, and the original Crosspoint Reader really got the ball rolling, but now seems to get stuck in discussions. The forks (especially the one I linked) has progressed much further and has better KOReader sync (as in actually syncs to the correct XPath position instead of some close-enough position), bionic reading, streamlined UI, etc. Give that one a shot!