pippellia on Nostr: For WN specifically you could do a number of cool things without having to reinvent ...
For WN specifically you could do a number of cool things without having to reinvent the wheel or having to manage graph databases.
Whenever a user receives a message request, you can call Verify Reputation with "source" the user key, and "target" the requester key.
This will return a rank of the requester as well as the top followers of the requester (similar to primal top followers on profiles).
You can then present the information to the user, and if certain criteria are met you can automatically hide the request (e.g. the rank of the target is very low).
Also, when a user is searching another one to send a DM, you could improve the search by name by using SortAuthors.
Imagine you are searching "Fiatjaf", and your DB returns 420 profiles. You can then sort these very effectively using their reputations, and then paginate the results.
Whenever a user receives a message request, you can call Verify Reputation with "source" the user key, and "target" the requester key.
This will return a rank of the requester as well as the top followers of the requester (similar to primal top followers on profiles).
You can then present the information to the user, and if certain criteria are met you can automatically hide the request (e.g. the rank of the target is very low).
Also, when a user is searching another one to send a DM, you could improve the search by name by using SortAuthors.
Imagine you are searching "Fiatjaf", and your DB returns 420 profiles. You can then sort these very effectively using their reputations, and then paginate the results.