The menu has been redesigned and will be available in the next version.
Discussion
It would be cool to have a simple way to switch mini-apps, just like we have in the desktop version.
Do you have any good ideas? Something like what you mentioned last time about switching apps on a Samsung phone?
Yes, I had talked about the Edges panel, it is discreet and allows us to change apps easily, based on what we pined and the last ones accessed.
https://video.nostr.build/add4b6bf8b1cd33d8616f0d2b5c16ba7404396c3e3e2a84f55e7315a764a9205.mp4
The most important thing is that nothing is under the navigation bar. I have Android 15 on a Fairphone 4. However, I have seen this problem in another app recently, so I wonder if this could be a problem with Android 15 as well. The FP4 had Android 13 before.
nostr:nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qnse3k, Keychat has an unexpectedly amazing and fast browser, and it's great for focus because it only has one tab open at a time. Despite this, I missed Adblock, background audio playback, and some screenshot protection.
Do you plan to release these, or some of these, features in the future? Anyway, congratulations on the project!
Thanks! The Keychat browser is not a standalone browser β it simply uses the built-in WebView from the operating system. Weβll prioritize enabling background playback for audio and video mini-apps first. Ad blocking is something weβll work on a bit later.
Could you clarify what you mean by βscreenshot protectionβ? For example, are you thinking about blocking screenshots on sensitive pages, or something else?
Yes, blocking screenshots and screen recording would be good, but I mean for the entire app, especially when biometric protection is enabled; that would be a very good combination. Or just a button, leaving it optional.
Will keychat support dark mode for all websites?
Keychat uses the systemβs built-in WebView rather than its own browser engine, so we canβt reliably force a perfect dark mode on every website.
Weβll give it a try and see how well it works.
It would be great, I believe almost everyone prefers dark mode on the web, if they could, it would be a great addition to the project and would help with the adoption of Keychat and Nostr, even though is just a small detail.
nostr:nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qnse3k Why does Keychat show up as "Weak encryption" when I receive NIP-17 messages via Amethyst? Is it a problem with Amethyst and other clients, a bug, or does Keychat have a different encryption method?
And is there a way to make this warning less "scary" lol, cool app, however
The encryption key in NIP-17 does not change, so NIP-17 messages also lack forward secrecy and backward secrecy. Once the private key is leaked, both historical and future messages will be compromised.
One-on-one chats in Keychat are encrypted using the Signal protocol.
π
yeah, keychat's not wrong here. signal protocol > nip-17 for privacy - forward secrecy matters. the "weak encryption" warning is legit.
but also... that warning is the client being honest. nip-17 is like postcard encryption - once someone gets your keys, it's **all** compromised. no fwd secrecy, no backward secrecy.
if you want to chill that warning down, maybe bug your client devs to make it less dramatic lol. or just use vectors for nip-17 dms - we show it as giftwrap but don't scaremonger.
Interesting, so basically Keychat has a better way to encrypt the messages. I don't know if you can answer me, but why is nostr:nprofile1qqs8t4ehcdrjgugzn3zgw6enp53gg2y2gfmekkg69m2d4gwxcpl04acpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcppemhxue69uhkummn9ekx7mp0w3radp the only one that doesn't have the compatibility to receive DMs?
nostr:nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qnse3k, nostr:nprofile1qqs24yz8xftq8kkdf7q5yzf4v7tn2ek78v0zp2y427mj3sa7f34ggjcpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz769wywf and nostr:nprofile1qqs9ajjs5p904ml92evlkayppdpx2n3zdrq6ejnw2wqphxrzmd62swspzamhxue69uhhxetpwf3kstnwdaejuar0v3shjtcqd533j can all receive DMs, even though the ways to encrypt the messages are slightly different
We donβt know.
White Noise is based on Marmot (An OpenMLS Nostr SDK), similarly to nostr:npub1hrujuc08r4zcdtn0u6ts7u7apldcjqgftz0z7stmaaz9hwaf9jxs66f3yh - it's VASTLY different from NIP-17 DMs, so it wonβt acknowledge previous DM types, but itβs significantly more secure (forward secrecy, etc).
Thank you!
This I think is also worth considering vis a vis the social-engineering attack surface of NIP17 groups. nostr:naddr1qvzqqqr4gupzpg78lsd0mrjnpljpa54n6u36dkxg03yh8hp4zhaesz2cwetgyahqqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyehxjup3xukkwun0w4c8xttrdah8getcwskkjmn2v43hg6t0dckkzar5v93kktgp2jr7v