I don't think there is any change in the API. My suspension is that after a recent upgrade to this server they either have a bug that they no longer sending an expected SUCCESS response, or it's taking too long to send it, and b then #AndStatus retries to b send it again, and I end up with dozens of the same replies until I realize it and delete it from the #AndStatus outbox. But that's a lot of assumptions on my part. I don't get the multiple replies using the web client or Mustard for Android. (Mustard is super old and hasn't been updated in like a decade, it still OStatus/GNUSOCIAL as StatusNet). #AndStatus doesn't have the same failure when I post a new quip, nor does it when replying to a post using my friendica account that I have set up as GNUsocial/Ostatus.
I know I don't get the repeating replies when I use Mustard, I'm guessing mustard just shoots and hopes for the best, #AndStatus has a retry mechanism.
Hmmm, seems to be an in compatibility between recent versions of GNU Social & #AndStatus. I suspect #GNUsocialjp isn't sending a success response that @andstatus is expecting.
!gjp
@mika83ac#AndStatus app has its unique features that make it a good choice for some users. And people always need an alternative, even if it is "very unpopular" for others ;-)
@z428 Frankly I personally read social networks rarely, and the #AndStatus app helps me keep a track of what's unread and look at that stuff and react at any place, even when there is no good connection. But what I value even more is a feeling that I really "own my data" :-) - I keep my conversations in the app for more than ten years already. I don't know why :-) @petrescatraian@volkris
@NEETzsche it all depends what your preferences are. I prefer #AndStatus for Mastodon/Plemora. I have at least half a dozen different fedi apps installed to try various things, but I think I end up just using mobile web more often than anything else (as I send this from #mustardMOD)
@dancingtreefrog Got you how. In order to investigate such cases #AndStatus logs are needed: they will allow to tell, why the app still thinks that the Note (Activity) was not sent. But probably a network problem occured during sending, and the app didn't get confirmation from a server about successful Note creation on a server. I thought that this should be a Server's responsibility to deduplicate/resolve such cases, and e.g. seeing that AndStatus client sends the same Note...
@veer66 hmm...me either. From this thread on #Friendica it looks very clear that I was responding to @phil's re-toot of @Haste's postbut you aren't mentioned in that OP, nor anywhere else in this thread as it now shows on my instance, so I have no idea what I or #AndStatus was doing that. I know I get some weirdness with #Diaspora contacts on #AndStatus with all replies showing as if they came from the OP, but never with Mastodon or other #AP contacts...
@isaakubus You could also try some older version of #AndStatus As you may see in the discussion that I linked to some years ago AndStatus had different implementation for line break option... Please follow up in GitHub issues
@AndStatus Hi, thank you for your excellent app, it is my number 1 app for fediverse maybe 6 years ago... I have a little question, does #Andstatus support #Lemmy accounts?
@gnu2 This could happen, when during sending a Note successful response isn't received from a Server (e.g. due to network problem), when in fact the Note was saved by the Server.. Later #AndStatus receives that sent Note as an unrelated one. Hence two copies.