Building products is really fucking hard. read.cv is impressive by itself. Add sites, posts, jobs, etc. and it's godly. @mehdi @shen @andy deserve every ounce of respect on their names, no matter how sad we are.

Recreating even a fraction of this is not a weekend project. Enthusiasm + talent go far, and we are HOT right now... But infra is $$$$. Time is irreplaceable. And this idea has been tried by many great *great* people. This is the best iteration so far, and it's going away.

I've spent the past few hours burning my knuckles considering "what if we just could keep posts". I've written authentication, user accounts, and now started working on an importer for the read.cv exports (thanks @andy for the idea!)

But the wall I keep hitting, after personally being a part of early Dribbble, Designer News, Good News, and now read.cv... Where is the sustain? How do we make *this* one live more than four years?

I'd be very happy to build this with anyone, if we can find an answer to that question. (For the record, there are things on read.cv I personally would have paid more for, if they were available, like a public API for my profile content)

There's a "public" API you can access at sites.read.cv/api/user/[user… As the URL suggests, it's used for Sites, but it has all the profile content. I discovered it a few months ago while poking around Sites lol

😩