Conversation:
Notices
-
@verius Local IDs (long numbers) may or even should be used internally to simplify local database design and improve performance. URIs are for data exchange via APIs ?!
E.g. in AndStatus we use numbers (local ids) as keys for relations between tables...
@maiyannah
-
@verius As @maiyannah explained, currently I'm proposing a new point of message UID/URI creation to help solving a problem of sending duplicated messages from a client to a server.
Message URI is exactly that field that can be universally used for deduplication in different cases. Including deduplication of messages that a client application received from different fediverse instances (using different accounts).
-
@andstatus @verius @thefaico Yeah, so, if we have that, and the messages have UIDs we know are unique, we can use that as a means of helping detect and suppress duplication. What I'd like to do is have the server send a challenge if the message sent to the API is duplicated, like "we already have a message by this user with exactly that contents in message <uid>, d…
-
@maiyannah I would say that the best response to posting of a duplicated message will include that existing message object, which the new message duplicates. So the client app will know for sure that the message was successfully sent already and will have that sent message without additional requests.
@verius @thefaico
-
@andstatus @verius @thefaico Yeah, I'd probably header it with some sort of thing saying "Im a duplication challenge" and the notice object. The uid would be in the notice object and could be used for further follow up checks in the client if desired.
-
@verius Having a Message URI generated by a Client application allows to avoid any message body comparisons. For the case, when this is not an intentional duplication/spam. But spam is another topic, out of scope of this conversation.
@maiyannah
AndStatus
maiyannah
All Hacker Poesy content and data are available under the