Would prefer something that could be federated and distributed so the cost of hosting is distributed and doesn't allow for a single entity to set ridiculous prices once they get popular, like Etsy did.

And AI will stifle creativity in all areas that it's used in. That's the problem with predictive models being called "AI". They are only as "intelligent" as the information they were trained on and will always be biased towards what that data set was biased on and won't be able to create anything truly new, only improve existing things.

Unstable, in technical terms, is not unreliable or buggy. Unstable means it often changes in a noticeable or significantly way. Instability is not necessarily a bad thing, it just means you have to be more aware and adapt to changes.

An average, nontechnical user will not like significant changes in an OS. They can barely handle changes in applications they use on a regular basis, much less the thing that controls their whole experience on the computer. Many users even prefer working around bugs to having to learn a new process.

This is what instability is about. Instability has a correlation to unreliability/bugged experiences, but is not necessarily a direct relationship. Higher instability is just more likely to result in problems.

That's what backups are for. No matter what solution I use, I would need backups. I used to use LastPass, but that just relied on LastPass to do the backups. I backup the database, but you can also periodically export the data and back that up somewhere securely on your own if you want it in a different format.

But i have no desire to compile and maintain a fork of software just to set a URL and auth token. And again, this is a license to modify the firmware, so they could at some point decide to revoke the license to modify the firmware or stop publishing security updates on their git repo to allow for merging into the fork I have to maintain. Probably won't if they are reputable and don't get acquired, but still a risk. It's just not worth it for me for any open product I purchase.

No, with home assistant they have a cloud server that has additional functionality that you can use or not. Home Assistant doesn't restrict access to the software on device it's running on.

With this, the device itself will not allow you to access its API endpoints without having a key that you need to purchase. And though they say it's a one time purchase, who's to stop them from releasing a critical security patch that invalidates the keys, even accidentally, or includes making the keys a monthly subscription going forward. Or what happens if that key gets exposed and you need them to generate a new one? Do you need to pay for that or is the device permanently compromised unless you build your own custom firmware?

You're allowed to modify the firmware to use a self hosted server for that functionality without violating the license, which is better than nothing, but then it's up to you to maintain your fork of the firmware. Why not just only require the key if you're connecting to their server and allow you to select your own server without needing to modify and maintain a fork of the firmware?

Agree email needs to be replaced, but what a crappy article. Especially love how they don't understand that things like the fact that CC used to be a standard letter writing concept and so, yes, people knew what it meant. Making me feel old. Yes people used to have to learn how to formally write letters on paper, and they had lots of things that could note additional information like ps, cc, att, and so on.

I'd love to see your implementation specs, code, pr any other technical details you'd like to share. I'm setting up home assistant and one of the things I want it to do is replace the functions of my thermostat and add some additional details.

I used to have a Nest Thermostat, but my furnace needed to be replaced a couple of months back and I got a Mitsubishi heat pump, but their thermostat sucks, and it isnt compatible with Nest because it's all wireless. I installed the WiFi add-on to the furnace so I can use the app, too, but it also sucks pretty bad. Plus I miss the functionality of it turning down the heat when I'm away to save money and turning it back on before I get home.

So I'm planning to implement my own solution and documenting and open sourcing everything. But it's going to be several months before I get to doing it due to other more urgent projects. So, I'm looking at everything available. I definitely will be setting up a small display to replace the thermostat and having motion detectors to turn on the display when you approach it to see the temperature and such and to supplement the home/away detection.

Anyway, I would love to see your implementation to see how you did this piece of it.

Easy solution, put in a sexuality/romance preference option of either straight, gay, bi, or ace/none and then set up those conversions like they used to be with a flag for whether it was enabled for that character gender and base it on this simple option instead of hard coded to straight like it used to be.

I mean making all characters bi/pan and characters not gendered is obviously easier, but it's not that much extra to do this than to do straight restrictions.

Fortunately, much of that can be mitigated by choosing estradiol patches or injections instead of pills so you can use a lower dose and put less strain on your kidneys. And recent findings that anti-androgens really aren't needed for most people means less strain on organs. Estradoil alone will usually trigger the body to produce less testosterone naturally.

But yes, people with existing conditions can be negatively affected. But often are just as negatively affected by their own testosterone in those cases.

Problem is that drug companies don't make the hormones for trans people and have generally refused to do research about using them for that purpose, but are perfectly happy to sell them for that purpose, because profit. So doctors have had to learn much more slowly.