Conversation:
Notices
-
@gargron andstatus does that sometimes
-
@gargron I am the best at spam#2
-
@gargron First wasn't labelled. I did five, all numbered except the first.
-
@gargron Looking at my dev instance it received all of them as well.
-
@gargron Strange
-
@maiyannah Could it be because they had a hash symbol and the first did not
-
@maiyannah Could it be because they had a hash symbol and the first did not
-
@maiyannah @gargron On duplicated posts please read this discussion: https://github.com/andstatus/andstatus/issues/83
-
@andstatus @gargron @thefaico In this case, I had sent the message successfully using andStatus, and then exited out of the app. Next time I checked andStatus on the phone it posted the status again. I notice it does this a lot if it's suspended - it attempts to resend the last status if its suspended, regardless of whether the server got it or not. It might be…
-
@maiyannah As written in the above mentioned discussion, I think this behaviour of the server would be much better, even better than Twitter does ;-): --- Meanwhile I checked how Twitter responses to posting the message ("tweet") with duplicated text. It returns HTTP error "Forbidden", even if the duplicated message is not the last message sent by this user. It will be far more…
-
@andstatus @gargron @thefaico I can't speak for Mastodon but we can leverage code that already exists in postActiv/GNU social to check for duplicated message by way of checking the message content. We'd just be using the existing rate limiting code for another purpose.
The question becomes how far back we go, and it still is only a bandaid for the fact that the application is sending notices in error.
-
@maiyannah There could be many reasons, why a client application resends a message, not only its own error ;-) Another quote from the old discussion: --- In this case, I guess, we need to decide on the expected behavior of AndStatus first. My intention is to ensure that messages, posted via AndStatus, will be actually delivered to the server. Hence it is expected that in a case…
-
@andstatus @gargron @thefaico Resending a message I already sent when I don't want it to is not desirable behaviour.
-
@maiyannah@community.highlandarrow.com I agree, and as I wrote, AndStatus resends only those posts, which were not successfully delivered to the server from the application's point of view.
-
@andstatus @thefaico Well, it's point of view is self-evidently incorrect since this duplication occurs regularly.
-
@maiyannah The point of view is incorrect, but it doesn't mean that this is a client's error or bug! And this why I proposed an intelligent fix at a server side...
-
@andstatus @thefaico As I said, I do want to repurpose the rate limiting code to create an API endpoint that someone can check to see if a notice with the same text already exists. However, it is still on applications to check that endpoint, once I have written it :)
-
@andstatus @thefaico This is what my tired brain is trying to get at - I can add that, but applications will still have to adopt the use of ti. It is not something I can make work automatically with no changes on the application side.
-
@maiyannah I think that relying on a client application to check for duplication is conceptually wrong, because this solution won't guarantee absence of duplicated posts at a server side. E.g. a client application reposts intentionally, or has a bug...
@gargron
maiyannah
AndStatus
All Hacker Poesy content and data are available under the