Untitled attachment

Notices where this attachment appears

1. AndStatus (andstatus@loadaverage.org)'s status on Friday, 21-Sep-2018 11:16:29 UTC AndStatus
   @1iceloops123 No no, blame GNU Social server. More details here: https://github.com/andstatus/andstatus/issues/83
   @jeff @hj @wowaname @louisoft01
2. AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 07-Mar-2018 05:35:39 UTC AndStatus

   in reply to
   @mcscx As I wrote already regarding duplicated posts: this is an effect of the "guaranteed message delivery" from #AndStatus side and "duplication problem ignorance" from the GNU Social server side.
   The long story about duplicated posts, caused by communication problems, is here: https://github.com/andstatus/andstatus/issues/83
3. AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 21-Dec-2016 17:37:15 UTC AndStatus
   @japananon I like that you already got acquainted with a Command queue of AndStatus :-)
   Regarding duplicated posts: this is an effect of the "guaranteed message delivery" from AndStatus side and "duplication problem ignorance" from the GNU Social server side. More on this here: https://github.com/andstatus/andstatus/issues/83
4. AndStatus (andstatus@loadaverage.org)'s status on Thursday, 08-Dec-2016 16:00:55 UTC AndStatus
   @deavmi Please read on duplicated posts here: https://github.com/andstatus/andstatus/issues/83
5. AndStatus (andstatus@loadaverage.org)'s status on Monday, 14-Nov-2016 11:59:33 UTC AndStatus
   @maiyannah If you really want to discuss this issue, please do it in https://github.com/andstatus/andstatus/issues/83
   Otherwise we are going in circles :-(
6. AndStatus (andstatus@loadaverage.org)'s status on Monday, 14-Nov-2016 06:20:14 UTC AndStatus
   @maiyannah I evidently couldn't explain to you, why current behavior is correct :-(
   Instead of pointing to inexistent bugs, please read our discussion on this topic and take part in it here: https://github.com/andstatus/andstatus/issues/83