6.Redistributions of any form whatsoever must retain the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"

Nothing about having rewritten anything so far. The decision to pull or rewrite appears to not have been made, further supported by RAWA's later update.

All it takes is a little work to find the sources (okay, minor pun) and a little care to not extend too far past what has actually been said by authoritative sources (there's that word again).

Now, true, I can't remember if that quote referred to an individual or a company. I wouldn't be surprised if the post had been lost in one of the topic-splitting moderations going on here.

I think the source of the confusion needs to be sorted out before accusations get thrown around.

In the Mysterium video Rand talks about the hold up. (last 30 min +/-) Cyan used plugins in the development software and in the runtime game. Those have to be removed as they are not Cyan made but licensed from 3rd parties.

I suspect that some just made some tasks faster during development. Others are likely code that gets embedded in the game. Knowing what those plugins do, why and how to work around them likely needs some explanation. Apparently there is one person that knows how to do that. I think it kinda explains the 'something else' too. However he did seem open to having others help with the work, thus Whilyam's posts for volunteer coders to help.

I found it interesting that Rand still would like Cyan to run the servers. But, he seemed clear that is dependent on circumstances.

Rand: We ah, we, lets see here, We're rolling down the, ah, I'll make a story out of this...we'rechugging down the open source path because we don't really have anything else to do, and we're hoping for things to do because we've laid off people we don't have any income and we need kind of money and then this other deal came in where people said well hey, we'd kind of like you to use your engine and do this stuff for us, and suddenly Mark DeForest who was the engineer of the Open Source Train, choo choo -[makes pulling whistle cord motion], suddenly got involved in other things and we have our plans laid of what we need to do, and some of it is just technical, we'll pull certain things out that are, that we’ve licensed that we can't just let the public use and we have to, we have plug ins that we have to be careful with letting out, and we’ve got a plan about how to do it but suddenly Mark DeForest was engaged in money-bringing-in-work so that took priority, so we still have no other plans other than to do Open Source and like to move it out there, this time we are thinking we want to do
something a little different... boy its been a while since we did all of this, ..but it’s… we’d like to run the server, or run servers, and, but still have Open Source where people are able to build stuff and adjust stuff but We'd be more the keeper of it. mm. and see where that goes, cause it seemed like that might be a cool way to do it that way, we'd keep things going but its still passing thru a filter, m, but anyway that’s the plans, and as soon as really we run out of work we will get back on that.

Sure, blaming the mods is the easiest way.

Just because Rand refers to them as "plugins" does not make them so

However, I can understand why Chogon or other programmers would have used that term when explaining the situation to a non-programmer. The third-party code does "plug in" to the existing code, but it's not at all like a compiled plugin for something like Firefox.

The correct term for code that Plasma uses which Cyan did not write and does not have a license to release as open-source is "3rd-party code/libraries".

Neither assumption is supported by the only messages from Cyan upon which the assumptions are based: