moderation note: I forked this out of Cred/Grain dynamics into its own thread.
Yes. This is specifically why every Initiative is a wiki- so that others can add in links that the author missed. Some future-feature ideas:
- Build a Discourse-wiki integration so that people who edit the wiki get some cred in the initiative
- Track which links came from which edits, so people who add a link actually get a share of the cred that flows through that link
Of course, as the community scales, this system would become too easy to abuse. But while we are in trust level 1 I think it will work well. In the future, we’ll likely build a dedicated UI for updating initiatives, adding/changing links, etc, which has a clever permission/review system built in.
The use of temporal information in SourceCred is both complicated and nascent. I could write a whole thread detailing how timing info in SourceCred works, as well as what the issues are with our current approach. I’ll try to answer your specific questions here, though, with an example.
In week 1, you have post P1. P1 gets (arbitrarily) 10 cred in week 1.
Week | P1’s Cred | P2’s Cred |
---|---|---|
1 | 10 | 0 |
In week 2, you have post P2, which gets (arbitrarily) 10 cred in week 2. P1 gets 0 cred in week 2. (Actually, due to the exponential decays built into time-based cred, it’s more likely to get 5 cred, but I’m ignoring that for simplicity of example.)
Week | P1’s Cred | P2’s Cred |
---|---|---|
1 | 10 | 0 |
2 | 0 | 10 |
In week 3, I like P2. This flows more cred to P2 in week 3.
Week | P1’s Cred | P2’s Cred |
---|---|---|
1 | 10 | 0 |
2 | 0 | 10 |
3 | 0 | 5 |
Now let’s suppose you go and retroactively edit P2 so that it included a reference to P1. Now when we next compute the cred, it will look more like this:
Week | P1’s Cred | P2’s Cred |
---|---|---|
1 | 10 | 0 |
2 | 5 | 10 |
3 | 2 | 5 |
So, in this example, your retroactive edit caused a lot more cred to flow to P1. It is indeed the case that right now you could attack SourceCred by going and finding your high-cred posts from the past, and adding references or mentions pointing towards your other work.
I suspect that we can come up with a clever way to mitigate this attack at the cred computation level, once we start using the edit timestamps from Discourse. However, if not, it should be easy to write tools that detect when this attack is happening, and we can then censure or penalize the attacker.
No; at the moment this information is discarded by the reference parser.