[nelsonenzo]

you could self host a website.

Or more realistically, if you are in web dev and wanted to show your work on your local machine - say when the CEO wants to 'check in and see how its going', you can just send them a link on slack and they can play with what your developing on.

[n42]

why do I need a tailnet to self host?

can't the CEO just use the Tailscale network to access it privately?

I just don't personally see a use case -- if I need someone to access the content, the box it is on is already easy to publicly access. if it's not, the only people who need to see it are on the Tailscale network

edit: I think I'm starting to see it. it's not for long term installations. I just feel like, why not just open the box to the internet at that point.

it makes more sense for the edge case(s) that might address friction with adoption. interim solutions, or temporary connections

edit2: I can also see how this might be useful for people living under an oppressive government

[bradwood]

> can't the CEO just use the Tailscale network to access it privately

How many CEOs you know gonna install a VPN client on their workstation to see your stuff?

[anderspitman]

IMO it will be much more useful when they add custom domains so you can host things like public websites.

[csande17]

Do they want you to host a public website? AFAICT all the inbound traffic to Funnel has to go through servers they operate, and historically Tailscale has tried to minimize the traffic they handle that way.

[anderspitman]

They explicitly mention selfhosting services like Mastodon in the article, so have high hopes that they will support use cases like this moving forward.

[n42]

the more I sit with it the more I can see different ways it might be valuable. even if it's just to simplify setup. the use cases just didn't really jump out to me this time, even as a happy Tailscale user