Yes. This is home-made out-of-band management, like HP’s iLO, Dell’s iDRAC, or generic IPMI. Not only is it a virtual KVM (keyboard/video/mouse), you can pass the host’s power button through this device so you can remotely power on or reset a hung or powered-off system, or mount and boot from a virtual floppy or ISO to completely reinstall the remote system.

In my country, the ISP rents you a modem and router. I told them I had my own modem and router during setup and my monthly cost is slightly less than their advertised price.

I am fortunate that my ISP gives me a routable address, but it is still only dynamic and may change a couple times a year. I would have to pay for a commercial plan if I want a static IP. Some other local ISPs use carrier grade NAT, but you can still request a publicly routable static IP with a business plan. Maybe you can ask your ISP for that?

Domain naming authorities require identification for the registration of domains. You cannot purchase domains anonymously. You can pay Njalla and they own the domain, and they’ll tell you that you can control it, but you have no rights to it in any kind of dispute.

I’ve been running a script every 60 seconds for 2 months now as a cron job and it still hasn’t been able to create a VM in their US datacenter. I just have a log full of “insufficient host capacity” errors.

Is there any sort of legal precedent that covers a situation where:

• I am a user on a network server.
• Meta connects their server to my server so their users and I can interact.
• Am I now bound by a terms of service on Meta’s server that I have not agreed to and may have never seen or been presented with?

When I joint my instance, am I implicitly agreeing to any terms of service that exist on any instance that my instance decides to federate with?#

Because she’s cereal experience lame.