# tailscale Published articles for tailscale. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Running a Self-Hosted Tailscale Control Server Behind a Reverse Proxy DevFeed: [Running a Self-Hosted Tailscale Control Server Behind a Reverse Proxy]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-15T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [tailscale](), [proxy](), [traefik](), [TLS (Transport Layer Security)](), [TLS handshake](), [Self-hosted](), [Homelab]() Tags: [dns](), [docker](), [h2](), [homelab](), [networking](), [proxy](), [reverse-proxy](), [security](), [self-hosted](), [tailscale](), [tls](), [tls-handshake](), [traefik]() ### AI overview This tutorial explains how to run a self-hosted Tailscale control server, Headscale, behind Traefik. It finds that the reverse proxy must use TLS with HTTP/1.1 only because Tailscale's noise handshake expects a full-duplex byte stream and can fail when ALPN negotiates HTTP/2. ### Source excerpt Headscale behind Traefik: tls.options=no-h2@file with alpnProtocols http/1.1, because the Tailscale noise handshake breaks when ALPN negotiates h2. ## Tailscale's Remy Guercio on what comes after token maxing DevFeed: [Tailscale's Remy Guercio on what comes after token maxing]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-05T23:49:35Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Artificial Intelligence](), [AI-assisted coding](), [experiments]() Tags: [agents](), [ai](), [ai-gateway](), [analysis](), [cost](), [experiments](), [model](), [tailscale](), [token]() ### AI overview An interview with Tailscale's Remy Guercio examines the shift from maximizing token usage to maximizing return on investment in AI development. It covers coding-agent adoption, rising bills across multiple AI tools, cost per task, model experimentation, and the visibility an AI gateway can provide. ### Source excerpt Tailscale's Remy Guercio tells Michael Grinich why the next 12 months of AI are ROI maxing: cost per task, model experiments, and what a gateway can see. ## Deploy a Private Hermes Agent on Render Securely with Pulumi, Modal, and Tailscale DevFeed: [Deploy a Private Hermes Agent on Render Securely with Pulumi, Modal, and Tailscale]() Original publisher: [Read original article]() Author: Engin Diri Published: 2026-06-24T00:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [Artificial Intelligence](), [Deployment](), [Self-hosted](), [Open Source](), [hosting](), [cloud-infrastructure](), [Code](), [ui](), [Messaging]() Tags: [agent](), [ai](), [ai-agents](), [building](), [code](), [hosting](), [how-to](), [modal](), [open-source](), [pulumi](), [pulumi-esc](), [python](), [render](), [security](), [self-hosting](), [server](), [services](), [tailscale](), [tutorials](), [typescript](), [ui]() ### AI overview A tutorial for deploying a private Hermes AI agent with Pulumi across Render, Modal, and Tailscale. Render hosts private services, Tailscale provides tailnet access, and Modal runs agent-generated code in temporary sandboxes. ### Source excerpt Personal AI agents had their breakout this year. OpenClaw crossed 100,000 GitHub stars within months of launching, and self-hosting your own assistant went from a hobbyist trick to something a lot of developers actually do. I wrote up how to deploy that lobster to AWS or Hetzner back when it was everywhere. The one people are switching to now is Hermes, the open-source runtime from Nous Research, and it caught on just as quickly. The reason shows up in every "I ditched OpenClaw for Hermes" thread: it actually learns, building up memory and writing its own skills as it goes instead of running off a static, human-written list. Here is the part the launch videos skip. Hermes writes and runs its own code, with no human approving the commands. A model that can write code will eventually write a bad one, and the only thing between that command and your credentials is the sandbox it runs in. That is the box you do not want on the public internet. Researchers found 175,000 exposed Ollama servers sitting open in early 2026, and attackers hijack the ones they find for compute. The fix is not a better lock on the front door. It is to have no front door at all. So this post deploys a private Hermes agent as one Pulumi program across Render, Modal, and Tailscale. The agent and its chat UI run as Render private services with no public URL, Tailscale puts the UI on your tailnet, and Modal runs the agent's code in throwaway sandboxes. One pulumi up to stand it up, one pulumi destroy to tear it down, around $50 a month. No Makefile, no CLI escape hatches, and an honest look at the few places "nothing on the public internet" still leaks. What is Hermes? Hermes is the open-source, MIT-licensed agent runtime from Nous Research. It runs continuously on a server rather than living in a browser tab, and you talk to it through a chat UI or a messaging platform like Telegram, Discord, Slack, or Signal. A few things make it more than a chatbot: It is model-agnostic. You point it at any provi ## How I Gave the Claude App Access to My Self-Hosted Second Brain DevFeed: [How I Gave the Claude App Access to My Self-Hosted Second Brain]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2026-06-13T06:45:00Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [Claude](), [Model Context Protocol](), [Self-hosted](), [OAuth](), [tailscale](), [Qdrant]() Tags: [claude](), [mcp](), [oauth](), [phone-app](), [self-hosted](), [solar](), [tailscale]() ### AI overview The author describes extending a self-hosted memory service to the Claude app through a remote MCP server. The design keeps the data at home while exposing an HTTPS endpoint through Tailscale Funnel and protecting it with OAuth 2.1, including PKCE and refresh tokens; Qdrant is also part of the setup. ### Source excerpt I gave the Claude phone app access to my self-hosted memory -- a remote MCP server over Tailscale Funnel, OAuth and Qdrant, running on a solar-powered PC at home. ## Use Your Mac for AI Agents: Self-Host Gemma 4 12 B with Pulumi and Tailscale DevFeed: [Use Your Mac for AI Agents: Self-Host Gemma 4 12 B with Pulumi and Tailscale]() Original publisher: [Read original article]() Author: Pablo Seibelt Published: 2026-06-04T00:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [gemma4](), [llama.cpp](), [Local AI](), [Infrastructure as code](), [macOS](), [On-device AI](), [multimodal]() Tags: [ai](), [download](), [gemma-4](), [gemma4](), [gpu](), [infrastructure-as-code](), [kubernetes](), [llama-cpp](), [macos](), [multimodal](), [python](), [tailscale](), [tutorials]() ### AI overview A tutorial for self-hosting Gemma 4 12 B on a modern Mac using llama.cpp with Apple Metal acceleration. It combines host-native inference with a local Kubernetes cluster, Pulumi infrastructure as code, and Tailscale for secure access, and reports validation results on a MacBook Pro with an Apple M3 Max and 36 GB RAM. ### Source excerpt If you run AI tools and agents, you've probably accepted three tradeoffs: your data leaves your network, you can't work offline, and your bill scales with usage. Open-weight models now run well on consumer hardware. Once the model is on your machine, your data stays local, inference works offline, and tokens cost nothing. If you own a modern Mac, you can run a high-quality model yourself. Gemma 4 is an open-weights model family from Google. This post focuses on Gemma 4 12 B, released in June 2026, using Unsloth's Q8_0 GGUF. The 12 B model fits comfortably on a modern Mac while leaving enough headroom for local llama.cpp and a chat UI. We'll use llama.cpp for host-native inference, k3d for a local Kubernetes cluster, Pulumi for infrastructure as code, and Tailscale for secure access. Prerequisites This setup was validated on the following hardware: macOS 26 Tahoe, version 26.5 MacBook Pro with Apple M3 Max 36 GB RAM On this machine, llama.cpp reported about 20 output tokens per second for a 160-token validation response with unsloth/gemma-4-12b-it-GGUF, gemma-4-12b-it-Q8_0.gguf, and a 131,072-token context. Sustained throughput varies by prompt length, thermal state, and llama.cpp settings. You'll need brew, docker, pulumi, and tailscale installed. We'll also install k3d during the process. Run Gemma 4 with host-native llama.cpp We use llama.cpp directly on macOS to leverage Apple Metal acceleration. Running the LLM on the host is more efficient than trying to pass GPU access into a local Kubernetes VM. Install the build tools: brew install cmake git Then build llama.cpp from source and download the multimodal projector. In validation, Homebrew llama.cpp 9430 could run text inference, but it could not load the new Gemma 4 12 B projector and failed with unknown projector type: gemma4uv. Building current llama.cpp from source fixed that. llm_home="$HOME/pulumi-gemma4-llm" mkdir -p "$llm_home/models" "$llm_home/logs" if [ ! -d "$llm_home/llama.cpp/.git" ]; then git clon ## Here's my list of reasons for using Opencode DevFeed: [Here's my list of reasons for using Opencode]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-03-17T20:00:00Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [User experience (UX)](), [client](), [servers](), [context]() Tags: [agentic](), [architecture](), [bugs](), [external](), [features](), [mcps](), [models](), [opencode](), [plugins](), [switching](), [tailscale](), [ux]() ### AI overview The author gives five personal reasons for using OpenCode: switching between models, its client-server architecture, subagent and mode features, opinionated user experience, and plugin customization. The article also notes that OpenCode has bugs and missing features, which the author says have not stopped them from using it exclusively for two months. ### Source excerpt Here's my list of reasons for using Opencode. 1. Switch between models on the fly ## I'm often experimenting with the bleeding edge models as they come out. I actively switch between models for tasks and I use them all enough where I can tell the difference. Opencode lets me switch between models mid-task or mid-conversation. Fluidly. 2. client-server architecture (a.k.a built-in remote control) ## I wrote about this and agentic fluidity in more detail but tldr: Opencode has the client/server architecture baked in. So I can just start an opencode server on one machine, expose it through tailscale serve and start using it on my phone or other machines. 3. Subagent + mode features ## I talked about this on my podcast in some detail but Opencode has the best implementation of subagents and modes. You can switch to a subagent definition as your primary mode, then operate other subagents from there. It makes orchestrator-type tasks super easy. 4. Opinionated UX ## I love that OpenCode is opinionated about their UX. They don't try to be Claude Code or Codex. In the process they have some really nice UX patterns like a sidebar with ongoing file changes, context/cost, MCPs connected etc. It's the first time I've not needed to worry about a custom statusline.sh or building one. 5. "Highly" customizable via plugins ## The plugin ecosystem is highly customizable. To the point where you can add new features, integrate with external services or even modify OpenCode's default behavior. The wonderful Jesse Vincent mentioned this to me when I was stupidly contemplating a fork. What's missing # It's not all rainbows and sunshine. Anomaly -- the team behind OpenCode -- is small. Which sometimes shows, because there's definitely bugs and some features missing. But I will say... none that's deterred me from using it for the last two months, exclusively. Go give it a shot. Many of the serious AI coders I know are really liking it and switching. ## OpenCode offers server-client access for on-the-go agentic coding DevFeed: [OpenCode offers server-client access for on-the-go agentic coding]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-02-20T21:04:46Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [agentic-coding](), [Command-line interface](), [servers](), [client](), [browser](), [tailscale](), [Artificial Intelligence](), [Open Source]() Tags: [agentic](), [agentic-coding](), [browser](), [cli](), [local](), [open-source](), [opencode](), [project](), [server](), [tailscale](), [terminal]() ### AI overview The article argues that OpenCode is a useful open-source option for accessing agentic coding sessions from multiple devices. It highlights OpenCode's server-client architecture, CLI and web modes, browser access, and use with Tailscale to connect to a development machine remotely. ### Source excerpt One of the reasons OpenClaw got so popular was how fluidly you can chat with and operate your agents. Pull up your phone, send a quick message on WhatsApp, and you're in business. As we focus more on agent orchestration1 in 2026, I think an important aspect will be access fluidity. How do you hop into your agent's context from any device, terminal, or IDE and just start coding? Claude Code supports this in a limited way, while others like Cursor and Codex take a cloud-based approach. The best option I've found for this "on-the-go" agentic coding is an open-source one -- OpenCode. OpenCode - your best "on-the-go" option for agentic coding. Server-client architecture ## OpenCode uses a native server-client architecture. You can simply spin it up in a regular terminal tab, just like claude or codex. But the power move is running it as a server and connecting multiple clients. A client can be your terminal tab, a mobile device, or a desktop computer. Each terminal tab becomes a new, isolated CLI session that connects to the server. Couple this with Tailscale, and you can securely connect to a dev machine running an OpenCode server from anywhere. Getting started ## I'd start by using opencode like a regular CLI tool. Once it feels familiar, switch to server/web mode. # advertises server as opencode.local opencode web --mdns # attach to a session # equivalent to starting a new claude code session opencode attach http://opencode.local:4096 --dir /path/to/project The beauty is you can open that opencode.local URL in any browser, and it's fully synced. Credit to my co-host Iury for tooting the OpenCode horn early, and my Instacart colleague Spencer for questioning my luddite tmux ways.2 I'll write a future post singing OpenCode's other praises. For now, if you're exploring the bleeding edge of agent access fluidity, don't sleep on it. See my post on AI paradigms. ↩︎ I noticed some memory leaks when using tmux sessions with OpenCode, and Spencer asked me: why not lean on the s ## Opentofu + Tailscale = Bootstrapped DevOps environment with VPN DevFeed: [Opentofu + Tailscale = Bootstrapped DevOps environment with VPN]() Original publisher: [Read original article]() Published: 2026-01-17T21:28:46Z Content type: tutorial Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [opentofu](), [tailscale](), [DevOps](), [Virtual Private Network](), [Deployment](), [Cloud](), [Server](), [Terraform]() Tags: [cloud](), [deployment](), [devops](), [hetzner](), [opentofu](), [tailscale](), [terraform](), [vpn]() ### AI overview The article demonstrates using OpenTofu with Tailscale to bootstrap a private network across development VMs. It presents configuration for deploying three IPv6-only servers and installing Tailscale with cloud-init, while noting that the approach is intended mainly for quick testing rather than permanent production servers. ### Source excerpt For the last few days, I have been playing with OpenTofu. For those who may not know, it's a fork of last Terraform as Terraform's license was changed due to IBM's acquisition of Hashicorp and is a Cloud Native Foundation project. It can be used to quickly deploy (and remove) resources from various cloud players. Yesterday came across this tweet from Tailscale about tailscale's module for deployment. Cloud-init can be tough, and we've heard all about it. So we built an open-source Terraform module, one that helps provide a more consistent Tailscale experience across AWS, Azure, GCP, and everywhere. No more surprises, OS quirks, or other mysteries: https://t.co/vn1ITU7Fgz pic.twitter.com/stcF6WuiD7 -- Tailscale (@Tailscale) January 15, 2026 It's cool and useful, though I find Cloud init way more useful since for me these tools are more useful for quick testing rather than a permanent production server. The idea of tailscale on devops VMs as they come up is pretty powerful, as it takes care of the private network between these machines, plus underlay doesn't matter, and hence one can use (cheaper) IPv6-only VMs. An example of OpenTofu config (which is similar to Terraform) to deploy three IPv6 only servers on players like Hetzner across Nuremberg, Helsinki, and Ashburn: main.tf terraform { required_providers { hcloud = { source = "hetznercloud/hcloud" version = "~> 1.59.0" } } } provider "hcloud" { token = var.hcloud_token } data "hcloud_ssh_key" "desktop" { name = "desktop" } data "hcloud_image" "ubuntu" { name = "debian-13" most_recent = true } resource "hcloud_server" "vms" { for_each = var.vms name = each.key image = data.hcloud_image.ubuntu.id server_type = each.value.server_type location = each.value.location ssh_keys = [data.hcloud_ssh_key.desktop.id] user_data = <<-EOF #cloud-config package_upgrade: true packages: - curl runcmd: - curl -fsSL https://tailscale.com/install.sh | sh - tailscale up --authkey=${var.tailscale_authkey} --accept-routes EOF public_net { ## Android Wi-Fi Sharing for Captive Portals and Device Limits DevFeed: [Android Wi-Fi Sharing for Captive Portals and Device Limits]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2025-12-26T20:30:06Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [Android](), [Wi-Fi](), [networking](), [tailscale]() Tags: [android](), [tailscale](), [wi-fi]() ### AI overview The article explains Android Wi-Fi sharing, which re-shares an existing Wi-Fi connection through the phone's hotspot. It argues that this can reduce captive-portal logins, work around single-device Wi-Fi plans, restore local device discovery, and, in some setups, route connected devices through Tailscale. ### Source excerpt Ubiquiti announced a new travel router. Much of the internet is excited. So am I. Then I tried to remember the last time I actually needed a travel router. You see, Android has supported a feature I'll call Wi-Fi sharing for years.1 Your phone connects to an existing Wi-Fi network and re-shares it as a hotspot. This might sound like a regular hotspot feature that most phones (including the iPhone) come with. But it's not. iPhones can share mobile data. They can't re-share a Wi-Fi connection as a hotspot. Wi-Fi sharing Your phone connects to Wi-Fi, and then re-shares that same Wi-Fi as a hotspot. This is different from typical hotspot functionality where the phone shares its mobile data connection (vs Wi-Fi). Neat trick, but why bother? Can't you just connect each device to Wi-Fi? Avoid signing every device into a captive Wi-Fi portal ## Captive portals are annoying when you're carrying multiple devices. I typically travel with 3-4 devices that want internet. Signing each one in, every time, gets old fast. Some devices are worse: Chromecast and Fire TV sticks are particularly painful to get past captive portals. If everything connects to your hotspot, you only deal with the portal once.2 Work around "one device at a time" Wi-Fi plans ## On a plane, I sometimes want both my laptop and phone online. Some paid Wi-Fi plans only allow one device at a time. Unless you're ok paying twice, Wi-Fi sharing is simpler.3 Hotels and conference centers do the same: sign-in plus device limits. Wi-Fi sharing works around it. Fix "devices can't see each other" networking ## This one is less obvious, but common in hotels and conference Wi-Fi: your devices have internet, but they can't see each other locally. Chromecast (or printers) won't show up as a cast target because it doesn't appear on the network. That's usually client/AP isolation.4 Put your devices on your phone's hotspot, and local discovery usually works again. Secure networking with a Tailscale setup ## This is slightly adv ## My Private Mini Kubernetes Cluster - Secured by Tailscale DevFeed: [My Private Mini Kubernetes Cluster - Secured by Tailscale]() Original publisher: [Read original article]() Author: Techno Tim Published: 2025-11-07T13:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Kubernetes](), [Virtual Private Network](), [5G](), [rancher](), [GitOps](), [Ubuntu](), [networking]() Tags: [5g](), [dark-mode](), [firewall](), [gitops](), [homelab](), [intel](), [kubernetes](), [latency](), [rancher](), [ssd](), [tailscale](), [ubuntu](), [unifi-cloud-gateway](), [vpn]() ### AI overview A tutorial documenting a private, three-node RKE2 Kubernetes cluster built on Beelink Mini PCs and connected securely through Tailscale over a 5G WAN. It covers UniFi networking, Ubuntu installation, PiKVM access, cluster bootstrapping, and Flux-based GitOps management. ### Source excerpt A compact Kubernetes cluster, completely private and connected over 5G - powered by Tailscale. 📺 Watch the video Why Build a Private Kubernetes Cluster? I wanted a way to run a full Kubernetes cluster that I could access securely from anywhere - no open ports, no complicated VPN setup, no public exposure. Tailscale made that possible by creating a secure network for exposing and connect... ## How Tailscale simplifies site-to-site VPN connections DevFeed: [How Tailscale simplifies site-to-site VPN connections]() Original publisher: [Read original article]() Published: 2025-09-23T17:57:09Z Content type: tutorial Language: en Sources: [Learn on Tailscale]() Topics: [Virtual Private Network](), [tailscale](), [networking](), [cloud-infrastructure](), [Security](), [Routing (disambiguation)]() Tags: [aws](), [azure](), [cloud-infrastructure](), [firewall](), [hybrid](), [networking](), [networks](), [tailscale](), [vpn]() ### AI overview This article explains how site-to-site VPNs securely connect separate offices, cloud environments, and on-premises networks. It compares traditional IPSec-based configurations with Tailscale's mesh networking and subnet routing approach. ### Source excerpt Learn how site-to-site VPNs connect offices and cloud networks securely. Compare traditional setups vs modern solutions that eliminate firewall configs and IP conflicts for good. ## Creating private services on NixOS using Tailscale and Caddy DevFeed: [Creating private services on NixOS using Tailscale and Caddy]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2025-09-13T15:48:00Z Content type: tutorial Language: en Sources: [Posts on Harsh Shandilya]() Topics: [tailscale](), [Authentication](), [proxy](), [Grafana](), [Server]() Tags: [authentication](), [caddy](), [integration](), [nixos](), [release](), [tailscale]() ### AI overview A guide to configuring private services on NixOS with Tailscale and Caddy. It explains the experimental Caddy integration, installation of the caddy-tailscale plugin, authentication-key configuration, and a Grafana setup that uses Tailscale identity for access. The article also notes device-limit and duplicate-dashboard-entry caveats. ### Source excerpt A simple guide to setting up private services on NixOS using Tailscale and Caddy with authentication. ## ArubaCX VXLAN Routing Packets Have Invalid Lengths DevFeed: [ArubaCX VXLAN Routing Packets Have Invalid Lengths]() Original publisher: [Read original article]() Published: 2025-06-12T05:08:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [VXLAN](), [networking](), [Linux](), [virtual machines]() Tags: [capture](), [ethernet](), [linux](), [netlab](), [tailscale](), [virtual-machines](), [vxlan]() ### AI overview A netlab IRB test exposed that VXLAN packets generated by ArubaCX's routing process reported IP and UDP lengths four bytes larger than the actual packet. The article uses packet captures to trace the issue to a VLAN tag removed during software VXLAN encapsulation without a corresponding length adjustment. ### Source excerpt This blog post describes yet another bizarre example of how reliable digital twins are, but don't worry; they all work great in PowerPoint. After "fixing" the integration tests to deal with ArubaCX's notion of VXLAN VNI having 16 bits, the bridging test worked, but the IRB tests kept failing. In the IRB test, the lab has two layer-3 switches. Each of them should be able to bridge within a VLAN/VXLAN segment and route across the segments. Read more ... ## Taildrop - transfer files between Android and MacOS DevFeed: [Taildrop - transfer files between Android and MacOS]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2025-05-01T15:03:32Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [tailscale](), [Network](), [Internet]() Tags: [android](), [files](), [iphone](), [macos](), [tailscale](), [windows]() ### AI overview The author reviews Tailscale's Taildrop for transferring files between devices, highlighting cross-platform support and uncompressed image transfers. The article also discusses Taildrive, an alpha shared-folder feature, and notes Taildrop's current limitations, including self-only transfers, no link sharing, and an Android caching bug. ### Source excerpt I use the Pixel 9 Pro as my daily driver and love it. But one notable feature I've always missed from the Apple ecosystem is AirDrop. I typically have WhatsApp for Mac open and dump things there for quick access between devices. Clunky, but it worked. Until I realized Tailscale -- a VPN1 that I love and use -- has a feature called Taildrop. The name suggests it's meant as an AirDrop competitor, and I've been super happy with it. I can now send images uncompressed2 to any of my devices. I'm not restricted by Bluetooth, proximity, or other limitations. Just need Tailscale running on the device. Advantages ## Not limited to the Apple ecosystem ### Probably the highlight here is that Taildrop works on any device that supports Tailscale. So between a Pixel, iPhone, MacBook, Windows machine -- no walls here. Unlimited file size ### There's no filesize limit. In all fairness, AirDrop doesn't have one either. Taildrive ### Another alpha feature they're working on, similar to Taildrop, is Taildrive. It's effectively a shared folder on the internet. If you're on the same network (Tailnet), you can download files from this folder from anywhere. This basically allows any folder on your device to become a mini NAS or file server. Bonkers! Constraints ## It's not all sunshine and rainbows though. There are some constraints and issues with Taildrop. Can only send to yourself ### Even if you add another user to your Tailscale network, you can still only send files to yourself. I imagine this is still an early restriction, but the good news is that Tailscale is thinking about relaxing this over time (maybe). This is clearly an area where AirDrop is superior since it can more conveniently allow you to send files to anyone nearby. Note this doesn't apply to Taildrive, just to Taildrop. With Taildrive, anyone on your Tailnet can access the shared files. Can only send files ### AirDrop handles sharing URLs or links elegantly. Share a URL from your phone to computer, and it automatically op ## OpenVPN vs. Cloudflare: Which is Best for Developer-Friendly Networking? DevFeed: [OpenVPN vs. Cloudflare: Which is Best for Developer-Friendly Networking?]() Original publisher: [Read original article]() Published: 2025-03-24T21:17:43Z Content type: comparison Language: en Sources: [Learn on Tailscale]() Topics: [Virtual Private Network](), [tailscale](), [Cloudflare](), [SASE](), [Security](), [Cloudflare Access](), [remote access]() Tags: [alternatives](), [cloudflare](), [cloudflare-access](), [encryption](), [remote-access](), [sase](), [security](), [tailscale](), [vpn]() ### AI overview This comparison examines OpenVPN, Cloudflare, and Tailscale for developer and engineering-team networking needs, including security, performance, remote access, and management. It describes OpenVPN as a traditional VPN requiring dedicated servers and manual configuration, Cloudflare Access as an identity-based Zero Trust alternative, and Tailscale as a WireGuard-based peer-to-peer approach for accessing internal resources. ### Source excerpt As VPN alternatives go, OpenVPN, Cloudflare and Tailscale each serve different networking priorities for developers, making the right choice dependent on security, performance, and management needs. ## Building The Roottrees are Dead DevFeed: [Building The Roottrees are Dead]() Original publisher: [Read original article]() Published: 2025-01-27T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Game Development](), [Godot](), [Homelab](), [Linux](), [Gitea](), [Docker](), [Git](), [Windows 11](), [tailscale](), [blender](), [Synology]() Tags: [diskstation](), [docker](), [game](), [game-development](), [git](), [gitea](), [homelab](), [linux](), [tailscale](), [windows]() ### AI overview The developer describes the technical considerations behind building the Steam version of The Roottrees Are Dead. The supplied excerpt covers the game's release and reception, a homelab using Linux, ZFS, Gitea, Docker, and Git LFS, backup practices, remote access through Tailscale, and development hardware. It also identifies Godot as the game's engine. ### Source excerpt The Roottrees are Dead was released on January 15, 2025 and it did much better than I ever expected. The reception has been amazing. In just over a week, the game hit the magic mark of 500 reviews on Steam, and triggered the "Overwhelmingly Positive" status. On BlueSky, Bloomberg writer Jason Schreier blew me away when he posted: "Seven days into 2025 and I've already played what I suspect will be one of my favorite games of the year: The Roottrees Are Dead." Wow! ## Assorted NixOS things DevFeed: [Assorted NixOS things]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2024-12-07T20:19:00Z Content type: article Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Nix](), [Command-line interface](), [systems](), [tailscale](), [Virtual Private Network](), [Text-based user interface]() Tags: [cli](), [commands](), [configuration](), [dependencies](), [errors](), [git](), [module](), [nix](), [nixos](), [nixpkgs](), [packages](), [repl](), [tailscale]() ### AI overview A running log of practical NixOS, Nix, and Nixpkgs notes covering flake metadata, the module system, package updates, the Nix language, REPL builds, fixed-output derivations, and Tailscale exit nodes. ### Source excerpt Running log of random things I've learned about Nix/NixOS/Nixpkgs ## A Better Mastodon Client DevFeed: [A Better Mastodon Client]() Original publisher: [Read original article]() Published: 2023-12-19T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [Mastodon](), [client](), [Streamlit](), [Embeddings](), [SQLite](), [Algorithm](), [Vibe coding](), [Artificial Intelligence](), [scikit-learn](), [tailscale](), [OpenAI]() Tags: [client](), [clustering](), [embeddings](), [github](), [github-copilot](), [mastodon](), [sqlite](), [streamlit](), [tailscale]() ### AI overview A developer describes building a Mastodon timeline dashboard that caches posts in SQLite, creates embeddings, clusters posts by topic, summarizes the clusters with an LLM, and makes the dashboard accessible on a phone through Tailscale. ### Source excerpt Last night I had an idea and went ahead and built it. I'd like to tell you about it. Find the source code here. ## Getting Started with Tailscale in 10 Minutes DevFeed: [Getting Started with Tailscale in 10 Minutes]() Original publisher: [Read original article]() Author: Alex Kretzschmar Published: 2023-11-22T00:00:00Z Content type: tutorial Language: en Sources: [Tailscale Community]() Topics: [tailscale](), [Virtual Private Network]() Tags: [getting-started](), [homelab](), [minutes](), [networking](), [tailscale]() ### AI overview A tutorial introducing how to get started with Tailscale in under 10 minutes. ### Source excerpt Everything you need to know to get started with Tailscale in under 10 minutes. ## Funnel and Serve: Tailscale Explained DevFeed: [Funnel and Serve: Tailscale Explained]() Original publisher: [Read original article]() Author: Alex Kretzschmar Published: 2023-11-09T00:00:00Z Content type: tutorial Language: en Sources: [Tailscale Community]() Topics: [tailscale](), [Internet]() Tags: [demo](), [funnel](), [local](), [serve](), [tailnet](), [tailscale](), [video](), [vs-code]() ### AI overview A demo video explains how to access local services over a Tailscale tailnet or the public internet using Funnel and Serve. ### Source excerpt Accessing your local services over your tailnet or the public internet is one command away, as Alex demonstrates in a new demo video. ## Funnel-y enough: Release Recap November 2023 DevFeed: [Funnel-y enough: Release Recap November 2023]() Original publisher: [Read original article]() Author: Parker Higgins Published: 2023-11-02T00:00:00Z Content type: release Language: en Sources: [Tailscale Community]() Topics: [tailscale]() Tags: [funnel](), [release](), [release-recap](), [serve](), [taildrop](), [tailscale](), [updates]() ### AI overview A November 2023 Tailscale release recap covering updates to Serve and Funnel, Taildrop, and automatic updates. ### Source excerpt Big updates to Serve and Funnel, Taildrop, and auto-updates in the latest Tailscale release. ## A homelabber's networking playground using VLANs DevFeed: [A homelabber's networking playground using VLANs]() Original publisher: [Read original article]() Author: Alex Kretzschmar Published: 2023-10-26T00:00:00Z Content type: tutorial Language: en Sources: [Tailscale Community]() Topics: [networking](), [Opnsense](), [Proxmox](), [tailscale]() Tags: [homelab](), [how-to](), [networking](), [opnsense](), [proxmox](), [tailscale](), [video]() ### AI overview A how-to video demonstrates how to create a segmented network zone using Proxmox, OPNsense, and Tailscale. ### Source excerpt Create a segmented network zone with Proxmox, OPNsense, and Tailscale in a new how-to video. ## Using a Tailscale Exit Node on Sketchy Hotel Wi-Fi DevFeed: [Using a Tailscale Exit Node on Sketchy Hotel Wi-Fi]() Original publisher: [Read original article]() Author: Claire Wang Published: 2023-08-18T00:00:00Z Content type: article Language: en Sources: [Tailscale Community]() Topics: [tailscale](), [Virtual Private Network](), [networking]() Tags: [exit-node](), [hotel-wifi](), [tailscale](), [vpn](), [wifi]() ### AI overview The article describes using a Tailscale exit node to circumvent sketchy hotel Wi-Fi. ### Source excerpt Circumventing sketchy hotel wifi using an exit node. ## tclip: A pastebin for your tailnet DevFeed: [tclip: A pastebin for your tailnet]() Original publisher: [Read original article]() Author: Xe Iaso Published: 2023-08-17T00:00:00Z Content type: article Language: en Sources: [Tailscale Community]() Topics: [tailscale]() Tags: [funnel](), [tailnet](), [tailscale](), [text](), [tsnet]() ### AI overview tclip is a Tailscale-powered pastebin for sharing text between machines or coworkers. ### Source excerpt Sometimes you need to paste text between your machines or coworkers. tclip is a Tailscale-powered pastebin that lets you do just that. [Next page]()