From d2ed71c447e6c2f87f05123556ba1b69c5551fb0 Mon Sep 17 00:00:00 2001
From: Ben Harris <ben@tilde.team>
Date: Wed, 11 Apr 2018 14:03:33 -0400
Subject: [PATCH] wildcard

---
 news/002_dns_redirects.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/news/002_dns_redirects.json b/news/002_dns_redirects.json
index cff4672..f7797d5 100755
--- a/news/002_dns_redirects.json
+++ b/news/002_dns_redirects.json
@@ -3,5 +3,5 @@
     "date": "dec 2017",
     "title": "username dns redirects",
     "author": "<a href=\"/~ben/\">~ben</a>",
-    "content": "hey all<br>there is now a dns record (and virtual host) that will redirect requests from [user].tilde.team to tilde.team/~[user] -- for example ben.tilde.team redirects to tilde.team/~ben<br><br>also, the redirect preserves paths, so you can link to something under your user directory like this ben.tilde.team/blog => becomes tilde.team/~ben/blog<br><br>there are no ssl certs for these subdomains, so you will have to request those with plain http"
+    "content": "hey all<br>there is now a dns record (and virtual host) that will redirect requests from [user].tilde.team to tilde.team/~[user] -- for example ben.tilde.team redirects to tilde.team/~ben<br><br>also, the redirect preserves paths, so you can link to something under your user directory like this ben.tilde.team/blog => becomes tilde.team/~ben/blog<br><br>there are no ssl certs for these subdomains, so you will have to request those with plain http<br><br>edit: there is now a wildcard cert from letsencrypt for *.tilde.team, so you can use https with your username as a subdomain!! :)"
 }