Right after updating to the new version I get this: 
#noStrudel v0.38.0 Is finally released. I've added and changed a ton of stuff and honestly should have released this as multiple smaller versions but I kept getting distracted.
Some of the notable changes:
- Support for nsecbunker and the new OAuth flow
- Added simple "Launchpad" view (most stuff will be added in the future)
- Restore scroll position when returning to the timeline
- Show unavailable events in threads
- Organized all the "other stuff" in a tools page
- Added support to cache events in local relays instead of the browsers cache
- And a ton more, read them all in the https://github.com/hzrd149/nostrudel/blob/master/CHANGELOG.md#0380 changelog
If you want to play around with all the new features you can find the client at https://nostrudel.ninja or you can run it locally using docker "docker run --rm -p 8080:80 ghcr.io/hzrd149/nostrudel:0.38"
And If you the app useful feel free to setup an autozap using https://www.zapplepay.com/autozap/npub1wyuh3scfgzqmxn709a2fzuemps389rxnk7nfgege6s847zze3tuqfl87ez
Discussion
Same here
The app is no longer using your NIP-65 relay list as the default relays to get your feed. This is in perpetration for using the gossip model to get the feed.
also In future updates my plan is to start prompting users to set their Inbox and Outbox relays correctly (4-5) instead of what it is right now with 20+
So now you can configure 20+ relays locally for the app to use and keep your Inbox / Outbox set to a reasonable 4-5
So when I select some relays there it will not interfere with other clients?
yes, I probably should have put a not about that on the UI but the "app relays" are only stored locally
This should allow you to switch them at any time. or switch to only a single relay 😁
I think this is much closer to the right way clients should interact with relays they connect to.
NIP-65 is outwards facing; is to announce to others how to communicate with you; but this is a separate thing of what relays you want a specific client to connect to.
NIP-65 even explicitly says so.
I think Relay Sets as defined in NIP-51 can be A way of grouping this relays you want a client to connect to
“Connect to my ‘work’ relay set”
“Connect to my ‘gardening’ relay set”
if users say "i wannan this relays" and client uses them and publishes duly
then this app is dogshit
seriously, "gossip model" is the most retarded shit and has retarded the client development because what the fuck, i publish a relay list, and then i go to another client and it goes GOSSIP fuck you
i should point out that this is a big problem for relay developers
how do you find a client that is gonna actually test your relay if it's running off on its own choosing arbitrary random, probably dev chosen relays?
uh, no. respect the 65 bro fucks sake
noStrudel is not using a gossip model yet. but its something I would like to implement. however whats been keeping me from implementing it is I need to find a way to ask the users permission (or make them aware) that the client is going to connect to random relays to get the feed.
Its also the reason I have not implemented NIP-42 yet. because I don't want to sign auth requests for the user in the background without at least making them aware first
its nice to encounter developers with humility and integrity. thanks.
