They have some problems with communication some of their proposals are very relevant but plebs is not properly informed. That problem works both ways.

Replies (1)

Current core team is over. Brand is FUBAR. Trust was with people and people betrayed and squandered the trust. Demonstrated disastrous moderation practices, engaged in disingenuous coresplaining. A "bridge" might've been a redemption arc if core 30 wasn't released, but now damage is done, and now they think about it? Sorry, no. It's been 2+ years. This is all #core-post-mortem material. New core cadre should probably: - EOL v30 - Release v31 with: a) Back out op_return damage b) Fix datacarrying c) revert relay fee drop d) Revert readme damage "What is Bitcoin" Also: - never bundle security releases with features or changes to policy - don't merge controversial PRs, regardless or perceived merit - revert transifex damage - consider unbanning knots from security disclosure - do security maintenance for more versions. I'm down with lower priority for features if we can get more versions covered in a non-coercive way (ie. be honest about "you can just not upgrade") There's probably more, but it's what I have.