[Mainsite] Reader ignores blocked status

[aiMute]

This needs to be properly addressed. Not just a chrome bug, but reader lack of check functionality if next chapter is by blocked group. With shit group(s) around it's really annoying reading chapter thinking it's a normal release only for it to turn out a low quality snipe that can't even get gender right, let alone provide a proper translation.

 

[Beregorn]

Kind reminder that we still would like for this to be fixed

 

[Pyoro]

Indeed. It's still such an annoying niggle when reading something where a proper scanlation group is lagging behind some trashy MTL. E-v-e-r-y chapter. People can do and read what they want, but if it's blocked, it really should be blocked (or maybe at least some "click to confirm you want to proceed to blocked content"), that should be the point of the function ^^#

 

[HaikenEdge]

Nearly two years since the original posting, and this still hasn't been fixed.

 

[Quarnozian]

Some publishers have come up with an annoying new tactic...

<- Suddenly a sub-chapter that doesn't exist anywhere else.

Of course this causes the reader to throw you at their group (even though I have them blocked, and had to use incognito mode to take the screenshot)... and when you skip the chapter the reader REMAINS ON THEIR GROUP, so you have to open the side menu to get to the button to change groups back to the only non-offsite group.