Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)M
Posts
2
Comments
91
Joined
3 yr. ago

  • I see! So I am assuming you had to configure Nginx specifically to support this? Problem is I love using Nginx Proxy Manager and I am not sure how to change that to use socket activation. Thanks for the info though!

    Man, I often wonder whether I should ditch docker-compose. Problem is there's just so many compose files out there and its super convenient to use those instead of converting them into systemd unit files every time.

  • Yeah, I thought about exposing ports on localhost for all my services just to get around this issue as well, but I lose the network separation, which I find incredibly useful. Thanks for chiming in though!

  • Pasta is the default, so I am already using it. It seems like for bridge networks, rootlesskit is always used alongside pasta and that's the source of the problem.

  • All of this is still irrelevant. If given the same hardware, one OS performs better than another, then one OS is obviously more optimized...

    You're saying a lot of words but it all just boils down to "throw more hardware at the problem".

  • How is this relevant? If an OS performs better on old hardware, it's still an indication that it is more optimized.

  • They're at different layers of the audio stack though so not really replacing.

  • Well....have you filed bugs for your issues?

    Most people have had a very smooth transition over to Pipewire. I have 4 Arch machines and Pipewire has been flawless. I am even using one machine for pro-audio usecases (REAPER, Ardour).

  • Man, I have GOT to try Truenas Scale one of these days. I see it recommended so often, but I was just too used to a standard Linux ecosystem to bother learning something new. I am assuming it gets you closer to the feel of a pre-built NAS during administration tasks compared to Cockpit and a SSH session lmao.

    I think I am just always afraid of being locked into a specific way of doing things by a vendor. I feel like I would get annoyed if something that I could do easily on standard Linux was harder to do on Truenas Scale.

  • I have zero trust in QNAP. QNAP knowingly sold several NASes with a known clock-drift defect in their Intel J1900 CPUs and then refused to provide any support. A bunch of community members had to figure out how to solder a resistor to temporarily revive their bricked NASes in order to retrieve their data. https://forum.qnap.com/viewtopic.php?t=135089

    I had a TS-453 Pro and my friend had a TS-451. Both mine and his exhibited this issue and refused to boot. After this debacle and the extreme apathy from their support, I vowed to never buy a pre-built NAS.

  • Lemmy really needs a concept of a "super-community", some way to group different communities together and have that grouping be subscribeable. Maybe creating a post within a super-community will give the user the ability to automatically cross-post to all the individual communities, although this could be abuseable.

  • You shouldn't trust ANY brand's pre-installed OS when it comes to your personal data to be honest.

  • The preloaded spyware OS

    Nowhere in that video did it say this. I am all for DIY NAS and I have an Arch-based one at home, but saying this while implying that that's what the source video you linked said is a bit disingenuous.

    To be honest, nothing about this UGREEN is any different from any of the other off-the-shelf NAS solutions out there like QNAP, Synology, etc. If you don't trust the UGREEN pre-installed OS, you shouldn't trust any of the other ones either. I am not saying you should, but my point is that this pretty par for the course as far as pre-built NASes go.

    Most companies do not provide support if you install a custom OS. That isn't a sign of vendor lock-in, just a matter of keeping support feasible in the long-term, especially since they're relatively new at this. If you want a custom OS, it is far easier and cheaper to just build your own.

  • I've been using it for years and now I basically can't live without it. I consider OpenWrt compatibility in all of my router purchases. Currently using a Netgear R7800 and a Belkin RT3200, both are going strong.

    It isn't as widely used because it can be finicky to flash sometimes, and that's if it's even compatible in the first place. Even if it works, you may experience a drop in performance unless OpenWrt supports using the routers hardware acceleration features. If there's no support, OpenWrt basically uses the onboard CPU to do routing and they're usually not all that powerful.

  • It's a native app on Windows and Mac?

  • You should do it. Easy to setup using either their official AIO image or the community-driven micro service one. I am using the latter and it's been amazing. It's completely replaced Google Drive, Calendar, and Contacts for me and with the DAVx5 Android App it feels like a drop-in replacement. I am also using the auto upload feature to back up my photos to it.

  • Not true. Cumulative updates also take a while, so do the .NET runtimes. Maybe you have a system with a super fast NVMe drive and a new CPU so you don't realize it, but other OSes can do much more with much less powerful hardware.

  • I use podman with the podman-docker compatibility layer and native docker-compose. Podman + podman-docker is a drop-in replacement for actual docker. You can run all the regular docker commands and it will work. If you run it as rootful, it behaves in exactly the same way. Docker-compose will work right on top of it.

    I prefer this over native Docker because I get the best of both worlds. All the tutorials and guides for Docker work just fine, but at the same time I can explore Podman's rootless containers. Plus I enjoy it's integration with Cockpit.

  • Settings and internet are fine. I dunno what to tell you. Very frequently Windows update shows its head, like I'll randomly want to restart my computer because I installed a piece of software that required it, and then it kicks off a long round updates when I just want to use my computer.

    I still think having to leave it on and let it run in the background is still just addressing the symptoms. An update process should be way faster than that so that such a thing isn't needed.

  • I turn off modern standby. I don't want my computer turning on when I am not around or when I am asleep. For laptops, modern standby is famous for turning it on while its in your laptop bag, causing overheating and battery drainage.

    I think if an update process is annoying enough to require something like Modern Standby in order to be "seamless", it needs to be improved.