Avatar
CappyNate🍁
18fcc139950a9cce3fee5ee4f4f46f3e3f0e338277dcc8bcd692b3ce0e94084e
Tech, money, startups, free-markets. Sidelined by undiagnosed neurological issues since 2020. 🕔 heatstr.vercel.app (Busiest Nostr hours) Banned by LinkedIn Nov 11, 2024.

Yes. But with this, clients need to make money. Subscriptions and donations are not a viable business model.

The only one that works is ads.

But a client that is not greedy with ad insertions, and shares that ad revenue with creators AND RELAYS, will both grow their bottom line and Nostr's userbase too. So so so important.

Thank god people are finally making sense on here. I thought I was in a parallel universe when boneheads were literally hating on algos.

We want algos. Good algos.

Capital G was my fav from them. Way back when.

I actually think Nostr has the easiest onboarding even. When explained simply:

1) Download Primal

2) Generate NSEC (don't lose, don't share).

3) Start posting.

Onboard in under 20sec just like it should be.

The confusion I get from others lies in the Nostr's structure. The "well how does it work if it's decentralized" or "what are clients, relays, protocols, zaps, events, etc".

I just skip explaining all that at the start so they can just use it first. Let them fill in the blanks later via exploration.

Thanks bud.

How did it get nuked? Fiatjaf posted a follower backup tool, I need to find the link.

Yup. As an ex semi-pro track athlete, creatine is the most effective supplement that isn't banned. Moderation, like anything.

That's client side though.

A good client aggregates then displays content. From what I can tell, Primal certainly does this and caches on their own.

It's then up to the client's algo to parse through that giant mess of events to generate a feed for each user.

Step 1 and 2 are already done. Instead of doing the final step 3, they go build donkey shit. lol

Nostr will explode when a client offers proper UX.

Nostr is just the server.

Right now, content distribution is utter shit. No algo. No notifications. No client cash flow.

It's a client-side issue, not a protocol issue. Whatever client solves this will both win, and #grownostr as a result.