fiatjaf
· 1w
The NIPs look good and I like the use case, finally someone seems to be doing this right.
The problem that remains is how to properly source this content. The only thing that comes to my mind is, as ...
Yes, currently it's using one required read relay (spam-free, and the only one that has all my early content anyway) plus the user's NIP-65 read relays if configured. Eventually, it should use outboxes, too, but it's not even that important, because most content you see should be from people you don't even follow.
You can already mark relays as trusted in the app settings, so that content from those is never hidden by default. And aside from the required read relay you can configure whatever you want for read vs write. Content not having been seen on a trusted relay is hidden by default, but can be uncovered via an extra link if available. (Already implemented.)
Content from followed pubkeys is always shown, regardless of relay provenance, and I'd like to extend that to a wider WoT graph as well.
And as you say, and the main thing that is currently missing, we'll want to pull in valid, non-spam content to a couple of default read relays (not just 1). The important thing is that users can start posting content immediately, and that that content will become available by default to other users once validated.
