nostr:npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8

i see you guys aren't on the google play store, was wondering why thay is as typically its been apple store where devs seem to get more delays rolling out to the main app stores. Or is it less of a priority since side loading is possibly on android? Thanks ๐Ÿค™

We submitted Keychat to both the Apple Store and Google Play at the same time, but itโ€™s still under review on Google Play. You can download Keychat from Zapstore nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 in the meantime.

Reply to this note

Please Login to reply.

Discussion

Right on, ty for the explanation

Personally I would recommend avoiding Google Play Store, as a more apt name for it is Google Spyware

Its not for me, working through how itd look to help some friends use keychat

Yeah, that's what I figured ๐Ÿ‘

In testing such things though, i got asked to confirm my id before downloading amethyst from the playstore using a burner google acct ๐Ÿคฎ That was jarring, thankful there are such good sideloading options in the android ecosystem.

Another question, i really appreciate the transparency in the raw data in the messages showing which relays sent the message. Considering keychat uses signal esque encryption, it isnt much of an issue if a public relay like damus or primal carried the note since they dont get any data thatd link it to my npub, ya?

Also, i tested with a relay.tools relay with nip-42 auth required to write to the relay. The raw data in the keychat message states 'nip 42 auth required' which my npub is authorized. Does keychat have plans to support that ?

note1hd4z2rl2x0n404v88va6m4cm2yxpj4esmmv0tsjkaavt9t0nmdys9kwnnd