Yeah, I think of two sides to labels. One is how you perceive yourself and one is how you communicate who you are to others.

For the internal labels, these are only useful to some people, and can change as often as you want, or you can chose to not use them at all and just be you. You decide. What they are useful for in my experience is self-discovery and helping you to decide how you want to present to others. So use them, or not, try them on for a while and see how it goes, switch them up. Treat them like trying on clothes at home. You can wear which ever ones you want, in whatever combination you want or just go naked. It's your house/brain.

External labels shouldn't be assigned and if they are you should ignore them. Don't let them affect who you are or how you behave or you just end up wearing masks. Now I say that with the caveat that masks are necessary in certain situations for safety or to preserve your job or whatever. But when you're free to be you in public, ignore those assigned by others. Again, using the clothing metaphor, it's like someone putting a hat on your head. It's rude for a stranger to come up to you and do that. Now it may be that hat looks great on you and turns out you wear it the rest of your life. But someone shouldn't put it on you, they should see that you might like it, hand it to you, and you decide to put it on or not. Same with labels. People can suggest a label, but should not try to assign one to you.

Problem with social labels is that it's not acceptable to go naked in many social situations. So you have to pick the ones you want or risk being forced to wear them. And in some situations, you will be forced to wear one without your consent. You just have to decide if it's worth being in that situation or if you should leave. And the other issue is that changing labels confuses people, just like significantly changing your clothing style might if you go from wife-beater and jeans to goth cat girl. So it's best to pick some base ones and then add on or make small adjustments as you go. There are lots of generalized labels like non-binary or gender-fluid that sound like might be a good starting point for you. Then you can add more specific ones later once you have internally tried them on for a bit or tried them on in safe spaces like with good friends who are open to it. Like starting out with a black tshirt and pants, then adding on a skirt or sweater later, you can add on something like demiboy which is a subset of non-binary and eventually get to more specific labels as you find them useful.

And also, something I always emphasize to people is that gender and sexuality are not directly related and sometimes even romantic interests and sexuality are not necessarily directly related. There may be a correlation for the majority, but it's not a direct relationship. So choose your sexuality, romantic, and gender labels separately at least the internal ones. Just realize that because language is weird, the most common romantic and sexuality labels are only meaningful when combined with a gender label (e.g. straight, gay, hetero/homosexual, etc), so it's good to find that first, but not necessary. There are more gender neutral sexuality labels, especially in the ace spectrum, or ones that explicitly specify the target gender rather than specifying the relationship the target gender has to your gender, like gynosexual.

And remember, we all change over time. Be flexible with yourself and don't worry about what you felt like in the distant past, only today. Gender, sexuality, etc., are much more complex psychologically than simply a single chromosome like many bigots pretend. It's mostly up to hormones and the way different parts of your body react to those hormones which can change over time from age, environment, diet, etc., not just your genes. Genes just set a starting point, and sometimes those get overridden before birth even. That's why people with an X chromosome can be born with a vagina and all the other combinations.

Hope that is useful. It's a deep interest of mine because my own journey has been complex. So I enjoy info-dumping about it. Lol

Selfhosted VaultWarden with Bitwarden browser apps and KeyGuard on my phone, which I like better than the Bitwarden app.

Mine has those, but it was a different model that had the hardware required to do WiFi. Likely it's not included and unless the device was designed to modify, it's likely that the motherboard doesn't have a way to add it easily and there won't be much space to do your own WiFi card and soldering if the board does have the connections and support in the firmware/BIOS. Best bet would be a USB WiFi card.

Anyone who isn't a loyalist and doesn't take this is likely in for a bad time. Better to have time to find another job than get fired for insubordination when they start the purge for not being loyal enough as defined in the letter from Trump and lose their ability to transition to other jobs or keep their other tenure related benefits.

That's for use of the website. Not the device.

I said from the beginning it's a deal breaker for me. You're the one trying to convince me it's not the issue I think it is.

And I'm not talking about the license to modify the firmware software itself. I'm talking about the EULA of the device itself. Pretty much any device you own that has any kind of software on it is not owned by you outright to modify as you wish. This website doesn't show the agreement, but if it has a paid feature to unlock, it has to have one somewhere.

But were talking about firmware here. My computer also has firmware and an OS. I never have to touch that. Home Assistant is an application that I run on a computer. And I don't have to modify the code in Home Assistant to get it to connect to another device. I just configure it.

I also install Linux on my laptop. Is that self hosting, too? We're not talking about a server or a "host" other than the hardware device itself that lives in the house. If I want the server functionality, sure that's self hosting the server software. Firmware and operating systems are generally not referred to as self-hosting since all devices need those things. Self-hosting refers generally to cloud-based applications, not standalone hardware firmware/OS.

This is a hardware device that is hard coded to connect only to a specific server that you have to pay to access if you want any API functionality. If I want to use my own I have to learn the programming language, figure out how to modify the Firmware, and then maintain a fork of that firmware indefinitely including making sure that there are no automatic updates since that would overwrite the modifications.

Alternative suggestions? I'm going to check out Fossify messages for now.

OK, I see. They decoded not to have the device respond to requests. It's not that the device has endpoints, it's that it's hard coded to connect to a specific endpoint and you have to build your own firmware in order to get it to connect to your own server.

That's still a deal-breaker for me. It's just that the connection is flipped. I don't want to have to build and maintain firmware to use the device in addition to maintaining the server. Why can't this be a setting on what server it connects to?

I think you're not seeing my point. This is in the hardware. It's simple to have a setting that defaults to connecting to the company's server and then have that setting allow for changing the sever target. Why do I need to build firmware to do that?

And, no, it's not acceptable to require forking, regardless of the ease of merging. It still means you won't get critical security updates without manual intervention.

And finally, it's requiring trust. If the company decides to change the license, you are out of luck. And again, the documentation and policies are already lacking, like what happens if your API key is compromised? Do you need to pay for a new one to be generated. These are on your local device.

And no, home assistant doesn't require self-hosting. It requires hardware to put the central system on, but doesn't require an external server for web services. This device is putting the lock inside the hardware you are purchasing. If I purchase hardware, I want it to be mine. Not subject to a license of what you can put on it, even if that license is initially very open. It's my hardware.

Home assistant does sell hardware that is totally open with no license on what software you can put on it. Most people put it on their own hardware. This is totally separate from the cloud service they offer which is for interacting with the sever over the internet and some other stuff. That cloud functionality is totally optional and you aren't required to modify the home assistant code base in order to NOT use the cloud. So it's not at all equivalent.

Did your keyboard mapping get changed? Try running this to check the current locale:

localectl status

Other settings are generally dependent on the distro you're using.

I think mailcow only supports Pushover for notifications, but it may have changed.