I assume nothing as I assume Iām a know it all
Discussion
š
I'm just imaginjng someone using a sports app, where the data set is limited to sportsy-things and the client is designed to maximize the sports information transmitted and the conversation is about sportsy stuff.
A sports app would probably be used in addition to Amethyst or Nostrudel or whatnot, and not instead of it.
Same with a recipe app, hiking app, or movie rating app.
Most definitely
I actually agree with what you wrote, on a different level. I understand the value added by having default relays or a standard filter, in an OtherStuff client. But I would prefer a client that allowed me to adjust both.
If I prefer my Biblestr show the Quran or Constitutional Law, that's my own business. Anything else is an attempt to limit access to information.
Another example would be a sports app that didn't include chess and darts. The app designers do not get to dictate what a "sport" is.
We have to own our own feed.
I think designing an app to be flexible is the only way to limit the forking of it. Nobody should get frustrated by the data they're being shown.
