Nostr with new Amethyst is retarded, I am sorry but I still think it’s the case. Amethyst tries to open hundreds of WS connections, and pull same data over and over. Any system for detection of DoS will flag it as such. Don’t blame the Proton, blame the inappropriate use of network resources by the software
Discussion
It did happen right after the update yes, I was thinking the same thing.
I do blame proton though, if you don't want me using the VPN, disable that, but don't ban my emails and proton pass and stuff.
Dos is a criminal offense, so it is better if the company pulls the plug instead of trying to “warn” you. I bet that they put all of your data on a legal hold too, so deleting shit is pointless.
Yeah, true. I explained actually in the email that I use it for Nostr and that Nostr connects to a bunch of different servers a lot, The were asking why I have an account and what I use it for.
It is the reason. So, now you have to pay more because someone is not thinking of the users when they implement “great” features
Use a proxy relay, that will disable the outbox mode. A WoT relay configured for your user, filter.nostr.wine or aggr.nostr.land are good choices.
I always think the best use of using VPN is when you are on public network ,
Yesterday I was drinking at coffee house and I switch on my VPN and it was great .
Also the same when I am at the airport , I used my VPN after log in to the airport public service .
When I am at home , there is no need of that VPN.
This will make you more traceable on Nostr. Image hosts, every relay, people's nip-05 servers, and any links that have previews will all see your actual IP address. This could be used to identify you potentially.
Is this true though? I've not noticed increased data usage, and though there are far more relays, most of them transmit little data. Here are the top 25 data using relays, after a day of use. After this it quickly tails off into single MB and kB.

In my experience uncompressed media is a far greater issue for bandwidth issue, with 2MB avatars and 400MB 3 minute videos 😂 When I made Flappy Nostrich the biggest issue was downscaling avatars to non ridiculous sizes.
I am more worried about multitude of sockets to random IPs, and their implications on security. Selective fetching and on demand connection to specific relays is probably fine, but that still can be insecure and may result in some exploit or user activity tracking. As I posted a few days ago or longer, even TOR crumbles under many connections to multiple sources. I don’t have the solution, but I think proceeding with caution is warranted.
There, in a more civilized and less casual language
An interesting article. I wonder if anything in Tor has improved these issues in the 15 years since it was written? A lot was about bitorrent itself having issues, but the third point could be of concern, if it still is an issue.
I think the issues was architectural, and that may have improved, but I also think that “the state” could inject enough nodes into network to uncover the origin.
I think for a lot of people using a proxy relay could be a good choice. I'm actually connecting to less relays on average than I was before when I set it up that way.
Is it a default though? The defaults will be used in majority of cases
No you gotta set it up, default is outbox mode. I'm not sure what relays would be a good choice for that and are free. I use my own WoT relay & Nostr.land, but I think aggr.nostr.land needs subscription, and a wot relay is less useful if it's not configured for your own npub.
Why are people still using that godawful fucking app?
I think this is an issue if you disable tor support in Amethyst. With tor enabled I see maybe 20-30 tcp sessions as I guess the rest of the relay connections happen via tor. With tor disabled I see over 1000 tcp sessions which as you say is retarded. This sort of thing is likely to get flagged by some DoS protection systems. I can see this also being an issue for users behind CGNAT where users are allocated a block of ports which may be limited. It might have actually been NAT session monitoring that flagged it with Proton as I believe their free VPN is NATed.