kjeldahl / Marius Kjeldahl is on Nostr

"86246f8077163016993c88d7f185c867c82e9f9fb6839703401a46801dbafc133d829544c4f8b225edd1df6dce72701b761094214072cad7cca8a7ea45bffdfc"

Last Notes

2025-02-20 10:08:08

- reply

I've done tons of work to make Pumpstr behave better towards relays and smarter connection pooling. When doing that I have turned off most/all "event caching", to make sure things behave like they should. I will re-enable event caching again soon, but then so that it only happens client side (not server side as before). Relay connection management in Nostr is not easy, so things are breaking while doing these changes. Additionally I'm doing work on the "feel" of the client (scrolling, persistant header etc) to make everything better. Progress is good, but some bugs will show up. Fixing everything asap though, usually within minutes from I notice anything. Thank you for your patience.

2025-02-20 10:00:15

- reply

Thanks, it registered (visible in my wallet), but feedback (and top list handling) is a bit buggy. I'm updating right now.

2025-02-19 19:02:42

https://cdn.nostrcheck.me/2e1b0646bb603b8c4febc648a2801d7134d18b5a766ad2bb87bf53db3eca0c6f/13436fc0103323be3f534de4f24023a5319906a3876e312488dea7bbd41c7c7f.webp

2025-02-17 22:54:28

As a developer, getting started writing a Nostr client can be a bit challenging. Nostr is supposed to be decentralized, connecting to whatever relays the user specifies. Weirdly enough, the user preferred relay lists lives on other relays. Which ones? You don't know. So even as Nostr users are supposed to maintain their own lists of preferred relays, a Nostr client app still needs to have some kind of dynamic/hardcoded list of relays to get that user preferred relay list. In addition, whatever list you start with, lists are dynamic. They come and go. Which means both as a Nostr developer and as a Nostr user, you need to do some upkeep to keep everything working properly over time. This is one area where Nostr could definitively improve. For all parties involved.

2025-01-27 12:29:22

- reply

Learn javascript first. Figure out which platforms you need to support. Do you need stricly native features and/or be tightly integrated with the phone OS? Then you probably need to look at native options for mobiles. If you need more "generic" support (both desktop and mobiles, and not a lot of tight integration with OS platform), learn javascript. Make websites, and PWAs if you need to deploy to phones and run offline. Then when you have an actual user base, then decide if you want to treat your users to that very optimized native polished look and feel. Native will always be better, but not always better enough to support the huge added investments needed for managing multiple native clients simulatenously.

2025-01-14 16:53:45

- reply

Thank you for giving it a try. Looks like you managed to withdraw as well. Thanks.

2025-01-14 15:15:13

- reply

Pumped with 1145 sats BCH, see https://pump.coinmachin.es/ (bitcoincash:qpxqv9vjyhc9lvhlq2p9np538mygte8aw5k7zsaj6n).

2025-01-07 12:24:55

Are there any statistics on Nostr client popularity? I'm primarly interested in the open source web based ones for now, as I need to start adding client support for "Pump!" (Zap using BCH). I'm also thinking about maybe doing a plugin first instead. Opinions? https://pump.coinmachin.es/top

2025-01-01 17:58:58

- reply

Pumped with 112963 sats BCH: bitcoincash:qph086ar4wet5a4jfy9kcwng9q7wqfnz6yqzqulpex

2024-12-09 19:43:59

What do I need to do to get a "BCH payment receipt" "kind type", similar to kind 9735 "zap receipt"? Assuming I need to demonstrate working code and/or write a complete NIP first, any suggestions on what "kind" to use while testing?

2024-11-29 23:00:32

So I'm thinking of doing the unspeakable. Adding support for layer 1 zapping to Nostr using BCH. Hate me gently.
https://nostrcheck.me/media/2e1b0646bb603b8c4febc648a2801d7134d18b5a766ad2bb87bf53db3eca0c6f/3ca126a98b3435f91ab856b490263c52dcd7fd91e3e491e9f0a5fe7292bcf257.webp

2024-11-05 10:03:12

https://namify.tech/ is a pretty good domain name generator. Any other favorites?

2024-11-05 08:22:05

Norwegian left leaning politicians are crazy. They recently introduced an Exit tax which will tax you on unrealized gains if you leave the country. There is one exception, you do not have to pay it if you move back within 12 years. But you can also not pay dividends from your company, where your risk that more than 100% of the dividend goes as a pre-payment towards towards the exit tax you owe (until it's paid in full). And if you company falls in value and/or your company goes bankrupt, you still have to pay the full Exit tax levied when you left. I wonder if any of the lunatics ever tried thinking about what the purpose of a "limitied liability" company really was when they clowned the latest taxes into place.

2024-11-01 17:00:45

I wonder how closely the zaps feature of #nostr is tied to #lightning, or if the nip(s) describing it would make it possible to have different kind of zaps? Of course that probably also depends on how maximalist Nostr users are.. :)

2024-10-21 14:08:14

So if I want to install a non-custodial BTC wallet to accept Lightning payments, what are my best options? The two I've tried already tell me I need to pay something to be able to receive funds (and that feature was well hidden until I pressed a "receive lighting" button..).

2024-10-20 19:27:26

- reply

Depending on how much "hardware" you actually need to test, the iOS simulator running on the same machine is probably still the easiest.

2024-10-19 11:15:15

- reply

Depending on how much "hardware" you actually need to test, the iOS simulator running on the same machine is probably the easiest.

2024-10-19 00:03:15

So what's the state of the art for testing PWAs using websockets on iOS devices on a local network these days, preferrably something with automated certificate generation (assuming wss is required)? Or should I still proxy everything from a live public server (with valid certs)?