Zangelbert Bingledack
Well-Known Member
- Aug 29, 2015
- 1,485
- 5,585
@Inca
I knew that was coming when I read your comment above
Technically BU is a consensus implementation by their definition, in that the user can set it to track Core consensus. It might be interesting to see the verbal contortions they have to pull off to ban BU if we push back on that point, but it may not be worth it.
"Banned for spamming implementations that let you break from consensus" doesn't sound good from a PR perspective for them. They'd probably go with "implementations that encourage breaking consensus," which is why I still think BU should default to Core settings, at least for now. That way they'd have to say the former one, AFAICT. Then we could counter, "Forced consensus is no consensus at all." (And they would counter, "Go use a different subreddit," we would counter, "Valuable namespace," etc.)
I knew that was coming when I read your comment above
Technically BU is a consensus implementation by their definition, in that the user can set it to track Core consensus. It might be interesting to see the verbal contortions they have to pull off to ban BU if we push back on that point, but it may not be worth it.
"Banned for spamming implementations that let you break from consensus" doesn't sound good from a PR perspective for them. They'd probably go with "implementations that encourage breaking consensus," which is why I still think BU should default to Core settings, at least for now. That way they'd have to say the former one, AFAICT. Then we could counter, "Forced consensus is no consensus at all." (And they would counter, "Go use a different subreddit," we would counter, "Valuable namespace," etc.)
Last edited: