Hey Desmond!

I’ll try return my aviators.

It’s bloat. You don’t need a client to create events and can imitate a client anyway. You know the poster pubkey, time of creation - what more do you need to follow up if critical?

Plus adding it means lazier coding as expecting a client (which will happen), means less exception or validation handling - and less robust implementations. Expect anything, never trust user input, validate everything.

Browser user agents are completely bull crap today - Apple iOS messages pretends it’s Facebook for previews, everything has WebKit/gecko, it’s just all incorrect bloat from a legacy time.

Optionally while testing is different and no real problem.

How does one apply to become sheriff?

Most iOS apps didn’t exist 3/4 months ago, at least publicly. Damus is around a year old (by memory) and now has lots of community pull requests with improvements.

Competition will come.

I think Nostr-rs-relay and some others have a gRPC hook that you can run some check before publishing is allowed. Paid member, or content or rate limit, etc.

I don’t know of anyone else using it, however I wrote a couple ML models and have a decent dataset for training. I use it successfully in production - however it only works for events with enough content, not reactions, reposts, meta, etc. Bayes model works with fewer resources than the FastAI model.

https://github.com/blakejakopovic/nostr-spam-detection

If you can filter spam, then it’s likely pretty good to scale as your grow.

Otherwise spam is around 10X non-spam events, if they add your relay or you sync from large relays.

We need to start educating people about cycles and how times of both scarcity and abundance will happen.

During growth phases, CEOs will hire like crazy because they don’t know how long it will last and they are competing against other behemoths.

During down turns, you simply can’t keep those heads employed and compete. It’s part capitalism and part innovation cycles.

Adding more employee protection, or hiring less people during growth phases doesn’t viable either, as both have significant side effects.

Being let go or made redundant is a hard time, and I sympathise. The government can’t stop it, or even minimise it in a meaningful way without side effects (including inflation).

I’m not defending CEO payouts or salaries. However a down cycle will last longer than any CEOs compensation package can prop up and keep all heads.

The best solution is an individuals diversity of income and to reduce reliance on a single income source or stream. Lessen the single point of failure (of income).

Bitcoin and Nostr can help empower individuals here.

I always liked this story of a simpler time. https://www.ssh.com/academy/ssh/port

I think this issue was that replaceable events kind range from 30,000 was defined before reserving 30,000-3 for lists, etc.

Everyone always seem to pick the first or last numbers in an open range.

Also, I don’t propose it gets auto-added to all URLs. There are privacy considerations too.

However a service can give you a referral link to share. But it can also be predictable too.

It’s more dynamic. And it gives reference to a Nostr identity. Maybe I want to strip referral codes unless they are in my Web of Trust or I follow them.

nostr:note178eyczcg68sdumn77xaslmtgdr6zfadx7zqgvgr5260l9jk566nqru4khd

The basic idea is dead simple payment for word of mouth (Nostr) referrals.

I actually don’t care how’s it’s implemented. The root idea was that I can post a link to a service (like Snort Premium, etc) with a checkout, where my link has a reference to my personal pubkey. Could even act like a coupon code and give a discount.

Then post checkout, and if that service gives referral rewards, that service can split or give a referral fee to that Nostr pubkey, as a referral payment reward/benefit. Use the Nostr pubkey (or other bech32 format with relays) to lookup their LNUrl Pay details - so it’s more dynamic.

#SadPanda 🐼

I think the #torrent events come from a RSS feed bot for EZTV. It’s a hashtag just added to all their feed entries, so it adds up over time.

Certainly I think advertising and a querying like a relay based torrent tracker or discovery protocol is possible for someone to build. Or even collectively.

Do you have a strategy around managing fake zaps? Or zap automation? Or I’ll zap your posts 10,000 sats, if you zap mine back 10,000?

At present zaps seem like value transfer, but once abused more widely, they are not exactly a measure of value.

And the furries a couple months before that. I wonder where they went?

Many thanks 😎

Something that could be interesting to develop for Nostr is a referrals extension for BTCPay or Lnbits.

Referrer is simply your pubkey. Add ?referrer=PUBKEY to the end of a link. Client apps can strip it off if you don’t want them. And upon payment/signup, that pubkey can get credited for the referral. Payment details looked up via Nostr profile.

There is some trust that you are being paid for each and every referral by the service, however, it’s a start anyway.

No need to sign up as a referrer. Leverages lightning. Instant payments. No problems with reverse payments.

I don’t want Nostr to turn into an ad space or marketing shitshow.. however if we can help people become more financially free from governments and a single income, while perhaps replacing marketing/advertising expense with kickback (word of mouth incentive) for a win, win, win, maybe it’s a good thing.

Yeah. I noticed this yesterday was a gap. Basically I don’t support lud16 values (email format of LNURL), only lud06, at present for ZAP validation.

I had a quick look, and I’m keen to get it working, but unsure the effort and any timeline as yet.

Nostr seems simple, but honestly the number of features and variances to try support or cater for, is very time consuming. Harder to find time as a sole dev atm.