Can I (or we) help hosting it ?

[ghost]

As I see on https://nyancat.dakko.us/ :

Due to bandwidth limitations, the Nyancat telnet server has been shut down.

Can we (Everyone with a server and spare space) help by hosting it ? You have the domain name, maybe a small script for mirroring around a public instances list could be nice :)

It would be a shame that this piece of internet history (mine for the least) dies like that.

[klange]

Hm... I'm trying to think whether it's feasible to provide some sort of proxy for the website while allowing a CNAME to forward telnet to other providers. If the new hosts don't run anything else, they may be able to forward all of their HTTPS traffic to the main site... The other option is handing out TLS certificates for nyancat.dakko.us to anyone in the CNAME list, but I'm not sure I want to do that.

[a-raccoon]

The official telnet has been shut down for a while now, and ALL of the listed mirrors are also dead. https://nyancat.dakko.us/#mirrors

We need more volunteers to mirror.

If you host a mirror, announced it on twitter @_klange

[memiux]

$ telnet 🌈🐱.memiux.com or https://🌈🐱.memiux.com

*Nyancating via Telnet has a limit of 10,000 glorious frames per IP every 30m.

[maswan]

nyancat.acc.umu.se or 🌈🐱.acc.umu.se is available now too, we limit to 1k concurrent users per frontend IP, but could maybe bump that a bit if needed, depending on resource usage (bandwidth is fine up to 5-10Gbit/s, cpu/ram is more constrained and we don't want nyancat to push out the rest of ftp.acc.umu.se services)

[syslino]

I just love this. I think I'll fire up a mirror as well!
@maswan May I ask you how you did yours?

I've got some dope TLDs to spare, server's up and ready! Just would love to hear some hints about how you guys built it.

Not that I'm in need of much load balancing - my machine idles most of the time anyways and this project seems silly enough to suppport!

Just give me some inspiration! 💋

[boppy]

by @syslino:

Not that I'm in need of much load balancing - my machine idles most of the time anyways and this project seems silly enough to suppport!

Ohh wow... We didn't expect this. Yesterday we set up a telnet-:cat: on the playground-server mentioned (I'm the second admin to that server) and, without even publishing any information, those scan-bots are creating full load on our (tiny) 100 MBit/s NIC just 20 seconds after starting the container. We had single connections transferring up to 1.2 GiB in one session (having no limitations in place).

Right now we are testing a non-default port. We limit to 5 cons per IP (by nginx) and 60 seconds of runtime (with -f option) with a maximum of 40 total connections (default with onetd). After 30 minutes of uptime there was not a single connection established.

If it stays that friendly to our resources we'll publish that mirror, but not on :23.

[a-raccoon]

Never, ever, host anything on standard service ports unless you're an enterprise server farm. :)

[boppy]

Never, ever, host anything on standard service ports unless you're an enterprise server farm. :)

But I do prefer to have visits on my home pages and I do totally like to receive E-Mails... So a standard port might not be the best idea for telnet, but generally... I keep with standards. There's an idea behind (most of) them ^^

[maswan]

I just love this. I think I'll fire up a mirror as well!
@maswan May I ask you how you did yours?

I installed the nyancat package from ubuntu 18.04 repo and then stuck an appropriate snippet in xinetd.d and then I was good to go.

There's a few hundred Mbit/s in "background" traffic, but not anything to put a dent into the rest of the services for us. I do wonder if I should set up a dedicated server though, since all these nyancat binaries do take up a fair bit of ram.

[dimaguy]

Hello everyone!
I am also hosting a mirror on a raspberry pi 4 on good ol' port 23
You can access it on dimahq.linkpuff.me
Currently it is limited by 5 connections per ip (10 minutes of delay) and has the lowest nice level possible (for those who dont know nice level is the one that defines priority of a process on linux), it has no guaranteed uptime but if anyone has any idea on how to secure it even more (besides closing the port lol) I could lower the restraints a bit.

EDIT: changed to a proper VPS