Sort:  

Truth machine.

I was busy being a butthurt idiot.

It was terrible decorum of me to post this.

I don't know what I should have done. It's been shit. I'm sorry.

The best part is, you said sorry, and acknowledged it. You didn't say:

I have a $5,000 report that might contain an apology, but you have to buy it, to find out.

That $5000 report is in my posts. All you'd need to do is read them. Plenty of reproducible scenarios contained in them, not sure how may hold water anymore, but I know that some do.

The report absolutley wouldn't contain an apology. I worked much, much harder than fuzzy knows for the ~$10-15k he paid me. All of these issues could have been avoided if stinc had made the wise decision to implement a grpc or swagger API instead of sticking with the websocket of doom.

"How hard you workes" has LITTLE to do with it.
I paid you for a job done. Not a job tried. Others nearly cry that i paid you 15k when i talk to them because they are already building it.

Loading...

The situation is far, far more complex than that sir. The situation is much closer to:

  1. Steem was even more infant than it is today when I began this work.
  2. Though it did exist, steem-js was far, far less mature than it is today, and @fabien hadn't come onto the scene.
  3. Steemit, inc presented steem's API/RPC as far more mature and reliable than it was.

This is the truth: Software can be like this. It's best if upstream realizes that its value comes from downstream. When upstream does that, it tends to stay mindful not to shit in the river or on downstream devs simply trying to implement their code (which in turn grows the value of their network).

Well they are opensourcing the whole thing with an MIT license now. It's not a websocket of doom from the latest announcement.

Some of that $50,000 worth of work that you claim you only got paid $15,000 for the "total of four attempts to build the thing." might be able to be reused.

In your hand off to Fuzzy, there should be plenty of pre-written code to show for the work you did.

See:

"Developers will drive Steem innovation, and for that they need full access to the codebase. So now they have it!"

https://steemit.com/steemit/@steemitblog/steemd-is-now-completely-free-to-use-with-an-mit-license

See:

So surely, I won't be driving any innovations around here. My input is clearly not desired or valued.

Code (faddat)
github.com/faddat/ingestron
(The rest of my output deals with server configuration, which I submitted detailed docs of to steemit.com and it would appear to me that steemit.com is now using those architecture docs. Their core thesis was: To enable web devs to really rock on steemit, steemit needs to have a "normal" web systems API on the back end. kinda like.....
https://github.com/steemit/sbds

Except I'd never mess about with Python. It's a freaking hellshow and is likely to create as many problems as it solves.

Code (Tuan)
https://gitlab.com/baabeetaa/steemdfeed

Oh, @intelliguy-- most of that $50k is in tearing-out-my-hair-bullshit-fees. If I'd known what I was getting into I would have declined the gig and remained friends with Fuzzy. I had no idea that stinc was overstating the reliability of their API/RPC, or that docs were non-existent or wrong. Or that Stinc just... "wouldn't recognize" obvious, repeatable, demostrable problems with its software.

I was happy to work for fuz at "friend discount" prices. He's a really great person, after all.

I think.

And if he is wondering when I'll just be done, well, there are two possiblities:

  • He doesn't realize the truth and his name and my whole experience with steemit.com and him will be tainted by this, but I can't do anything about it.
  • He does realize the truth.

Come back as a new alias without your photo. Like the other 300 altcoin devs who kept releasing the same variations of various coins over the last 3 years.

Just in your commits, use plain language without any emotion tied to it, and no one would know it's you.

Good code, is good code, and it doesn't matter who writes it.

P.S. Check out https://github.com/xeroc/piston-lib

Python Library for Steem

Last commit was 7 days ago with a version bump

The command line tool that is bundled with this package is called piston and helps you

browse,
read,
post,
comment, and
deal with your funds

By the way, on one of your "4 attempts", you might have tried just talking to the steemit website like a basic web browser through HTML and cookies.. the site can be parsed. It's rudementary, but with tweaks it could have worked.

How many people did that with coinmarketcap.com, pulling data, or even blockchain.info who are novice programmers. It's awful, but it could work...

I used piston.

There were issues, but not because of piston.

More recently, in an attempt to complete the same work (no joke like 2 weeks ago) myself and @l0k1 hit troubles caused by steemd with piston. Single-quotes in json, eh....?

Nice, steemd, nice.

Oh, and guess what dude, no fucking way I'm going to use a fake identity to contribute to Stinc's repositories.

Well you know what Fuzzy wants. If it was me, I'd secretly code something up over the coming months, and deliver it anyway..

(Especially as piston gets better, and so does steemd)

If I was this knee deep, and it bugged me. I'd just do it. If he didn't want to take it after it ran... well.. I still gave him a workable product in the end. That's the only thing that would make me feel better.

Each and everyday people are doing amazing things... just look at esteem. The guy is doing all of that... unpaid... luckily he can do it without money.

You'll find yourself with spare time here and there. Make it a mission. Fuzzy will say don't bother. But if you showed him a sexy website that actually works, with the specs that he wanted..

Time could create some healing and this will end nicely.

I have to qualify that it was my error with the incorrect JSON output, by using a python-language-parser.

Also, steemd is a mess of spaghetti and cryptic and complex c++. They may have finally open sourced the code, but i doubt anyone wants to take on the burden of management. It was designed as a monolithic block, as is often the case in hurried code development whipped by corporate bosses.

In fact, I was rather shocked to learn that in the early days after Golos started up, that golos and steem nodes were broadcasting invalid transactions to each other. This is a nightmare of bad programming practises.

They didn't need to open source it. Nobody wants this shit. They need to deliver on the promise of modularising it and turning it into a fabric instead of a monolithic chain.