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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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
I’ve read that if you or your family depend on some kind of firewall provided by a company (and removing or disabling it is not allowed), then that firewall might outright refuse to connect to such a domain, even if the domain was never used. (Basically outright blocking .xyz at the root.) It’s not applicable in most cases but it is definitely a case of overzealous “protection” software. It’s just an unpredictable outcome and a risk. If you don’t plan on hosting email and don’t use a firewall like that, then it would be marginally acceptable.
I would still strongly recommend a .com or .net. The only advantage of using lesser known (or of low reputation) TLD is that more domains will not have been taken. I’d rather just try to be creative or pick something longer with .com.