this post was submitted on 02 Jul 2023
65 points (93.3% liked)

Selfhosted

40717 readers
382 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
 

I hope this post is not too off topic. I thought that it would be nice to see the address of all the small self-hosted instances of Lemmy (1~5 users).

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago

https://outpost.zeuslink.net

I started a habit a while back ago of naming any servers I run based off of names from Greek mythology - my primary server is Zeus but most forms of just "Zeus" in domain form are already taken. Similarly, I call the quasi-internal network that this server runs (since it's a hypervisor) "ZeusNet"...

Problem with that name is "ZeusNet.net" is redundant and would irk me, I wanted something that still ends with the .net TLD (though my personal domain ends with .network).

This, zeuslink.net is what I came up with given that "link" can mean "network" and the combination isn't as redundant as "...net.net"!

Funnily enough, originally my instance was originally under the colony subdomain which I quite liked... But unfortunately I didn't set things up properly due to how I have everything else setup, and I had already dipped just enough in the federation that when I reset everything so that it actually worked properly, the keys that my server identified with no longer matched which broke my ability to federate properly. Which then forced me to reset everything again under a completely different subdomain (I'm glad it was on a subdomain instead of the root domain for that reason) since Lemmy doesn't have a "self destruct" option like Mastodon has (which tells all connected instances "Hey, I'm going down - forget you knew me" as far as I understand it).

And that is the origin story of my domain, along with the subdomain. Thinking about it now, I should copy all of this as a standalone post on my instance 😅