Status posting Idempotency

Every time the currently composed status changes it updates the idempotency key with a timestamp, so it stays the same if the post status request fails, but changes every time user willingly changes the content in any way or the form is cleared after successful posting. Server won't let through statuses with the same idempotency key so this eliminates double posts when user thinks a status didn't go through and hits submit again without changes.

added 1 commit

• bca77ef9 - update changelog

Compare with previous version

can be const

true, it could due to how js's const is borderline useless with objects, let makes it clear that the data is getting mutated. it's mostly just a semantic and not a technical reason to use it here

it could lead to different optimization by JS engine, anticipating that that reference to object might change

not reason enough to change it, it's a local variable with a very short lifespan, assuming optimizations of the underlying VM and changing code because of completely unproven assumptions is a really bad practice

lgtm

Very nice!

merged

mentioned in commit 0ea23a03

mentioned in issue #595 (closed)

mentioned in issue #760