8 ms·
> How come [the Github version is not convenient]? You went through the trouble to create a "free" HTML version of it, so you already know the answer to that q
by anonytrary 8y ago
> How come [the Github version is not convenient]?
You went through the trouble to create a "free" HTML version of it, so you already know the answer to that question. In any case, thanks for the link and thanks for posting your book to Github.
Regarding the Twitter permissions, the last time you checked was too long ago. You are asking for read and write permissions when you only need read[0] permissions.
Forcing people to market it on Twitter gives me the impression you aren't confident that people will share your book organically. Maybe you should just make the HTML version free like you said you would. You might even have more success in making people pay for the HTML version, compared to lying about it being free. I'm sure people would pay to read a beautified copy of the book, if it's any good.
[0] https://developer.twitter.com/en/docs/basics/authentication/overview/application-permission-model.html https://developer.twitter.com/en/docs/basics/authentication/...
- deleted 8y ago[deleted]
- bevacqua 8y ago> You went through the trouble to create a "free" HTML version of it, so you already know the answer to that question. In any case, thanks for the link and thanks for posting your book to Github. The GitHub experience was worse back when I implemented the HTML version on my own site, because they weren't rendering AsciiDoc back then. Regardless, I implemented it because it was fun to integrate all the things (O'Reilly Atlas, GitHub, Twitter, and my site's automation processes) and as a way to centralize all if my content on my site.