Does Luke suck to work with? Clearly
Is he out over his skis on the csam stuff? Yeah I think so
Is Luke the reason people are running knots? Not really. People are mad at core, and core can fix this with one simple trick.
Literally just bring back datacarriersize and let people do the thing that everyone says does not matter.
I think this was true initially
At this point the narrative has gone so over the edge of core being malicious that a debate on technicalities is completely impossible imo
And that‘s on nobody but Luke and his two braincelled prodigee
Isn’t this often the case that once things stay in the public eye like this nuance and prober discourse go out the window ? Leaving the idea of possible malicious intent to the side.
I don‘t think Luke has malicious intent
I think he is a hardcore autist who is actually concerned about CSAM and following the law that has psyched himself a bit too far into believing that he must save us all from these evils because otherwise the apocalypse will be upon us (which doesnt mean that this absolves him of responsibility)
But yes, imo the way our platforms are built exacerbates the doomsdaying and that is true for all things
The "journalist" tries to get back on her feet. By now she has lost so much credibility that she can safely be regarded a 3 letter agency asset.
I was looking at the malicious intent through both sides.
On core:
moving and deprecating a feature for users that their base are clearly are divided on, just feels like bad mgmt.
On Knots:
Dividing a community on the premises of CSAM.
My own 2 sats:
Although possible today we don’t need more ways to spam even if they are more expensive and still require other software to extract.
On luke personally don’t know the guy but this community is full of special folks 😄
Would love a platform that kinda prevents us all from getting too tribal on these cases ( a man can dream )
I think nostr actually does a really good job at that - its really become my happy place on the internet where i can choose what I see and engage however and how frequently i like as opposed to some nefarious algorithm deciding for me.
I agree re core to a degree as Im not versed enough on how harmful these currently workarounds are that are being used. I do think that a lot could have been mitigated by explaining these things clearly (Realizing that I have a media platform and that I could also do smth about that instead of complaining).
What I do think an interesting and very overlooked question in the spam debate is is who qualifies what counts as spam, and I find that a slippery slope - kind of like qualifying who a terrorist is.
Today it may be JPEGs, tomorrow it could be a rollup, etc.
You definitely are trying to use your platform for a good purposes I appreciate all the work 🫡 and we always can do better ✌️just keep on keeping on
Yeah I just think a bit of give on the core side would go a long way. Mike Schmidt started doing this by putting up a pr to un-deprecate datacarriersize and it’s a good start.
datacarrier was never removed. the current pending-release notes say:
```
-datacarriersize is increased to 100,000 which effectively uncaps the limit (as the maximum transaction size limit will be hit first). It can be overridden with -datacarriersize=83 to revert to the limit enforced in previous versions
```
20% of Noderunners and climbing are on Knots. How much further do Core want to push it?
The issue is these guys had good reasons to get people riled up. Could have been defused quickly if there was a consistent, logical argument coming out for changes but there wasn’t for a while. Instead we got gaslighting, “paternalistic censorship” and actively antagonizing comments.
It was a shift in thinking, communicated poorly, and the worst part was otherwise smart respected people dipping to unnecessary lows due to open source bad blood.
The outcome is instead of having a somewhat hard conversation about the reasons for core wanting to nuke mempool policy, we’re now having the conversation about whether people are going to run core at all. Much worse.
The solution isn’t more Luke bashing its core building trust with people again. Arguably the easier thing, the hard part is eating a bit of humble pie.
Op_return has been discussed since 2014.
There is a bitcoin mailing list for everyone to see.
Mechanic and Ocean started this FUD campaign attacking Core in May.
Core devs and core supporters are right to defend this bullshit FUD campaign.
