So, what would the most useful email/board notification be? When any region/game mode hits 5? Or should it be a bit earlier at 4?
@Schnorki
3454
replies
510994 views
Description
Description by
Bisu
Can be used to make Runewords:
I personally would like the notification for even a level 3, as in this inorganic setting it can jump to 6 really quickly.
I mean, a discord channel for each category (12 total) with a message for each change would be ideal (with some delay to deal with trolls), but don't know how difficult that would be to implement
I mean, a discord channel for each category (12 total) with a message for each change would be ideal (with some delay to deal with trolls), but don't know how difficult that would be to implement
5 can be too late for notification.
Do you have plan for some API or callback? I like to have overlay with status of 3 regions.
Do you have plan for some API or callback? I like to have overlay with status of 3 regions.
I came home twice and saw Asia 4/6. I turned on the PC and the game - little time passed before 6/6, probably no more than 30 minutes. But, I do not know how long 4/6 "hung" before that. 5/6 is clearly very late for notification.
+1 for 4/6 for sure and 3/6 optional if possible.
That's a tough one, mainly because the answer is different for everyone. Ideally, we'd have some sort of notifcation-subscription where everyone could subscribe with their own settings of interest.Teebling wrote: 2 years ago So, what would the most useful email/board notification be? When any region/game mode hits 5? Or should it be a bit earlier at 4?
@Schnorki
That means..
1) With their own game mode preferences (aka the same filtering they use to view the list itself) as I for example will never care about a classic or hardcore walk but would want to be notified about any significant progress in both, ladder and non-ladder and any region for softcore expansion.
2) With their own preference as to which level triggers an alert.
Looking at previous walks and how quick the "final push" can sometimes be, starting only at 5 is probably a bit late. If you wanted to generalize it, I would say notify at 4 and then again at 5. Or maybe even for every increase. Ultimately though, this also depends on the method of delivery. For example:
a) I get an email sent upon reaching stage 5. I won't see this until my mobile syncs and prompts me with the new email. That alone costs time again and by the time I see the notification, the walk may have already been triggered. I'd hence want to set this one to be delivered a stage earlier to create at least a bit more of a buffer.
b) The list overview here, that I keep open on my desktop, gets a built-in push alert that triggers a nice and loud alert noise when it hits 5. This one I would get instantly, assuming I'm at least at home, and it would hence not need as much buffer added as an email notification. (This would be my Dream by the way..just leave the list open and get an audio ding every time the stage increases for any of the modes/regions I am viewing, at any stage)
Do note that notifications being successful, rather than annoying, obviously depend on trolls being dealt with. And while that is already massively better than it was, some are still here. A couple ideas to deal with that:
- Add a "report" toggle flag to the status update so that when I correct it back from the troll's 5 to the actual 4, it can feed directly into a moderator list of known trolls to deal with, giving mods a view of who set the last different status (i.e. who trolled it), in turn just making troll-hammering easier. (make that toggle only available to high trust users/mods/contribs to avoid trolling of the anti-troll)
- Limit status updates to accounts with at least 1 trust and an age of at least a month. Not sure how much this would really do tbh, you'd have better Insight into that already from the troll logs but I wouldn't be surprised if remaining trolls are more with folks who just made a troll account.
- Only send notifications if the new status has either been confirmed (say submitted by 2-3 different users) or if it has lasted for more than 2 minutes (most troll submissions seem to be corrected within 30-45 seconds, sometimes a little over a minute).
That's my current thinking.
Seems all the changes are logged in DB so in that case there is possibility to automate the process. Just to make query to get the cases where the event state changed further and then was corrected backwards. Such we can get the id of the user that reported incorrect increment and then check for how often he did so in the past and give him temporary/permanent ban to use this feature.
Still there is a chance for mistake. So it would be great to consider also the experience on the forum and some other factors and not ban but give the warning for some instead.
Still there is a chance for mistake. So it would be great to consider also the experience on the forum and some other factors and not ban but give the warning for some instead.
Notification on Stage 4/6 is better - you have more time to prepare for DC.Teebling wrote: 2 years ago So, what would the most useful email/board notification be? When any region/game mode hits 5? Or should it be a bit earlier at 4?
@Schnorki
Clearly this could spiral into a huge amount of complexity with regards to what I actually have to code.
Current thinking is this:
Notifications only sent for progress updates that have been verified by at least one other reporter.
Name of last reporter shown so that mods can be notified of obvious troll accounts (we take care of the rest).
Notification sent at 3/6 (upcoming) and then at 5/6 (imminent).
Simple opt-in/opt-out UI for users for these notifications but no customisation of which mode sends notification.
Ability to select just board or just email notifications or both.
Removal of Non-Expansion modes completely to simplify and uncrowd the tracker.
Yes, I am building out an API that I will provide access for to selected devs who are making things like discord bots.
Bear in mind ladder launches very soon, I have to ruthlessly prioritise the most important things over nice-to-haves.
Current thinking is this:
Notifications only sent for progress updates that have been verified by at least one other reporter.
Name of last reporter shown so that mods can be notified of obvious troll accounts (we take care of the rest).
Notification sent at 3/6 (upcoming) and then at 5/6 (imminent).
Simple opt-in/opt-out UI for users for these notifications but no customisation of which mode sends notification.
Ability to select just board or just email notifications or both.
Removal of Non-Expansion modes completely to simplify and uncrowd the tracker.
Yes, I am building out an API that I will provide access for to selected devs who are making things like discord bots.
Bear in mind ladder launches very soon, I have to ruthlessly prioritise the most important things over nice-to-haves.
Someone just changed status from 2 to 3 to Asia. Corrected.
Sounds like a good enough starting point.Teebling wrote: 2 years ago Clearly this could spiral into a huge amount of complexity with regards to what I actually have to code.
Current thinking is this:
Notifications only sent for progress updates that have been verified by at least one other reporter.
Name of last reporter shown so that mods can be notified of obvious troll accounts (we take care of the rest).
Notification sent at 3/6 (upcoming) and then at 5/6 (imminent).
Simple opt-in/opt-out UI for users for these notifications but no customisation of which mode sends notification.
Ability to select just board or just email notifications or both.
Removal of Non-Expansion modes completely to simplify and uncrowd the tracker.
Yes, I am building out an API that I will provide access for to selected devs who are making things like discord bots.
Bear in mind ladder launches very soon, I have to ruthlessly prioritise the most important things over nice-to-haves.
My only comments in that context would be:
- Also add a notification for 4/6 (so 3/6, 4/6 and 5/6). 3/6 has repeatedly taken forever and 5/6 to 6/6 has gone VERY quickly more than once. So having 4/6 as a heads up in between, before the 5/6 that is sometimes just sprinted past would be quite helpful.
- Simple game mode selection/notification filtering would not be essential for a starting implementation but would be a very nice to have.
As for the API, I'm wondering whether it might make sense to just make that public? Mind you, I'm not saying that's something you need to do and support and I'd totally understand why you would want to limit it. I'm just curious (inspired by that video posted yesterday) as to how many folks actually built a scraper bot for the tracker page here which, if replaced with a streamlined API, would likely significantly reduce the traffic caused by them. It does feel like traffic/load has increased a fair bit lately (subjective, naturally) as site response hasn't been as reliably fluid at times as it was before the tracker.
Someone wrongfully updated Asia to 5/6. Corrected to 2/6.
Too bad, would've made my Asia-AFKing actually worth it..
First I want to say, thank you for all the work you've put into the tracker and the site in general.Teebling wrote: 2 years ago Clearly this could spiral into a huge amount of complexity with regards to what I actually have to code.
Current thinking is this:
Notifications only sent for progress updates that have been verified by at least one other reporter.
Name of last reporter shown so that mods can be notified of obvious troll accounts (we take care of the rest).
Notification sent at 3/6 (upcoming) and then at 5/6 (imminent).
Simple opt-in/opt-out UI for users for these notifications but no customisation of which mode sends notification.
Ability to select just board or just email notifications or both.
Removal of Non-Expansion modes completely to simplify and uncrowd the tracker.
Yes, I am building out an API that I will provide access for to selected devs who are making things like discord bots.
Bear in mind ladder launches very soon, I have to ruthlessly prioritise the most important things over nice-to-haves.
I work as an iOS / Android / Backend web developer. I would love to have an API that I could interact with to get status updates. Since my background is mobile, my idea would be to create an app that the user could configure preferences for region, progress level, etc to set off notifications. It would be an interesting project that would give me a chance to work with some of the features I don't use much at work. That said, I'm not sure when I would find the time to get it done.
I understand the more complex this becomes the more work it requires to set up and maintain. I've seen feature creep double the number of hours in a project. I feel your pain with this coming week essentially being crunch time before ladder starts.
I don't think Blizzard wants to provide us such API.Stets wrote: 2 years ago I would love to have an API that I could interact with to get status updates
We can update the status manually, just give the right to some trusted persons.
pm me here (d2. Io) for trade
Pretty sure Stets meant an API that I build - one that spits out JSON values for the progress tracker on the site, not Blizzard (who seem to not be interested in building D2R APIs at all).mockingbirdreal wrote: 2 years agoI don't think Blizzard wants to provide us such API.Stets wrote: 2 years ago I would love to have an API that I could interact with to get status updates
We can update the status manually, just give the right to some trusted persons.
Lazy day today. Does it means that merchants sold their sojs before ladder simply, and frequency of walks will be much lower?
To be fair, the last walk was a measly 10 hours ago, give or take. Farmers need sleep, too.Szambodiver wrote: 2 years agoLazy day today. Does it means that merchants sold their sojs before ladder simply, and frequency of walks will be much lower?
You are right, I’m just frustrated due to being logout…
Similar pages
Advertisment
Hide ads
Greetings stranger!
You don't appear to be logged in...
gensymmed
Pai
SchnorkiNo matches
Teebling
6853Admin