Don't get me wrong I'm rooting for koinos and think the vision is great. I will probably mine a bit as well but I'm disappointed with this distribution, I think it could have been done so much better...

Using proof of work mining on Ethereum for the distribution goes against your goal of being the most decentralized blockchain. Only a very small group of people will a) know about KOIN in this 180-day

Sure I do, it's because I find what you write and share interesting :) Decentium is the best platform*, it aligns incentives between authors readers and the platform without inflation or other games that

Yep, I'm the founder. We are trying something different than Steem, no inflation or app specific token, just tips that come with visibility. Think Patreon meets Medium. You need RAM to deploy contracts

I think EOS so far the only platform where you can build an app that has an UX that does not suck. DPoS has its problems but it's still the best real world governance model IMO. I don't think that it is

Dead is a strong word :)

It is not stealing and all private keys remain untouched.

Thanks, although I find it hard to trust someone who's favourite pasta dish comes from a can here's the answers to your questions: Did you act alone in the decision to formulate this patch? Yes Besides

Hi Anthony, I'll answer your questions if you answer some of mine: Are you in the employ of Steemit Inc. or have otherwise rendered services to them or Mr. Ned Scott in exchange for any form of compensation

I disagree about the limitations of uri schemes stated in that article. Having callback url's does not exclude native applications at all (they can just have their own uri scheme to deep link back into).

I'm curious, why do you say that on-chain transactions are the better option for login compared to signing a message with your key proving ownership?

The error you got says you need to send the correct fee, looks like you're sending 30 when it wants 3?

Seems legit

Thanks! Looks like it needs to be upgraded to support https transport instead of WebSockets. Little point in doing it now though with HF20 around the corner. I might create some tool that helps people

Thanks!

Hmm, maybe I'm missing something but wouldn't it be impossible to dedupe the files if they have to be encrypted with the users public key before storing in IPFS? And without that feature what sets this

Cool but wouldn't it be very hard to scale a service selling large files on this when you can't dedupe content?

Thanks Sara! :) 🧘🏻‍♂️

Also worth noting is that dsteem works in web browsers so if those are your socket clients you can just get the operation stream client side directly

Yeah that is a implementation limitation, feel free to open an issue about it. However in your case you don't want to create a new stream for every client that connects, that would be very inefficient.