This is the way to go. last version of noStrudel I hastily added support for client side WoT and filtering based on that and it didn't work well. I've been fighting performance issues ever since
ManiMe's avatar ManiMe
Prolly the most valuable thing to come of this @npub1heal...vp8p #wotathon will be that, by attracting all the WoT stakeholders with all their WoT ideas, we might FINALLY be able to build consensus around a WoT connect NIP standard … that everyone wants to implement! #priceless View quoted note →
View quoted note →

Replies (4)

You "hastily added support" in the last version and you already give up on doing this client side? I was very happy when I saw you added these filters just half an hour ago, so I'm concerned you are having second thoughts now! I had asked for this so often and have not noticed performance issues but even if I did, I'd trust this can be rectified. I'll zap you to help you get this fixed ;)
Why do we need a wot nip? Wot is subjective anyway, so there can't be a "right way" to do it. Service providers are fine, but I see it as a client's prerogative to choose how it's implemented.
I'm not completely giving up hope for it, but I want to explore other options before trying to optimize it further Mainly looking for a better way to do username search since trying to build and then index the WoT ends up killing most browsers that are not running on a desktop machine
I agree, but it’s worth the try to find / discover how this concept could be ‘standarized’ (or multiple, I dunno)