6 ms·
The important things is to keep the limiting/filtering features client-side. That keeps the user in control and the power dynamic in balance. The protocol shoul
by _bxg1 9y ago
The important things is to keep the limiting/filtering features client-side. That keeps the user in control and the power dynamic in balance. The protocol should provide as much information as possible (priority level, tags, maybe even attributes for brand name or a logo image link), and it should be up to the client to provide the best possible experience given that information. That also allows for different clients for different types of users.
One thing that could also be interesting is standardizing subscription/donation information as part of the protocol itself. So that users can easily do those things across all their sources at once (via their client), rather than going to separate websites and walking through their unique subscription forms.