Since PB users’ calibrations are not yet good enough to see the future, you can easily avoid MoR spoilers by subscribing to the email or RSS alerts for new chapters & reading them as appropriate.
This is the obvious solution, but I want to reread what I’ve currently read, and have some time to think about the story and try creating an accurate causal model of events and such in the story as I read new!Adele material (Eliezer says it’s supposed to be a solvable puzzle). I don’t have time to do this right now, so in the meantime, I try to avoid spoilers.
I used feed43 to create an rss feed out of recent predictions. Then I used feedrinse to filter out references to hpmor resulting in a safe feed. (Update: chaining unreliable services makes something even less reliable.)
You could do the same for the pages of recently judged or future or users you follow. I think feedrinse offers to merge feeds (into a “channel”) before or after doing the filtering. But if you find someone new and just want to click on the username, you’ll leave the safe zone. Even if you see someone you have processed, the username will take you to the unsafe page.
A better solution would be to write a greasemonkey script that modified each predictionbook page as you look at it.
The final feedrinse feed works in a couple of my browsers, but not chrome. Probably sending it through feedburner would fix it.
The regexp I used in feedrinse was /hp.?mor/ It is case insensitive and manages to eliminate “HP MoR:”, “[HPMOR]”, etc. It won’t work if they spell it out, or just predict “Harry is orange” without indicating which story they’re predicting about. In that case, someone will probably leave a hpmor comment, but this doesn’t see such comments.
Is there a good way to avoid HPMOR spoilers on prediction book?
If you are skilled in the art of Ruby, then yes. Otherwise, maybe. People (myself included) have been complaining about the lack of tagging/sorting system on PB for quite some time, but so far, no one has played the hero.
Is there a good way to avoid HPMOR spoilers on prediction book?
Since PB users’ calibrations are not yet good enough to see the future, you can easily avoid MoR spoilers by subscribing to the email or RSS alerts for new chapters & reading them as appropriate.
This is the obvious solution, but I want to reread what I’ve currently read, and have some time to think about the story and try creating an accurate causal model of events and such in the story as I read new!Adele material (Eliezer says it’s supposed to be a solvable puzzle). I don’t have time to do this right now, so in the meantime, I try to avoid spoilers.
I used feed43 to create an rss feed out of recent predictions. Then I used feedrinse to filter out references to hpmor resulting in a safe feed. (Update: chaining unreliable services makes something even less reliable.)
You could do the same for the pages of recently judged or future or users you follow. I think feedrinse offers to merge feeds (into a “channel”) before or after doing the filtering. But if you find someone new and just want to click on the username, you’ll leave the safe zone. Even if you see someone you have processed, the username will take you to the unsafe page.
A better solution would be to write a greasemonkey script that modified each predictionbook page as you look at it.
The final feedrinse feed works in a couple of my browsers, but not chrome. Probably sending it through feedburner would fix it.
feed43 was finicky. The item search pattern was:
{_}
{_}{%}{%}
The regexp I used in feedrinse was /hp.?mor/
It is case insensitive and manages to eliminate “HP MoR:”, “[HPMOR]”, etc. It won’t work if they spell it out, or just predict “Harry is orange” without indicating which story they’re predicting about. In that case, someone will probably leave a hpmor comment, but this doesn’t see such comments.
If you are skilled in the art of Ruby, then yes. Otherwise, maybe. People (myself included) have been complaining about the lack of tagging/sorting system on PB for quite some time, but so far, no one has played the hero.