WYGIWYG

  • 1 Post
  • 333 Comments
Joined 1 year ago
cake
Cake day: September 24th, 2024

help-circle
  • Maybe.

    I think the pushback stems from a bunch of different things.

    It’s genuinely bad at some things. asking it to make a clock out of CSS and HTML is mostly awful.

    Historically, it’s been really bad at everything. So if someone hasn’t done a serious dive on it recently, they’re going to have the impression that it’s even worse than it really is.

    A lot of people don’t understand how to use it, a lot of times it’s like working with a monkey’s paw. You’ve got to pre-guess all the things that could go wrong and keep adding detail until it has no choice but to do it right. And even then, you have to come back and do iterations sometimes.

    It’s making a bunch of oligarchs extremely wealthy, for no good reason, on the backs of the working class, while we can barely buy RAM. At the same time, they’re burning through a hell of a lot of natural resources.

    They’re shoving options and features down our throats and making us pay for them even if we don’t want to use them.

    Some people are genuinely scared that corporations will use it to replace skiled labor with unskilled labor, which they are.

    I have seen advanced versions rewrite an entire cross-platform basic interpreter in a couple of tries.

    I lost a rather complicated Python program I wrote to manage projectors for my Halloween display. I had it make a framework. I went through all of my different options and modes one at a time and explained exactly how they needed to work. I recreated a couple of weeks of work in a couple of hours and added a significant number of features.

    It’s crap like make that admin page look good on a cell phone that’s absolutely bananas. That’s a feature I would never have the time to sit down and work on because it’s not that big of a deal. But it would literally be a day of trial and error on multiple test devices for me to write it myself.

    Would it be better received if it were marketed differently? Probably a little bit. But not beyond the things that I wrote about. It would be a subtle improvement in visibility I feel.









  • rumba@lemmy.ziptoSelfhosted@lemmy.worldQuitting Spotify for Navidrome
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    18 days ago

    Can’t crossfade, developers won’t add the features the server doesn’t support it. I get a random crashes at least once a session. Search sucks because I don’t feel like wiring up elastic. Doesn’t stream large lists, browse to P? With 5000 artists and 20K tracks? Forever.

    The beta is a little smoother but doesn’t address any of my issues with it.

    Symphonium is 100 times better, never crashes, solves lists/streaming by downloading the lists and handling them locally.








  • 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.