BITKARROT on Nostr: Problem with Keet is the frontend is still not Open Source after 3 years. I am ...
Problem with Keet is the frontend is still not Open Source after 3 years. I am grinding on this hard because I was an early beta tester.
Can't really see the deets, unless you want decompile all of that javascript.
What are they hiding and why so long???
My guess is either they want a moat or they are insecure about other devs coming in for a look and outperforming them in a short time.
totally sus.
Maybe this note will get them to open it up.
Published at
2024-11-04 20:12:44Event JSON
{
"id": "ba637b67a2025c00a8e35bf6bd3774650c056002658197f830bf0e2a59cd2609",
"pubkey": "3878d95db7b854c3a0d3b2d6b7bf9bf28b36162be64326f5521ba71cf3b45a69",
"created_at": 1730751164,
"kind": 1,
"tags": [],
"content": "Problem with Keet is the frontend is still not Open Source after 3 years. I am grinding on this hard because I was an early beta tester. \n\nCan't really see the deets, unless you want decompile all of that javascript. \n\nWhat are they hiding and why so long??? \n\nMy guess is either they want a moat or they are insecure about other devs coming in for a look and outperforming them in a short time.\n\ntotally sus. \n\nMaybe this note will get them to open it up.",
"sig": "2d3c8a3a7a1f8269dda790ec47481d29adc1720c4069749df79a6c82c15a4839671dd8a57ddad4522e7ace9f12e993d008330f0c6abcce93673df4cecc22f599"
}
