You are viewing a single comment's thread from:

RE: Say Hello To DBooks: A Book Publishing Platform On STEEM - Publish Your Books And Earn.

in #writing7 years ago (edited)

Okay..

I really love your points raised. A second option that has been discussed is making the 20% we get from posts serve as a monthly reward pool which will be shared amongst writers based on the percentage of the overall total reads generated by their articles on the platform during the course said month.

That would be a better way to provide writers with long term sustainable income. We really appreciate your criticisms and I must assure you that most of these issues have crossed our minds

We're going to provide writers with as many options as possible to generate sustainable income and they can choose their own poisons

However, these are still early days for us and we would need all the help and funds (the initial purpose of the 20%) we can get to develop the product properly

We're taking things 1 step at a time.

Sort:  

I really love your points raised. A second option that has been discussed is making the 20% we get from posts serve as a monthly reward pool which will be shared amongst writers based on the percentage of the overall total reads generated by their articles on the platform during the course said month.

After the first couple of months, this is going to be heavily weighted toward those with established presence on the platform and almost none of it is going to go to newcomers, and that's the way it's going to be until you shut down the project.

Now, that might be exactly what you want, but from the perspective of someone who is coming along later, they have almost no chance of competing in the midterm with those who already have an established presence. You are basically holding them in with the hope that they will be someone who is recognized as a creator within this niche in coming cycles.

You have effectively, philosophically, re-created "publish or perish" as well as a system which simultaneously rewards simply having been on the platform the longest. I am not sure that was entirely your intention.

Also, you immediately open yourself to be the target of some sort of distributed bot "reading" swarm, given that you are going to distribute that 20% by "reads." If I can buy up votes on the blockchain, I can most certainly buy "reads" for the same distribution mechanism.

It's hard to get away from the multilevel marketing whiff coming off of this. After all, let's consider the degenerate case in which no books are voted up for a month. There will be no 20% to take. It doesn't matter how established the writer is, they get nothing. Now let's consider the case where the number of people publishing books on the system triples, but the number of consumer and consumer-hours does not. In that period, each view becomes worth effectively 1/3 of what it was before. Unless the amount of the 20% taken can grow faster than the number of people who want to be involved in the system by a good amount, it becomes more advantageous for those already in to keep people out in order to protect their rewards.

You've just reimplemented a reward pool that mimics the same failure modes as the Steemit reward pool. It just keys often easier mechanism to automate.

However, these are still early days for us and we would need all the help and funds (the initial purpose of the 20%) we can get to develop the product properly

Unfortunately, you need to do more than minimum viable product to have a successful rollout. You have to have a system built in theory which actually does what you say you want it to do. It needs to be resistant to exploitation by automation, because we already know that sort of exploitation exists on the platform we've got. It needs to not set up mechanics which actively incentivize bad actor behavior. It needs to decide what it wants to do before you start implementing anything.

I realize that the "don't think, go fast, fail fast" process is popular in Silicon Valley circles, but I've always been fond of replacing that whole architecture with "don't fail."

For me, as a writer who is already published, I need some kind of understanding of the theoretical underpinning of how it's all supposed to work devoid of handwaving, and which reflects a fair amount of consideration about my experience as a user, to be the kind of person that gets on board this sort of thing.

I may not be the kind of user you're targeting. You may be looking for the people who are just looking for a lighter weight, less promising vanity press. Which is fine, as far as it goes, but if so you probably need to really lean heavily on what advantages your system will provide over what already exists on Amazon and Google Books – and if you can't answer those questions, find some answers to them.

There are a lot of ways for independent authors to self publish these days, ones in which they retain most of the rights of distribution going forward after publication. You have to compete with those.

I think the 20% distribution is actually a valid strategy. It doesn't have to be based on views.. could be based on likes too. It would be the same thing as Steem extending the voting rewards from 7 days to like a year we'll say. The only difference is that it's capped at rewarding only 20% and not the full portion of money.

Besides Steemit, DTube seems to be the most popular steem-based app right now. But with your argument, they too fall to the demise of the 7 day cap. Great video content takes as much effort to produce as anything else.

I think the real issue is with Steem. Steem misses out on a lot of use-cases by limiting us with a 7 day reward pool. One solution would be, when they release the ability for people to create their own tokens, to also be able to choose a time limit for rewards.

With that said, I agree with what you say, and I think DBooks suffers this problem at a much greater length. Also, the design of the MVP is very weak (a bookshelf as the background???).

I will say that fundamentally, the idea of DBooks is pretty interesting. If we were to imagine the centralized version of it, it would be like Scribd.

Thanks for your insights. You've raised very cogent points which we will seriously consider and discuss at length to better improve our business model

Thank you very much

We're really committed to this project and would love it to be fair, just & self sustaining for as long as possible

We really appreciate these criticisms and we would take them as constructive.

You've made very valid points. We are going to re-strategize and come up with answers to these honest concerns of yours and I'm sure others will share the same.
If the reward pool system based on views seems flawed, what do you think about a voting system like what we have in steem witnesses?
You've shared your concerns, we've listened. Now we would love to listen to suggestions if you have any. I truly appreciate your inputs, it just goes to show you care and you're passionate about what you love.

You do realize that the voting system that we have in steem witnesses is functionally identical to the voting system that we have to slice up the reward pool, right?

That is to say, it literally depends and scales based upon the amount of vests in your account. It is not, contrary to some popular belief, simply a straight "number of votes" voting system. Like everything else that ultimately uses rshares under the hood, it's all Proof of Stake.

That would actually be no change at all.

Honestly, the best suggestion I can offer you is "don't do that." You are effectively asking me "what's the best way to drive this screw with a hammer?" The tool you're bringing to bear on the problem is the wrong tool for the job.

Among the mismatches the fact that steem is a public blockchain and every single transaction which occurs on it is public runs directly counter to the aims of your project, which is to control access to content. That's not how this works. That's not how any of this works.

At heart, beyond the public versus private dichotomy, you have a problem which will always exist for the steem blockchain as it is constituted and designed from the ground up: content older than five days old cannot be given value. That's a hard limit. It would require at minimum a hardfork to fix, and you might be surprised how many things under the hood might break as a result.

These are the two biggest problems and that there really aren't suggestions or solutions to them. They are quintessential.

If you want to establish a distribution network/publisher based on a public blockchain, and especially this public blockchain, those of the big hurdles.

And that sucks, but it's the nature of the world. I think you have picked the wrong project.

You would be better off rereading hardfork 20 and what it's going to bring to the platform and start putting together an interface which will take advantage of the opportunities for curation of content that is being posted anyway, possibly taking as inspiration Utopian.io and publications on Medium. If you can get a prime seat at the table for that, focusing on literary content, you may have an operable project.