Just to clear up a few things. (I'm @mandica, the founder of XSPEC and still here for anyone new to this)
All the discussions about code snippets and code cloning and implementation of protocols is a bit stagnate. This is the nature of open source development. There is no secret (and never was) that XSPEC was build on SDC. XSPEC never claimed to be proprietary code and is based on Bitcoin in the end as many others are. This point has been laboured ad nauseam and if your objection to a crypto is based on it's Bitcoin / SDC / Monero code provenance then you will seek out other projects. The fact that XSPEC is open source and based on other open source code is not a basis on which to claim a scam if you are a thinking person.
@jbg and Bryce are working on the code and as you all know, not every update is shown on GitHub immediately. GitHub is a not a live window to follow updates. Nobody as forced anyone out and in fact Spectre has very dedicated community and in fact, I would suggest that a dedicated community is what will succeed in driving this forward. XSPEC now also have steady development funding and will hire. The community will make sure that XSPEC will last for years to come and with a solid dev fund we will have the resources to develop the project. The team is together and strong and nobody has left for anything else. I am working on something auxiliary that will benefit XSPEC in the long run but can't say anything right now.
XSPEC is not a scam, we are just trying to provide a quality functional privacy focused cryptocurrency against a tide of FUD and shit and we will succeed. I have nothing more to say and there is nothing to discuss. Adversity brings out the best in us. Discard XSPEC at your peril.
Do you have anything to show us as evidence that two full time developers have actually implemented something besides those few lines of code? I would really love to see it because I stil hold my xspec.
Why have we been told that xspec wallet automatically checks for the Tor connection, and if doesn't find it it tries to use obfs4 obfuscation? One doesn't have to be C or C++ genius to implement this. It is very simple actually.
I could even accept KISS method here, but this would understand transparency, openness, documentation which explains people how should they use the wallet and obfs4.
Even something in the lines of 'Guys try first if the Tor is working, if not, drop the obfs4 exe to that folder, copy this configuration file to another, restart the wallet and check again.' or even admitting, telling people 'some issues have appeared, it doesn't work like we expected, and we are busy with implementation of 1.4 wallet.'
So:
obfs4 doesn't work as we have been told.
Automatically adjusted ring size was promised for 1.3.5 and on official site it is stayed that it has been implemented with 1.3.5.
1.4 code was supposed to be uploaded to github month ago.
I would be 100% ok with the project if jbg or someone address and fix these issues.
Under assumption 1.4 is far away from being implemented (bugs don't matter), I would stil be ok, but in this case you have to explain to the community why did you collect donations, and claimed two devs are working full time, because we don't see the results of this work? Please refer to the code they implemented?