In my last post, I accused the Hive dev community of gatekeeping.
I realise this might not be intentional behavior from all parties.
It sure pisses me off though, so here's an example:
Further up in that conversation, @sorin.cristescu had trouble changing the authorities/permissions of a Hive account to multi-sig/weighted permissions.
@pharesim and @mahdiyari stepped in to help.
Since I mention them here it's only fair to emphazise that those 2 are actually helpful and knowledgable.
First they were unsure, if the order of the accounts should be alphabetical.
🙄
Last time I checked, JSON (or JS dictionaries for that matter) are not ordered.
I am just a hobbyist, but I know that much.
(Which btw doesn't mean that it was implemented correctly, but that would be against convention at the very least and poor code imo)
Anyways
They somehow solved the issues.
From their public conversation I can't quite figure it out...
@pharesim provided a custom script powered by beem.
Now that's all fine and I am happy that Sorin resolved the problems alright.
My Issue
My issue here is that this happened christmas last year.
And this has happened before. Many times.
And when you go check the documentation you get this:
'Just use beem'
I have crawled beem so many times already to look up how @holger80 solved it, to basically reverse engineer what the correct call should look like.
What the fuck do I need the HIVE docs for then?
Also: holger (bless him) tried to simplify things by converting strings to ints (and back) behind the scenes for our convenience. However, that's not great if you need to figure out the underlying API calls.
API Docs
This is the actual call and the API definitions.
account_auths is a dictionary.
THANKS!
Is it Lazyness?
You'd think, that someone takes this and updates the docs, maybe?
So the next person doesn't have to go through the same shit again?
Just fucking paste in an example auths dict, with example weights.
Warn ppl not to brick their auths, perhaps?
This is critical shit, especially when you change owner auths.
That I even have to type this out and explain pisses me off so hard...
Why don't you do it?
- I am not getting paid
(while others make $$) - My contributions get ignored
(Until I make a mistake, then they'll all come) - I still can't be fucked to use git - I personally never use it, as it annoys me.
- A good API should respond with a descriptive error message, which points out the issue.
(I used OpenAI API and could just try JSONs out and the API would point out the error and even provide links to examples - 😮 Imagine that!)
Actually, a good API can document itself ('help?')
9 years
And you'd think someone steps up to fix at least the docs...
Yet, we have a bunch of imposters labeling themselves as developer in that discord.
I know some of them couldn't even code 'hello world!' without chatGPT.
Can we at this low point (price) please start weeding out some trash, while we are at it?
Ask your favorite witness to step up and fix the docs - See how that works out!
https://api.syncad.com/
APIs have been getting documented recently and you can say all of them are now documented on the API side. The specific problem you posted as an example is a rare case. It is not fair to say everything is like that. And that specific problem could be solved by hived returning proper error messages.
So, API docs have gotten better and they are in a very good shape compared to what we had. That website, https://developers.hive.io, is a bit of a mess and it always needed work. And it has been getting some work done by blocktrades team.
Ranting to your rant about weeding out people.
We don't get new users. We have not been getting new users for years now. Our "developer user base" has been the same people for years. The discord you posted is an example of that. It is shrinking and not expanding. The owner of that particular discord has left Hive years ago. The other developer space, a mattermost server managed by guitlyparties, has not been growing either.
The solution is and has always been to get more users. More users will solve majority of our problems.
When I wanted to use the Hive APIs, there was no documentation at all and nowhere to get help. Hive is so great n all, you would think there would have been plenty of help guides and sample scripts people could just adjust as needed for most basic tasks. Hive is just not popular enough i guess.
There always was documentation, but the name Hive makes it hard to find them with online search. Because the name is incredibly bad.
I dont think there was, especially for Beem.
beem was always well documented. That's how I taught myself all I know about this chain.
I've complained about its design a lot, but not the code or the docs.