> © 2024 CoLaptop. All rights reserved.
Website copyright is out of date by two years... And the website has been online since then. https://crt.sh/?q=colaptop.pages.dev
> Thank you for your interest. Please submit the form below and we'll get back to > you within 2 working days. > - Team @ CoLaptop.com
Also colaptop.com is not even registered anymore. If I had to guess the pages.dev site stayed up but the domain and email are nowhere.
This is basically the same price as the cheapest options on Hetzner: https://snipboard.io/C9epWo.jpg. Sure my old laptop does have more RAM and a bigger SSD, but I bet it's also less reliable than Hetzner's servers, and is likely to suddenly die some day. So is the tradeoff really worth it? It's hard for me to believe that this is a genuine improvement for most things. The only definite winning case I can think of is if I have a process I want to run, but I don't care if it just suddenly stops working. But when would that ever be the case? and to save a couple dollars per month?
Edit: Maybe this is what github is doing :P
Its a page hosted on CLoudFlare's "pages.dev" service. Their method of contact is a Google Form which does have an email address on this domain "CoLaptop [dot] com", but that as a web address does not work.
I'm not sure they have their act together.
Laptops aren't designed to be servers - peg your laptop CPU and GPU at 100% and see how long it lasts, I've done this before and the answer is about "2 months", yep sure, this effort isn't targeting that workload, but how many bad apples does it take to start a fire? In their page they say "kubernetes server - no problem" kubernetes DOES keep the CPUs busy, not pegged, but busy enough so that they wont step down their frequency.
I admire the effort to reuse old tech, but boy oh boy would I not want to be a sysadmin here!
No fires, no hardware problems. No special cooling other than the mini-split that was in the closet to cool the server rack. They just kept trucking. But modern hardware is much more high strung and I don't doubt you'd have weird failures.
Edit: Back then VMs were how things were done and RAM was seemingly always the bottleneck by a mile, so the cluster did add up to a meaningful amount of extra performance compared to not having it.