Avatar
Rizful.com
97f848adcc4c6276685fe48426de5614887c8a51ada0468cec71fba938272911
Rizful.com: Free, easy-to-use homebase for Bitcoin on Lightning. ✉️ Free Lightning Address ⚡ Fast, reliable zaps & Lightning payments 🔌 Connect to hundreds of apps with NWC 🛡️ Enterprise-grade uptime & reliability Created by the team behind The Megalith Node, one of the biggest routing nodes on the Lightning Network.

There is a big lightning node BitcoinVN. Don’t know much about it but it is definitely active.

I dunno. Seems like a complicated battle between two companies, not sure any particular lessons can be drawn.

Interesting. What would the use case be that wouldn't be be covered by, like, a VPN and an Incognito browser window?

nostr:npub19hg5pj5qmd3teumh6ld7drfz49d65sw3n3d5jud8sgz27avkq5dqm7yv9p For NWC implementations, do you recommend any specific relay implementation, or, more specifically, any particular settings or configuration with the relay? We're using #nostream for our NWC-only relay, and it does work, but also we're fighting an issue where our application loses contact with the relay, typically after 24+ hours up of uptime. (Note: I have no evidence that this is nostream's fault, could very well be something wrong we are doing on our end.)

When our app loses connection with the relay, we stop getting events from the relay, but can easily restore it just by restarting our relay-listening-script.... but we need to find a better solution.

At first our issues with #nostream were easily explained by various rate-limiting stuff that #nostream has in its default conf... but even after working through those issues, we're finding that it's hard to keep up a solid websocket connection with our relay for multiple days at a time. Seems like NIP-47 nostr:npub19hg5pj5qmd3teumh6ld7drfz49d65sw3n3d5jud8sgz27avkq5dqm7yv9p is maybe unusual because it requires a SERVER to have a LONG-LIVED connection with a relay... whereas typically relays are designed to talk to clients who probably won't be subscribing for more than a few hours at a time?

The problem is very likely in our code, we're using a lot of Ruby nostr stuff https://github.com/wilsonsilva/nostr -- and I think Ruby is just not great for long-lived event-based websocket stuff. So we're thinking of building a nodejs layer that intermediates between our Ruby app and the relay....... .. but in general, are most NWC server-side implementations using a particular relay implementation or settings?

Let me know if you can't find the right part of the nostream GitHub repository and I'll send you a link

Why not? You just provide an array of integers in the configuration file to whitelist or blacklist certain event kinds. From looking at the code of various projects, like Primal and others, it seems like a very common thing that developers will come up with their own nonexistent event, integer kinds, and use them for various things.

nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q performance on iPad is pretty good. One thing is that the zaps tab which should show I guess incoming zaps is empty.

nostr:npub1l5r02s4udsr28xypsyx7j9lxchf80ha4z6y6269d0da9frtd2nxsvum9jm looked at https://github.com/duozhutuan/NostrBridge. .... looks interesting. What I would like to know actually is "what would you actually use this for?" like what is actually the real world purpose of it? Maybe it's obvious to other people, but I looked at it and I thought what would be the purpose of doing this relaying?

If u don't want to run your own node on your own machine, check out Rizful

Really? I thought there was this whole "great firewall" thing that just blocks big parts of the Internet?

We did a lot of NWC development for nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq ... what helped was looking at open source code from COINOS and ALBY, if you can't find the repositories, let me know and I can dig them up. But really the MOST useful thing is nostr:npub1yxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96s8c399s site https://supertestnet.github.io/nwc_tester/ ... to test your implemenation. Also you an look at the code of this site to understand how it works from the client perspective..... Finally, I can't imagine doing NWC development without running your own relay, at least for dev purposes, because it really helps to look at the logs of the relay to see the messages coming to and from your NWC implementation. Finally, read this 10 times... .https://github.com/nostr-protocol/nips/blob/master/47.md .. and then put it into an LLM and ask questions about it or have it talk to you about it... I find with complicated stuff like this, it's really critical to make repeated attempts to fit it all into your brain, over several days....

There's a little discussion on nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq at the (much feared) bitcointalk.org forum. If you've had a (hopefully good?) experience with Rizful and have anything to add, it would be awesome if you could add a note.... here is the discussion thread.... https://bitcointalk.org/index.php?topic=5528378.msg65110570#msg65110570

#asknostr When I have a server which is subscribing to a relay -- actually, my own relay, which I control -- and both the server and the relay are running on stable connections, "in the cloud", how long should I expect the subscription to remain "up and stable"?

Because relays are mostly designed with browsers in mind... and those browsers or apps will typically not subscribe for HOURS on end...

I'm asking because while using #nostream I find that, even if I whitelist an IP, in reality a server --> service websocket connection doesn't stay open indefinitely. So I'm now implementing a "kill this subscription and start a new one" logic, running I think every 3 hours.....

Remember, the confusion of the average person is actually the most important natural resource in the Western world. If people stopped being stupid -- specifically, if they stopped endlessly consuming crap that they don't need -- then everything would collapse and we'd be back to subsistence farming.

We've made better explanation of the image-scanning-for-nostr idea, including full API docs. Please take a look here: https://docs.megalithic.me/lightning-services/nsfw-image-detection-for-nostr/

Good question. Answer not straightforward. Got a few other questions from other people too, going to answer them all in a faq which I will link here shortly

Here you go. Let us know if this helps: https://nostr-media-alert.com/

Replying to Avatar Rizful.com

@YakiHonne @fiatjaf @PABLOF7z @miljan @ hodlbod This proof of concept shows real-time events that we've found on Nostr relays which are likely bad enough that Google or Apple, if they discover them being "served" by an app like @primal or @Damus or @YakiHonne might decide to take action and remove these apps from the App Store and Google Play. Here is the dashboard where you can see the events: https://nostr-media-alert.com/ .... .... There is definitely an argument to be made that the best course of action is just "do nothing" and wait and see if the apps get removed. From another perspective, it might be nice (in my opinion) if NORMIES, when they first sit down with a Nostr app, aren't immediately blasted with porn. One way to do this would be for relays to consume these "scores" we are producing (and others could produce also), and allow new users to "opt-in" to seeing hardcore porn in their feeds, instead of just like assuming that they will want to see it?

nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm I keep finding that there is some kind of data loss going on with the alby browser extension.... today for example I used it and it seems to have forgotten my nsec and generated a new one....

Replying to Avatar Rizful.com

#asknostr among the problems that Nostr faces, the child porn problem is a very, very, very bad problem.

A VERY bad problem.

What is the current thinking among developers about how to deal with this?

Nobody likes censorship, but the only solution I can think of (SO FAR) is running an image identification service that labels dangerous stuff like this, and then broadcasts a list of (images, notes, users?) who are scoring high on the "oh shit this is child porn" metric. Typically these systems just output a float between zero and 1, which is the score....

Is anyone working on this currently?

I have a good deal of experience of running ML services like image identification at scale, so this could be something interesting to work on for the community. (I also have a lot GPU power, and anyway, if you do it right, this actually doesn't take a ton of GPUs to do even for millions of images per day....)

It would seem straightforward to subscribe to all the nostr image uploaders, generate a score with 100 being "definite child porn" and 1 being "not child porn", and then broadcast maybe events of some kind to relays with this "opinion" about the image/media?

Maybe someone from the major clients like nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q or #coracle or nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg or nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 has a suggestion on how this should be done.

One way or another, this has to be done. 99.99% percent of normies, the first time they see child porn on #nostr ... if they see it once, they'll never come back.....

Is there an appropriate NIP to look at? nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 ? nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft ? nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr ?

@YakiHonne @fiatjaf @PABLOF7z @miljan @ hodlbod This proof of concept shows real-time events that we've found on Nostr relays which are likely bad enough that Google or Apple, if they discover them being "served" by an app like @primal or @Damus or @YakiHonne might decide to take action and remove these apps from the App Store and Google Play. Here is the dashboard where you can see the events: https://nostr-media-alert.com/ .... .... There is definitely an argument to be made that the best course of action is just "do nothing" and wait and see if the apps get removed. From another perspective, it might be nice (in my opinion) if NORMIES, when they first sit down with a Nostr app, aren't immediately blasted with porn. One way to do this would be for relays to consume these "scores" we are producing (and others could produce also), and allow new users to "opt-in" to seeing hardcore porn in their feeds, instead of just like assuming that they will want to see it?