Slackware 1.2, because it came on a CD in the back of a fat paperback manual I got at Barnes and Noble. It was only later that I learned what a distro is.
Currently on Fedora with a Frankenstein desktop of my own concoction.
synestine
joined 2 years ago
This is how my partner and I do our notifications. We've got "him", "her", and "us", depending on who needs the notification. Whenever either of us gets a new device, I add it to either of our groups and then works.
Skipping forward/back between scenes mostly. It's either that or the time skip, which works, but is more work and less accurate.
It's more because they provide an ONVIF interface or an RTSP stream that makes them self-hosting darlings. Them being Chinese white-labels and cheap is mainly a side-bonus.
What are your recommendations if not them?
Wait, you object to their feely-distributable firmware updates? Seriously? Without those, your CPU is vulnerable to exploits and known hacks.
Really? Which ones?
You mean besides Fedora?
From what I've seen from running it the last year or so, yes, most Z2M releases add/change a large number of things. I use the Docker container, and I backup my mapped data directory between releases, but I have had no release related issues. Sometimes new items or features appear in Homeassistant, but it has always worked for me.
I agree that it is awesome to use Kodi as a Jellyfin front end. I use some CoreElec ARM boxes that directly support all the codecs I use. My problem is that the Jellyfin plugin only updates content at startup, so I have to restart Kodi before it picks up changes made since the last restart. I've asked around and either no one else is having the issue or they didn't chime in.
As far as I can tell, it has always used the dotNet 6 framework.
Odd, I only have to reboot mine for updates. Other than that it seems fine running on a Linux VM with 2GB RAM, after the initial setup.
And it uses the dotNet runtime 6 so I'm unclear on what roadmap you refer to.
True, but SQLite is not recommended in production settings, and is quite often the source of Nextcloud slowdowns, in my experience. A dedicated DB is the first thing I recommend for a production Nextcloud instance.
Oh and to be clear, in this instance, "production" means "people depend on this", be that your family group, team/department, fraternal order, church group, etc. as opposed to "I'm just playing with this thing."