That said, it isn't fun for firmware development.
I have daily driven it for 6 months or so. Most things work great but more niche uses like embedded firmware development, digitally signing documents (impossible on bazzite as far as I have found) and anything that requires udev rules or interplay between software.
Otherwise it is great! Much better day to day than opensuse Kalpa.
Crazy enough, I have everything going that I want to on my server!
As far as my server goes, I have everything I need. Maybe setting up something for sharing files over the web if needed. I used nextcloud for that before it killed itself completely and I realized I never really needed it.
Next is working on my smart home because we had to fully strip the house to renovate. KNX first, zwave for things that KNX doesn't have or are crazy expensive, ESPHome for everything that the other two can't accomplish. Minimal 2.4GHz interference and don't have to rely as much as possible on flaky wireless in a brick house.
SLG46826V-DIP SLG47115V-DIP SLG47004V-DIP
These are the breakout boards of their respective chips.
These chips are the 3 "multiple time programmable" chips in their line (if I have the right ones, I put them in my mouser list a while ago). Which means that once you program them, they aren't burned in with those settings and can be reused.
There is also a "debug mode" where you don't program them at all but program all the settings after boot so that the settings are cleared again after the chip is repowered. I have never used it, but that is what the renesas rep told us during our technical call at work.
They are super handy at getting rid of all of the logic needed for amplifiers, CC/CV circuits, etc...
There is also a company called palantir which is pretty much a cyberpunk corporate distopia surveillance company.
Or you use one GreenPak device and OTP it based on the model and have it cheaper and more reliable, any supporting circuits like drivers, FETs, bulk capacitance, etc.. Would have to be designed per-model anyway on MCU based design.
From what I remember, Seagate has a rough year most years when it comes to reliability. Especially the 12TBs. But to be fair, most of the Seagate drives are >1 year older than the WD drives. Though when you compare then to the old HGSTs with a 0.08% average failure rate 😅
Also the 22TB WD drives at 1% after less than 2 years of service. Oof.
Trakt also sells your data off to whoever wants it even though they explicitly say that they don't. https://trakt.tv/privacy
I hadn't had anything on any ad service about harry potter in years. Never searched anything about it or anything. Watched a quarter of one movie via jellyfin on linux completely locally with the trakt plugin. A few hours later I had harry potter advertisements everywhere that I don't have an ad blocker.
It really really depends on what you have for heating.
Floor heating + heat pump? You don't need to mess around with target temp much because the principle behind it is thermal mass buildup and maintaining that. You have to tune thermostatic valves on the room level. Then you can have one central thermostat simply slightly change the target temperature with many hours of delay. That doesn't seem too useful to me to automate.
Do you have radiators? Then you can get zwave or ZigBee valves and tie them together with whatever thermostat that you want in home assistant. Then you can set per room/zone heat depending on whatever sensors you have.
Do you have central forced air heating and air conditioning? Then you have pretty much target temp and on/off control unless you want to put in motorized automatic registers or redesign your entire duct system for per-room duct valves.
Individual heat pumps/airco units with radiator based heating is the most "per room" customizable and probably the most useful to put automations on in Home Assistant.
Ventilation can be useful by monitoring CO2 levels and humidity. Then you can use either the fan units themselves or socket switches to actuate those and put whatever sensors you want wherever it is useful.
I am probably missing some stuff here, but there are only a few HVAC setups that actually benefit from automation, in my opinion. Mainly ventilation, infrared, and non centralized forced air heat pumps. Plus heating and cooling is something you want to work 100% flawlessly even if your router dies, your home assistant falls off a cliff, and your ZigBee/zwave controller dies.
Different philosophy.
Ntfy uses pub-sub like MQTT. It publishes messages and anyone (with access) can subscribe to it. Want to connect 250 clients across 50 people to have the same messages delivered? Easy.
Gotify uses end to end messaging. A user creates an application on their chosen client. Gotify uses a REST api send the notification pulled from the chosen app to the user who made it. Want to do the same as above? You have to set it up 250 times. Gotify was the first to have authentication and some people say it is more robust, but I can't speak on that. Also gotify is easier to set up and makes sense for a single user.
Someone can correct me if I am wrong, but that is the biggest architectural difference.
I saw it just yesterday.
And a week ago.
And a month ago.
And I had it myself 2 months ago, fixed by going to the online element client that just happened to still be "verified" after a while of no use and then I could verify the rest of my clients. I would be SoL if I didn't have one of my original sessions upon making the account years ago still. Interesting system.
That was in the 1 encrypted chat I am a part of.
99% of rooms aren't encrypted so are completely and totally insecure anyway. Which I guess is fine for community discussion spaces.
I like fluffychat but it doesn't have threading. Element is also fine and what I have to use on desktop because neochat fucks up so much, but I can't use it on my phone because it causes an extra 1%/hour drain on my phone battery in the background which is insane. Uninstalled it a year or two ago.
Holy shit, I never found smoothness in the OSM editor. Does that actually effect routing priority?
That might be a game changer for making my local area much better on OSM.
Gotta be slightly careful with those spins though because there is near-zero documentation.