the obsfucation that apparently other devs I talk to have a hard time finding.
I feel a bit trolllish now. I wish jake the best of luck but he is dangerous to work with. Id drink a beer with him, but not pay him for work again under any circumstances.
Well, I feel like "obfuscation" is a very specific thing. For example, when I download minecraft.jar and I want to take a look at the code, it contains obfuscated .class files. Normally, it's fairly trivial to decompile a .class into a .java file. It's not ideal because it won't have any comments, but it's usable.
But since Mojang obfuscates, the resulting .java file is practically unusable. So developers had to deobfuscate the .java in order to get anywhere, which is a huge project.
I haven't seen anything like that for STEEM, at all. I assert that the STEEM API is not obfuscated in any sense.
The problem i am having is not that faddat took the money and really just said "duck u fuzzy", he has kept bringing it all up like it is Steems fault and THEN uses THAT to try to sell his future project.
Then brings me into it...
ALL I want to do is produce value. Plant beautiful fucking seeds and watch them grow into epic trees with sweet fruits and heavy yields...
Yet instead I get to carry this constant lead weight around that I invited into my life and even worse--my own personal sphere of trust.
At this point...If faddat shut up and built something, and would leave me and anything connected to me out of it, id be cool. But this seems impossible for him. He either doesnt realize the damage he is wreaking like king kong, is intentionally trying to cause drama and destruction, or sees value in producing drama to get people to buy into something he will never build.
(or maybe he will build it? noooooo proof of this. at present 5% chance imho).
See, you made it my reputation versus yours. So I've got to do this, if I care about my reputation, because I trusted you-- and you told me that you knew that the APIs had been deliberately flawed-- LONG AFTER you'd hired me. Don't you think that might have been better to disclose up-front? That way, I could have told you from the start-- "there is no way to build that on this codebase because this codebase (I'm speaking of graphene, mind you) is unadulterated sewage.
And that fuzzy-- THAT is why you "have problems hiring developers": you have your head so far up graphene's ass that you can't even be bothered to have a comparative look around. Why do most folks who build against graphene fail?
It does not behave as the docs claim it does
DONT hire ANYONE to build ANYTHING on top of something you know is fucked!
Instead, tell the TRUTH-- graphene obviously wasn't meant to be anything more than a scam, because someone who wasn't scamming, WOULD CARE ABOUT THE QUALITY OF THE INTERFACES!
This is something that people who "give a fuck" would do. Ensure that all user-groups are able to use the software-- in the same manner that the documentation states.
If I were a better, wiser man, I would have gone apeshit to every cryptocurrency site out there the second you dropped that grenade in my lap, senor "happily goes along with a scam"
Oh faddat you must think i dont have info on you that you think noone knows about. Ive been quietly getting research together. Some of it starts making me realize why you move around so much. Want to attack me AFTER screwing me out of 15k? Can you please just leave me the fuck alone?
Fuzzy, you must have info on me that I don't know about, either. Post/state/do whatever you want man. I'll go through line by line and say what is true or not. Anything. Have a ball.
Go for it dude, say whatever you'd like. Anything.
the obsfucation that apparently other devs I talk to have a hard time finding.
I feel a bit trolllish now. I wish jake the best of luck but he is dangerous to work with. Id drink a beer with him, but not pay him for work again under any circumstances.
Well, I feel like "obfuscation" is a very specific thing. For example, when I download
minecraft.jarand I want to take a look at the code, it contains obfuscated.classfiles. Normally, it's fairly trivial to decompile a.classinto a.javafile. It's not ideal because it won't have any comments, but it's usable.But since Mojang obfuscates, the resulting
.javafile is practically unusable. So developers had to deobfuscate the.javain order to get anywhere, which is a huge project.I haven't seen anything like that for STEEM, at all. I assert that the STEEM API is not obfuscated in any sense.
The problem i am having is not that faddat took the money and really just said "duck u fuzzy", he has kept bringing it all up like it is Steems fault and THEN uses THAT to try to sell his future project.
Then brings me into it...
ALL I want to do is produce value. Plant beautiful fucking seeds and watch them grow into epic trees with sweet fruits and heavy yields...
Yet instead I get to carry this constant lead weight around that I invited into my life and even worse--my own personal sphere of trust.
At this point...If faddat shut up and built something, and would leave me and anything connected to me out of it, id be cool. But this seems impossible for him. He either doesnt realize the damage he is wreaking like king kong, is intentionally trying to cause drama and destruction, or sees value in producing drama to get people to buy into something he will never build.
(or maybe he will build it? noooooo proof of this. at present 5% chance imho).
No man.
See, you made it my reputation versus yours. So I've got to do this, if I care about my reputation, because I trusted you-- and you told me that you knew that the APIs had been deliberately flawed-- LONG AFTER you'd hired me. Don't you think that might have been better to disclose up-front? That way, I could have told you from the start-- "there is no way to build that on this codebase because this codebase (I'm speaking of graphene, mind you) is unadulterated sewage.
And that fuzzy-- THAT is why you "have problems hiring developers": you have your head so far up graphene's ass that you can't even be bothered to have a comparative look around. Why do most folks who build against graphene fail?
It does not behave as the docs claim it does
DONT hire ANYONE to build ANYTHING on top of something you know is fucked!
Instead, tell the TRUTH-- graphene obviously wasn't meant to be anything more than a scam, because someone who wasn't scamming, WOULD CARE ABOUT THE QUALITY OF THE INTERFACES!
This is something that people who "give a fuck" would do. Ensure that all user-groups are able to use the software-- in the same manner that the documentation states.
If I were a better, wiser man, I would have gone apeshit to every cryptocurrency site out there the second you dropped that grenade in my lap, senor "happily goes along with a scam"
That is quite a bar you've set for yourself.
Users make the decisions about blackjack and hookers.
l0k1 and I make the chain.
I'm curious about how you plan to document your platform. Like, how do you plan to define/approach the intended audience?
For example, do you have a strategy for determining what topics are too simple to bother explaining?
LOL.
Oh faddat you must think i dont have info on you that you think noone knows about. Ive been quietly getting research together. Some of it starts making me realize why you move around so much. Want to attack me AFTER screwing me out of 15k? Can you please just leave me the fuck alone?
Fuzzy, you must have info on me that I don't know about, either. Post/state/do whatever you want man. I'll go through line by line and say what is true or not. Anything. Have a ball.
Go for it dude, say whatever you'd like. Anything.
Naw i simply said i have it. Because ive learned you are 100% reverse to who you act like you are. Im not like you man.
Sad. So sad.
The one I was told about. By fuz. That the api was made "deliberately difficult to use" by St. Dan.
Except that is retarded. And as soon as I heard that I should have been shouting it from every rooftop.
And THAT is what I fucked up here. And I'll openly confess that one:
I've done mighty wrong by not disclosing all of this much sooner. I will be posting the conversations shortly.