Condenser provides 'higher level' information. The further you deviate from the core functions of Hive, the more complicated (and unreliable) it gets.
Reputation for example is abstracted. It never was a core feature of Hive, but was built on top of it.
And here is when I found that my reputation hasn't changed with the last 100 posts I published 😂
Whenever you get a vote (up or down) it affects your reputation.
So yeah, something went wrong.
I am not familiar with all calls in the documentation.
I have never touched get_discussions_by_author_before_date
There's also no guarantee that the calls are properly documented and I raged about that a while ago:
I have since been told that the documentation is incomplete on purpose, because the higher level (hivemind) stuff, will be abandoned in the future in favor of a HAF infrastructure.
https://peakd.com/dev/@felixxx/hive-api-reference-incomplete
I am pretty sure there is no extra table that saves how high your reputation was at a given time. That would be a very long database table that makes an entry after every vote you ever received and that for every user... too much data for too little benefit...
I could look into the above call more closely, depending on how important it is for you.
Generally, I'd say: stay away from get_discussion and anything reputation for now. They are soft.
block_api, account_api are core features and the most reliable...
What an unusual purpose LOL also considering that I guess that this situation is going on since a long time, and this doesn't sound like something which could help increase adoption...
Don't worry, I chose that key only to see if was able to access it, but I could have chosen a different one! oc I had to choose one that wasn't working properly among all the available keys 🤣
Gotcha!
Well...
I actually went ahead an wrote a whole post about it...
Already seen and upvoted! :) Happy to see you posting more snippets and useful tips! As soon as I can I will read again it and use it to make more progress with my coding.