• 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2023

help-circle
    1. I’ve learned a number of tools I’d never used before, and refreshed my skills from when I used to be a sysadmin back in college. I can also do things other people don’t loudly recommend, but fit my style (Proxmox + Puppet for VMs), which is nice. If you have the right skills, it’s arbitrarily flexible.

    2. What electricity costs in my area. $0.32/KWh at the wrong time of day. Pricier hardware could have saved me money in the long run. Bigger drives could also mean fewer, and thus less power consumption.

    3. Google, selfhosting communities like this one, and tutorial-oriented YouTubers like NetworkChuck. Get ideas from people, learn enough to make it happen, then tweak it so you understand it. Repeat, and you’ll eventually know a lot.


  • I don’t think anyone intends public funds to be quite that sticky; public education is itself a public good, and having once attended a public school really has nothing to do with developing a product 20 years down the road.

    Also, writing open source code can support a viable business. Not every example has been successful, and some have been sold to hypercapitalist owners who wanted to extract more profit, others have failed to keep up, but Canonical is doing alright with it, Red Hat did for a long time, among others. Plenty of bigger tech companies also employ people to write open source software, despite it not being the company’s main business, React, PyTorch, TensorFlow, and so many other projects. Those engineers definitely aren’t working for free.





  • I mean, the problem isn’t the existence/obviation of jobs, but what we do next when it happens. If the people whose jobs are automated away are left out with no money or employment, that’s a serious problem. If we as a society support them in learning something new that puts their skills to good use, and maybe even reduce the expected working hours of a full-time job to 35 or 32 hours a week, that’s an absolute win in my book.









  • No the number is public. The IPv4 addresses allocated to the US are about 1.524 Billion, and there are ~332 million people in the US. Most of those IPv4 addresses are allocated to servers in datacenters, but individual people having a public IP for their house is really common. Yeah, your devices are behind NAT, but you can get one. To their point, in countries like India, people outnumber IPv4 addresses so much this isn’t possible. Just getting people there online in a way they can interact with the IPv4 Internet is tricky to do well.