prose.sh Read page using custom domains for links

[michaeldingler]

The "read"/discovery page for prose.sh (i.e. what's deployed at https://prose.sh) links to the subdomains, even if the user has a custom domain. For example, my much neglected blog's latest entry would be linked as

https://pseudocode.prose.sh/stylin-too

instead of the more "canonical"

https://michaeldingler.de/stylin-too

Downsides:

• Multiple ways to reach domain might not be intended by user
• Search engines reference subdomain link
• Less obvious for potential customers that pico/prose offers subdomains in the first place.

For comparison, the Bearblog Trending page at https://bearblog.dev/discover/ links to a custom domain, if present (and also the full url in any case, but that's a slight digression).

[antoniomika]

Hey @michaeldingler,

Thanks for dropping a note. This is partially due to a limitation in how we handle custom domains.

The custom domains feature is currently "stateless", meaning the user doesn't have to do anything to get custom domains working on our side and all configuration has to occur from their side. It all utilizes DNS and we do JIT checks to make sure things are configured properly.

Benefits of this are we can confirm user domain ownership AND give the user ultimate flexibility (with using CNAME/wildcards in DNS) but have the downside that you mentioned of it being hard to go back and find the user domain.

@neurosnap maybe we should add a column to the user's entry (for prose) and project (for pgs) to keep track of the domains associated? Not sure if the added complexity is worth it though as we're currently pretty efficient with that handling logic. Could pave the way for us to limit custom domains if needed in the future though, so could be a good future proof?

[neurosnap]

#132 related