On 2013-06-25 17:09:33 +0200, gregor herrmann wrote: > /* > JFTR: > - I don't understand "data loss" in this context.
In general, when posting a tweet, the user keeps the contents until the tweet has been sent. Since no errors are reported, the user can assume that he can remove the contents on his side. But since the tweet hasn't actually been posted, the contents are lost. This is a bit like a MTA that would simply remove the mail messages from the outgoing queue, even when the mail is rejected. > - And I don't think "grave" is correct as long as bti works with > identi.ca; but since this is about to change any time now when Evan > finishes the move from statusnet to pump, it will be ok Real Soon > Now, so let's leave it. - And looking at the actual issue is more > important anyway :) > */ Yes, but the "grave" was also about the (silent) data loss (only 140 characters max per tweet, but still data loss). -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
