Windows200000/TwitchDropsMiner-updated

Maybe another hash has to be changed

woctezuma opened this issue · 3 comments

woctezuma commented

Problem

No response

Suggestion(s)

I have noticed a second hash was changed in the original repository. See the following commit:

To be compared to the current state of your repository:

TwitchDropsMiner-updated/constants.py

Lines 302 to 307 in 69d73be

# returns all available campaigns
"Campaigns": GQLOperation(
"ViewerDropsDashboard",
"8d5d9b5e3f088f9d1ff39eb2caab11f7a4cf7a3353da9ce82b5778226ff37268",
# no variables needed
),

Additional notes

I have no idea whether this is important, but I mention it in case it is needed. For reference, you both changed another hash:

TwitchDropsMiner-updated/constants.py

Lines 308 to 316 in 69d73be

# returns extended information about a particular campaign
"CampaignDetails": GQLOperation(
"DropCampaignDetails",
"e7acdecb05429a62f5984bdcb27ee938ae20543579bf73c3ae44e7c822bc4f54",
variables={
"channelLogin": ..., # user login
"dropID": ..., # campaign ID
},
),

Windows200000 commented

It seems to run fine both with the new and the old one. I put it into in-dev for now and will speed up an update to master if I get crash reports.
6423220

Thanks for the help!

  • 👍1
woctezuma commented

After reading this message, I realize the hash mentioned above may not have to be updated:

Indeed, it seems only one hash needed to be changed, and the hash mentioned above was a failed first attempt.

We will see.

Windows200000 commented

After reading this message, I realize the hash mentioned above may not have to be updated:

Indeed, it seems only one hash needed to be changed, and the hash mentioned above was a failed first attempt.

We will see.

The fact he got a new hash there still means this one is more likely to be supported, but as you said, it might also be fine.

  • 👍1