Topic on User talk:Blazikeye535

I disagree with your arguments against the formatting of this RFC stating that it is "messy," as this appears to be the way it works on Miraheze Meta as well. While I understand your problem with requesting too many things at once, when it comes to related proposals, it's kind of repetitive to make separate RFCs for each one of them.

It's not just the fact that there's too many proposals, it's also how they're written. They provide almost no detailed explanation as to how the proposals work or why they're being proposed in the first place. There's also the fact that RfCs work best as simple "yes or no" style proposals, which this RfC doesn't do. That leads to supports being scattered on what exactly to do with almost everyone having a different proposed answer, which makes it impossible to come to a definite decision as I said before.

That's not how it works on Meta, and the way it works on Meta is also messy. What should have been done there is a much more coherent structure.

Well is my Source Reliability-O-meter RFC okay?