@Flockstr you need to add a way to search by location. 

There are too many events to look through manually.  

 @Luke Dashjr @jack @MartyBent @ODELL
I've been thinking on howtoo solve the dust limit problem @OCEAN is facing. The simplest and most practical approach would be to follow the coinjoin model of having multiple pools for different size miners. Based simply on the hash rate the miner is bringing to the table, they would be placed in a pool that ensures their rewards are above the dust limit based on pools hash rate limit. 

Ex. You run 3 pools, A, B, C, with 100, 10, 1EH limits respectively. Then you can filter an individual miner to the pool where their hash rate falls between 0.1% to 5% of the pools hash rate limit. Or something along those lines. 

No accounts, no KYC. Just filtering based on hash rate only.   

 @2d9873b2 people need to take this self-sovreignthings more seriously. Instead of immediately running to nostr and complaining, they should first see if they can solelve the problem themselves. 

24hr HTLC lock times are not an attack on #lightning, at most they are simply taking advantage of your own lax routing policy. If you don't like it then simply change your routing policy. It's as simple as than.

Overall good improvements.