Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
This is an "x-y question" - what are you actually trying to achieve?
Clearly you are concerned about... someone.... knowing your home IP address - who, and why?
The aim of private frontends are to limit the data being sent to their actual counterparts (eg Redlib for redddit or piped for y.t). This includes mapping usage patterns to respective IP addresses. If I am the sole user of a self hosted service, then cloud providers and big corps could easily do that.
True, but.. First, they get way less data because most JavaScript was cleared out and that cuts tracking by 95% (just to put some figure). Secondly, the idea with those frontend is to have some control (e.g. recommendation algorithm is cleared, or you get to access content without an account, etc.) so, overall there are advantages. Of course, it's a compromise situation.