So it won't connect to LNBits via its own wallet API, but you can install the LNDHub extension in LNBits and that will allow Zeus to connect to each individual wallet you set up within LNBits.
Will these lightning addresses support Nostr zap notes (kind 9735)?
I love Zeus. Very simple and straight forward and supports many ways of connecting.
Kind 9735 is the kindest kind of all kinds.
Nice! Is there a plan for these to make it to the f-droid repositories or have these on a repository that could be added to F-droid?
I have a burner number and bogus email address on the ready for situations like these. That's all anyone will get from me.
Also, ya, you can print my receipt out. I don't need you to email it to me just so you can then flood my inbox later, thanks.
I did that to a directory the other day. I habitually chown'd when I meant to chmod. doh!
A few Nostr client features I would like to see:
Currently, most clients I've seen blast every relay for request of notes from all your followers. This results in a ton of bandwidth usage unless you really become selective in which relays you're requesting from. But if you limit the number of relays you request from, you limit the reach of where you can see notes from which can reduce the decentralization of Nostr.
Be requesting following notes from all relays, as most people have probably noticed, this results in quite a bit of bandwidth usage. Since most of us are using Nostr on our mobile phones, our data plans can take a pretty heavy hit.
What I would love to see in some clients is statistics on what percentage of those we follow we are seeing notes for on each of our relays. Now, there will always be those we follow that aren't posting notes and so we won't see anything from them on any relay, but overall we'll get a better idea as to which relays are the most popular among the people we're following. I know Amethyst on Android provides download statistics for each of the relays, but I would love to see what percentage of those we follow are being seen on each relay we request from.
This leads me to my next feature request. As I mentioned earlier, most clients blast every relay for requests of our entire following list. The reason clients do this is because Nostr is not meant to be a reliable network and you never know which relays will be up or down at any given time. For client performance reasons, the client simply requests from every relay in a best effort attempt to get notes back. If clients had to wait for a relay to return results back before requesting from the next relay, the experience would be very slow for the enduser.
However, if given the statistics of which relays among those we follow are most popular, it would be awesome if the enduser had a choice in how the client would retrieve notes from relays. On Wifi? Blast away with requests to every relay. On mobile data? Sequentially request notes from relays in order of relay preference. Allow the enduser to specify relays in order of preference. Preference could be "where most of my following are" or "these relays perform best", etc. Doesn't matter the reasoning, just allow the user to choose. Then the client will request notes from each relay in sequential order. After receiving notes from people on relay #1, the client will then ONLY request notes from relay #2 for those you follow that we're not received from relay #1. This will avoid the downloading of duplicate notes and thus avoid a ton of bandwidth usage. This sequential requesting will continue through each of your preferred relays. A timeout can be set to limit waiting too long before proceeding to request from the next relay. Performance will obviously not be as good when it comes to retreiving notes, but giving the enduser an option to choose how the client retrieves notes would be a huge benefit, especially when using Nostr over cell networks.
It I'd also funny how everyone has their own different preferences. I love heat and am comfortable at temperatures 80F+. Anything cooler than 70F and I get chilly and need to be in long sleeves. My wife on the other hand is the polar (no pun intended) opposite.
Needless to say the thermostat is kept busy between the two of us. Haha
Ya, good point. Looks like it was last updated on the Playstore in Oct, 2022 and is based on Chrome 107. Not good. Looks like there is another browser called Mises that supports extensions, but is based on an even older version of Chrome 105. Would love an Android browser that allows extensions. I'll probably stick with native apps for now.
Testing out my nostr relay multiplexer to see if I can save some mobile bandwidth.
I wrote a guide using kiwi browser for Android https://orangepill.dev/nostr-guides/guide-nostr-key-generation-and-management/#steps-to-setup-and-use-on-android-devices
Oh nice! I didn't realize Kiwi browser supported extensions. Very cool! Thanks!
Would really love something for Android.
I was just on the bird app and went to go zap someone and then realized I couldn't....how boring.
Same. Vegan diet and play tennis 4 times a week. Blood work is great with ApoB levels @ 50-65mg/dL.
I think this has a lot to do with it. Nostrgram is a great desktop client, so it makes sense that it gets the most use while people are sitting at their desks during the week.
There was some discussing about this with the original proposal of NIP-57. I think it was a mistake to go with LNURL rather than some nostr specific implementation. With one-sided verification of the zap, it is too easy to forge that zaps were made. It works for now and is easy to roll out, but I think longterm we'll need a better nostr specific solution.
