My conclusion in the #OnlyZaps experiment is that it should be an app's choice and not a user's choice.
Apps can optimize for offering reactions [x]OR or not offering reactions. Doing both well at the same time (giving the user a choice to enable or not) is a herculean (UX) effort for the small teams we have today.
Don't like the choice your client has made? Find and fund another client that aligns with your choice. I can guarantee you will be better served.
Vitor Pamplona
npub1gcx…nj5z
2023-04-23 00:05:29
Author Public Key
npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5zPublished at
2023-04-23 00:05:29Event JSON
{
"id": "5e5eb04ab6e893b7d15cce51bff484ae51c32d7d6057f8fe5eb3763fbc355596",
"pubkey": "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"created_at": 1682201129,
"kind": 1,
"tags": [
[
"t",
"onlyzaps"
]
],
"content": "My conclusion in the #OnlyZaps experiment is that it should be an app's choice and not a user's choice. \n\nApps can optimize for offering reactions [x]OR or not offering reactions. Doing both well at the same time (giving the user a choice to enable or not) is a herculean (UX) effort for the small teams we have today. \n\nDon't like the choice your client has made? Find and fund another client that aligns with your choice. I can guarantee you will be better served. ",
"sig": "4071b35b037781e313abeb7e985123451b05c8edd59abc2edcf5af905b14060d4e19c6e9f0665a122a397a9e5eff80b01e11439c5a88481a08775e8ba995ead6"
}