Damn. I’m really sorry this is happening 
Thank y’all for all your hard work.
It looks like joindiaspora.com was one of the largest instances according to Fediverse Observer. Such a shame it’s going to be shut down. At least the point of the Fediverse is that it’s all decentralized so if one server shuts down, the others won’t be affected.
I am afraid we are too late to salvage the ForgeFed forum discussion on Feneas. But thanks to @realaravinth the forum has been archived and can still be navigated somewhat at archive.org:
I also downloaded the posts using Discourse’s API, which can be used to replay posts and contents. It may not be as seamless Discourse’s migration implementation but it can be used to preserve threads.
A copy of the downloaded data is available on the forgefriends Nextclould instance.
Also for anyone who wants to save their own data: Go to Profile > Activity and select “Download all” to get a zip-archive of your content.
I’m still wondering why the lack of response.
Probably for the same reason the org is shutting down. Nobody has the time or energy to do it.
Welcome to SocialHub @Nyla_Smokeyface
It’s an instance of Diaspora, which only federates via the Diaspora protocol. It’s disappearance would be sad, but it’s already not reachable by most fediverse users.
Reading between the lines, Feneas folks might be talking to the user community of JoinDiaspora to see whether there are volunteers to take over hosting exenses and sysadmin/ podmin duties.
Yes, this does make the 'verse much more resilient than centralized services. But users of others services can be affected by server death, things like losing contact with people, and threads breaking due to contributing posts being on the dead server.
Was trying to access talk.feneas.org/t/81, and saw that it’s now 404. Without --insecure, I even get an SSL expiration notice from curl:
curl https://feneas.org
curl: (60) SSL certificate problem: self-signed certificate
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the webpage mentioned above.
curl --insecure -I https://talk.feneas.org
curl: (6) Could not resolve host: talk.feneas.org
…Oh. At archive.org. Solely realised after writing this.