|
Post by Miss Wings on Sept 2, 2015 5:10:52 GMT -5
arghhh!! when the hell will the site be up and running again? i haven't been able to log in for 2 days now and i'd just found an old story i wrote so i was going to update it.
|
|
|
Post by RandomPasserby on Sept 2, 2015 7:13:51 GMT -5
I haven't tried to log in, but I was very confused as to why nothing appears to have been updated since yesterday.
Especially since September 1st, 2015 is when the first of the epilogue-only Next Gen would have been going to Hogwarts (something I'm doing my best to ignore)
|
|
|
Post by Miss Wings on Sept 2, 2015 11:37:01 GMT -5
No one had been able to log in or update at all. Wonder if fanfic follows JK on twitter who posted about JSP starting Hogwarts and so they blocked access as a conspiracy?
|
|
|
Post by Kitty279 on Sept 2, 2015 12:15:18 GMT -5
Didn't notice that at first, as I mostly look at my favourites list and there it's normal that days go by without updates. Though I wondered about the lack of reviews for some. The last ones were from the 1st, and then now over the last hour or so some updates came. Strange thing is, when I checked the main HP page, the last update was from the 30th, nothing from the 1st. Then I tried the homepage again; tried two hours or so ago, and nothing. But now they have posted an update with an explanation, though it still doesn't say much. But I looked at the twitter account they lik to, too, and there was nothing, either. If the problems have been going on for so long, you'd think they say something *shakes head* What is that account good for, if not for that sort of explanation when FFN itself goes on strike?
|
|
|
Post by Miss Wings on Sept 2, 2015 14:47:03 GMT -5
on the fan made fanfic.net facebook page a lot of the writers were complaining but the creator of the page stressed that it wasn't a page sanction by .Net but at least it helped show i wasnt the only one having trouble.
|
|
|
Post by Kitty279 on Sept 3, 2015 0:06:46 GMT -5
You know, if that was a little private site, I'd even understand, as the owner would have more to do than just look after the website, but FFN has, to my knowledge, professional staff, so it's rather pathetic that they can't inform about problems in a timely manner. It's not been the first time, after all, and even if the website itself refuses to be updated, what is their Twitter account for? Even my favourite archive works faster - and the owner is very ill.
|
|
|
Post by RandomPasserby on Sept 3, 2015 12:12:52 GMT -5
The funny thing is, AO3 went down for two hours last night.
What happened. Five tweets updating progress while they tracked down a (volunteer) systems admin and got it fixed.
|
|
|
Post by Kitty279 on Sept 4, 2015 15:13:13 GMT -5
Figures - and confirms my opinion about FFN once again.
|
|
|
Post by Miss Wings on Oct 23, 2015 13:22:10 GMT -5
Once again- anyone having troubles with the site or is it my browser?
|
|
|
Post by Kitty279 on Oct 23, 2015 15:19:17 GMT -5
At the moment, the site seems to work normally for me. I had rather problems today morning, but that was 15 hours ago.
|
|
|
Post by Miss Wings on Oct 23, 2015 15:21:06 GMT -5
thanks kitty, it may be this windows 8. i've got a new laptop and certain things don't agree with windows 8 sadly.
|
|
|
Post by Kitty279 on Oct 23, 2015 15:29:16 GMT -5
There's a reason why I prefer my MacBook ... At work I have Windows 7, that was slow today, too.
Can you try alternate browsers? Between IE, Firefox and maybe Chrome, you might find a solution?
|
|
|
Post by Miss Wings on Oct 23, 2015 15:42:02 GMT -5
I mainly use IE for fanfiction as I can leave it a certain size- book size and chrome for everything else.
|
|
|
Post by Kitty279 on Oct 23, 2015 23:52:51 GMT -5
Maybe it's really the IE, then. Some years ago, I was using it at work, too, and frankly, in the end it got so bad some pages didn't even build up properly any more, FFN included. The whole layout of pages was shot to hell, no picture was more than a small box with a question mark etc. Finally complained and got Firefox, since then I only had problems when FFN itself was the problem.
|
|