Plebstr was forcefully changed to Openvibe recently. I wouldn't really mind all that much if:
1) Plebstr had zaps working. Openvibe does not. Zaps imho are a core functionality for a nostr client. Releasing without them is ok, but not force switching users without them.
2) I was notified this was going to happen. The only reason why I even know what happened is that I accidentally stumbled upon a post talking about this in my feed.
Forcefully replacing a not perfect, but working app with an unfinished one without notifiyng me is something I really do not applaud. As much as I like the idea of interoperability with other platforms/protocols, this makes me wonder whether to even give openvibe a chance.
Not to be
#plebstr #openvibe
ancapone / An Capone 🌗
npub1363…mepl
2024-03-20 17:12:18
Author Public Key
npub1363f98sscslf6hhq9gkh9fjhsvn8x7p4h6577sd969n9yhhgg7yqwpmeplPublished at
2024-03-20 17:12:18Event JSON
{
"id": "b92b3e11d8d83ef13b86d7a6e8211d9b568b6d38c9b9ff3c43988330d9f47657",
"pubkey": "8ea2929e10c43e9d5ee02a2d72a6578326737835bea9ef41a5d166525ee84788",
"created_at": 1710951138,
"kind": 1,
"tags": [],
"content": "Plebstr was forcefully changed to Openvibe recently. I wouldn't really mind all that much if:\n1) Plebstr had zaps working. Openvibe does not. Zaps imho are a core functionality for a nostr client. Releasing without them is ok, but not force switching users without them.\n2) I was notified this was going to happen. The only reason why I even know what happened is that I accidentally stumbled upon a post talking about this in my feed.\n\nForcefully replacing a not perfect, but working app with an unfinished one without notifiyng me is something I really do not applaud. As much as I like the idea of interoperability with other platforms/protocols, this makes me wonder whether to even give openvibe a chance.\n\nNot to be \n\n#plebstr #openvibe ",
"sig": "15fa1e1ced265ea1be337f30a803b2a7c1b0d9e9e4f37289758d53aa4ac3df5d6ba81f0dde820c87b0094ca7f66f373a38923b4674cbf76655afbcb70d9c76b8"
}