4 ms·
This came up when we were working on this, the team at ReadMe has been very responsive about this and I don't feel like we'll be trapped on the platform. They u
by codezero 12y ago
This came up when we were working on this, the team at ReadMe has been very responsive about this and I don't feel like we'll be trapped on the platform. They use Markdown for almost everything except some widgets, and since I'm going to use mainly Markdown I don't feel locked in.
I also feel confident that if I kindly asked for the contents of my site, the team at ReadMe would send it on over in what ever way they could. That may change in a year, but I doubt it, if anything, I bet they'll have a more automated way to get content in and out.
The ToS sounds pretty standard for "content" sites... that is, they have to have the rights to display the content, since they are the host. In my experience you're much more likely to get a shady crawler copying your content and reposting it than the service you pay using it in ways you didn't expect.
edit: woops you deleted. I think your questions were very valid, so I'll leave my reply :)
- forsaken 12y agoSorry about that. I thought it sounded negative and didn't want to talk badly about the product. My question was basically "Are you okay with publishing content on a site that owns the content?" I imagine they are building export tools in the future, and this is just the first version.
- codezero 12y agoI don't think it was negative, that's exactly the kind of question my co-workers asked when we were talking about ReadMe. I'm OK with it. I've found that more often than not, questionable third parties skimming content and republishing outside any control tend to steal your content and misuse it more than providers that have a solid service do. I trust the ReadMe team to do the right thing and if they don't, instead of leaving supportive comments on Hacker News, I'll rant :)