4 ms·

Thanks! I'm happy to hear you like it. I'm still working on the details, but I want to create an easy way for someone to sell their blog's content as an ebook

Thanks! I'm happy to hear you like it. I'm still working on the details, but I want to create an easy way for someone to sell their blog's content as an ebook subscription that works on any eReader and isn't locked into a single platform (I'm working on adding PDF output and some more formats soon!). There are two models that are possible: monthly fee, or percentage of sales. I think I can do both -- percentage of sales for people who are just starting out, and a monthly fee for heavy users who want a volume discount on their sales. I apologize if this is a bit vague, but I'm still trying to figure out what will be the most fair and sustainable way to do pricing. I'm also working on the terms, right now I just prohibit using this for anything illegal, which would include redistributing content you don't own or isn't under the Creative Commons. This is a very nuanced issue: I think it is perfectly fine for someone to use my service for a feed like Ars Technica as long as they don't redistribute the ebooks that I generate for them. In other words, it's fine if you use my service as a "RSS Aggregator for eReaders" if that's your intended use case, but it's not fine if you post up a Mobi file of Ars Technica's content to The Pirate Bay or something like that. Let me know if you have any questions :-)

jacquesm 14y ago
> right now I just prohibit using this for anything illegal Forbidding such use doesn't limit it though. If you're going to profit from this in some way make sure you don't accidentally set yourself up as a prime target for a lawsuit based on contributory infringement. This means that before you get into the money stream you have to make 100% sure that the content you profit from was acquired legally.
- shantanubala 14y ago
  I'll definitely be getting some legal advice before setting up any kind of paid service, but do you have any specific advice or guidelines to follow? I'm assuming that right now, I can just say, "this is an RSS aggregator like Google Reader, and it's up to users to comply with copyright laws," but it would definitely be tricky once I begin charging. In general, would some kind of automated verification like Google Apps (DNS records or sending an email to the owner of the domain name) suffice? Anyway, thanks for the help! EDIT: The nature of my app is very similar to Stitcher Radio (http://stitcher.com/ http://stitcher.com/). They seem to have a really detailed signup page for podcasters (http://stitcher.com/contentProviders.php http://stitcher.com/contentProviders.php). That seems to be the best way to protect against infringement.

jacquesm 14y ago

> right now I just prohibit using this for anything illegal Forbidding such use doesn't limit it though. If you're going to profit from this in some way make sure you don't accidentally set yourself up as a prime target for a lawsuit based on contributory infringement. This means that before you get into the money stream you have to make 100% sure that the content you profit from was acquired legally.

shantanubala 14y ago
I'll definitely be getting some legal advice before setting up any kind of paid service, but do you have any specific advice or guidelines to follow? I'm assuming that right now, I can just say, "this is an RSS aggregator like Google Reader, and it's up to users to comply with copyright laws," but it would definitely be tricky once I begin charging. In general, would some kind of automated verification like Google Apps (DNS records or sending an email to the owner of the domain name) suffice? Anyway, thanks for the help! EDIT: The nature of my app is very similar to Stitcher Radio (http://stitcher.com/ http://stitcher.com/). They seem to have a really detailed signup page for podcasters (http://stitcher.com/contentProviders.php http://stitcher.com/contentProviders.php). That seems to be the best way to protect against infringement.