Thank you for the tough love, fiat 😅

Yes, the "follows who follow" IS a WoT API service - there is no other realistic way to solve this problem.

That said we're slowly working to make this service provider: (a) faster and more stable, (b) a DVM or more likely return a signed nostr message - vs the current plain response-, (c) some client-side verification, (d) allow swapping service providers, once we settle on a standard.

These WoT service providers obviously will compete in a nostr open market.

nostr:nevent1qqsqqqyq62rlh8hgy74vmhs5lad7u36m5lqvzn2c87cm5h2vhxq9psgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5psgqqqqqqspp6zhy

Reply to this note

Please Login to reply.

Discussion

What? Why would it need an API? All nostr data is public and searchable by connecting to a few relays no?

Nostr was designed poorly and relay admins and devs are lazy so wot is what they came up with to ruin nostr

You say poorly, I say practically.

You say devs are lazy, I agree.

Then without any facts or leading arguments... conspiracy theory.

So relays being an open spam box is practical?

Nostr started small and basic. This is what has allowed it to have so many contributors and products being built around it. This is what I call practical.

Creating an open network that everyone can use at scale is hard, spam has never beem solved at the protocol level.

lol did you miss out on the entire Fediverse, Matrix, and XMPP? All designed way better

Subjective.

Sometimes all you need is a bunch of sticks to prop up a thing, not a perfectly crafted table. Sometimes that bunch of sticks is more versitile.

Hey, time will tell.

dude, nobody designs software this way........This is a day 1 problem...

it's really biting them in the nuts now isn't it?

Is it?

Yes. lol. You know nothing about software huh

My nostr experience is pretty fine, for social media, for zaps, for keeping a private spreadsheet via sheetstr, and for blogging.

I also don't see a wave of nostr devs getting frustrated with technical debt or bad design and quitting, heck I see interest growing.

Look out the other window friend.

Relays do not provide this kind of data aggregation

I just wanted to say I love zap.store and I use it for basically all my apk needs, by the way.

I like that you're keeping it somewhat closed for now, relying on your own relay with your own moderation, which to me is the right way to do it, as I said in nostr:naddr1qqyrze35vscrzvfcqyghwumn8ghj7enfv96x5ctx9e3k7mgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6qcyqqq823c0z85e2

But also I think that ideally you wouldn't rely on a centralized API. Having it be an open protocol helps, of course, but still it's not ideal. For some things I guess a centralized API is the best choice (like it's better to use Git servers instead of publishing code blobs or deltas as Nostr events) but it feels like this is a task that wouldn't require one? Or maybe it can be redesigned to work more as a relay instead of as a different protocol entirely? I don't know, just throwing my thoughts. What is the WoT service provider doing after all?

Thanks 🫂 and as I said in my quote-note the situation will improve with everything I mentioned.

It is a way to get the "follows who follow" feature in an optimal way (fast, data efficient, and sorted by pagerank to improve recognizability - if that word even exists). With the tradeoff of partially trusting a service provider.

Great article, btw.

💜