BitShares Forum
Main => General Discussion => Topic started by: Akado on January 16, 2016, 02:39:05 pm
-
Question in the tittle. I'm honestly surprised because I've never heard of emercoin
On the annoucement https://azure.microsoft.com/en-us/blog/azure-blockchain-as-a-service-update-3/ it mentions:
Emercoin: A leading digital currency and Blockchain platform that focuses on innovative, scalable enterprise services.
I haven't searched but I doubt it has all the features that their homepage mentions implemented already.. Like BitShares..
So, what could take us there? How did they manage to pull an Azure like ethereum? Azure should go for the best options, well, we're one of the best. I dont recall Emercoin having any PR so our lack of it doesn't make it the reason... Probably they know someone there?
What could take us there? Anyone has any contacts ?
-
The key value system is a direct ripoff of namecoin aliases, then they tie it into the ddns system.
There is a dns server built in, and a pay per click model builtin which is interesting...
No unittests.. Its a sell for me.
-
The key value system is a direct ripoff of namecoin aliases, then they tie it into the ddns system.
There is a dns server built in, and a pay per click model builtin which is interesting...
No unittests.. Its a sell for me.
I never even heard of it, I can't really give my opinion on their tech but it's an amazing feat getting on Azure. I wonder about us. I think we'd have a shot, unless of course that was achieved by someone with the right connections, which we seem we're lacking. But if they did it I'm sure we could too.
If Emercoin did it...
https://twitter.com/AkadoSang/status/688386356679172096
Future prediction:
Azure partners with BitShares > NASDAQ adopts BitShares as a trading engine.
-
For starters, you need to define the protocol and document it in details. Not just have a reference client code, but actual protocol packet by packet definition.
-
They have good documentation and examples of applicaoons of their "features", for example leveraging the key value system to extend to any abstract business with data requirements in decentralized fasshion... so we need marketing related documentation to entice managent of azure and the likes.. developers can look at the api documentation.. azure will pick us up no prob
-
@xeroc is this kind of detailed documentation included on your worker proposal too?
-
@xeroc is this kind of detailed documentation included on your worker proposal too?
This couls definitely be done and I am already working on the serialization code of transactions .. once i figured that ot completely I can of course document it properly and go over to the block format etc...
-
They have good documentation and examples of applicaoons of their "features", for example leveraging the key value system to extend to any abstract business with data requirements in decentralized fasshion... so we need marketing related documentation to entice managent of azure and the likes.. developers can look at the api documentation.. azure will pick us up no prob
What exactly is "marketing documentation"?
-
They have good documentation and examples of applicaoons of their "features", for example leveraging the key value system to extend to any abstract business with data requirements in decentralized fasshion... so we need marketing related documentation to entice managent of azure and the likes.. developers can look at the api documentation.. azure will pick us up no prob
What exactly is "marketing documentation"?
http://emercoin.com/content/EMCDPO.pdf
http://emercoin.com/EMCDPO
That is just for the name value system.. See how they extrapolate with examples to trigger the readers imagination(marketing).
And then follow it up with a technical writeup
http://emercoin.com/EMCDNS_and_NVS
And that is for the copy paste code of namecoin.cpp 0,6,3... They took the name system and did documentation on it and made it "sexy".. Appealing to external people out of crypto.
The only innovation here is the ddns which i dont know is custom or copied, and relating it to thr name value system through lookups.
Its more fluid than what we have to a lehman. The migration guid should be less prevalent because newcomers wont care for bts 1.. Perhaps it should be the use cases link instead or, "what is bitshares"? And start talking about the big picture with links to the individual features we offer and within therr the links to tech documentation.. If we create this flow and get lehman to test it out snd repeat back what we want them to learn then its ready to go for azure.
Took me several clicks just now to read what i wanted i was jumpimg around.. With empty space on the side there should be some graphic symbolizing the feature it is talking about.. It will invite readers to stay on the pages that are important... Especially omes describing features..
All we need is for ppl to feel they are educated quickly about what we are about without trying to sound so smart that you need to be an engineer to "get" the idea of bitshares. We want them to say oh ok cool it can do that? What else? Ok cool i dont need the tech details you have sold me, seems like smart ppl behind this one.
The "features" marketing documentation should probably follow the guideline:
1) what problem are we solving? (Think outside of crypto)
2) why current solutions are not sufficient
3) validate that we are capable of solving and extendimgnthe solution with outside thembox thinking (so they will feel as if only we can solve related problems going fwd, basically hand holding)
4) how the feature works roughly for a lehman
5) what else can bitshares do? (Other marketing pages for other features)
Documentation to a project is like unit testing part of development.. It is equally important to the actual features.. If you only have half you wont have many ppl giving a shit especially ones that review it at a higher level to see if its worth more effort to integrate with.