Response from Resure:
@Roget - EN Responses to that tech questions, please forward them if you can:
These iframes are coming from scpnet.org. Who is running this webserver, and what kind of hardware does it have?
scpnet.org is domain name dedicated to various SCP Foundation related services (we're using it for our tags search, random pages, etc). Currently it's pointed to my dev server hosted in Moscow, but when interwiki "beta" will be over, I'll migrate it to Linode server in Frankfurt (https://www.linode.com/) (4GB RAM, 2 VCPU, 40Gbps Network) so both EU and US users will have fast network connection with low latency to that servers.
We served up a few million requests last april, if I'm not mistaken. Is this going to give a 404 eventually, if the hardware gets overrun?
Few million requests per month is not so much, app that renders interwiki block uses resources pretty efficiently. We can also stress-test server by adding block to the scp-wiki sidebar for a few minutes and then checking server vitals. Currently it serves requests for almost all big branches except SCP-EN and it uses something like 5% of server's resources.
Also, I want to know exactly how it works and what it does on pages that have no translations, how often it is updated, etc.
It fetches lists of pages via WikidotAPI every hour, implementation itself is opensource (http://github.com/resure/scpnet). On pages with no translations it will be empty (example: http://scpfoundation.ru/scp-1003-ru)
And btw
In fact, this is why I haven't proposed implementing my "True Random SCP/Tale button" that I developed a few months ago. Helen's webserver might asplode from simple volume.
We have similar thing (https://scpnet.org/wikidot_random_page), currently it's only for SCP-RU pages, but we can provide such service to any SCP wiki branch including SCP-EN (and to the projects like Wanderers Library too).