This is an issue for those of us who use talon when on public transit in cities which haven't gotten around to full connectivity yet. (e.g. NYC.)
When connectivity drops (which happens frequently at rush hour when thousands are trying to connect to towers and access points once one enters a station) clicking like or retweet does nothing. When connectivity returns, one is able to click those buttons and get a response of "sending..."
Ideally, the program would notice that connectivity has dropped and queue those requests for when connectivity returns. (And perhaps note accordingly that those requests have been queued, and give us a place to see the queued requests.)
Is that possible or would that require a major rearchitect?
This is an issue for those of us who use talon when on public transit in cities which haven't gotten around to full connectivity yet. (e.g. NYC.)
When connectivity drops (which happens frequently at rush hour when thousands are trying to connect to towers and access points once one enters a station) clicking like or retweet does nothing. When connectivity returns, one is able to click those buttons and get a response of "sending..."
Ideally, the program would notice that connectivity has dropped and queue those requests for when connectivity returns. (And perhaps note accordingly that those requests have been queued, and give us a place to see the queued requests.)
Is that possible or would that require a major rearchitect?