Elara

cross-posted from: https://lemmygrad.ml/post/5913910

Over the past few months, I've been working on legally changing my name and gender. Throughout my journey, I've noticed a glaring lack of information about the process. The information that I could find has been incomplete, outdated, or both. Also, most existing resources assume you know how to do things like send mail, but I'd never done any of that, so I had to figure all of that out for myself, with some help from my amazing friends, of course.

So, I decided to document the entire process in detail to help other trans people who want to do the same. So far, I've only covered updating California state documents and some U.S. federal documents, since that's where I live and what I have experience with. I tried to include answers to every question I had, and details about how in-person visits to various government facilities work so that people like myself wouldn't be as anxious. I also wrote guides on the other skills you'll need to complete this process, including sending mail, filling out checks, etc.

However, this process is different everywhere. I only have experience with California, but I'd like this resource to grow into something that can help people everywhere, so here's how you can help:

1. Write about your experiences: If you've completed or are working on a legal name and/or gender change wherever you live (including places outside the U.S.), document the process. Once you're finished, contact me (Elara) at [email protected], and I can work with you to get your resources published. Also, feel free to contact me if you need help documenting your experiences or even navigating the name/gender change process itself, and I'll try to help as best I can. You don't have to be an expert or a perfect writer, just sharing what worked for you is enough.
2. Check existing info: If anything on the website is difficult to understand, incorrect, outdated, or you just feel like a change needs to be made for whatever reason, let me know! I want this resource to stay accurate and helpful to everyone.
3. Share the resource: If you know anyone or any community that could benefit from or contribute to the information in this resource, tell them about it. I'd like this to help as many people as possible.
4. Provide feedback: If there's anything you think could be improved, let me know. I'd love to hear your ideas.

Here's the link to the full resource: https://trans.queer.my.id
And to the California guide specifically: https://trans.queer.my.id/books/california

Feel free to message me here or email me at [email protected] if you're interested about contributing to this or just want to talk about it!

Hello, and welcome everyone to this week's weekly discussion thread, a time-honored tradition of our group!

Since Comrade Pup Ivy is currently on a fun vacation with the tea club, and definitely not locked in a basement until he denounces Dr. Pepper, this week's thread is brought to you by your favorite ~~matrix server overlord~~ friendly server admin :3

I hope you enjoy!

• Matrix homeserver and space
  ◦ Theory discussion group on Matrix
• Find theory on ProleWiki, marxists.org, Anna's Archive, libgen

Welcome again to everybody! It's your favorite ~~matrix server overlord~~ friendly matrix server admin :3
Make yourself at home. In the time-honoured tradition of our sect, here is the weekly discussion thread.

● Matrix homeserver and space
  ● Theory discussion group on Matrix
● Find theory on ProleWiki, marxists.org, Anna's Archive and libgen.
  ● Audio versions by Socialism For All (just keep in mind that he's an ultraleftist)

Welcome again everybody, from your favorite ~~matrix server overlord~~ friendly matrix server admin! Make yourself at home. In the time-honoured tradition of our group, here is our weekly discussion thread.

● Matrix homeserver and space
● Theory discussion group on Matrix
● Find theory on ProleWiki, marxists.org, Anna's Archive and libgen

I built this thing over several years using money I got as a gift on birthdays and holidays. It runs most of what I do online, and it's also what's hosting this image.

I run lots of services on it, such as Nextcloud, OnlyOffice, SearXNG, Gitea, Woodpecker CI, MinIO (S3), Home Assistant, Lightweight Music Server, LURE Web, etc. It only uses about 50W of power on average due to the efficiency of the SBCs. It's all managed by Nomad, Consul, and Traefik.

As for security, the SBCs are on a segregated network where only trusted devices are able to access them and they cannot access any other devices on the network. The trusted network is protected by a 41-character WPA3 password that only I remember, and no ports from the servers are directly exposed to the internet (they go through a TCP reverse proxy on a cheap $3.50/month VPS). TLS is negotiated directly with my servers though, so the VPS never sees any unencrypted traffic.

It's been very useful to me and I love working on it, it's really fun.

I just noticed this community. I have lots of SBCs (17 of them). It's kind of my thing lol. Here's an article I wrote about something I did with Pine64's Star64 RISC-V SBC: https://www.elara.ws/articles/riscv-cluster/

Welcome again, everyone! Make yourself at home. In the time-honoured tradition of our group, here is our weekly discussion thread!

We have a Matrix homeserver, where I am your ~~overlord~~ friendly server admin :), at genzedong.xyz. See this thread for information about our Matrix space.

Short reading list for new MLs here. To find theory, try marxists.org, Anna's Archive, libgen, or Sci-Hub (for scientific articles). If an article is unavailable, try the Wayback Machine.

I can already see his fanboys doing mental gymnastics to justify this one.

Generally, I'm opposed to any telemetry in any project, open source or not. However, there was recently a discussion about adding telemetry to the Go programming language's tools, and Go is my primary language. My initial reaction was outrage, I don't want Google spyware on my system, but reading the proposal for how it was actually going to work changed my opinion.

Here's a link to the proposal: https://research.swtch.com/telemetry. It was designed for Go, but the author believes it can be applied to other open source projects as well.

It was originally going to be opt-out, which I disagree with, but the Go team has listened to feedback and it will be opt-in instead. This is the first telemetry proposal I'm not completely opposed to, and I might even enable it on some of my devices.

While Google has had a very bad track record with spyware, this proposal actually seems reasonable and carefully designed to take privacy into consideration. The system will only collect numbers and stack traces. The numbers are statistics like the amount of times a Go tool has crashed or the amount of times a feature was used. Every week, with a 10% probability, a report will be sent. This amounts to an average of just 5 reports per year. The reports will contain no identifying information, not even a randomly-generated ID, they will be publicly viewable, and the decisions about what to collect will be made in an open, public process. All the code for this will be completely open source. It only applies to the Go tools themselves, not programs compiled with the Go compiler, and all the collection logic is local, with the metrics being stored in files that you can inspect to see what will be sent.

It seems like this proposal would preserve privacy while still providing only the necessary data to allow the Go team to improve their tools. What are your thoughts on this?