That sounds very similar to my plan on Tesco mobile although my data is limited to 1.5GBs. What is your experience of 3? I've heard bad things about them and worry about the quality of their coverage. Would you recommend them? And if you don't mind me asking: where in the UK are you located?
I was there too and don't believe that the problem was with the ticketing system. They overestimated the maximum capacity. The Swamp 81/Numbers stage was massively popular and had a max capacity of 700... for an event with 15,000 attendees.
It seems so obvious to me now, but I just realised that is something that I do; I focusing on understanding what is causing a bug and how to fix it, but not why the bug occurred in the first place and how to prevent myself making similar mistakes in the future!
The point is not that it can't be done securely, it's that they don't want the hassle of being responsible for a large amount of sensitive information. By not storing the information in the first place they can guarantee that they won't be hacked and have their customers data stolen.
iOS push notifications are created on a server and then sent to the users iPhone. This means that the server must know about the event in order to generate the push notification that you see on your phone.
When you send a message from WhatsApp to your friend, the message is not sent directly from your phone to his. What actually happens is your message is sent to WhatApp's server, which then generate a push notification and sends it to your friends iPhone. (Push notifications must originate from a server. Your friends iPhone cannot check for new messages, instead it is told when there is a new message).
In Sparrows situation, they have no control over Gmail's server, and so they do not know when a new email is received and therefore cannot send a push notification to the users iPhone. Sparrow could store everyone's Gmail credentials on their own server and regularly check Gmail's server for new messages for each of their users and, if there are new messages, send a notification to the relevant user. However, this would mean that Sparrow would have to store everyone's Gmail credentials in one place which has certain security implications and, understandably, they do not want to do this.
The iOS push notification service works by having a remote server determine when a push notification needs to be displayed to the user. The only way for Sparrow to do this would be to store the gmail credentials of every user who uses their application on a server (instead of each individual users iPhone). This would obviously introduce a lot of security considerations that Sparrow don't want to have to deal with.
Alternatively, Apple provide an API that certain apps may use to regular check for updates by running code on the iPhone, but Apple are not allowing Sparrow to use this API.
I might have misunderstood you. Do you mean that if they don't want you to share the content then they shouldn't sell it to you, because you will share it regardless of what the terms of the sale dictate?