[woodandsteel]

>You're right, there are a ton of great ideas and suggestions for how to make IPFS better that we haven't gotten to yet

I love the idea of IPFS, but let me ask you the question, when is it finally going to be ready for people to easily deploy? A year from now, 3 years, 5 years? Or maybe you have no idea?

Don't give some vague answer about how you are working on it. Give me a reasonably specific prediction, or say you have no idea.

[singron]

Isn't this kind of an unreasonable demand? It's not like software isn't ready for anyone one day and ready for everyone the next. Considering just about nobody can give an accurate software development forecast for even objective milestones, it seems ridiculous that there would be any reasonable answer to this.

[charles_f]

Beyond the question of the possibility of giving a precise answer, did OP lose sight of basic courtesy?

As far as I know IPFS is an open system contributed to by volunteers. Making those kind of demands for deadlines in such an aggressive tone is way out of place.

[woodandsteel]

No, I am just asking for honesty. Either they have some sort of idea when it will be basically usable, or they don't. I am not saying they have to meet a deadline, I am asking when they think they are going to get there.

And why do they need to be defended by others? If I am being unreasonable, why don't they just say that themselves?

[bardan]

Who says they need to defend themselves? If I come across somebody making unreasonable demands I ignore them.

[woodandsteel]

I am not asking for an exact answer, just an approximate one. And if they honestly have no idea, then they should say that.

[TheColorYellow]

I want to call out this attitude as incredibly entitled and related to the exact root cause of all the open-source drama we've been seeing lately.