SocialHub.activitypub.rocks has been down for over a week with no resolution in sight. For the history of FEP to be preserved, these links would also need to be archived.
@realaravinth wrote a script that crawls a forum, which was used to archive Feneas forum for ForgeFed discussion. When SocialHub is up it could be run on it.
There's also likely an robots.txt admin setting to determine whether crawlers are allowed to crawl, that may also affect how archive.org operates on the forum.
Thanks for the ping @circlebuilder :)
The script was meant to archive only the forgefed tag/topic but if required and with SocialHub admin's consent, I could modify it to periodically archive the whole SocialHub to archive.org.
There's also likely an robots.txt admin setting to determine whether crawlers are allowed to crawl, that may also affect how archive.org operates on the forum.
I took a look at it, it seems to be crawler-friendly.
Note that Hellekin together with Hetzner provider managed to trace down the issue (likely due to new IPv6 functionality introduced at Hetzner), and since then the SocialHub is working alright again.
If it is crawler-friendly, then consent is not needed, the content is out there. For instance Sebastian found topics in Google Cache while the site was down. Archive.org doesn't archive in a manner that is browse-able. But we may ask anyway.
Being mindful of scope for this issue, I think it's most important to archive FEP discussion threads when or after they've gone FINAL.
Agree. That should really be part of the standard procedure of FEP finalization. Maybe even by checking in the entire discussion(s) as markdown docs to the FEP. I requested a markdown view of an entire topic which is now implemented.
But before FINAL when SocialHub is down all the 'prep work' is inaccessible. Now the outage was long, but fixed. Could as well have been permanent.
Just used Archive.org to save the discussion for FEP-8fcf and since it was a long one I had to save it twice, once from the beginning of the thread and once from the end.
Added links to archived discussion for each of FEP-8fcf and FEP-400e so this practice is current now. What's still left is to add this practice to FEP-ae4d.
The final FEPs are published to https://socialhub.activitypub.rocks/pub/fep-f6f8-title-of-the-fep and indexed at https://socialhub.activitypub.rocks/pub/fediverse-enhancement-proposals
So this is probably what you want to track for changes.
The final FEPs are published to
https://socialhub.activitypub.rocks/pub/fep-f6f8-title-of-the-fepand indexed at https://socialhub.activitypub.rocks/pub/fediverse-enhancement-proposalsSo this is probably what you want to track for changes.
Is that page generated automatically or how will it get updated?
Currently it's updated manually, but see the following post for ways to automate:
https://socialhub.activitypub.rocks/t/standards-fep-forum-permissions/2677/7?u=how
This was resolved with #48
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?