damus will stop working when you follow around 1800+ people. the only thing I can think of is some algorithm that looks at all the people who haven't posted in awhile and only probabilistically include them in the filter.
The relay pool model (damus) straight up breaks when you follow too many people. The proper fix is have people spread across different relays (outbox), then you can break apart the large query into smaller ones.
TIL: Damus has a Dunbar's number
Jesus, my Dunbar number is a lot lower than 150 lol
Explains a lot
Any chance we could do like a Poisson distribution to determine the probability and filter those out? Or am I trying to way over complicate this?
We’ll just get outbox working and then we’ll see if that helps. nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8 has been working on getting nostrdb updated and the local relay model working, so hopefully we can start getting that going soon
Keep rockin guys. Most of this stuff is over my head, but I do work in forecasting and supply chain. Just trying to think about how to apply some of that to the Nostr world.
What about just better relay filtering? Follow lists could be their own relay and could be broken into multiple lists/ relays. Would be awesome if damus ran its own instance of relay.tools and just started spinning up relays left and right.
If "outbox" works, can you not divide the people you're following into chunks and use separate connections to the same relay?
We’re actually doing that now, but for some reason there are still issue we are trying to figure out. At some point it becomes a bandwidth issue regardless
Back in 2022 i had the idea of a custom query you would send to relays that was basically “give me all the notes whos authors are on my kind 3” no need to send your entire contact list each time, but its very ad hoc
This might be the current situation, but it doesn't seem fundamental to me. If there's a way to reliably reproduce these issues it should be straightforward to optimize
nostr:npub1rzg96zjavgatsx5ch2vvtq4atatly5rvdwqgjp0utxw45zeznvyqfdkxve couldn't find your note about the unfollow tool or id have added it here. Also, looks like number closer to 1,800 than 1k
Maybe this has changed but I remember seeing a clear difference when going lower than 1K. Suddenly notes weren’t being rejected by relays. This was many others experience as well
Here’s the note. Might be a different issue. Not sure
nostr:note1htu2eecyyevzf6gsulcuemplvzazxhuc00lp26ted2zeqht5z6qsd4ggvr
Ah thanks. I'll stick with sub 1k just to be safe. ⭕️🐸
thats what I do. maybe we need to put big warning sign in the app when the user gets in the 1000+ range
Hey jb. Tagged you in a note other day that's related. For some reason the latest people I try to follow get automatically unfollowed a day or so later. Similarly, unfollowing people seems to get undone too. Not trying to harp on my pet issue, just in case you know my issue or want to make a note. Thanks
#damus
was damus the only client you were using?
No I use primal 5% of the time for reasons. I try not to frantically click things there that might conflict with actions I made on Damus (follow/unfollows).
do you ever follow/unfollow on primal? that might wipe out your damus actions since they may not be synced with other relays
I thought about that. Possible i did early on, but I avoid it now and still have issue. Example is nostr:npub1c428ddtenhga69v2aj8p7vvlrnww7fmgjxt8pu0d868nuue6zueqz5yl59 who every 2-3 days I am no longer following. 🤷♂️
Clicking to your profile page kills Amethyst 🤒 wonder if its from loading all your follows
seems ok here
Latest update (within last week) supposed to fix according to vitor, so might be ok if updated
stats say 92 follows but idiv. count is 800 or so on rough est./
I see 747. nostr:npub162zpxufpw8pnuytaf0gfxzkqtvk9rvcwkvppa7x57y3n7qkfpg4shatdhy are you using the same relay set on all clients you use?
Oh I didn't really understand rands comment. My guess is I do not. I'll align them better and see what that does. In back of my head I think it could be connected to me following that hashtag (the thing that was crashing amethyst when viewing my profile)
Surprisingly, Looks like I am consistent across two clients I use.
I follow something like 925 people, so wanted to trim some so I could add while staying below 1k, but yeah it's screwy for some reason. Not a huge deal as it only seems to effect latest follows like enigma lol
What happens if you remove the primal relay? (When not on primal)
Will give it a try and let you know (takes a day or two for stuff to happen). Thanks node/quant
The primal one is their proprietary caching service. You need it for primal to work. I don’t think you do on Damus though. Might solve your problem. Only trial and error will tell
Is it actually proprietary? I thought it was all open source
Maybe I added it when I was doing primal NWC zapping a while back. Will follow up in couple days 🫡
Yeah, have notified vitor several times, been that way a few months but next release should fix . Not sure if related
1800 per phone 😂
Sounds like a reason for people to repost, since folks can't follow everyone
Maybe bin them by last seen, then check more recent bins more frequently. This ensures that people that are only on a couple times a week get almost the same priority as those who are on daily.
What happens if you follow 2k people who post all the time? What about 10k? Damas won't have this problem, but what about specialized clients that follow 100k+?
We might need to add separate commands to the protocol to upload filter sets that can be referenced in queries. Or maybe a way to reference a follow list note as a query param.
I want feeds for bins by post frequency anyway, I've talked about that a lot and I think it would be pretty cool. just need to calculate post frequency to begin with...
I guess I was thinking of doing the lazy and cheap thing: just use last post time. It's probably good enough for most things.
