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
First of all I would suggest getting your own domain. There's many TLDs and ccTLDs that will let you get a domain for $10/year or much less.
If you don't want to pay then at least get a subdomain from somewhere reliable. Preferably a DNS service because you also get DNS management this way. My recommendation is DeSEC because it's a German, privacy-oriented non-profit and it has a modern interface and modern features like an API, security tokens, support for recent record types, DNSSEC etc. And if you later decide to get a paid domain you can keep using DeSEC for it very easily.
Secondly, does your fediverse single-user server really need to be exposed to the internet to get updates? Can't it pull them from other servers? That way you would reduce your risk a lot.
Isn't this what I just did?
mydomain.eu.ccEven if I can't get it to renew for free next year, the experience of setting stuff up should be worth it.From my limited understanding of APub, it needs to be exposed/findable in order to send updates and for my
user@serverto show up. I'll be reading https://www.w3.org/TR/activitypub/#server-to-server-interactions to know betterTunnel through an existing server? Or what, exactly? Wouldn't connecting through an existing fedi server also enforce its blocklist down to me?
I mean the second part from the end (
.eu.). That's not yours, and that means that themydomain.part can dissapear at any time. The owner can also do all kinds of unpleasant things that can affect your online presence.By "your own" domain I mean getting something of your own in that 2nd spot instead of "eu". It doesn't have to be on the
.ccregistry, it can be any established TLD like.com,.net,.org, it can be a country TLD aka ccTLD like.cc,.nl,.deand so on, or it can be a so-called "novelty" domain like.dev.Having your own domain means you can own it in perpetuity (well... old, established TLDs are better at this than novely TLDs) and have much better control over it.
Visit a domain registrar like Porkbun and have a look through their TLDs, check some prices, the privacy of your personal data etc.
Avoid registries that allow "premium" domains, it means that the registry can suddenly decide that the domain you own is very cool and force you to pay hundreds or thousands for the next renewal or lose it.
I'm not entirely sure on how you propose to use your server: if you just want to read stuff or also want to be able to post.
Your server can do things with another server in two ways, by exposing an open port and allowing the other server to do stuff locally through that port, or by connecting to a port opened on the other server and doing stuff there.
If the fediverse protocol mandates having a local port open to do stuff like posting, it may be impossible to avoid doing it.