• 0 Posts
  • 73 Comments
Joined 2 years ago
cake
Cake day: December 29th, 2023

help-circle






  • the thing that everyone always glosses over is that jellyfin should not be run on a public network. it has known security vulnerabilities… that includes VPN remote proxy, so now you have to have external users on your actual VPN, and if that’s the case then plex will work fine because it’s “local”, and has a lot more features

    (and my main issue: media segments don’t work on swiftfin)



  • yeah viable is such a variable concept

    i guess like… i have a friend that is a lab tech, and he vibe coded a stand alone HTML and JS page for their team to take CSV and filter it… the excel process they used before was horrendous… in that case, i guess that’s a viable product: it works, isn’t buggy (or at least bugs will become well known and able to be manually avoided or worked around)… i’d say that’s an MVP but wouldn’t be so if you wanted to productise it


  • vibe coding is trash for MVPs… it’ll get you there, but as always the achilles heel of vibe coding is maintenance and bugs

    vibe coding is great for a POC, but the defining difference between a POC and an MVP is that a POC is made to be thrown out, doesn’t have to work all the time (you can say “ah yup just need to give it a kick” when you’re showing it off and manually intervene)

    vibe coding is good to show a basic, unmaintainable, non-production version of a feature of function, but then you need to take that and manually build it into your MVP - perhaps by copying some minor parts of the POC, but verifying every step


  • perhaps for that particular group… though i had a friend whose old af macbook air had stopped updating literally years ago, and he still used it because it still worked… but then apps slowly stopped working

    i installed linux on it, and he was actually really keen to give linux itself a go, and it worked great for him!

    i gave him an old macbook a little while after that, and he’s back on macos now, but he said he’d switch back in a heartbeat if there were problems (slowness, update compatibility, etc)

    i guess the thing being he’s not really technical enough to care about the OS other than outcomes, but also was actually interested in linux itself to learn for the sake of it… he’s a lab tech, and vibe codes data manipulation tools, so not a lot of IT-related skills, but always interested in learning










  • many “unused” IP addresses are unused because they’re kinda like having spare parts: if you’re planning on extending your network in the futures, your IP block kinda should reflect your end state (ie the parts you need over time to replace or “build” new hosts)

    or for blue/green deployments where it’s likely that at least half the IP range will be used in terms of process, but unused most of the time in terms of reachability

    and then there’s weird things with splitting up IP blocks into subnets with a division of 3 (the minimum needed for dealing with net splits etc) - eg across availability zones… there are always “waste” IPs because you can’t divide multiples of 8 cleaning into 3