@mitch @silas Here's the ones that support NWC: https://github.com/getAlby/awesome-nwc?tab=readme-ov-file#nwc-wallets
Lightning Node Connect is another option, though it has much less support https://github.com/lightninglabs/lightning-node-connect
There's always direct connecting to nodes via Tor, but I don't know how willing app devs are to do that.
@alecksgates I mean, it's not the only one.
@alecksgates But I guess we do have semi-stable identifiers in the form of Lightning wallets. That's probably why we've abused it for this manner.
The Lightning wallet is our social network.
@alecksgates Nostr sort of got that right by having the payment sent to the wallet and the metadata sent back to Nostr. They still comingle the two in part of the LNURL process though.
It's also easier to do that with a social network where you can look up people in a social graph and send them a message/data.
We don't really have an equivalent other than the socialInteract tag. Those can change over time and vary across feeds.
@alecksgates The comments are honestly more important than the payments for the artists. They like to know that people are listening and enjoying their music.
@alecksgates Musicians don't know what shows their music is being played on. The music podcasts pick up and play whatever songs they want to from the index.
They would need to check pretty much every podcast/music podcast to see which one played their music.
@alecksgates The apps are hosting this metadata service, but there's no reason why it couldn't be moved to the podcaster host and pointed to in the feed with your metaBoost tag.
That would work well if you're the main podcaster, but how would guests and musicians know where to find the info?
Musicians have their music played on many different music shows and podcasts. They would need some way to collect and aggregate that data.
@alecksgates Sending the URL in the wallet transaction lets that person know they have new metadata to check. How would they know that otherwise?
I agree it's not the best solution but rather the best one that we have that's been adopted so far.
The best one would be one that works with Monero and any other value method besides Lightning.
@alecksgates The new metadata is being hosted by the apps on their servers rather than the wallets. That's not really a great solution either, but it's the best we have so far.
@dave @ChadF @js I grabbed the latest copy of this https://developers.hive.io/quickstart/#quickstart-hive-full-nodes
The api.openhive.network and hiveapi.actifit.io endpoints weren't working for me earlier. hive-api.3speak.tv and hive-api.arcange.eu weren't working either, but those are flagged as down. My bot is primarily using api.deathwing.me now.
Interesting that that one uses v1.28.0 whereas the others are using v1.28.3. I wonder if there's a version difference that I'm not accounting for?
