kalle

nostr:nprofile1qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszxthwden5te0ve5kzar2v9nzumn0wd68yvfwvdhk6tcpzamhxue69uhkzarvv9ejumn0wd68ytnvv9hxgtcpzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcpz4mhxue69uhkummnw3ezummcw3ezuer9wchsz8thwden5te0dehhxarj9e3xjarrda5kuetj9eek7cmfv9kz7qg6waehxw309aek2mnyd96zumn0wdnxcctjv5hxxmmd9uq3vamnwvaz7tmjv4kxz7fwd4hhxarj9ec82c30qyfhwumn8ghj7un9d3shjtnxxaazu6t09uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uqzqdxj75n57x2clnfvkfrrm2l2mhu2y8uy4njzg8dg3qprhuzueqy42q66z9I'm trying to connect with NWC from zeus v0.11.3 to my lnbits node. Zeus says "Error connecting to your node". The debug log in lnbits says: 2025-09-05 21:29:28.90 | INFO | New websocket connection at: '/api/v1/relay' 2025-09-05 21:29:28.91 | INFO | 185.195.236.83:0 - "WebSocket /nostrclient/api/v1/relay" [accepted] 2025-09-05 21:29:28.91 | INFO | connection open 2025-09-05 21:29:28.95 | INFO | New subscription: 'sub:1' 2025-09-05 21:29:29.26 | INFO | Closing subscription: 'SWVMA2reKjcKdn9mDKY2km'. 2025-09-05 21:29:29.26 | INFO | Unsubscribe from 'SWVMA2reKjcKdn9mDKY2km'. Original id: 'sub:1.' It seems zeus unsubscribes, why is that? Can I get logs from zeus to see its side of the quarrel. Or do you have any other hints?

#asknostr plz explain. I don't get this. nostr:nevent1qqsrq5uv8atvdflp49mnaaknq4wh0esrmmych2uznrd0fxzyv835lkspr9mhxue69uhhqun9d45h2mfwwpexjmtpdshxuet59upzqu0v40vtdve4frs8tlcpkv2k3l76r8g2cfugqe7ejv5vdhjgskt4qvzqqqqqqy9h4svs

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z Amethyst 1.01.0 keeps crashing on startup. Anything I can do besides reinstall app?

My ride this week

Sad! 9 left. What took it? Wouldn't a fox have brought its prey home? This is southern Sweden.

nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 the Bitrefill app version 4.2.0 won't install due to a hash mismatch.

Meanwhile on X nostr:npub1cev2qfuqv5s9jm5a6yvhc8ne8cdl9mh459m5g8zz759s7pw9fayqnketlq

The block weight limit is the spam filter.

I think the notion that the blockchain is Bitcoin's database is wrong. * the UTXO set is the database * the blocks take the database from one consistent state to the next. * the blocks are needed only by newly started nodes to recreate the database. In this context, * OP_RETURN is not bloating the database as it never enters it. * Encoding data in non-OP_RETURN outputs does bloat the database. Switching what you call "the database" doesn't change the problem with bloat, but maybe the perspective changes a little bit.

Who can argue against "Induced Atmospheric Vibration"? Boss: You made 1000x fee overpayment. What the fuck, Kalle!!! Me: IAV! Boss: nostr:nevent1qvzqqqqqqypzpn92tr3hexwgt0z7w4qz3fcch4ryshja8jeng453aj4c83646jxvqyghwumn8ghj7mn0wd68ytnhd9hx2tcpzahx7um5wgkkjerz8ghj7cmpvd5x2ttjv4kxz7gqyqkzyzxw6gwduf9xy2lps9tq5ry402l0tteq7wyht8phpat87yef5wl5gru

How do people manage their relay list(s)? I find myself unwillingly replacing my published relay list when trying out new nostr apps. Ex: I normally use Amethyst, but tested YakiHonne and edited its default relay list (added my outbox relay). This caused Amethyst to start using the yakihonne default list. Should I stop publishing my relay list, or maybe only publish the "greatest common list"? Is there wide support for that? Lots of Qs, but I'm confused.