I think that you and every1 who is on knots "side" should make screenshots of that behaviour. You have very interesting observation here.

This is a good suggestion

i have them muted so i don't have to see them i made a PR to #jumble to fully hide them because the abuse from these clowns was getting too much for me. well, it was them plus this jerk trying to claim i was talking about a debunked physics theory which i wasn't, that tripped me to "ok i've had it with seeing these jerkoffs on my screen at all". it really seems like some coordinated attack on knots users on nostr. there is a bunch of people who are playing along with it that i doubt are in on it but are joining in because they are also jerks.

It reminds me of when Israel attacked Gaza (the latest time). Remember all those npubs that suddenly appeared, supporting Israel? They were all fairly similar - a picture of a person wearing a suit, with a kind of "evangelical" look about them. All just woke up started debating people here. If you didn't notice it, then please start noticing... This is what an influence operation looks like. We're seeing the same thing again with npubs supporting Core. Obviously there's an agenda. Where are those pro Israel npubs now? Have you seen any activity from them recently? No. They were here on a job. Same now. Same pattern, like there's a playbook or something.

I haven't reached the blocking point yet, but I can see this is heating up, so likely soon. And I have a bit of imposter syndrome, since I'm not really on y'alls's level with the technicals. But my more "empathic" (not really, but in a sense) heuristics have never failed me, ever. All my Spidey senses are going bonkers...

i have reached a threshold with tolerating the waste of my time that is caused by trolls. i have now successfully had my favorite nostr client,

Jumble

A user-friendly Nostr client for exploring relay feeds

updated with a feature that allows you to completely hide muted replies including basically all of the thread from the muted user's post down. so *almost* nothing appears to alert you of it unless you replied on the thread with said user, by replying and then muting afterwards. wasting people's time with nonsense is an offense, in my book. very small, but the rightful response to it is to completely disappear this person from your client. if someone did this shit in real life, i'd bend over backwards to never see them again. i got so much of this shit in my life i'm finally 100% done with it. i already was ghosting people for worse abuse in person than these clowns are doing but they have driven my threshold right down to the point i'm taking direct actions to stop them interrupting my day. and, enabling other people to do the same thing. at least two people immediately were excited to enable this feature that i saw, i would expect that it will become quite popular and a lot of people will enable it, and want it to retain that setting automatically on other devices they use the client with.

I think I should start using this client more.

i'm starting to want to help add features/fix it also. i used to ask for things, but since i started my new job i learned a bunch of stuff about how to add features to this app, so i just went and made one and he was so nice to basically immediately update it with some extra polish. i haven't got any immediate ideas of what to contribute but my paid gig project i'm going to use its code to implement a simpler feed viewer for their site and maybe some of the components will make their way from there into here. notably, updates of people who have listings on nostr marketplace protocol (the actual listings probably isn't something we'd want, so it would also need a way to know which web client to open to view it. which will be the one i'm being paid to work on). it is becoming a very popular client because it is fast, clean, simple, and does all the important things, it shows gallery posts, vlogs, audio posts, and a bunch of other things. when you try it out, check what pops up on the button that is like 3 lines narrrowing down like an inverted triangle, this is the filter and it shows you how many different kinds of events it displays. it's really nice.

How does it know who I'm following? I'm not logged in but its got people responding to me at the top, which seems odd, considering how many people use nostr that I don't follow.

probably because it's a relay that you use, i think it usually opens with nostr.wine so it would show newest events there which you are part of

Ohhhhhhh. Huh. Cool.

I also noticed a random burst of new BS on this subject in my feed, which is why I weighed in. I was also wondering why this is big again when blocks are already empty. Are we worried about the security budget or not?

Personally I'm quite happy with empty blocks. I'd like fees to be higher, but I'm also never not gonna ninja in my 1 sat/vbyte tx, which I was quite proud of back when fees were actually kinda high a while back.

It started because people recently extrapolated what 100KB of contiguous data could be used for and having to decrypt that data to verify the transaction's validity would likely trigger anti-virus software labeling Core as "malicious content." Inscripting data is one thing because you'd have to reassemble the data using a certain specialized compiler. With 100KB contiguous, the bytes would be more or less in plain text, any image or video compiler could view the data natively. THAT is why people are getting upset. There is a very REAL chance that random strangers will send you, let's call it "bad stuff", that according to current law makes you a fed target. And outside that is disgusting to most people. This is why I never argued about the merits of OP_RETURN it's really just about property rights. My computer, my software, my rules. Want to make my node a CP magnet? No thanks, I'll run something else.

This PR linked solves the problem for every encoding attackers can invent unlike the treadmill of chasing new filters. It also works in a safe way for you, because all data is deniable always. A attacker can invent a new way around the filters and post CP as the first TX using that method. No way to defend it because the only way to close every hole is to stop accepting new transactions at all. Because of that filters cannot and will not ever protect you from CP being stored in your chain state. Step back and remember, the proposed filtering is authoritarian control over bitcoin transactions. Think of the children + we must do something, this is something, we must do this. Classic government marketing for new authoritarian bullshit.

GitHub

blockstorage: XOR blocksdir *.dat files by maflcko · Pull Request #28052 · bitcoin/bitcoin

Currently the *.dat files in the blocksdir store the data received from remote peers as-is. This may be problematic when a program other than Bitco...

Apparently no one is worried about the security budget…

I am aware of that PR, as of yet that is not in the build and is a theoretical fix to that on a deniability basis. Again though, bitcoin is a monetary network and the claim that the thing hindering a robust layer 2 is the size of the OP_RETURN field, is dubious at best. By my estimation therea not a single need for the datacarrier size to be over 100 bytea even in the most complex layer 2s I've seen. Now minting a shitcoin on bitcoin however takes much more data. I am less concerned with the "Think of the children" wrapping paper than the "Limiting arbitrary data is authoritarian" wrap. It is smuggling so many intended consequences I haven't even thought of the unintended ones.

I'm not. The cure is just higher value, IMO.

This just seems like a better argument. Massive respect for both of y'all.