(#5gswu6q) @crunch Oh that's very interesting... You _may_ have found a bug perhaps...
What can you tell me about what `salty-chat -d read` says?
And can you message yourself?
In fact try to also message my Echo bot at `echo@mills.io`
matched #asztpnq score:11.34
Search by:
Search by 1 mentions:
(#5gswu6q) if you did somehow generate a new key, I'll have to delete your `cruned@mills.io` account on my broker and you'll have to delete your key and do this all over again ๐
matched #b6mzdja score:11.34
Search by:
Search by 1 tags:
(#5gswu6q) @crunch I'm assuming `kex1xvt0ckp9qqhpda2x9sj9399sw8ze0nmem858ca4p38jdl2y0lu7sy3f40d` is your public key? Also are you using the chat tui? I tried sending you messages back but I'm not sure if you received them? ๐
matched #dcs4ota score:11.34
Search by:
Search by 1 mentions:
(#5gswu6q) @prologic
here you go, getting anything through on the echo? Because straight away for this one - I'm getting a decryption error as soon as 'test' is sent
Is there a way to force it to use another key - it's trying to use bread.key but it's also created crunched.key - both with vastly different tokens but both pertaining to the same user? crunched@mills.io
matched #n4wwgjq score:11.34
Search by:
Search by 1 mentions: