I don't believe that devs should have to reveal their identities. These are open source projects. Criticise the code, not the coder. Identifying yourself as a dev only introduces yet another vulnerability to the coin: if the coin becomes successful, the dev could be persecuted. Nobody is behind Myriad, yet it continues to receive updates. When a security hole has been found in the multi-PoW system, the Myriad community has been quicker to release updates than DigiByte. That's with one single anonymous dev, and a community of contributers. Myriad is not dependent on its devs like DigiByte is.
The new Myriad website is in development, by the way. Check
http://reddit.com/r/myriadcoin for information
I was hoping to stay out of this conversation, but since I both discovered and fixed said security hole I thought I'd share my experience as a contributor. Every time I pointed out a flaw and offered a solution to DigiByte, Jared immediately welcomed my ideas and code. On the other hand, when I did the same for Myriad I was largely ignored. I should also add that there is an unfixed security hole in Myriad's multi-PoW system that DigiByte does not and will not have. As for releasing the fix sooner, in both cases it was decided to simply work the change into the next planned hard fork. It just happened that Myriad's planned hard fork was for a sooner date.
On a more philosophical note I do agree with you that people shouldn't need to know the identities of developers of a collaborative open source project. But the key word here is collaborative. Most coins are too much cathedral and not enough bazaar, to use the terms from
https://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar. DigiByte development has been more closed as of late, and it's one of the few things I will criticize it for.
Edit:
DigiByte copied Myriad's multi-algo design, and Myriad released a fix for the timewarp, as well as a fix for the work computing function, before DigiByte did. The fact is, Myriad keeps its security more up to date than DigiByte.
Nope, this is factually inaccurate. DigiByte fixed time-warp in November 2014. Myriad had to "fix" time-warp 3 times, the last of which was February 2015. In fact, Myriad copied their final time-warp fix from DigiByte.