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

help-circle

  • PiHole, Jellyseerr, Radarr, Sonarr, Emby, Syncthing, Homepage, Home Assistant, and Snipe-IT.

    PiHole is self explanatory.

    Jellyseerr, Radarr, Sonarr, Syncthing and Emby are used for media management and streaming, alongside a remote seedbox.

    Homepage is a locally hosted browser landing page with widgets for network monitoring.

    Home Assistant for locally hosted home automation controls.

    Snipe-IT for asset management. Way overkill for a home user, but it’s free to self-host. Make sure all my assets are listed, can upload receipts, photos warranty info, manufacturer info, etc. so it’s a single place to find all of that information if I ever need it.




  • This is what I did after running consumer Linksys and ASUS routers, including with OpenWRT.

    I moved to a Unifi setup and haven’t had any issues. I can manage it remotely if I need to, like another household member needs something changed or fixed. I’ve never had to restart it to fix an issue, it just works.

    Easy upgrades without having to replace the entire setup and move settings over manually. Especially easy wireless upgrades, almost just plug and play replacing the old access point antenna.

    And if you need just a small setup and you run a home server you can run the management software on there instead of something like their dedicated Cloud Key device.



  • This is exactly the kind of issue that the average person might deal with, or it will be a deal breaker and they’ll never try again. Even if you can customize something via a config file, the average user will never do that. If there is no easy GUI in a normal location (like system settings) for something they want to adjust, it might as well not exist.

    Average users either will accept all the inconveniences, or none. If it is more inconvenient than what they are used to right off the bat, they will go back and never try again.


  • Until something breaks, or doesn’t have a GUI. The average user seeing a terminal means they will abandon it. And even if they are willing to handle a terminal to fix an issue, the toxic community members that flock to be the first to respond condescendingly to new users will turn them away permanently.

    Linux communities have some of the most helpful users, but they also have people worse than a League of Legends game. And all it takes is one of them to turn the average person away forever.


  • Exactly, and let’s give them the benefit of the doubt since we don’t know. The librarian or assistant helping OP probably just doesn’t know much about the IT stuff other than how to help people get on the wifi. And it is entirely possible that they’re NEVER seen anyone even try the port before, that’s not common at all. Actually managing the IT infrastructure at that level is almost surely NOT part of their job.

    WiFi has been included in essentially everything for over a decade. I mean even ignoring laptops having Wifi way before mobile devices, even going back to the origin of smartphones for the masses, the original iPhone had Wifi back in 2007, that’s 17 years ago.





  • I think the difference is the intent of who will use the program.

    Is the intended user the developer themselves and that’s about it but they’re making it available for others? Then just having the code is fine. It should still be properly documented however. Devs forgot their own shit code all the time, the documentation is there for them as well when they forget or come back to a project years later.

    However if the program is intended for use by people outside the developers, then a regularly updated compiled binary should be expected. They are likely already going to be compiling it for themselves, making that process produce an updated binary release in GitHub isn’t too much to ask for something intended for others to use that the dev is already likely making anyway.