Cope is writing notes mocking the attackers.

This mitigation will work just as well as minrelaytxfee once it's properly merged in Bitcoin Core and people can easily switch it on.

I don't expect a supermajority of node runners to patch their nodes with my stopgap solutions, but I expect them to understand how the patch works and demand it to the dev team.

At any rate I'll keep building tools and making noise. I can do this all day.

Ahhh, this hurts!!!!

😂😂😂😂😂😂😂

What #Bitcoin desktop wallet do you use?

Thanks

Wasn't able to zap gratitude.

Drop an invoice for 250 sats here.

⚡👍

Hi Vitor

Where is amethyst in fdroid, do I need an extra repo?

I got 2 zaps a few minutes ago but you are right, I had a problem with my nodd, I couldn't pay for my burger with Bitcoin LN this lunch, my node gavean error twice. Maybe I'm under DoDS attack somehow?

No wonder why most use custodial in that case.

Thanks for trying to zap anyway.

I use my own BTCPay server if you wanna help thr stats.

Any views on which wallet is best to use with your own lightning node

What you cannot copy and what's your Android setup?

I'm the author of gossip, a desktop client not a mobile app, but I have someting to say on this. Gossip downloads only about 4MB when I start it in the morning and run it for an hour. Since that is several orders of magnitude less than some other clients, I thought I'd make a list as to why:

1. Duplicate Events - many clients subscribe to the same filters on all of the "read" relays. So if a person has 10 read relays, they get each event 10 times. They could subscribe in a way that only gets N copies, where N is set in some setting somewhere (gossip defaults to 2 or 3).

2. Not Dynamically Connecting to Relays - when clients don't dynamically connect to the 'write' relays of whoever you follow, users are incentivized to add lots and lots of relays as a hack to try to get that content, aggrevating issue 1. If clients smartly went to the write relays (based on relay lists), all of the content a user has subscribed to would arrive (in best case scenario) and users would no longer feel the need to add massive numbers of read relays.

3. Counting how many followers you have is expensive. Kind-3 contact lists are long, and you need to pull one for each follower to make such a count. Especially if done across many relays (where the same ones are pulled multiple times, once per relay), this could be 10-20 MB on it's own. Then how often is the client triggered to recount?

4. Downloading of avatars: gossip caches these so it doesn't have to re-download them. Any client that uses an IMG tag and doesn't have a browser caching is probably downloading these over and over, at worst case every time a post scrolls into view.

5. Content images and content web page pre-rendering: This can be very expensive, but is probably unavoidable on rich UI clients. Gossip is a "poor" UI client, without any images or prerendered links (it just shows links that you can click on to open your browser). But with caching, repeated downloading of the same thing can be avoided.

6. Re-checking of NIP-05 could be done periodically, perhaps daily if it failed or every 2 weeks if it passed, probably the worst strategy is every time a post scrolls into view.

There are probably others.

Ordinals…talk to me…

- The good?

- The bad?

- The ugly?

Making a show on this tomorrow and want to know your thoughts. Can they be stopped? Should they be stopped?

Pushed a hotfix to iris that seems to keep relay conns open. History download could be worse, but at least new messages appear.

Hello from iris.to! I haven't used this client in a couple weeks. It's so damn smooth! The only thing it's missing is **image upload** and **Lightning support** on profiles and posts.