> some content can not be translated, or the translation can not be displayed
Translations are always a guess and best effort. We could potentially add features to mitigate the issue, such as a setting to define your own language prediction minimum confidence level (currently 50%), or allow you to force translation from the language of choice.
> when Damus is relaunched, it will re-request the translation of the previously translated content
We also don’t cache the original notes when Damus is relaunched. If we want to go down the route of caching translations, we probably also want to cache the original notes. I’ll ask the Damus contributors what they think about that.
Here’s the fix: https://github.com/damus-io/damus/pull/998
I’m able to hide the keyboard if I tap on other input fields. Give that a try.
It’s a known bug on Damus. Sorry, we just haven’t gotten to it yet.
Yes, but I think that can remain an implementation detail. Don’t think it needs to be part of the Nostr protocol. In fact, the problem described here seems like a small corner case and very theoretical, and the proposed solution seems a bit over engineered comparatively. Any request can be man-in-the-middled. There isn’t really anything specific to translations. HTTPS solves some of this I think.
I looked at that a bit. The Swift hashtag parsing code handles Unicode properly but the C hashtag parsing code does not, and the latter is the one that needs fixing, I believe.
Agreed. I don’t understand why this is necessary.
No idea but I’ve had it enabled before I found out about Nostr and it’s been fine.
#[0] jack intensifies scroll bug
(epilepsy warning) https://nostr.build/av/nostr.build_65b7bf275d827c825dc310a5a6f0ec9812c084a1c3dcc48be0b4b2d3e94a4904.mov
