From @FictionPress
"We are experiencing packet loss due to upstream provider. All services are in degraded state pending a fix from our upstream service provider. We will keep everyone updated. Services will be slow or inaccessible in the meantime."
408, 503, and 504 errors everywhere. The only thing that seems to be working for me is its main page, but other people have said that not even that is loading.
Oh, apparently today they rolled out a change in how the series listings are done. The new default is alphabetical. Once you pick a series to look at, you'll see the normal thing of recently updated stuff on down. If you wanted it in alphabetical order instead of by number of fics, then you have a simpler time. Anyone else is going to have to narrow stuff down by the letter when doing this.
Looks like ffnet pruned everyone's favorites to 500, just as well some people's favorites was getting ridiculous to load especially with some of the scripts I run.
Looks like ffnet pruned everyone's favorites to 500, just as well some people's favorites was getting ridiculous to load especially with some of the scripts I run.
Good thing I do not use FF.NET favorite system... limiting me to 500 would erase some 11,000 of my favorites, though admittedly that is all favorites, not FF.NET ones, for FF.NET, I only have 5,851 story and author links pointing to the FF.NET site.
Looks like ffnet pruned everyone's favorites to 500, just as well some people's favorites was getting ridiculous to load especially with some of the scripts I run.
According to their Twitter feed, this is a temporary measure while they fix a problem with profiles on the desktop site. The full lists are still there for the mobile version and the app, and eventually they'll be restored for the website, as well.
Well, I'm not in Europe, but no, I was not so much interested due to a belief it was a virus or such, but instead was more curious if it was across browsers... since I can see it in Lunascape in all modes (Gecko/FF, Trident/IE, and Webkit), and can see it in Edge, I'm assuming everyone is getting it.
While I can understand FF.NET doing it I guess, seems odd to me that after all these years they only start now.