"Your binder is expired" - notification keeps respawning

TappedOut forum

Posted on Nov. 26, 2016, 8:50 a.m. by SadisticMystic

Every so often, I'll come here to check things out and see that I have one or more notifications in the top bar. Invariably, one of these will be a declaration that my binder has expired.

Beyond the question of why the hell a binder has an "expiration date" to begin with, its recurrence doesn't even make sense. "Yes, I already got your message that my binder already expired...last week...and the week before that...and the week before that...If it's supposedly already expired, how can it possibly expire again, and why do you need to update the date attached to the notification every single time?"

In this case, most of the cards I had in my binder, I had actually moved in the mean time over other channels. I tried deleting all the cards, but for some reason it's impossible to actually delete the binder itself, so that the site no longer sees anything that can expire, and I can stop getting crap-flooded with these utterly inane announcements.

Epochalyptik says... #2

The binders expire to prevent you from getting match notifications with users who haven't been online in years.

You get regular reminders so that in the event that you want to keep trading, you're aware that your binder is outdated and not generating matches.

November 26, 2016 12:25 p.m.

SadisticMystic says... #3

Is there supposed to be any way to actually remove the binder itself, or at least get a bit of server side logic to go "Hey, there are no cards in this binder, it cannot possibly matter when it was last updated because there are guaranteed to be exactly zero stale matches that the expiration is suppressing"?

November 26, 2016 2:42 p.m.

Epochalyptik says... #4

yeaGO, consider an option to set a binder to private (like decks) such that it wouldn't generate matches or expire? And to ignore empty binders?

November 26, 2016 6:31 p.m.

yeaGO says... #5

that option is already available, but i do think tuning of that notification is in order, too

November 27, 2016 12:54 a.m.

This discussion has been closed