Changing the CredSperiment weights

[Beanow]

@burrrata

Currently there’s a binary distribution between platforms: code and non-code. This is mostly due to the infrastructure we’re using rather than cultural values. When we have Supernodes this will all be much easier (hopefully).

This particular point I think is interesting to touch on too.

Right now, we have one bridge between GitHub and Discourse Cred. Which is through Identities. Which I mentioned a bit here: Add identity for vsoch by Beanow · Pull Request #9 · sourcecred/cred · GitHub

@Beanow

Yes :] quite a lot of our cred comes from the forums. This [PR] uses a 3rd plugin (identity) to combine your accounts.

This matters quite a bit for cred, because now the “weight” from both github and discourse is merged as well. In your case, most of your cred is currently in github. After this is merged your likes on discourse will have a stronger effect, because they’ll carry the weight of your github cred as well. While previously they’d be separate.

I’m working on another major way to bridge GitHub and Discourse Cred. With Unified reference detection.

@Beanow

Description:

In a recent update Discourse reference detection was added. Where GitHub detection was already present. However currently the two don’t leave their own ecosystem. GitHub can’t link to Discourse and vice-versa.

This proposes a system where each plugin can instead define it’s “referencable” types and reference detection functions to SourceCred’s core, allowing the core to cross-reference between different plugins

With this system in place, it will be much easier to flow cred directly between nodes and across the different environments. So posts can link to issues, can link to PRs, can link to topics, can link to users, …