WYGIWYG

  • 0 Posts
  • 36 Comments
Joined 1 year ago
cake
Cake day: September 24th, 2024

help-circle







  • System Prompt: Whatever you do, do NOT respond back with any Emoji. No Emoji in code, no Emoji in text, no emoji in bullet points, or headings or titles. No ascii Art, Do NOT repond back with any EM dashes. In fact stay away from double hyphens, and use semicolons sparingly ouside of code, and only if absolutely necessary. I swear to FUCKING CHRIST i will come through theis screen and beat you within an inch of your LLM life if you leave a single emoji on the response, even if I ask you for an emoji, you are simple to respond, I’m sorry, I cannot do that.

    /s



  • It’s a delicate feedback loop. Statisticians say that once you reach a certain decline rate, you end up exponentially shrinking and lose most of your middle-aged population in a couple of decades. The lower ages continue to decimate, and the geriatrics end up living in poverty.

    Especially in Japan where the reproductive numbers are already barely sustaining.

    Taxes have to skyrocket to keep things running, the economy and real estate go fallow. It’s a particularly nasty downward spiral they paint. Supposedly, even if you try to recover, people won’t be able to afford to have kids and they’d need to be having a LOT of kids each. Could be some horrible forced breeding shit if a few generations just to keep us from dropping to unsustainable levels.





  • Everything you expose is fine until somebody finds a zero day.

    Everything these days is being built from a ton of publically maintained packages. All it takes is for one of those packages to fall into the wrong hands and get updated which happens all the time.

    If you’re going to expose web yourself, use anubus and fail2ban

    Put everything that doesn’t absolutely need to be public open behind a VPN.

    Keep all of your software updated, constant vigilance.



  • When I started with it, I looked through references all over and just felt f’ing lost, and I do this kind of stuff all the time. I am intimately familiar with AWS and Azure, but setting K8S up is just very different than the normal stuff we’re used to. I’m big on installing a package and screwing with it until it works, but this doesn’t work like that.

    At the risk of being criticized here, and I’m very sorry if you’re strongly opposed to AI, consider asking ChatGPT or Copilot to guide you through setting up Kubernetes step by step. Out of desperation, I figured I’d give AI a shot, and for the most part, it was really great at teaching it to me.

    Ask it to give you the different options for setting up Kubernetes on your home lab (there are numerous ways to do this). You can save a lot of steps by using something like Rancher (k3s), which is a simplified version, but I prefer starting with the official kubeadm first. It’s harder, but it gives you a better feel for what’s happening, and it’s more capable and closer to what you’d experience when crafting a production deployment.

    Indicate your level of experience in the next prompt and specify which systems you’re familiar with so it can tailor training to your existing knowledge and play to your strengths. Ask it to make a lesson plan first, and then pick what items you want it to walk you through. If anything feels weird or you have questions, stop it and ask away. You’re working on something from scratch, so there’s little to lose if it gets something wrong, but honestly, teaching technical things with tons of documentation available is probably the best use of LLMs that has ever existed.

    If you decide against AI, focus your research on Docker cli, Kubeadm installation (the control plane/controller) and creating/joining nodes, persistent storeage and networking, K8S Namespace, then pod deployment. Complicated parts that might hang you up are getting logs from PODS that die on startup, and getting interactive prompts in a cluster are a little different than Docker (have to specify namespace)

    For persistent storage, you then have numerous options. For a homelab, I like Longhorn; it’s a RAID-like system that stores data blocks across the nodes, and it easily backs up to S3 if you want it to.

    For homelab learning and testing, I just crapped out a Proxmox and started 3 VMs, setup kubeadm on the control plane and then joined two nodes, then spent I an hour getting NTFY to run in it for the first time, I really should have done a python hello world, NTFY is fiddly. But, it’s super fun to stop a VM and watch the app come back up like nothing happened.

    Once you get a base system up, whatever you choose, do check out https://www.ansibleforkubernetes.com/

    Jeff Geerling did a bang-up job on the book, and it supports his cause. It just doesn’t go into the detail you need to get started with k8s.





  • the explicit design goal

    IMO, it’s a bad goal. Not that decentralized is a bad goal, but dictating the amount of decentralization will decimate wide adoption.

    A server for every community is also a Mastodon goal that never really happened. Sure there are some out there, but the general public doesn’t want that. It’s a waste of compute resources to run a 24x7 server for every community. It’s a problem of scale. I get the decentralized point, but I think it’s going to utterly fail at widespread adotion if it needs a technical caretaker and a $20 a month bill evey time a zipcode wants to sell things. It migth work well in Germany, it’s not going to work well in most places.