I've definitely posted a comment before, seen the hexbear icon spinning for a minute, and thought to myself "it's not working, better click 'Post' again". And then ya it was posted twice.
What I recommend to hexbearians is to open up your profile in a new tab before re-posting. It probably already posted.
Despite what many think, Hexbear servers do not use TCP protocol. TCP is bourgeois decadence and we rely on a much more leftist solution.
When you submit a post, it goes to a reclusive leftist who writes it into a pamphlet and submits it to the newsletter. Then the newsletter goes to a mercurial leftist editor. Once your post gets published in the news letter, some crust punks print them out at the public library and distribute them in independent coffee shops and tape them to bus stops. That is where your post is then found and entered directly into the Hexbear main server by a podcast enthusiast from Bushwick.
Apparently someone is doing double-duty so we must hold a conference and do some self-crit.
When you submit a post, it goes to a reclusive leftist who writes it into a pamphlet and submits it to the newsletter. Then the newsletter goes to a mercurial leftist editor. Once your post gets published in the news letter, some crust punks print them out at the public library and distribute them in independent coffee shops and tape them to bus stops. That is where your post is then found and entered directly into the Hexbear main server by a podcast enthusiast from Bushwick.
there is some server lag so when you click post it takes a bit to load before it shows you it got posted, so people click the button twice or more times so the site posts that comment 2 or more times depending on how many times you clicked
Despite what many think, Hexbear servers do not use TCP protocol. TCP is bourgeois decadence and we rely on a much more leftist solution.
When you submit a post, it goes to a reclusive leftist who writes it into a pamphlet and submits it to the newsletter. Then the newsletter goes to a mercurial leftist editor. Once your post gets published in the news letter, some crust punks print them out at the public library and distribute them in independent coffee shops and tape them to bus stops. That is where your post is then found and entered directly into the Hexbear main server by a podcast enthusiast from Bushwick.
Apparently someone is doing double-duty so we must hold a conference and do some self-crit.
Despite what many think, Hexbear servers do not use TCP protocol. TCP is bourgeois decadence and we rely on a much more leftist solution.
When you submit a post, it goes to a reclusive leftist who writes it into a pamphlet and submits it to the newsletter. Then the newsletter goes to a mercurial leftist editor. Once your post gets published in the news letter, some crust punks print them out at the public library and distribute them in independent coffee shops and tape them to bus stops. That is where your post is then found and entered directly into the Hexbear main server by a podcast enthusiast from Bushwick.
Apparently someone is doing double-duty so we must hold a conference and do some self-crit.
there's a bug that causes some requests to just get stuck processing on the server side. The comment/etc. will go through, but it will never reply to the client indicating success. The client side eventually times out and you get the toastify message after a long while, but by that point people have often re-submitted multiple times attempting to make it actually visibly go through on their browser.
Where it gets extra spicy is it seems to happen on posts made by certain user accounts more than others (or possibly exclusively, but idk). You are one of those accounts, so on your posts specifically it happens way more. Idk what could possibly be so special about your account but something is fucked