NationStates Jolt Archive

Hello! I have been finding that, after I make decisions on issues, a result I did *not* pick is being implemented in my country.

The first one (a week or so ago) was a vote on political parties and how much money they could receive from private donors. I'm sure I chose to set limits on the amount and yet my country now has a "corrupt" :( government that allows unlimited sponsorship of political parties.

So, I thought maybe my finger slipped and I mis-voted.

However, today school uniforms are compulsory in my country when I clearly voted yesterday for students to be allowed to dress in their own clothes.

What can I do?

Thank you.

Laurel of The Semi-Frozen Wilds

This happens sometimes, and we are still trying to figure out why.

This happens sometimes, and we are still trying to figure out why.

Do you have a web accelerator program with prefetching such as Google Web Accelerator or Fasterfox? These programs download all links on the page, so if you click one, another may load, by accident. If you do, disable nationstates.net

This solved the problem when I had it. But there may be other causes.

Hope that helped, Salusa.

Do you have a web accelerator program with prefetching such as Google Web Accelerator or Fasterfox? These programs download all links on the page, so if you click one, another may load, by accident. If you do, disable nationstates.net

This solved the problem when I had it. But there may be other causes.

Hope that helped, Salusa.


I should have thought of that. It's the best solution that I've heard yet and I'm pretty sure that I know how to fix it.

I should have thought of that. It's the best solution that I've heard yet and I'm pretty sure that I know how to fix it.
Change submission from GET to POST?

Change submission from GET to POST?
Yes, actions that change state on the server should not use GET. This is precisely why (well, ok, RFC 2616 is why, but user agents assume you're following it). I don't know if that's what Salusa had in mind, but it's what he should have in mind.

Aaw, thanks all. I'll look into the "accelerator" angle and see if that helps. Thanks again.

Yes, actions that change state on the server should not use GET. This is precisely why (well, ok, RFC 2616 is why, but user agents assume you're following it). I don't know if that's what Salusa had in mind, but it's what he should have in mind.

Unfortunately, we break this rule all of the time, and most agents expect people to, so won't precache even URLs with GET parameters. However, if you notice, most of this site uses implicit parameters, so the accelerators don't even recognize that they are CGI scripts. This partially has to do with when this site was made. POST requests require either a form or javascript, and we've been trying to avoid both. However, this means that even our modifying links don't look like a CGI request.

We're looking into this. (Pyth, if you have wise ideas, let me know, I have some ok ones.)

Honestly, I won't really be content unless we use a POST. You know I'm a REST supporter. I don't see the difficulty with using radio buttons. People had to fill out a form to create an account or login, anyway. It's not like we have to worry about browser support. The other solutions I can think of involve JavaScript or removing all the other links on the page that announces your decision.

It seems like the web accelerator should cause other problems, as well, like joining every region you look at.

admin fight?:p

Nope. There's not much sense in fighting at this point. I may have the cream pies, but Salusa has the server access.

*grins*

seems I was right betting on Sal and not the newbie admin:D

Nope. There's not much sense in fighting at this point. I may have the cream pies, but Salusa has the server access.

Very true. :-)

That being said, Pythagosaurus is absolutely right when it comes to standards, and in the future we'll try to be more careful. Retrofitting can be more difficult though.

Aww I don't think I'll like radio buttons at issues.. :rolleyes: