-
Notifications
You must be signed in to change notification settings - Fork 61
Conversation Rewards Hot Fixes #673
Comments
Anyway it seems like Github creates a lot of unnecessary HTML tags like:
is encoded as images are encoded as |
Available commands
|
We should be reading the source code of the comments instead of what is rendered on github for sure. For example, if you try and edit your comment, you will see the source code. Lets be sure to get that. |
I did some research here and realized that we must use |
But if we want to use HTML tags in the config than we must convert the raw Markdown syntax to HTML. This task was about moving from Markdown to HTML |
It was supposed to be for unambiguous config property names. Check the referenced conversation, specifically this comment. #383 (comment) But ultimately either way, the current way the incentives are calculated isn't good. |
I see, this was misunderstanding on my end. So we should parse the comment in Markdown format and convert HTML tags in the config to the Markdown equivalent? |
Yes I just figured that in the config it's much clearer to use HTML. So it's easier to config. As we see now the comment incentive calculator must consume the raw source code or else this won't work. The raw source code is probably going to be markdown. What happens if it is partially html? Will mdast handle this? |
Mdast will leave html as it is. |
@whilefoo The time limit for this bounty is on Mon, 28 Aug 2023 12:57:23 UTC |
Do you have any updates @whilefoo? If you would like to release the bounty back to the DevPool, please comment |
@whilefoo are you still working on this |
<a><img>
and code blocks<pre><code>
so rewards calculations are way higher than they should be.Conversation Rewards
pavlovcik: [ CLAIM 50.8 WXDAI ]
diamondnegroni: [ CLAIM 2.7 WXDAI ]
Originally posted by @ubiquibot[bot] in ubiquity/sponsorships#4 (comment)
The text was updated successfully, but these errors were encountered: