Friendica.World status, support and issues

Improvements in uptime were observed yesterday and today. I definitely hope uptime will prevail.

I can still read a handful of articles in the local feed on Raccoon, so someone must have access. However, the web interface has been totally inaccessible for at least the last week (and sporadically available for months before that).

@n816Life@lemmy.world

For me, Friendica is and has been partially up. I even posted something on my own profile Saturday and it managed to federate to other Fediverse platforms (Mastodon and Calckey).

For me, only specific functionalities aren't working, such as searching for federated content (such as this thread on Lemmy, for which Friendica returns "No result"), as well as (and this seems to be the major bottleneck) the "/network" tab.

The "/network" tab ("My friend's conversations") will definitely return Gateway Timeout. It's an alias to the index page (i.e. the page loaded when friendica.world is accessed via typing friendica.world on the browser and hitting enter), which will also return Gateway Timeout.

Being aware of this, my approach has been accessing Friendica.World through direct URLs for parts outside the "My Friend's conversations" tab (e.g. the direct link to my own /profile, or the direct link for DMs).

Sometimes it'll return "Service Unavailable" or something similar ("No server is available to handle the request"), to which I simply wait a bit then try to reload until it loads.

So, my advice is trying to:

1. access Friendica using direct URLs (e.g. your own profile's URL, someone else's contact URL, or friendica.world/message) instead of accessing the main.
2. avoid clicking/going to "My Friend's Conversations" as it'll certainly result in "Gateway Timeout"
3. when faced with "Service Unavailable", wait a few seconds and try to reload.
4. when needing to interact with posts outside Friendica (e.g. Lemmy), prefer using other platforms (e.g. I'm using Calckey to reply to your Lemmy thread) because the fetch of federated content isn't working properly.

I suspect that the downtime stems from the way the "My Friend's conversations" is requested by default whenever a Friendica.world user tries to access the instance's website, so this may keeping the server stuck in a bottleneck trying to pull federated content.