|
Top-level
 @liaizon I’m not arguing against it, I just don’t think it’s something to automate. If you make it some joint space (GitHub repo, shared wiki), orgs can fill it out on their own or others can ask / fill out an about page. I’m pleased to see folks like Kissane tag CoSocial alongside SocialCoop — because it is the core of why we’re doing it. I’d love to help more co-ops take the step. 2 comments
@liaizon I’ve run large amounts of “fake APIs” on GitHub. Basically a set structure that then runs a GitHub Action to turn all the info into a single JSON file that can get published. Happy to talk more about this and get a sample going in the CoSocial repo. I’ll do an example I understand the nuances of “GH means only devs can update” hence also my wiki comment. |
Gregory's Server
@boris I am not proposing to automate adding this information. The idea I was that if there was a way for instances to semantically describe their own structure so that information could be easily showed to outside parties who are trying to understand what instances are run responsibly and fairly and have the chance at longevity. Personally I think github is the worst place to have to go for this info. Wikis are great but unless every instance uses the same wiki we are back to the same problem