In fact, it might only work at the client/application layer since other relays would pollute the ordering.
I know Primal has their own backend that sits in front of relays. This type of behavior will probably become the norm.
In fact, it might only work at the client/application layer since other relays would pollute the ordering.
I know Primal has their own backend that sits in front of relays. This type of behavior will probably become the norm.
Well thought out, you would have to turn on just that relay to get the experience. I don't know if it would be a pattern but we can see new clients behaving this way.
It's too much to ask a user to disable other relays to get this UX; best for the application itself to multiplex the user's relays, index them, then provide this view into their content.
Yes, I agree that the experience is not good.
I'm not a developer. But I would find value with an option that resides on the client.
With following options:
1- Algo on/off
2 - weekday lunchtime Algo. I have a few minutes and want to see higher weighted content based on specific criteria
3- weekend evening Algo. I have more time and different attributes are applied to content that is more broad.
I can set this on my end via my client and effects no one else's feed.
My2sats.