I don't comment from my main account any more on account of hivewatchers.

I'll send you an upvote shortly. I had to investigate this, as this was strange and i never seen this in any sampling before. The bot is supposed to only downvote those who support the hivewatchers proposal [and give an upvote to those who support return proposal #0].

The official condenser api is fundamentally broken when looking up proposals by user support. When you search for a user individually, it will not just pull up that user but the next supporting user in alphabetical order, rendering it pretty useless without working around this bug.

This is the data it pulls out when your name is searched, in regard to hivewatchers.
...
{"id":152909,"proposal":{"creator":"hive
watchers","daily_pay":"95.000 HBD","end_date":"2026-07-31T00:00:00","id":293,"permlink":"the-hivewatchers-and-spaminator-operational-proposal-for-the-period-2024-2026","proposal_id":293,"receiver":"hivewatchers","start_date":"2024-02-01T00:00:00","status":"a
ctive","subject":"The Hivewatchers & Spaminator Operational Proposal for the Period 2024-2026","total_votes":"69109941774005079"},"voter":"jacobpeacock"},
...
So obviously you should not have been downvoted by the bot, which controls the curation trail of my main.

To work around this bug, the bot was to instead pull up some 400 active proposals at a time. Then jumping to the location in the data where the hivewatchers proposal is by string match, find the end of the hivewatcher's proposal index in the array, and check to ensure a voter match.

In investigating your case, it appears that the condenser isn't always pulling up hivewatchers in this data set of 400 (400 should be more than enough,considering the proposal id number goes up to about 330 (and only about 100 are active)-which suggest the condenser is even more bugged than I previously believed, as 400>100), particularly with your username. It can find it when it is set to 1000.

When it cannot find hivewatchers, the string index stays at the 0 index, makes a substring from 0 to the end of the first proposal. Whatever the case may be, whether it was in some header data, or whether your name was found in the first proposal in the list, it found you as a match, saw a profit, and proceeded to downvote in error.

I have adjusted a quick fix to change the 400 to 1000. And soon, I will make sure the result set from the condenser does indeed contain the hivewatcher's string ("the-hivewatchers-and-spaminator-operational-proposal-for-the-period-2024-2026") shortly.

upvote sent, but I see you muted me.

It is still not finding hivewatchers when 1000 records are pulled for some users, but the code successfully breaks (exit) and will soon be changed to skip.