Fantastic work, mate :) I will be looking into this (at some point) to try and get a grip on what % of people have auths in steem auto, and see if their voting behaviour is influenced by that, or other auths they have.
I think this will lead to some very interesting analytical opportunities :)
I also have written one that does a combination of both, for every user on hive, I haven't run it yet as I know it will take some time, but the skeleton is there to get a complete census of last "posting" activity, last activity in general, and authorities given.
Awesome. We have so much information on the dusty corners of our chain that a lot of people don't really look at. My mind is too analytical to not look in those places. :D
Once we know the scope of a group / audience / behaviour, we can then extrapolate to what percentage of staked HP is on auto pilot, and what percentage of staked HP appears to not be.
Although, as I mentioned last time, there's a gap where the authority is not granted, but the voting is still automated by a locally running script, or something hosted on other infrastructure - so it won't be a complete definition of the sizes, but - a rudimentary, (albeit unreliable) baseline of the manual curation % on chain - both by users and HP :)
oh, that's smart, i think i'll have it add the HP at time of scan to the db too, might make some of it a bit easier, select sum(vests) and a JOIN from authority where authority_granted = "steemauto" would do 90% of the work.
Yeah, alternatively, it could be an inner join on the extracted list after the fact. Lots of ways to do it, depends on what has the least computational load, much of a muchness at the end of the day, given the large amount of accounts.
The problem with my thoughts is they are often far too ambitious for my current skills, (or my hardware! - like my recent post about AI detection using a local llm) so I am constantly trying to expand said skills :D