“@email@example.com I noticed the same server deficiency for GNU Social also.
This is an effect of the "guaranteed message delivery" from #AndStatus side and "duplication problem ignorance" from the Server side.
I hope pump.io will fix this some day @firstname.lastname@example.org ?!
The long story about duplicated posts, caused by communication problems, is here: https://github.com/andstatus/andstatus/issues/83”
Funny, Dianara and other clietns have no such problems.
The server very clearly replies HTTP 200, or otherwise, whatever error applies. Simple as that.
I find it hard to believe that AndStatus posted 6 or 7 posts correctly, and the server failed to reply "OK, success" every single time.
Plus, the reply has a lot of valuable information about the post that has just been created, beyond the "ok, received correctly".
@email@example.com I see that you didn't read that "long story" I referred to in my previous note ;-)
The point is _not_ about client applications.
There could be lots of reasons, why a client application sends duplicated posts: incorrect implementation (like the yesterday's test post), communication problem (e.g. when that HTTP 200 response from a server was not delivered back to a client) or even deliberate decision of a User to send the same post again and again... - In any case a server should not unintelligently deliver the same content to the same audience...
If you're interested in this topic, please start from reading https://github.com/andstatus/andstatus/issues/83
As a side note: I see that a reply to a note with a title should by default have the same title. Like for emails?!