jamiew / helium-discord-bot

Helium hotspot stats & leaderboards for your Discord server
13 stars 3 forks source link

Add `hotspot stats [magic-animal-name]` command that shows individual stats #24

Open jamiew opened 3 years ago

jamiew commented 3 years ago

Ideally would just pull the 7d and 30d stats from the Hotspot Details dashboard

Could also re-use hotspot stats like hotspot stats slow-burgundy-mandrillo

slow-burgundy-mandrill
11Kj6LV5M51PzPjBVbtgESL625SsrzdPoi59PDPQ2xdeozNuRuq

passed witnesses (1d/7d/30d): 2 / 15 / 60
failed witnesses (1d/7d/30d): 1 / 4 / 12
passed beacons (1d/7d/30d): 2 / 11 / 40
failed beacons (1d/7d/30d): 1 / 8 / 9
challenges constructed (1d/7d/30d): 5 / 35 / 150

Something like that

Combined with hotspot activity you can get a good picture of a hotspot right in Discord!

Could even link to Explorer, DeWi ETL, Helium.place, Hotspotty, etc too

ch40s commented 2 years ago

+1 for this one

ch40s commented 2 years ago

It would be awesome to have such a stats command (or a new "status" one) for individual hotspots accepting (names or addresses) showing a summary like:

HOTSPOT NAME / HNT(24H) / REWARD-SCALE / HOTSPOT-STATUS (Online/Offline/etc.) / RELAYED (True/False) / LISTEN-ADDRESS / PORT-OPEN (True/False)

jamiew commented 2 years ago

There is the “hotspot activity” conmand but that is different. Love to have one like this too! And thank you for the other PR will review and merge asap. Away this weekend :) -- @jamiew https://twitter.com/jamiew | https://jamiedubs.com https://www.jamiedubs.com/

ch40s commented 2 years ago

Thanks @jamiew , I wish I was able to help you more with actual pull requests. In general, I think it's important to have the option to get this information (stats and analytics) for individual hotspots without having to add them to the database. That would be very useful for Discord communities where the members don't want to necessarily add their hotspots or their ownership information for their own reasons. They still need a quick way to troubleshoot a hotspot or check their current status. In addition to that, we don't flood the API when we only care about a single or a couple of hotspots. Now each time we hit the API for all the hotspots in the DB.