Works for me on summit.
There is a sticky saying that the VPS is being throttled for a week. Meaning things will be slow.
Growing pains.
Try loading it and wait. If that doesn't work maybe try clearing your cache for summit.
Works for me on summit.
There is a sticky saying that the VPS is being throttled for a week. Meaning things will be slow.
Growing pains.
Try loading it and wait. If that doesn't work maybe try clearing your cache for summit.
Hola, they had an issue with bandwidth getting gobbled up, it's resolved but reliability won't return untill next week.
Their post about it is hosted on the service you can't see because it has the issue they are explaining in the post.
However if you search the fediverse for fedinsfw there are posts explaining this elsewhere.
It looks like it uses CloudFlare.
Testing it just now, I frequently get a CloudFlare timeout trying to talk to the remote box via Firefox -- it's the line between CloudFlare and the instance or the instance itself with issues. Via $ wget https://fedinsfw.app/, it eventually returns the root page, but takes a (highly variable) amount of time. Very slow, though, even then.
It'd probably give you better performance if you log into another instance as a home instance, and then browse whatever community you're interested in via that instance, plus taking load off fedinsfw.app, especially if that instance does image caching; that'll offload some of fedinsfw.app's bandwidth usage to other instances.
I am able to access it pretty consistently on interstellar and the web, but it is so slow it is not really a decent experience.
For me, connecting from the U.S., takes around 5 -- 15mins, but I can barely vote on anything.
I remember there is a post stating that LemmyNSFW is eating up the VPS resource, and the provider throttled the VPS, which also include FediNSFW. My guess is that after LemmyNSFW is down, people are eagar to backup that instance, which created an absurd amount of traffic.
They actually fixed the issue with their service, but the bandwidth alottment was already used up. Connection reliability should return to normal next week.
It's kinda funny not funny, the post explaining the issue is hosted on the instance you can't access because it has that issue.
all 9 comments