Test
Maybe to avoid double-threads if someone clicks it accidentally or something.
Let’s see what the rabbit has to say. :)
Sorry if that sounded stupid.
All your karamas are belong to us.
10 years ago | edited 10 years ago
1
Maybe there is a double meaning. Closing the thread closes this particular discussion. Closing the thread again closes the society as a whole.
Remember in an isolated system, entropy will always increase and this will prove that the system is inherently unsustainable.
Personally I think @flabbyrabbit is simply testing the second law of thermodynamics.
Or maybe I just had too much coffee…
10 years ago
0
Coffee is dangerous ^^
I remember that I had to click 3 times to close my last thread ;)
10 years ago
0
I just closed the post which I created for Street Fighter and it got closed in 1 click.
So is this some bug? Because I too had to close it twice whenever I created a thread earlier and its different number of clicks for other users too. @flabbyrabbit enlighten me (if you have time). :D
- @IAmDevil
Its good to be back! :D
Ok will try on this thread itself.
Edit: Just tested it, still the same. Clicked it once but the thread is still open as you see it.
- @IAmDevil
Its good to be back! :D
10 years ago
1
When you close a thread there is a unique url - does this change in any way between attempts @IAmDevil ?
Indeed @flabbyrabbit it is strange. And yes @sabretooth the URL must change when clicked, I didn’t notice it earlier when I closed any thread but this time when I clicked to close this thread the URL remained the same.
- @IAmDevil
Its good to be back! :D
10 years ago
0
@IAmDevil : Can you try in a different browser and let us know if it is the same or if it works fine on another browser.
This problem is real, not a myth. I experienced it sometimes and there were some users saying: “Weird! I swear I had closed this thread before!”.
- @IAmDevil
Its good to be back! :D
10 years ago | edited 10 years ago
0
IAmDevil : Try it in Internet Explorer Next.
I think it needs two clicks. Because I clicked it once via mobile and second time via my PC so that makes two. Again strange!
And what was that @tlotr ? My username invisible or may be in gray color. I remember that being used in a level (where we had to paint the screen). Lol
- @IAmDevil
Its good to be back! :D
10 years ago
0
It’s in the same color as the background. I cannot make the name grey if I put the @ sign in front. It automatically changes to white color.
10 years ago | edited 10 years ago
0
[quote=IAmDevil]I remember that being used in a level (where we had to paint the screen)[/quote]
I really hate lame challenges like that. They are too common and teach nothing :)
Back to the topic. It certainly does seem to be browser-based issue, but why it happens is a total mystery. Any update on this?
The only thing that springs to mind is that the CRSF token is being overwritten, which should only happen if you open another tab (with a close thread link in) and then click the link in the original tab.
@flabbyrabbit I am pretty sure that was one of the conditions when this happened to me. When I close, usually it’s after replying or editing the last post to say “thread closeed”, and when I’m editing sometimes I have two instances of the same thread (the thread itself and the post edit page); after updating the post I close the thread.
Sorry if that sounded stupid.
All your karamas are belong to us.
Hmm… Yes @flabbyrabbit it seems to explain that somewhat. So as a solution can it be made like when we click close thread it closes the thread and takes us to a new tab? Would that help?
- @IAmDevil
Its good to be back! :D
10 years ago | edited 10 years ago
0
Is CSRF protection even necessary for closing threads? I mean each close thread link has its own unique URL and this can only be seen by the user who started the thread in the first place. Due to this acting as a secret token, I don’t see that anyone could apply a CSRF attack in order to make a user close their thread.
EDIT: The only issue is that the token could be subject to bruteforce depending on the length, so hash the token or ensure a strong entropy and everything will be just dandy :)