Hi Maarten,
Maarten Dammers <maarten(a)mdammers.nl> writes:
because
loading is stupid right now, it stores all monuments into a
javascript variable (see the HTML source).
Ok. How does this scale to the 1,3M
items we have in the database
right now?
Very badly :)
I'm sure the WLM international team has some money
to get another
(bigger) VPS if needed.
I'm glad accepting donations for the project, but let's not lose time
with this right now
I will advertize the real cost of this when I sync my database with
those 1.3M entries.
I expect I will have to spend $65-$125 for the redis datastore and
$35 and $35-$70 for the server itself. So $100 to $200. I'm fine
spending $200 for september -- and ask for donations if the cost
is more than that -- thanks to thousands of visitors :)
It should be compatible with
http://translatewiki.net/
. In short: Use
message variables and store all the i18n messages in a separate file.
That way we can it's easy to get a lot of translations in a short time.
Sure.
I'll
publish the code on thursday at best, I don't have enough spare
time before this, the biggest priority is to get the asynchronous
stuff working.
Isn't it already in git? Just the share the link :-)
Nope -- not that I don't want, but I implemented a rough backend with
an admin/password access, and of course the password is readable in my
code, will fix this before thursday (I'm out of town from monday to
wednesday, and spending time with family today!)
I just don't want to loose time over it and keep
things focused on
getting a map for WLM. The map subdomain is just easy to setup.
I definitely don't want to bike shed of the domain name.
Sure. My goal is to build something useful for wlm-ers first,
of course, since that's the best way to see if the service can
survive past the WLM competition.
Keep up the good work!
Thanks!
--
Bastien