Exactly. The American justice system is obscenely expensive, cruel, corrupt, and not very effective at reforming people to prevent recidivism.
e.g. California's largest employer is the prison system. Ridiculously wasteful and expensive.
Other countries have far more effective rehabilitation and education programs in prisons. For example Japan has mandatory military-like drills and education for inmates to learn discipline and life skills so they have a better chance after they are released.
I'm not a scholar on this topic so I don't have a specific formula. I just know our current system is horribly broken.
There's plenty of lazy third+ generation Asian-Americans. The quality of parental upbringing is vitally important to success in life.
Note: I'm a 5th generation American. The cultural pressure can survive a very long time. I intend to similarly punish my kids, for their own sake.
My politically incorrect thought: America might be improved if we changed nothing about the criminal justice system except added caning as a possible punishment.
Opinions?
You sure it isn't the disappointed parent thing?
While your suggestion would work in isolating frequent posts to only followers of that topic, I strongly prefer the Twitter communities-like format for a moderated special interest group for multiple reasons.
* Anyone else can post but designated moderators keep signal-to-noise ratio high by removing off-topic stuff.
* Individuals get credit for good posts and followers.
I would totally use it if Nostr gained similar moderated group capability.
Elon could cut his losses and avoid a nasty battle with the SEC if he instead integrated LN now.
Hey all! Here's a new nostr relay implementation I'm working on: https://github.com/hoytech/strfry
It's still in beta/dev, but pretty close to production ready. Most interesting feature is a merkle-tree based set reconciliation protocol for syncing messages between servers.
This is a new account and with no profile. Have people verified this is the author for sure?
Upgrading or migration to a different platform is far more complicated than a fresh install unfortunately.
This is a good value for a home self-sovereign LN node.
* CPU much faster than RPi.
* 8GB: you should add another 8GB (DDR4 SODIMM 2400 or faster) or replace to max out at 32GB RAM.
* That's a 1TB SATA HD. You could add a nvme 2280 SSD to gain storage redundancy for your critical LN database. SSD's are at an all time low price now. I recommend TLC drives without HMB like Samsung 970 Evo Plus, Teamgroup MP34, or Crucial P2. 2TB is very affordable these days.
* You could also replace the spinning hard drive. Elimination of moving parts improves reliability. For 2.5" SATA I recommend the 2TB Crucial MX500 that's been below $120 recently.
* Most of the cost is your new drives. These drives will outlive the machine. If the machine dies you can simply move the drives into another machine. Linux won't care about the underlying hardware. It should work with zero or minimal reconfiguration.
I've been testing a similar model here. The screen and keyboard are of lower quality and music sounds bad from these speakers. These economy business laptops make excellent servers when you're able to buy them cheap enough which often is possible when fleets of corporate machines are liquidated.
There is risk in buying used. You want to immediately stress test the device including CPU, RAM, and disk after you receive it so you know if it needs to be returned. You want to flash the firmware to get security updates. That however has risk of bricking which would become a complicated discussion with the seller.
Note: Several other models are suitable as dual internal SSD home servers. I don't often post about them though because quantities for sale are not high. In this case the seller seems to have many for sale and the price is good.
Please follow and zap if you want more self-sovereign LN advice like this. I could be convinced to write a guide of what to do after you receive a used Thinkpad. I've lost money buying and testing non-refundable duds so you don't have to.
https://mobile.twitter.com/i/communities/1563029300911058944
Please also follow my Twitter community where small tips are written more frequently.

