1. it is xterm, xterm.js to be sepcific
2. uses no-vnc. if you own the repl theres a way to set the vnc server password and access from your own client, but i forget how. probably on the replit docs/blog
Again, let me stress this: xterm.js is providing the console only. Any visual things, including the x64 window, are provided by the VNC connection, which is completely independent of the xterm console.
A few weeks ago, I published Amtrak.js, an NPM package which allowed for easy access of the Amtrak API. If you know anything about the API, it is not a simple process fetching data.
I expected that apps and websites would pop up using my library (and the rehosted API at api.amtrak.cc), but none ever came. As my uni classes cooled down from the start of the year, I decided to take it upon myself to make a train tracking app.
My main intention here was to have it use quite a bit less data than Amtrak's official website while also being less clunky on mobile. Why? Well, trying to track your train on 3G and the page happily munching through 10MB of data as fast as possible is, well, not ideal.
I should probably make a more technical writeup over how all of this works at some point in the future, but feel free to ask questions and I'll do my best to answer!
Some people have theorized it wasn't Amtrak who wanted the bs encryption (also probably why the keys haven't changed in 3 years and they've made no effort to prevent people from grabbing this data) but actually some sort of National Security jargon.
The thing is, you're probably right. Over time they've been restricting items for bots in over 100 servers. Right now its to see the users in the server and also to see the statuses of these users.