PrivateSend and PrivacyProtect (preferred) both sound good to me.
Yeah, I think that PrivateSend and InstantSend are nice and to the point. To make the two similar will be better going forward, IMHO. Keeping it simple is key for mass adoption.PrivateSend and InstantSend.
The more telling the words, the better Joe Average understands what it's for.
And, since I'm the poor soul who will most probably implement this in the CORE-client, it makes life MUCH easier to have words which are BOTH adjectives/adverbs and verbs, both for the UI and for the documentation as well.
I already did it as PoC with PrivacyProtect instead of Darksend (see https://github.com/dashpay/dash/pull/760), and it was (semantically) a mess.
I think we should ditch the names of these altogether. Attributes of currencies shouldn't have names especially when the underlying protocol can change. So it would be appropriate to say Dash supports privacy and instant transaction, but why does the process need a name? I'm sure both Darksend and InstantX won't be the final implementation or strategy we'll use, it'll get confusing to keep renaming them every 2 years. We could even have 2 or 3 separate subnetworks with different protocols.
Dash has instant transactions and privacy built in... sounds good to me
I agree, these features should be unnamed in future versions of Dash - a integral part of the package. Whatsapp introduced end-to-end encryption some days ago, did they name it "encryptiX"?
Dash has instant transactions and privacy built in... sounds good to me
No because it's default and you can't turn it on or off voluntarily like we can do with IX and DS over the Dash-Qt GUI. I fully agree that names can be ditched when the feature becomes default and not a choice. But until that's the case we still have to worry about naming opt-in features for distinction and marketing purposes.
PrivateSend and InstantSend.
The more telling the words, the better Joe Average understands what it's for.
And, since I'm the poor soul who will most probably implement this in the CORE-client, it makes life MUCH easier to have words which are BOTH adjectives/adverbs and verbs, both for the UI and for the documentation as well.
I already did it as PoC with PrivacyProtect instead of Darksend (see https://github.com/dashpay/dash/pull/760), and it was (semantically) a mess.
That's okay for the documentation, but that can't be put on a checkbox or button of the wallet. For this we need good replacements for Darksend and/or InstantX. IMO InstantX is already quite good, I wouldn't replace it.