you can’t change users unless it benefits them
trojan horse nostr:note19mj78atqal7ajdr40mvuqst64znxtakjepd0gac2st54f5d9n3rqe4ved0
At least it has a fingerprint sensor unlike the Portal…
become the employer
Podcasts are paid off
ah so you want to go the Nostr Plebs way… :)
but not everyone will want to use it and it will lead to a lot of people being disappointed, compared to a dedicated NIP-05 service
Oh. Don’t bother with NIP-05.
Pubkey whitelist is easier and people with other NIP-05s can use it.
nostr:note13yn672a45c57j6sw9fwhjymv0e2l2sw6nmncxgfk6pqksgmmjknqakvl9monly a matter of time before the RF spectrum becomes unusable
GM.
Today I will be attempting to run a “real” relay that only accepts posts from verified NIP-05 npubs.
I don’t imagine this be difficult, but I’ve never tried this beyond what nostr:npub1aghreq2dpz3h3799hrawev5gf5zc2kt4ch9ykhp9utt0jd3gdu2qtlmhct provides.
it’s not verification
Who is saying “its the users being lazy”? Are you saying that nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj or is it someone else?
To be clear, I certainly am not.
not you specifically
it just seems to be a general mentality that nsec management for example has to be hard and people have to adjust to it
developers when they can’t make something simple when they didn’t even try: “it’s the users being lazy!” nostr:note1r7kn47mslfrcqtyezt448rzy0mplwekagyr2ckvp7qkfwnz4wh7qqhgun3
First, not everything is on Nostr.
Second, Nostr notes are not non-repudiable because of the many ways they could get compromised, even with a remote signer (signing some unintended notes before access is revoked)
And you still need a relay to store that note… which will become harder and harder
Personal relays don’t fix this because they are limited to people who know how to run a server, and are intentionally limited to a small group of people. Also, maintenance cost will only go up while the benefit doesn’t change.
It does not.
whatever type of error you are having must be a more widespread issue than a few pages to be triggered so often
the ideal program would have a small pool it nonstop allocates to and deallocates from and a pool it very slowly checks and rotates allocations in/out
write random data and CRC it as I said
you then want to stop the process and get a debugger if there’s a mismatch and see the physical location along with identifying the RAM module
pick 2: security, performance, affordability