this post was submitted on 01 Aug 2023
34 points (97.2% liked)

Selfhosted

37829 readers
649 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 1 year ago
MODERATORS
 

I was reading this guide on how to run a snowflake proxy, and I'm considering doing it.

https://snowflake.torproject.org/

I'm currently renting a small VPS for my self-hosted services, and I have some spare capacity. So I was wondering, are there any downsides that I might be overlooking?

My self-hosted services are on a URL with my real name. Could there be any privacy or legal implications for me? (I don't live under an authoritarian regime)

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 11 months ago* (last edited 11 months ago)
  • The entry node doesn't know what data is being transmitted (or from where that data is) only who it's being transmitted to.
  • The middle nodes know nothing about the data and just know the previous and next hop.
  • The exit node knows what data is being accessed (if it's not being accessed via Https) but not who is accessing it

So in other words: no, you're not transmitting unencrypted data