Disable multiple new notifications for series with multiple scan groups

[ArcanonArg]

An option so that every notification of a new chapter appears only ONCE in the follow page or groups the notifications of the same chapter would be nice, getting notifications of the same chapters 20 times just cause 20 groups decided to start doing the same series its obnoxious.

 

[comeonnow0]

The chapter 200 jamboree is such an edge case that doesn't seem like it's worth getting worked up over.

 

[BestBoy]

I'm pretty sure this has been rejected before.

 

[MrIncognito]

Occurrences like this Kaguya Singularity are not really all that common, and making this into an actual usable feature (rather than functioning exactly as requested here, which is... less than ideal for a few reasons) is somewhere between "complicated" and "unrealistic"

 

[bigtiddyoneesan]

Kaguya Singularity

This is the official name now.

@MrIncognito

rather than functioning exactly as requested here, which is... less than ideal for a few reasons

What do you think should be changed in OP's suggestion to improve it?

 

[MrIncognito]

@bigtiddyoneesan
First of all, it leads to the question of "when there's multiple options, what does it show?"
Does it show:
[ol]
[*]The first ever release (implied by suggestion)
[*]Releases from certain groups
[/ol]
If we go with option 1, it means that whoever gets the release out fastest wins, and then likely nobody is happy because scan groups will be upset that speedscanners essentially silence them and readers will be upset as everyone tries to compete to get something out the fastest and intentionally release shittier products. Additionally, we have to worry about how this interacts with the blocklist, which depends on how that is implemented.

If we go with option 2, that raises its own problems. This already assumes one additional database row per user per follow, not even accounting for the fact that your "preferred group" might eventually drop the series. Then what do you do about that? Will any further releases by whoever picks it up be hidden because it's waiting for that group? Do you default to option 1 as long as the "preferred group" hasn't released yet? In which case, people will be upset when they read that first one, and then their follows list hides that and shows them the chapter again as unread when the preferred group releases. Do you want to allow the user to make a "prioritized list" of preferred groups, which then increases the complexity and storage space used?

 

[bigtiddyoneesan]

@MrIncognito
Those are compelling reasons as to why this feature should stay rejected yeah. The only one I thought of before reading your post was the 'speedscan' one.

But to play devil's advocate, if this feature were to be optional, the speedscanners would only benefit from the small portion of users that actually turned this option on (assuming it's turned off by default, which it should be ofc) to begin with. By this, I mean that the users with this feature on most likely wouldn't care too much about translation quality, as long as the translation is acceptable enough to be on the site. As for the users with this option off (the majority), they would be more likely to wait for higher quality scans/translations, as they already do. The silencing of (usually) better translations would only occur for the small portion of users that turned on the option in the first place.

Then again, it would stand to reason that most users that read the option and its description wouldn't understand its implications, and possibly stunt their reading experience by turning it on after thinking "oh yeah that looks helpful".

But yeah, I was never in favor of this suggestion to begin with lol. Like you and comeonnow already said, this isn't a usual occurrence, which pretty much makes it a non-issue.