| 1 |
I had some fun writing a scraper consuming output of replay index... but due to the way data is displayed ("5 months ago"), it is only possible to get 1 month resolution that way.
|
1 |
I had some fun writing a scraper consuming output of replay index... but due to the way data is displayed ("5 months ago"), it is only possible to get 1 month resolution that way.
|
| 2 |
\n
|
2 |
\n
|
| 3 |
I
think
the
only
way
to
get
around
that
is
to
iterate
over
all
battle
details
and
get
the
date/time
from
the
replay
download
link.
It
is
not
a
problem,
as
I
really
would
like
to
see
accurate
stats.
But
it
is
beyond
stupidly
inefficient.
.
.
and
will
generate
about
235'000
requests
(
+
3-5%
due
to
rampant
win32/sql
errors.
.
.
for
a
total
of
about
6.
5TB)
,
so
if
someone
with
db
access
want
to
provide
data
before
I
take
that
route,
you
are
welcome.
|
3 |
I
think
the
only
way
to
get
around
that
is
to
iterate
over
all
battle
details
and
get
the
date/time
from
the
replay
download
link.
It
is
not
a
problem,
as
I
really
would
like
to
see
accurate
stats.
But
it
is
beyond
stupidly
inefficient.
.
.
and
will
generate
about
235'000
requests
(
+
3-5%
due
to
rampant
win32/sql
errors)
for
a
total
of
about
6.
5GB,
so
if
someone
with
db
access
want
to
provide
data
before
I
take
that
route,
you
are
welcome.
|
| 4 |
\n
|
4 |
\n
|
| 5 |
Any other efficiency improvement would be welcome, such as displaying date of game in the index partial view or optionally returning data in json format. But no action is strictly required.
|
5 |
Any other efficiency improvement would be welcome, such as displaying date of game in the index partial view or optionally returning data in json format. But no action is strictly required.
|
| 6 |
\n
|
6 |
\n
|
Fun facts about zero-k.info/stats