"So... Who's a good follow around here?"

"Oh I recommend:

nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m nostr:npub1cn4t4cd78nm900qc2hhqte5aa8c9njm6qkfzw95tszufwcwtcnsq7g3vle nostr:npub1hu3hdctm5nkzd8gslnyedfr5ddz3z547jqcl5j88g4fame2jd08qh6h8nh nostr:npub1el3mgvtdjpfntdkwq446pmprpdv85v6rs85zh7dq9gvy7tgx37xs2kl27r nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc nostr:npub1a2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sdcw83a nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z... Or just follow the top 10 entries on the trending list."

"What clients are there?"

"For Android, use Amethyst and for iOS, use Damus."

"Know any good hashtags?"

"#coffeechain #asknostr and #ßitcoin"

"How do I do relay management?"

"Just subscribe to nos.lol and relay.damus.io."

Reply to this note

Please Login to reply.

Discussion

er.com/fxzR.gif

"Know any good hashtags?"

* Makes one up. *

(Did she do it on purpose?)

Sincerely humbled by the mention here, thank you. However I seriously don’t belong in this wonderful group of Nostriches, I’m just an idiot that enjoys shitposting and drinking red wine! 💜🫂

#plebchain 🫂

Hugs and love buttercup

I keep following you and Damus keeps undoing that 😂

CaptnJack refollows me at least 3 times daily.

Something is buggy.

This is actually another potentially subtle but huge problem with the protocol that is not what people think the standard issue is.

When you get to around 1400 follows you will start to hit relay note size limits for your contact list. This means only a few relays with larger contact size limits will accept your new follows.

This may lead to the perception that follows are dropped, but what is probably happening is that most relays are not getting your new contact list after a follow.

I am updating damus to use a local relay list in nostrdb so this alleviate the issue, but its still a big issue since your contact list will stop syncing eventually.

nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn has a completely new way to do follows with individual events, but it would be a huge hardfork on the protocol.

Ok stupid question from a non-nostr dev, why didn’t the protocol have individual events for your contact list? That seems really obvious when you’re designing stuff like this

I would not say that it’s obvious, kind3 was simple and it has worked for years. There werent even 1400 people on the network when it first came out. If we over complicated the protocol on day 1 by trying to plan for every future scenario it might not have taken off.

Event sourcing contact list events *is* more complicated. It takes more storage space, and hits relay return limits (500) if you’re trying to pull the full list, which forces you to do multiple paginated queries to sync your list. It’s doable, just a bit annoying.

Sinplicity is nice, when you're starting off, and they probably didn't anticipate it exploding this quickly.

You can see the same issue with the kind and NIP-numbering. Probably didn't realize how many variations this would balloon to, so they didn't plan for a modular or hierarchical structure.

99 probably seemed like a pretty big number. 😂

And now it's like

This explains a lot.

Thank you Will for staying on top of the game and keeping Damus the best iOS client. Preciate you man.