RE: Zensur auf Hive?

avatar

You are viewing a single comment's thread:

Peakd is at least honest with regard to the actual reputation of @wochenblick in contrast to, for example, hive.blog, the posts are still not displayed directly and with a negative reputation (ON THE PROFILE!), In the view under #deutsch they are therefore omitted completely ... and at the latest then it definitely starts with the censorship / targeted defamation.

I'm aware of one recently reported problem with reputation calculations for a user (reported yesterday), which we plan to look at on Monday (most of our development team was off for Corpus Christi holiday). This is an API server-level issue, not a web site issue. It's possible this could lead to a discrepancy in reputation calculations on sites using different APIs at this moment, or if different sites were making different API calls to get the reputation. In the normal course of things, the API servers all function the same nowadays, however. Global muting lists have been removed from API node servers and replaced by decentralized lists which are "opt-in" rather than enforced on users.

deutsch
0
0
0.000
5 comments
avatar

Thanks for informing us :)!
But i still got some open questions about this:

Is @wochenblick the one reported on or was there another account?
I could not find ANY other examples this happened.

Are you absolutely sure, that no one could have flipped a switch in any way, that has caused this problem somehow on different API´s? The timing this happened (including some taken actions) is more than giving this a fishy smell?
And if so, just this one account??

The problem seems to be solved now, your API is also back working fine with this one example i can to do tests on. @pharesim ´s API is not working at all and @roelandp ´s is producing errors, but at all: any information for the public about what caused this problem? Different versions, old "blacklist implementation" on old versions running or what ever? I can´t think of a misscalculation causing this for just some API´s without running different versions or something to be honest?
https://beacon.peakd.com/ is sadly not showing any versions api´s are running.

Would be very nice to get detailed input on what exactly caused this problem as soon as it´s clear, cause i might have to say sorry for some things ;).

0
0
0.000
Reply
avatar

Are you absolutely sure, that no one could have flipped a switch in any way, that has caused this problem somehow on different API´s? The timing this happened (including some taken actions) is more than giving this a fishy smell?

Yes, I'm sure no such switch has been flipped on hive.blog web site or api.hive.blog. BlockTrades operates those two sites, and for security reasons, very few personnel have access to those sites.

For other API nodes, it is up to each operator, of course, but I'm pretty sure none of the API node operators have targeted any users for censorship. And I'm also sure that all the Hive API node operators that I'm aware of use the new code where the centralized blacklists have been removed in favor of decentralized, opt-in lists. So it would require some amount of coding work by the API node operator to block a user in this way.

Condenser itself (the code used for hive.blog) still does have a centralized blacklist, because individual operators may need to hide specific articles to comply with legal regulations (GDPR, DCMA notices, etc), although instances of such blocking are incredibly rare.

Several API nodes are in the process of updating to the new version of hivemind that we just released, which could explain down time/errors on some nodes. And as mentioned already, we do know of one reputation error in the new code that is being worked on now. So we'll probably need to do a new round of upgrades later this week.

0
0
0.000
Reply
avatar

As for details about the issue, I just finished chatting with primary developer for peakd, and he told me this:

Header is computed from
curl -s --data '{"id":4,"jsonrpc":"2.0","method":"call","params":["database_api","get_accounts",[["wochenblick"]]]}' https://api.hive.blog
11:12 AM
Posts is from
curl -s --data '{"id":5,"jsonrpc":"2.0","method":"bridge.get_account_posts","params":{"sort":"blog","account":"wochenblick","limit":1,"start_author":null,"start_permlink":null,"observer":"asgarth-dev"}}' https://api.hive.blog
Seems to be a different value at the API level

The actual issue is that the first call goes to hived (blockchain node), which has correct value, and the second call goes to hivemind (which has the bug that causes it to compute wrong value).

This has been confirmed by our hivemind tech lead, wrona, who reports:

dan
9:45 AM
Ok, so the weird thing for me is that peakd.com reports 60 rep for this user on profile, but 2 for articles. Both peakd.com and condenser are using api.hive.blog. So it seems like peakd uses different source for this data in it's profile.
So both report 2 for rep beside the articles
This may just be a problem with peakd. I'll ask peakd guys about it.
wrona
10:03 AM
yes seems so. api.hive.blog returns negative rep. for wochenblick where hive-2 instance returns: 9863690427572 (hived 9859483834254)
dan
11:17 AM
yep, I just confirmed that peakd uses two different API calls (one to hivemind, one to hived), and that's why they show the two separate values.
0
0
0.000
Reply
avatar

Thanks for solving this including all necessary information needed to follow up, guess i owe someone a sorry now :).

Keep up the good work and enjoy your day :)!

0
0
0.000
Reply