Is one of the implementations of relay server holding up better under load than the others?
Tips could be in secret and have nothing to do with the social network.
Zaps leave an unnecessary public record that also adds to social value because it shows enthusiasm and encourages other people to also zap.
It's fine once you get past the learning curve.
Have you considered long press on a note could pop up a menu?
Currently most other apps like a web browser long press lets you select substring for copy & paste. That isn't needed anymore with Android 13+ clipboard because it lets you select a substring from the clipboard after a larger amount of text is copied. Thus Amethyst could use long press for a different purpose.
BTW could you please add the Translate toggle on every note? Perhaps in the right context menu. I currently have no way of requesting a translation of Japanese posts while I have the Japanese keyboard installed. I want to toggle translations on and off per post. That is helpful in language learning.
BTW why is the right context menu button missing when you zoom into a particular note? Perhaps long press could be the alternative way of calling for that menu?
Outside of the notifications tab how do I see who liked, boosted, or zapped a particular note? Is that Missing from the UI?
How does that client work? Does it have a note proxy where it connects to various relays on your behalf?
Not asking for refunds. Relay software authors and relay operators need to be paid for quality service to be sustainable in the future. Everyone is trying hard and that's all I ask for. Thank you for your good work!
That said I'm interested in your opinion on this approach to make paid relays more sustainable.
#[3]
4 out of my 7 paid relays appear to be struggling. I began to experience far more problems when these older paid relays have problems.

I see listings of many new paid relays. I'm hesitant to pay for more random names. I want to read about what type of hardware they are running, network capacity, and what level of system administration experience the paid relay operator has. All of that is relevant to ability to provide quality of service. If would also be useful for some kind of relay health & uptime statistics to be monitored by third parties. That too is a service that people should pay for.
#[0]
I'd block you but your arguments are so bad it's funny.
Banning doesn't work on Nostr except for the the extreme measure of the relay blocking the client IP. Since they often can't meaningfully block IP's without collateral damage and administrative burden, public relays can't do much to truly block a bad user as it is costless to generate more npubs.
"Ban" in your client is only hiding those messages. Your client still needs to download their garbage in order to filter it from your view. Maybe you don't notice but client-side filtering means both the relay and your own resources are being consumed by messages you don't want to see.
Some clients tell users to cope better with resource consumption by telling them to turn off Global and Public Chats entirely. Then you download a lot less since you see only people you follow.
The only real solution here is to use paid relays where there is a cost to getting blocked by the relay.
Web of Trust informing relay-to-relay synchronization of a "Strong Set" of popular npubs would go far to reduce spam while also helping the relay servers to cope with load.
I'm beginning to see free read-only from paid relays isn't working. The paid relays are struggling now under read-only load to such a degree that is paid users can't use them. But if relays require private keys to read then a non-custodial personal proxy server would not work until subkey delegation becomes a real thing.
Nostr needs work.
Is it just me or are the relays struggling more in the last day or two? Even the usual paid relays are throwing errors for me. Meanwhile a bunch of npubs are unfindable by my clients and many notes aren't loading.
#[0]
Added Bolt12 feature request for Damus in app wallet. H/t
#[1]
#[2]
#[3]
Bolt12: https://github.com/damus-io/damus/issues/683
Damus in app wallet: https://github.com/damus-io/damus/issues/627
Given most nodes can't do BOLT12 the best we can do is to specify both in your profile and indicate which you want to be tried before the other.
They're collaborating on improving the specification and working on interoperable implementations. That's how open protocols should work. There's really only one entity that isn't cooperating in that way.
CLN, soon Eclair, eventually LDK.
The specification has been a draft but usable in CLN for years now. They warn you don't tattoo a static BOLT12 QR code yet because the spec could change before final.
In practice Iris requesting deletion a few times over a day or two eventually purges my accidental note enough that it no longer appears in my Amethyst client. Yes it sucks that it can't reliably work on the first try but it does eventually work. It doesn't work on the first try because your connectivity to relays is not reliable.
"Request Deletion" is the honest way to name it.
I zapped #[4] 's first post where he replied "Hi" to me.
Hmm stacker news supports zaps?
I zapped #[2] from Amethyst which opened Strike to pay the invoice. Subsequently I don't see any zap notes on Luke's account. Luke uses Iris which doesn't matter (right?)
Is Luke's receiving end not NIP57 compatible? Or are the missing zap notes due to my Amethyst plus Strike used to pay?
He's emotional and out of control. He fired an engineer for telling him the truth. He permanently banned a prominent Bitcoiner this week who mildly criticized him.
His reply literally happened between the time it took me to post and subsequent viewing of my own post.
I remember your scheduler from the early 2000's. It was ahead of its time. 😀
It can happen as a race condition if you use two clients simultaneously and you get unlucky in timing. In order to avoid that risk I close one client before opening another with the same npub.

