Avatar
Charlie Fish
d77637850017cffa7a61c7032db0f28be947d5487f9d504aabe4449a91b53cff
Software Engineer (iOS - ForeFlight) 🖥📱, student pilot ✈️, HUGE Colorado Avalanche fan 🥅, entrepreneur (rrainn, Inc.) ⭐️

Making great progress too. Hoping to have a patch submitted to nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s by the weekend for review. But MIGHT slip into next week.

Interesting. Although don’t love the fact that at first glance it doesn’t look to be open source.

I've seen a lot of posts here recently about Twitter/X Spaces. Makes me wonder if #nostr could do something similar 🤔

Replying to Avatar Alex Gleason

Sweet. It's very similar to what I'm doing. I have in-memory and SQLite implemented here: https://gitlab.com/soapbox-pub/ditto/-/tree/main/src/storages?ref_type=heads

We should try to nail down a common storage interface we can use between projects. I believe it's a good idea to base it off the ES6 Set interface: https://gitlab.com/soapbox-pub/nset just with async types.

That nset is super cool. Will try to find time to look at the code later.

Duplicate entries is a problem for mine.

It would be cool to have an extension system that provides a storage interface and you can just plug and play. Almost getting into ORM territory tho.

It’s still VERY early stages. But that is one of the concepts of my #nostr relay. You can currently use in memory, file system, or SQLite. On my radar to add Postgres and remote relays, and hopefully more. https://github.com/rrainn/nostr-relay

My guess is lots of #AI. But considering how prevalent AI was last year, it's probably a fairly safe bet lol. I haven't kept up with the pre-event stuff too much tho.

It's #CES week! What are you most excited to hear about? 💻

On my original/root post? Or? I don’t think my replies have PoW (NIP-13) setup. 😝

Yet the problems with high fees and long transaction processing times persist.

Also if you’d be willing to share what software you’re running on your node that would be super interesting too. nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424

Sure! NIP-42 is a way for clients to authenticate to relays. From the user perspective it’s seamless and invisible to you.

But it enables a relay to know what user/pubkey is connected to their relay. This is primarily used for paid relays (ex. filter.nostr.wine) or relays that only send your DMs to authenticated users (ex. nostr.wine).

filter.nostr.wine for example before NIP-42 required you to change the URL to include your npub so they knew who was connecting. However that isn’t very secure and it didn’t provide true authentication.

I’m sure there are a lot of use cases I’m missing. But at a high level it allows a relay to verify who a user/pubkey is that is connected to their relay.

Hopefully that helps explain it.

Replying to Avatar Derek Ross

you're not wrong. Lightning makes it a bit harder. the easiest options for controlling your own keys with Lightning is to use the "node in your phone" solutions from Breez, nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 z nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg , Phoenix, or Blixt. These are by the far easiest self custody options, but using these comes with a bit of a trade-off because you are not managing the node or the channels or the liquidity as much, you're letting the application and service provider do this for you. Therefore, these options all come with various fee rates for sending and receiving sats over Lightning.

The harder method, the one that I personally have done for 3+ years, is to run your own Lightning node on a dedicated piece of hardware or server. You're in charge of the channels and liquidity. I won't lie, it's a pain in the ass. However, I don't have to pay fees to any provider.

As for tutorials, I always recommend my man nostr:npub1rxysxnjkhrmqd3ey73dp9n5y5yvyzcs64acc9g0k2epcpwwyya4spvhnp8 and the videos on his YouTube channel.

What about running your own Lightning node makes it frustrating?

#asknostr

nostr:note1qqqqqq30zgjrk0czh098f5p3v4dsygvkl9ntahhd4sp9j3cxkheqadfaav

The purgeable space feature of #macOS makes it an awful operating system for #server use cases. #nginx doesn't seem to support using purgeable space to fulfill its operations.

I completely missed that 😂. I misread Nostur as Nostr.

That’s what happens when you basically never delete apps 😂

I created my own #nostr #relay #server a while ago. But just now open sourced it. Still not the most stable, and lots of work to do. But serves the purpose of ensuring my notes remain stable. Check it out at: https://github.com/rrainn/nostr-relay #opensource