FanFiction.NET issues
- Thread starter PCHeintz72
- Start date
That doesn't stop the interstitals. You get a blank page with a link to go straight to the story, but it's still something that has to be interacted with to actually see the content.
I've taken to hacking the cookie expiration. fanfiction.net sets a cookie named "adblocker" with a value of "1" when you select the one-day adblock. This cookie is set to expire in one day, after which you get ads again. So, simply modify the cookie expiration date to something much farther into the future (say a few years ahead). Firefox and Opera are both quite amenable to this; it's possible with third-party apps in IE, and outright impossible in Chrome with the current version.
I've taken to hacking the cookie expiration. fanfiction.net sets a cookie named "adblocker" with a value of "1" when you select the one-day adblock. This cookie is set to expire in one day, after which you get ads again. So, simply modify the cookie expiration date to something much farther into the future (say a few years ahead). Firefox and Opera are both quite amenable to this; it's possible with third-party apps in IE, and outright impossible in Chrome with the current version.
The main difference seems to be that I don't have a fanfiction.net account and don't plan on getting one. Non-members get interstitals (at least from the U.S. mirror), while members "only" get banner and Flash ads. With interstitals, the ad is blocked by ABP, but you still have to click through to get to the story.
My own solution to ads has been NoScript + RequestPolicy -- text ads come through fine (a reward for sites that use minimal advertising), but Flash and DHTML monstrosities are killed, along with any scripting requests from unknown servers (removing a significant vector for Flash and Acrobat exploits). It's a lot more work to set up than ABP, though, as it's a pair of whitelists rather than a blacklist.
My own solution to ads has been NoScript + RequestPolicy -- text ads come through fine (a reward for sites that use minimal advertising), but Flash and DHTML monstrosities are killed, along with any scripting requests from unknown servers (removing a significant vector for Flash and Acrobat exploits). It's a lot more work to set up than ABP, though, as it's a pair of whitelists rather than a blacklist.
Four days worth of updates are not appearing in my favorites, my profile page is not loading, the individual story sections won't load (most of the time) and general shittyness seems to be what is happening to me.
Edit: Emptying the cache and repeated page refreshes help to clear up most of the problems.
Edit: Emptying the cache and repeated page refreshes help to clear up most of the problems.
I was going to say... I've been pretty much fine... in the last several days only FF.NET issue was 2 stories I had to use easy workarounds to get at the newest chapters to appear for.
On rare occasions. That happens, and has been for years. I see it myself because the feeds update faster than the site, and that has nearly always been the case.
I've had no FanFiction.NET RSS/ATOM feed problems. Category feeds have been getting updates for practically every category I monitor for FF.NET.
No problems with caches, and a couple days ago I left a review.
I've noticed a slightly higher than normal number of reviews for older stories, mostly people asking where updates are. But that tends to fluctuate so did not think much of it.
Can't help with alert system or C2 issues though, I have none of either.
On rare occasions. That happens, and has been for years. I see it myself because the feeds update faster than the site, and that has nearly always been the case.
I've had no FanFiction.NET RSS/ATOM feed problems. Category feeds have been getting updates for practically every category I monitor for FF.NET.
No problems with caches, and a couple days ago I left a review.
I've noticed a slightly higher than normal number of reviews for older stories, mostly people asking where updates are. But that tends to fluctuate so did not think much of it.
Can't help with alert system or C2 issues though, I have none of either.
I find the http://b.fanfiction.net/atom/... feeds tend to "stick" more than the http://www.fanfiction.net/atom/... feeds. And adding or removing a trailing '/' also can change the result.
From multipule computers with the same IP and no caching between them.
From multipule computers with the same IP and no caching between them.
Huh... what are you using for reading the feeds?
I use SharpReader, while the interface is a bit spartan... I like it like that, and practically never have a feed issue. It has full support for RSS/ATOM feeds. Some feed readers do not properly report updated feeds, only new feeds.
Also... if you add or remove the trailing '/' (from links) and especially '\' (from folders) inside some feed readers, and import or export by OPML files, I find that can alter how the feeds are imported. I've noticed this with the old SauceReader (no longer available) and FeedBandit (a sort of unofficial Feed Reader originally made as a Microsoft demonstration product that has been taken much further).
I import my feeds from generated OPML files into all my systems, which while not the same IP, is from the same location on the same internet providor.
I use SharpReader, while the interface is a bit spartan... I like it like that, and practically never have a feed issue. It has full support for RSS/ATOM feeds. Some feed readers do not properly report updated feeds, only new feeds.
Also... if you add or remove the trailing '/' (from links) and especially '\' (from folders) inside some feed readers, and import or export by OPML files, I find that can alter how the feeds are imported. I've noticed this with the old SauceReader (no longer available) and FeedBandit (a sort of unofficial Feed Reader originally made as a Microsoft demonstration product that has been taken much further).
I import my feeds from generated OPML files into all my systems, which while not the same IP, is from the same location on the same internet providor.
What... I deliberately blow that info awy as often as I can.
I on a near daily basis go out of my way to delete all cookies and temp files, blowing out all my logins and saved passwords and any potential credit or financial info. Assuming they can get to them in the first place of course.
So I am always relogging in on the sites I go to.
Heck... I did so this morning.
I'm afraid anyone hacking my cookies or history really will not be getting all that much out of them.
I even occasionally, using a program I wrote, scrub my favorites files of all extranious info, as potentially they can get hacked as well, and in many cases they contain info they do not need to have, such as tracking info on how often used or accessed, even advertizing is sometimes dumped into them.
I on a near daily basis go out of my way to delete all cookies and temp files, blowing out all my logins and saved passwords and any potential credit or financial info. Assuming they can get to them in the first place of course.
So I am always relogging in on the sites I go to.
Heck... I did so this morning.
I'm afraid anyone hacking my cookies or history really will not be getting all that much out of them.
I even occasionally, using a program I wrote, scrub my favorites files of all extranious info, as potentially they can get hacked as well, and in many cases they contain info they do not need to have, such as tracking info on how often used or accessed, even advertizing is sometimes dumped into them.