He's dead Jim

After careful consideration of all the variables, I've decided to scrap the project. Reasons:

Interest and feedback from target audience was not even lukewarm, it was actually non-existent. This is most likely something that might have been alleviated by better PR work on my part, IF I was the sole problem of the project.
The elephant in the room: Developing AND supporting dozens of integrations. Rotor already integrates with a dozen of external services. Writing the initial implementation for an integration wasn't that hard (with the exception of Twitter perhaps), maintaining all of those integrations while simultaneously implementing new ones will result in an incredibly high workload in the long run. I would probably be left without much time to work on new projects.
I was not satisfied with compromises users would have to live with using the product. Rotor's editor is actually quite capable but how much of your content would get lost in translation when publishing would vary greatly:

Publish to Blogger and lose all Embeds (Youtube, Twitter etc.)
Publish to Facebook and your carefully crafted article containing Code-Blocks, Images, Quotes etc. would end up as plain-text.

And the list goes on.

I have another project on the list that does not suffer from the problems listed above while sharing a lot of functionality with this project, meaning I will be able to jumpstart the new project. The outlook of getting back on track with a new project using the fast lane, greatly eases the pain of conceding defeat.

Peace out!