twitter has a system by which posts in a short time frame will not result in duplicate posting, i have noticed cohost does not seem to have this and some people may accidentally empty share the same post multiple times
it would be nice if there was a way to prevent this accident, without preventing people from intentionally sharing the same post multiple times
speculation:
cohost seems to use a PUT verb for posting and in the request there is not a CSRF token like one might expect from a site that uses a POST. including such a token that's generated when the post page is loaded would allow for the server to detect when the same page is submitting a PUT more than once, preventing double posting perhaps simply returning the postId of the first successful post
7 people like this idea
1 Comment
pinball
said
over 1 year ago
as an additional note, i've noticed i've accidentally double quick-shared posts and so the system to help avoid this would also need to keep that mechanism in mind
pinball
twitter has a system by which posts in a short time frame will not result in duplicate posting, i have noticed cohost does not seem to have this and some people may accidentally empty share the same post multiple times
it would be nice if there was a way to prevent this accident, without preventing people from intentionally sharing the same post multiple times
speculation:
cohost seems to use a PUT verb for posting and in the request there is not a CSRF token like one might expect from a site that uses a POST. including such a token that's generated when the post page is loaded would allow for the server to detect when the same page is submitting a PUT more than once, preventing double posting perhaps simply returning the postId of the first successful post
7 people like this idea