
s38b35M5
@s38b35M5@lemmy.world
Fuck u/spez
- Comment on Why can't I access this service over the LAN? 6 days ago:
- Comment on Why can't I access this service over the LAN? 6 days ago:
Its always DNS.
But seriously, I’m not familiar with qui, but there could be a whitelist approach to access by default. Maybe it’s blocking access until you whitelist or configure it to accept all.
Its not likely your local firewall is an issue since you can access other services, but the fact that you don’t know means you should find out. I think Debian uses
ufwby default, but I think Debian ships with it disabled. - Comment on Looking for a solution for training videos/courses (+ big list of LMS software) 3 weeks ago:
After reading your post body, I realize this isn’t what you’re looking for, but at least for honorable mention reasons:
- Comment on Vaultwarden while allowing family emergency access 1 month ago:
+1 for simple. Something you don’t need to host.
- Comment on The Death of Traditional VPNs: How DPI Firewalls Use Machine Learning to Fingerprint Your Traffic 2 months ago:
And DPI relies on endpoints using their CA and MiTM certificate. It’s not like it can happen without your knowledge (at least on personal devices). After implementing DPI on multiple different firewall devices on home and enterprise networks, it’s a fairly deliberate setup process on the endpoint. Not a, “they can listen in whenever they want,” scenario.
But fuck this bot 🤖
- Comment on Is there room for Windows selfhosters? 2 months ago:
That’s not Linux, though; that’s docker.
- Comment on Is there room for Windows selfhosters? 2 months ago:
Maybe now. .NET wasn’t always open, used to be Windows-only, was buggy, version-dependent (but not as bad as the jre could be; true), and had (still has) poor resource-management. I think you’re talking about .NETCore.
That said, I wasn’t commenting on the code viability (I’m not a professional developer) so much as the support overhead required (back when I worked support) for the different versions of .NET, especially when MS stopped including v3.5 in Windows except by using “features and programs” or downloading and installing it manually.
- Comment on Is there room for Windows selfhosters? 2 months ago:
Many of us started running Windows Server and endpoints with Cisco PIX firewall (am I showing my age here?) but in my case, the cost and substandard tools turned me away. I was running A DLNA server and using WDS (yes, very overkill for home, but fun to learn for work), but then I found TrueNAS (then called FreeNAS) running on BSD. I now run a simple share from there and Kodi on my (Linux and Android) user endpoints. I don’t bother with imaging anymore, and use
ddfor backups to my NAS. My Firewall runs OPNSense (BSD) and I run OpenWRT on two TrendNet WAPs.I’ll never go back to MS. It’s just not a welcoming platform from my perspective. Don’t even get me started on .NET or the various and sundry “redistributables” constantly required by every tool you try to use.
- Comment on Is there room for Windows selfhosters? 2 months ago:
my distaste for MS grew
This is a natural progression. Inescapable.
- Comment on Plex now will SELL your personal data 1 year ago:
I completely agree. I thought Plex would be fast in the collective rearview mirror as soon as they started forcing connections to their servers, pay-walling, etc. I also had issues with the database corrupting and causing huge slowdowns. I spent days trying and failing to preserve my ratings, watch data, etc.
In the end, I switched to a much simpler setup of an NFS/CIFS share accessed by Kodi on my Nvidia Shield TV. If Kodi chokes (happened once since 2017), I can just wipe the app and/or reinstall and then import the local metadata (XML or NFO IIRC). That takes about five minutes. It just works. Kodi also gives me access to the IAGL, so that’s a huge plus.