...
misleading impression
...
i'm no coder/software engineer/programmer but when we conclude in our discussion that this is your work around to get privacy--that's is super lame. i don't need to look at the code/ white paper to know stuff, i just look at the results and it is as clear as day, DASH private send is like the cassette tape in it's dying breath

There is nothing misleading there because nothing was implied/promised. Your demagogic approach fails to prove anything.
And you seem to agree that timing attack the way you described it is impossible. Good

Usability issues is a whole different question and not related to the things we were discussing. But sometimes you really do have to read the manual to use the new tech.
nothing was implied or promised by Evan for more than a month, but he knows something and the plan is set--he will make maternodes with a certain amount of coins locked (1000 DASH) and turn it to a HYIP

... and the other tech stuff of course.
makes sense why a person/s have to orchestrate an instamine..a perfect motive to grab as many coins as possible and reduce the supply from 84M to 21M...
the instamine issue was always portrayed here as an accident...but I'm putting
"MOTIVE" on the table here

i agree you found a work-around the timing attack, but still you have to follow the lame-ass manual...and as i have mentioned before, the FBI prosecutor found a way around bitcoin mixers, DASH was forked from bitcoin and private send was a fork of coin join...you get the picture? ... DASH privacy was over that's why monero flew above DASH, ZCASH will too.