@agd Working on this now. I started off making it so that when a user is unauthenticated, all blogs and posts return a 404 (to not reveal the existence of any blog). But I'm wondering if it'd be better to send a user to the login page, instead, for better convenience. If so, we could still obscure existence of individual blogs by simply sending all routes to the login page when unauthenticated. This could be the same for the API -- all routes would just require authentication.

I'm going to go ahead and finish this up.

Current status:

I think we'd just redirect people to the correct route -- this would allow instance admins to set it to anything they want without modifying the app itself. For example, they could even choose a default blog to land on if they're running a multi-user instance.

So let's say I set default landing page to about. Does it means that when visitor lands, he/she will be redirected to /about, or will stay on / but about page will be rendered there?

Just to add: https://distbin.com adds the original URL to the cc property on the Create activity.

From certmagic:

Remaining work here is mentioned in T536: Compile all static / default assets into binary.