Is read.posts.cv and posts.cv an option?
Posts for web is humming along! Curious if you’d rather a subdomain or a new TLD? 1️⃣ posts.read.cv 2️⃣ posts.cv 🤔
when the beta invites were sent around on twitter, everyone took pains to say it was "postS" not "post". i myself checked several times. some alts: dispatch.cv memos.cv friends.cv club.cv
I think the two will be tightly coupled - but having the two profiles separated feels like they address two different but symbiotic use cases for now
In my experience subdomains are better used for internal organizational structure. TLD with a path are better for UX. Also, simpler is almost always the right choice. So #2 would be best :)
I thought you were planning to merge read.cv’s Explore with Posts later on So I was expecting read.cv/posts :) TLD otherwise
2️⃣ seems easier to remember. What’s your thinking on read.cv’s relationship to posts atm?
2 is catchier, but 1 makes more sense. read.cv/posts There’s no posts without readcv. At least for now.