this post was submitted on 22 Apr 2025
39 points (93.3% liked)

Selfhosted

46265 readers
178 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
top 4 comments
sorted by: hot top controversial new old
[–] scrubbles@poptalk.scrubbles.tech 4 points 1 day ago* (last edited 1 day ago) (1 children)

Holy yikes batman. That's a lot of trust and open ports right there to the public internet. Not to mention running a tor node is incredibly risky for the hoster personally. Individually these projects are good, in one bundle I'm heckin suspicious.

Edit: it's just a relay node at least, but still, this is targeting inexperienced people to run a bunch of containers, and I don't think the risk is fully explained there.

[–] glowing_hans@sopuli.xyz 2 points 1 day ago

yeah an exit node would be the most dangerous

[–] mesamunefire@lemmy.world 5 points 2 days ago (1 children)

Interesting, I used to help on the bionic side a long time ago.

I thought it was quite heavy on resources? What are they doing on the docker side to help out? Limiting the CPU?

[–] acockworkorange@mander.xyz 1 points 2 days ago

No clue, but they could use nice.