nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z man, the outbox build is totally unusable for me.. wat are we gonna do :worriedface:
I feel bad now for thinking it was a good idea. Although it is pretty nice for responding to notes, just not feeds?
Why is it unusable? What's happening?
I think it's overwhelmed connecting to relays.. The feed is stalled out showing mostly just my notes, and then a very thin set of other notes. I miss many notes that should be there. Says 1/900 connected type thing, or at most sometimes 100.
Hum.. does it open like that or it gets there with usage?
Umm, I was feeling like it was working ok, but I realized that was in a particular thread view seemed more complete, but the main view, very quickly became un-usable after just a few times opening it. I tried hard close, and soft close, .. just updated it today to see if anything was better.
Unusable just means it doesn't update, right? It's not slow to scroll, switch pages or anything like that.
I wonder if an exception is killing the thread that updates the feed and it just stays stale. Does that seem that could be it?
Right, it isn't slow in the app, just the app doesn't load very many notes. I have TOR turned off and I mentioned I do see a lot of dns queries being throttled by android itself, so it basically can't connect to anything I think (or very few, like the first however many.. I think it just can't connect. Now that I think about it, maybe that's why it worked better when I first ran it cause TOR is on for everything by default..
Very interesting. Tor will be the default because it is indeed faster, but I will test without it to see.
This is on a real phone, right? Not on the emulator (which has some issues)
on graphene pixel 8a yeah.
What's the maximum it connects to?
It's hit or miss. Earlier I opened it and it only said 1/900. I opened it again just now it said 346/900.
Hum... The 1/900 seems like something else. Maybe there is a conflict when starting..
yeah, i mean, any time the phone screen turns off, or i switch apps, it reconnects and that was when I was seeing a lot of it exhausting the dns query pool of 256 it said.. and basically just tons of unable to connect errors.
It's weird because the app waits 30 seconds to disconnect after you send it to the background.
yeah, I'll do some more testing, it had not occured to me that TOR would be faster because it doesn't have to use DNS.. It could be the VPN provider too, just hating me for doing all these lookups every minute or so lol. Hmm. I have a hard time with this 900 relay # too, I mean, that's one relay per follow, seems like the absolute worst case it would try to connect to all of them.
You know what.. you do have a LOT of repetitions, like many different filter.nostr.wine relays. Maybe that's the issue with DNS.
Or maybe we just need to chuck connections to multiple seconds. I saw somebody online saying that it is benefitial to not start everything at once.
I'm unsure if graphene has extra protections in place for the network stack too, do we need to crowd fund you a graphene phone for testing?
Either way, yeah I think most network hardware or software will balk at 900 lookups in a few seconds.. unless it's hitting a good cache. Which is probably flushed each time I switch VPN.
Are you using with VPNs?
yes mostly, except for when i forget. tried a few times without and still got the dns throttle
usually yes. i tested it a few times without and its the same.
like right now my feed is just you me and one other person in the last *hour (conversation tab). I know for sure there is more than that going on ..
Is the app being killed all the time? I will do some testing on this.
i think so, i mean i typically only open it for a few minutes at a time normal usage, and with not many notes in there yeah i keep closing or switching away..
the logcats did say it closes connections pretty quick, and or, reconnects regardless each time (its always done that tho?)
this was my main concern before switching over to it. you basically need to make sure everything is super optimized and hardened. i also can't imagine doing it without the local relay model.
