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.
- 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:
> Any issues on the community? Report it using the report flag.
> Questions? DM the mods!
- 1 user online
- 218 users / day
- 9 users / week
- 244 users / month
- 841 users / 6 months
- 0 subscribers
- 542 Posts
- 8.93K Comments
- Modlog
A problem with the
.lan
TLD (maybe others from this list) is that web browsers do not consider it a TLD when you type it in the address bar, and only show you the option to search for that term in your default search engine. You have to explicitly typehttps://
before it, to have the option to visit the URL.E.g type
example.com
in the address bar -> pressing Enter triggers going tohttps://example.com
. Typeexample.lan
-> pressing Enter triggers a search forexample.lan
using your default search engine.Little known trick–or perhaps everyone knows it and is quietly laughing behind my back–with Chromium browsers and Firefox (and maybe Safari, I’m not sure), you can add a slash to the end of an address and it will bypass the search.
So, for example, my router on the LAN goes by the hostname “pfsense”. I can then type pfsense.lan/ into my address bar and it will bring me to the web UI, no HTTP/s needed.
You can throw a
/
after to force it to recognize as a URL too.