In your project issue tracker add a price tag to each feature or bug-fix issue submitted by users. Let users pay what amount they would like to their desired issues. If an issue gets enough fund, do it. If not enough fund is raised for an issue in a fixed time window, return all those monies back to users and start over. Simple, huh?

Redmine

Because 3x storage and bandwidth usage is more expensive than 1x. The difference is specially more noticeable in large scale for the hosters than for clients.

FYI: Google Code has been banned to Iranians for years.

Nice suggestions, but I wouldn't count that as "web development".

No need to do heavy stuff in JavaScript. Just put the whole page under a visibile cover and remove the cover using JavaScript on page load event. >:)

Just use i386. You can even run i386 userland over an amd64 kernel. I can't see the big benefit of x32 over this scheme.

Because X11 can be run over Wayland, ssh -X should continue working. So I'm not so worried about that.

Because not enough money was donated to Quanta developers to show that "people are waiting...".

I guess he was talking about Israel.

Put security first please. All major browsers have got a bad track of security issues.

On Mozilla platform, JavaScript is not "one small part". Major parts of the browser and add-ons logic are implemented in JS. So the faster the JS engine, the faster the whole browser.

You're simply in a very wrong oversimplification. Iranian society is more complex than that. (I'm an Iranian who arguably knows Iranian society better than 99% of other slashdotters.)

You meant popularity-contest.

Google bans download of Google Chrome in Iran (and probably a few other countries.) It redirects me to http://dl.google.com/service/prod_unavailable.html