I agree with the general point about supporting each other - A lot of trans people only got through those early years because someone else shared information or offered help, and I donāt think that responsibility disappears just because you pass.
That said, Iād be really careful about normalising DIY surgery. Sharing information about accessing healthcare where itās unavailable is one thing, but procedures like orchiectomy, FFS or VFS arenāt something people should be trying to DIY. The risks are enormous, and Iād rather see us fighting for accessible, affordable, high-quality care while also supporting people who are forced into difficult situations.
You donāt necessarily need QubesOS to get better isolation. You can package unsupported applications as Flatpaks yourself and run them with minimal permissions. The downside is the maintenance burden, and Flatpak sandboxing isnāt as strong as Qubesā VM-based isolation. Itās a useful middle ground, but it doesnāt completely solve supply-chain risk. Qubes can be good, but it's all about your friction budget.
Phishing actually is a core branch of hackingāspecifically under Social Engineering. It's not really like walking through an unlocked door; it's more like a con artist dressing up as a locksmith and convincing the homeowner to hand over the keys.
Hacking applies to the entire attack surface, which includes the human element, further more there are whole phishing campaigns that are heavily automated and often deliver stealer malware, making them a full cyber attack.
This wasnāt a technical compromise of Signal itself, but phishing/social engineering is still a form of hacking.
Yeah, a lot of us migrated over. It feels a bit weird at first but you'll get the hang of it pretty quickly. Just have a look at the communities you can join that interest you!
Iām pretty sure ā -rā flag actually stands for ā --resizefsā . When you include it, ā lvextendā automatically runs the appropriate resize command (ā resize2fsā ) for you in the background immediately after the volume is expanded.
Please fix the wording of this post, I got confused, I thought you were talking about the age demographic you are targeting. I think you mean the amount of games you have.
If you point Traefikās forwardAuth at the internal service (e.g. http://:3000/api/auth/traefik), TinyAuth doesnāt see the correct X-Forwarded-* headers or original host, so it wonāt return the auth headers properly.
if you switch to using the public URL instead, the headers should start working ā but only once using the full endpoint:
I run a modest Lemmy instance (lemmy.blehiscool.com). Itās not on the scale of lemmy.world or anything, but itās been around long enough that Iāve had to deal with some real growth and scaling issues. Iāll try to focus on what actually matters in practice rather than theory.
Infrastructure
Iām running everything via Docker Compose on a single VPS (22GB RAM, 8 vCPU). That includes Postgres, Pictrs, and the Lemmy services.
This setup is great right up until it suddenly isnāt.
The main scaling issue I hit was federation backlog. At one point, the queue started piling up badly, and the fix was increasing federation worker threads (Iām currently at 128).
If you run into this, check your lemmy_federate logsāif you see:
āWaiting for X workersā
thatās your early warning sign.
What Actually Takes Time
Once your infrastructure is stable, the technical side becomes pretty low-effort.
The real time sink is moderation and community management. Easily 90% of the work.
On the technical side, my setup is pretty straightforward:
Auto updates: Watchtower (with major versions pinned)
Monitoring: Uptime Kuma
Backups: Weekly pg_dump + VPS-level backups
Backups are boring right up until they arenāt. Test your restores. Seriously.
Where the Gaps Are
The main gaps Iāve run into:
Pictrs storage growth
Images from federated content add up fast. Keep an eye on disk usage.
Postgres tuning
As tables grow, default configs start to fall behind.
Federation queue visibility
Thereās no great built-in āat a glanceā viewāyou end up relying on logs.
My Actual Workflow
Nothing fancy, just consistent habits:
Daily (quick check):
Check Uptime Kuma
Skim logs for obvious errors
Weekly:
Check disk usage (especially Pictrs)
Monthly:
Update containers (after reading changelogs)
Verify backups can actually be restored
As needed:
Moderation decisions
What Iād Do Differently
If I were starting over:
Set up proper log aggregation much earlier (still a weak spot for me)
TL;DR
Infra is the easy part once stable
Moderation is the real workload
Backups matter more than you think (and need testing)
Logs are your best friendābut painful without centralization
Happy to answer specifics if youāre planning a setupāthereās a lot of small gotchas that only show up once youāve been running things for a while.
I agree with the general point about supporting each other - A lot of trans people only got through those early years because someone else shared information or offered help, and I donāt think that responsibility disappears just because you pass.
That said, Iād be really careful about normalising DIY surgery. Sharing information about accessing healthcare where itās unavailable is one thing, but procedures like orchiectomy, FFS or VFS arenāt something people should be trying to DIY. The risks are enormous, and Iād rather see us fighting for accessible, affordable, high-quality care while also supporting people who are forced into difficult situations.
Hey! Don't be mean, they're so close to forming a thought!
You donāt necessarily need QubesOS to get better isolation. You can package unsupported applications as Flatpaks yourself and run them with minimal permissions. The downside is the maintenance burden, and Flatpak sandboxing isnāt as strong as Qubesā VM-based isolation. Itās a useful middle ground, but it doesnāt completely solve supply-chain risk. Qubes can be good, but it's all about your friction budget.
Humans optimise for convenience eventually.
I wish I could sleep like that cat, that dream must be really something, whatever is going on up there!
Happy Pride!!!!!!!!! š³ļøāš
That is the fluffiest Del Monte loaf I have ever seen.
Phishing actually is a core branch of hackingāspecifically under Social Engineering. It's not really like walking through an unlocked door; it's more like a con artist dressing up as a locksmith and convincing the homeowner to hand over the keys.
Hacking applies to the entire attack surface, which includes the human element, further more there are whole phishing campaigns that are heavily automated and often deliver stealer malware, making them a full cyber attack.
This wasnāt a technical compromise of Signal itself, but phishing/social engineering is still a form of hacking.
Yeah, a lot of us migrated over. It feels a bit weird at first but you'll get the hang of it pretty quickly. Just have a look at the communities you can join that interest you!
Welcome!š
Iām pretty sure ā -rā flag actually stands for ā --resizefsā . When you include it, ā lvextendā automatically runs the appropriate resize command (ā resize2fsā ) for you in the background immediately after the volume is expanded.
Which makes it a convenient, single-step process.
He's like:
"HOW DARE YOU INTERRUPT MY SLUMBER!"
Do a backup image of the partition first before you run these commands.
If you decide to use all free space: sudo lvextend -r -l +100%FREE /dev/ubuntu-vg/ubuntu-lv
Should suffice I'm pretty sure.
Reddit moment: criticizing Reddit under a Reddit ad.
Please fix the wording of this post, I got confused, I thought you were talking about the age demographic you are targeting. I think you mean the amount of games you have.
I think the setup script that applies the config changes is documented here: https://codeberg.org/celenity/Phoenix/src/branch/dev/docs/install.md
Great idea ā I was worried my computer wasnāt reporting enough about me.
Yeah, autocorrect got me on my phone ā fixed now š
Do not go gentle into that good night.
If you point Traefikās forwardAuth at the internal service (e.g. http://:3000/api/auth/traefik), TinyAuth doesnāt see the correct X-Forwarded-* headers or original host, so it wonāt return the auth headers properly.
if you switch to using the public URL instead, the headers should start working ā but only once using the full endpoint:
https://tinyauth.domain.tld/api/auth/traefik
Not just the root URL.
That way:
Also worth double-checking that your header names match exactly (e.g. Remote-Groups vs Remote-Group).
So in short: donāt call TinyAuth directly by IP, go through the domain + correct path.
I run a modest Lemmy instance (lemmy.blehiscool.com). Itās not on the scale of lemmy.world or anything, but itās been around long enough that Iāve had to deal with some real growth and scaling issues. Iāll try to focus on what actually matters in practice rather than theory.
Infrastructure
Iām running everything via Docker Compose on a single VPS (22GB RAM, 8 vCPU). That includes Postgres, Pictrs, and the Lemmy services.
This setup is great right up until it suddenly isnāt.
The main scaling issue I hit was federation backlog. At one point, the queue started piling up badly, and the fix was increasing federation worker threads (Iām currently at 128).
If you run into this, check your
lemmy_federatelogsāif you see:thatās your early warning sign.
What Actually Takes Time
Once your infrastructure is stable, the technical side becomes pretty low-effort.
The real time sink is moderation and community management. Easily 90% of the work.
On the technical side, my setup is pretty straightforward:
pg_dump+ VPS-level backupsBackups are boring right up until they arenāt. Test your restores. Seriously.
Where the Gaps Are
The main gaps Iāve run into:
Pictrs storage growth Images from federated content add up fast. Keep an eye on disk usage.
Postgres tuning As tables grow, default configs start to fall behind.
Federation queue visibility Thereās no great built-in āat a glanceā viewāyou end up relying on logs.
My Actual Workflow
Nothing fancy, just consistent habits:
Daily (quick check):
Weekly:
Monthly:
As needed:
What Iād Do Differently
If I were starting over:
TL;DR
Happy to answer specifics if youāre planning a setupāthereās a lot of small gotchas that only show up once youāve been running things for a while.
A more neutral way to put it is that libertarianism and anarchism both value individual freedom, but differ on the role of the state.
Libertarians generally want a minimal state (for things like courts, police, national defense), while anarchists want to eliminate the state entirely.
There are also different kinds of anarchistsāsome are anti-capitalist, while others (like anarcho-capitalists) overlap more with libertarian ideas.