I've made a few easy to spin up services. Heck, you can even run it off your phone.
Nanogram https://gitlab.com/here_forawhile/nanogram
Spreadsheet Server https://gitlab.com/here_forawhile/spreadsheet
Library Server https://gitlab.com/here_forawhile/libraryserver
Torum (HN Clone) https://gitlab.com/here_forawhile/torum
A source repo link often gets more traction here than a link to what might turn out to be a closed, probably subscription based, service. The repo's main readme likely links direct to the product/ service/other main location [if the forge isn't being used as that] or demo location [if a public demo instance exists] should that be where I want to go immediately.
Though maybe posting both the repo link and a "live" link would be better still.
If you want to make the point that self-hosting is trivial, then show a site that you are hosting with your setup instead of just pointing to gitlab.
https://nonogra.ph/running-a-website-inside-a-website-07-15-...
I don't feel the need or want to share my services with the world to demonstrate that.
I simply do not want to announce my address here, it's ancillary to the discussion...you shed a layer of security by deciding to make your address public, non of which would benefit the whole point of any of the services I linked.
Circling back to the main discussion of indie web, tor is a great alternative if your circle of visitors is of reasonable size and you want a place outside of the commercialized internet. It's available to anyone.
Paying the penny will certainly give you robustness and reliability...but honestly that's part of the fun of indie web.
>you shed a layer of security by deciding to make your address public, non of which would benefit the whole point
It's possible to host something with no intention of making it internet-public. I also have services like that, that I only use myself or with friends. GP argument is that they don't want to share the onion link to their website, because (bluntly) we are not invited. Onion domains are actually relatively private (i mean unguessable - unlike clearnet domains), so it's possible to host private websites without any additional authorization.
Having said that, onion links carry a implicit baggage, so while I think they're great for sharing things with (technical) friends or a private VPN, they're probably not the best way to host services intended for public.
But this is completely opposite of what most people hosting pages online are doing. Ask a thousand people why they are using Github pages, or Vercel, or netlify... how many of them are not looking for a cheap/free way to have something in the public internet?
Apparently [1] there are also ways that Tor Browser supports, for directing visitors to the onion address via the “normal” internet:
- Onion-Location
> The Onion-Location method was introduced on Tor Browser 9.5 as a way for service operators announce their Onion Services in their regular HTTPS sites. It's specified under tor-browser-spec's Proposal 100 - "Onion redirects using Onion-Location HTTP header".
- Alt-Svc
> Similar to Onion-Location, the Alt-Svc method also uses an HTTP Header (the Alt-Svc Header, specified by RFC 7838), which means that the user first need to access the regular site before their browser discovers the alternate Onion Service address.
> But contrary to Onion-Location, the Alt-Svc method:
> - Does not support an HTML tag, as it relies entirely in the Alt-Svc Header.
> - Is fully transparent: all the discovery and upgrade happens automatically, without user intervention.
- Additionally, they also speak of future possibilities for DNS or DNSSEC-based Onion Association.
[1]: https://onionservices.torproject.org/research/proposals/usab...
Of all the compromises we have to do (relying on Telco providers, equipment manufacurers, etc), using Nearlyfreespeech is the less risky one. They have no history of abusing the trust users have placed on them, and service costs virtually nothing.
Imagine you are in a conversation with a stranger. You want to show him your personal website. Consider the following two sentences. Which has the highest probability of actually helping him getting on your website?
"Go to myfirstnamelastname.com. Yeah, it's spelled with a K."
"Go to $FIFTYSIXRANDOMCHRACTERS.onion. Oh you need to use the onion browser. Let me help you install it on your phone. Can't find the service? Oh my bad it's actually $FIFTYSIXRANDOMCHARACTERS.onion. There you go."
This is a common pattern for ex-national carriers in many countries btw - they believe they should be paid by both sides for all traffic that traverses their network, not just by one side, because they feel like they are God of the Internet in that country.
Not 100% independent then. You still depend on your isp.