Hi humanitee.... its been awhile. your points you raise here are valid and have solid merit. There does seem to be a bit of a vacuum at times. I think what would be helpful would be to start a weekly "state of the Union" address by Evan or someone on the dev team. Lets say every Friday there is a paper, vidoe feed something of that nature that everyone can look forward to. this be compiled into a weekly statement then released through all the channels, here, IRC, the website darkcointalk, media etc etc. This would address the hyper sensitivity to lack if regular information and would give adopters and investors something to look forward to. By nature of what we are doing here... it would have to be technical in nature and not a feel good press release, hut a real nuts a bolts "where we are at" this week. Thoughts?
I would like anything remotely close to what you are saying.
I realize the technology is always changing, and I am happy about that. You don't get anywhere without making incremental improvements to your basic design over time.
We don't need all the information, I think the ring signature aspect could stay secret up until 1-2 weeks before going live. But stuff like IP obfuscation should get some addressing if it is in fact going to be in RC4. There are a multitude of pre-existing ways to accomplish that, so which one have we chosen? By addressing that, you give credence to the incredible claim that OUR COIN HAS FOUND A REPLACEMENT FOR RING SIGNATURES.
Do you not agree, however, that there should be a balance? Too much technical talk and the masses' eyes glaze over -- and they outnumber us techies a lot to a little. And then you have the fact that DRK's tech is contently changing -- just how out of date is the whitepaper for example. Talking about details then changing them confuses people technical or otherwise. Maybe the balance is too much swung toward generic information at he present, but move too far back in the opposite direction and there will be problems all the same.
I agree, but the masses don't have to read the post. You want the people like me, like AlexGR, to understand the current state of development, to understand the technology.
I can't sell something I know nothing about. I can't defend DRK with general statements.
"Don't worry DRK is getting IP obfuscation."
"How does that work?"
"IDK?"
Point taken.
Though I feel that this information will come as the tech is set in stone and definitely will be available when Darksend is open-sourced as anybody will be able to take a look at the code.
The real problem is that DRK got sidetracked for nearly two months in fixing masternode payments. And while MN's are needed for the current iteration of Darksend, the issues delayed everything and pushed the coin off message. It has been a stupidly long time since anonymity was discussed in this thread. With MN's mostly out of the way, I think you will get what you are asking for in fairly short order -- maybe even a bit today
Absolutely. I feel like some things should be kept secret and some things should not. However, sharing the tech ideas allows the community to vet it, and although we might not be amazing cryptocurrency programmers, we might have some ideas that are moderate improvements. Even Anonymint would then have enough information to once again engage Evan in technical discussion.
To make sure I understand, you're essentially suggesting two things:
1. Provide information to a group of key communicators.
This is a standard part of an information campaign, just not something I've gotten to yet. Having said that, in this case I'm not sure it would have made all that much difference.
Incidentally, I said I would need to ask Evan about I2P. Neither that nor IP obfuscation are slated for RC4.
2. A weekly status update.
As I said a day or two ago, this is something we started in the few weeks leading into the first launch of RC3 (we titled them "Development Updates"). After that, there was information coming out more or less every weekend, so that was used in lieu of. After today I'd like to resume them, where confidentiality permits.