. .
O .oOo. .oOo. o o .oOo. o.oOo.
O O O O O O O O O O'
OoOo. Oooo` O O O. .O Oooo` O
O O O O O `O O' O O
0OoO` `OoO' `OoO'o.`O' `OoO' O
reflect's "oh so nice rc5/ogr stats pages" - now with some graphics!
Before anyone asks, it's not a real team, by configuring your client you're NOT joining a team. You're just
getting some nice stats from our server, that's all.
We update 10 minutes past every hour for both OGR and RC5.
==================================================================================================================
In order to substitute your email address with a nick of your choice, email reflect@acggbg.org with the following
information: your email address, your desired nickname, your ISO country code (like uk, de, es, dk, se.. )
==================================================================================================================
Stats are found here:
OGR
RC5
To configure your client, follow these steps:
Start the client with the -config switch (or for AmigaOS, right-click and choose configure.. )
option 2, buffer and update options, then
option 6 for proxy settings, then
option 2 and choose No for automatic server selection, then
option 3 to name your own server - www.acggbg.org, then
option 0 as many times as needed to save and quit.
Restart your client, flush your blocks and check back in 30 minutes.
We would like to acknowlege another Amiga DNETC page out there, Distributed
Amiga who has helped out alot in our efforts.
By using this proxy server, you get the graphs, by joining the Distributed Amiga team, you help the effort. Be
sure to do both, if you love stats!
Updated Sat Jan 6 13:24:15 CET 2007
Update: Now the rc5 stats are up and running.
Update: Now the graphs displays correctly.
Update: E-mail addresses are now mangled. Does NOT affect main dnetc servers, only these pages.
Update: Now we can substitute your email with your desired nickname. See above how to make this possible.
Update: As some of you may have noticed, the nickname substitution rarely, yet sometimes failed. I've traced down
the bug and it should not occur again.
Update: It is starting to take some CPU time to process the logs, so I've decided to reduce the statistics
generation to once an hour.