GitHub is a git hosting provider, but it also has its own service software for all the peripherals - organizations, issues, pull requests, all the user account management stuff, etc. AFAIK those parts are mostly/all proprietary.
GitHub is a git hosting provider, but it also has its own service software for all the peripherals - organizations, issues, pull requests, all the user account management stuff, etc. AFAIK those parts are mostly/all proprietary.
I just went through this exact process (not for the first time) two weeks ago with a bug in the golang standard library. Fun times. Deep in the dependency stack of a container build my team doesn’t own so who knows when I’ll get a fixed version.
Take a look at the global human population chart over the last few millenia. Things can seem sustainable when there are a million people on the planet. When there are 8 billion things are a bit different.
Was that meant to rebut the idea that Meta wants to federate with other ActivityPub services? The fact that Google did the same thing with XMPP, gained user share, then defederated once they achieved critical mass - classic EEE?
Are they using an off the shelf ActivityPub implementation (if so, which?) or just implementing the protocol themselves? If it’s the latter, which I expect it is, then implementing the protocol does not save development time or effort. It’s just a set of specifications that they decide to conform to, rather than doing things some other way that may better suit their business goals.
“We” haven’t moved anywhere, I just chimed in for the first time with my interpretation of what the other person was talking about. Jeez.