@nprofile1q... sounds good. you want me to open to you instead? Are you more in need of inbound or outbound?

@nprofile1q... @nprofile1q... @nprofile1q... @nprofile1q... @nprofile1q... I am actually using [email protected] now as my lnaddress. It has a proper keysend .well-known fallback, but the apps don't seem to even attempt to send any metadata with the payment, just a plain lightning payment to my address. Why might this be? Is the logic hard-coded to only gracefully handle alby and fountain lnaddresses?

@nprofile1q...
This must not be working, I've got boosts from several songs this week that don't show up here
@nprofile1q... @nprofile1q...

@nprofile1q... @nprofile1q... @nprofile1q... no worries, joins are always tricky!

@nprofile1q... @nprofile1q... @nprofile1q... also for what it's worth, after I visit the Podroll Atlas I can't hit my RSS feed because that service basically DDoS'd my feed, so when I try to hit my feed now it gives me a 492 "too many requests" error 💀

@nprofile1q... @nprofile1q... @nprofile1q... nope, we have 22 shows in the podroll tag currently and it's the most we've ever had. We don't cycle thru them, I think about 14 or so have been in there for over a year and the rest are relatively new adds, but we've never had more than 2 dozen in there.

@nprofile1q... The atlas also falsely shows our podcast as recommending over 6k podcasts:

https://atlas.rss.io/#946122

The problem is our feed lists exactly 22 podcasts in our podroll. We have *never* had more shows than this listed, not even close lol. Something definitely is off somewhere in the chain of data.

cc @nprofile1q...

@nprofile1q... @nprofile1q... well that's probably the biggest problem in development and in any human collaboration attempt in general, really. we can only do what we can do. so it's great to say the hosts should do it, i tend to agree because that makes sense, but the reality is some hosts will and some won't, the bigger they are the longer change takes usually, and each individual can only affect the parts we have a direct hand in.

i don't see a big privacy difference between relays vs hosts tho

@nprofile1q...

yeah this is another option, everyone has read but write is limited

you have a lot of flexibility with a relay. and you can allow access via pseudonymous provable identities which is convenient.
@nprofile1q... @nprofile1q...

@nprofile1q... @nprofile1q... you could whitelist pubkeys you want to give read/write to or read only to. then they in turn could use the data stored there for whatever they need it for on their end and likewise you on yours.