Anything from baby stuff, groceries, shopping, planning, wine tracker app, simple/fun/useful data things, etc…
We have Tailscale on our phones and can instantly and privately see without deployment or anything crazy via our secure VPN.
Think shared Claude Artifacts that don’t live @ Anthropic.
Tried to first do this with Cloudflare Tunnels (because I love Cloudflare), but between the broken dashboard side of Zero Trust and nightmare of Warp… it was basically impossible to setup. I guess that’s all super enterprise, which seems to be very anti-Cloudflare philosophically to not be able to self do things.
Will check out Quick Tunnels but I think it’s missing the bigger integration offerings Tailscale has/does still.
You can also use Tailscale serve to get a HTTPS url like Cloudflared but it's only visible to your tailnet. Be careful using Cloudflare tunnels because they are public and bots start poking around immediately.
> Anything from baby stuff, groceries, shopping, planning, wine tracker app, simple/fun/useful data things, etc…
Can you elaborate on this? Sounds really cool!
Getting it to do what I wanted with a traefik front router with cloudflared talking to arbitrary subdomain that is spun up and broadcast from the other project side was very painful in a "this could be more friendly" way.
It has been truly bulletproof though since then so that's almost enough to make me go reread all the docs.
edit: yeah, it says no account creation, neat!
So cloudflare sees your plaintext. Btw: tailscale does not (but ssl errors and warnings are unavoidable)
They can monitor extreme outliers. It’s not an issue for them.
I bet these new tunnels end up being a fraction of a percentage point of their network traffic.
I've migrated many companies off of cloudflare, usually because they end up pissing off companies when a contract renewal comes up and they slam them with massively increased bills and almost useless support if you aren't very high paying enterprise. I don't know how many CF support tickets I've just given up on over the last 15 years, usually related to their admin page, workers or some weird thing their system does that wasn't documented and I just stop getting responses and definitely don't get fixes.
If you ever worked in webhosting the Cloudflare wordpress/etc extensions are everywhere and back when I did work in hosting tons of support tickets were made because of CF. Could be way better now, I don't go near that industry these days.
The casual CF user sticking it in front of a blog they rarely look at and the business forced CF user has a very different experience. I cringe and seriously consider if I'm interviewing for an infra role and they use cloudflare. Usually it's startups that grew into larger businesses.
I'm not trusting any of these corporates any more
We live in an age of monkey-see-monkey-do management.
When Microsoft axed its QA team, it gave permission for everyone else to make the same stupid mistake.
https://github.com/anderspitman/awesome-tunneling
I have played around with frp, bore and ngrok.
While testing it locally Codex by itself suggests using CF Tunnels but what's more interesting it actually used the Quick Tunnels.
Coming from days where I get warnings of vibe-coded generated code using deprecated code or older APIs, I must say using something so fresh is quite impressive.
> Free, secure tunnel for everything you are building.
> Preview and ship ideas globally in seconds with Quick Tunnels. Deploy your local application to the Internet with a single command.
Clicking through Explore Cloudflare Tunnel leads us to:
> Looking to expose public applications? This documentation covers Cloudflare Tunnel use cases for private networking and Zero Trust, like VPN replacement and private network access. For publishing public web applications, APIs, and services to the Internet through Cloudflare refer to ...
The vps runs a custom image that is 2.54 Megabytes. It has a custom kernel with almost everything but networking and wireguard disabled, a fixed-size fs with pre-allocated blocks and inodes to hold the vps wireguard key, and a single pid 1 binary that calls the kernel directly to set up the routing rules, generate a new wireguard key on first boot and save it to the fs, print out the wireguard public key to the console, and loops reap. Updating involves building and uploading a new image, assigning the vps to use it, reboot, wait for the public key in the console then set it on the nas so they can talk.
Thought it was very cool
[1]: https://developers.cloudflare.com/cloudflare-one/networks/co...
ssh -p 443 -R0:localhost:9051 free.pinggy.io
(Free for 1h each session)
> Free tunnels are meant to be used for testing and development, not for deploying a production website.
[0: https://developers.cloudflare.com/cloudflare-one/networks/co...
It does the exact same thing, except supported by a global network of volunteers around the world.
Sure, you get some latency, but this is actually ideal for testing. You should know how your service operates in non optimal lightning fast conditions.
The obvious difference (and thus massive advantage) of the cloudfare product is that it is accessible over the normal internet without needing to install a tor client.
I'm sure that works for some subset of the population where all potential users are already comfortable using Tor; but imagine trying to share your PoC website with the designer/client and you are asking them to install Tor browser.
Is different than sharing your work with a client.
I personally wouldnt make it SOP to utilize a complely free service like this to share my work. I'm not saying it's not convient, it definitely is.
But you shouldn't subject a clients product to terms they probably aren't aware of.
I used to use a service called ngrok for this, but it's nice that Cloudflare is offering one now.
My initial thought was desktops generally run 24/7, with laptops running when in use. At least for the customer at the market intersection for this type of product.
This type of quality downgrade is scary, and it's everywhere now.
I think that rule is more of a "we reserve the right to..." rule, but it makes me sad because I'd rather not open up ports on my router to expose my Jellyfin to my parents.
- find my approximate physical location
- regularly scan ports on my IP and wait for me to accidentally expose a service I didn't mean to
- track me in any access logs they have access to