I still don’t get why this is separate from read.cv 😬 there seems to be significant overlap?

Posts for web is humming along! Curious if you’d rather a subdomain or a new TLD?

1️⃣ posts.read.cv
2️⃣ posts.cv

🤔

2️⃣ seems easier to remember. What’s your thinking on read.cv’s relationship to posts atm?

Ok posts.cv coming very soon ahhhhhh 💥

Nah I don’t think we would change read.cv right now

Number 2 solves the access is a easier way.

Fair enough! We’re cannibalizing ourselves faster than anticipated hehe

And for that reason I’ll go with subdomain. Don’t bother risking creating a new brand/name from it since you’re not sure about its future.

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️⃣! for simplicity.

but are you ready for the post.app and posts.app conversation? people get confused.

Nom nom — in that case I vote (2) if you want to start signaling the difference between the two and move users into posts being the primary product. The (1) makes me think posts is a feature of read. Not sure if that’s what you guys want to signal.

2 is catchier, but 
1 makes more sense. read.cv/posts 

There’s no posts without readcv.

At least for now.

No worries, only reason I ask is b/c it seems like read is a feature in posts, but that’s only from my perspective!

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

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