"Buzz"-Groupchat of Spot-On compatibility with "Fire"-Groupchat of Smoke Messenger

[Sammysupport]

"Buzz"-Groupchat of Spot-On compatibility with "Fire"-Groupchat of Smoke Messenger requires equal phrases for

• Room Key
• Salt Key
• Hash Key

and also

• AES 256
• Sha384

in Smoke last both cannot be adjusted. In Spot-On per default or per "delete fields" instead are:

• AES256 (still number A) and because of alphabetical order now
• blake2v_512 is per default (instead of Sha384).

Please add a Check-Box "Smoke-Messener-Compatibility"

which hides the fields

• Magnet-Bookmark
• Magnet-Field
• Magnet Delete-Pulldown
• Room-Frequency
• Room-Encryption-Type
• Hash-Type & Set to Sha384
• Delete

and sort all three/four/five remaining values each per one line

Name _____ | [X] "Smoke-Messenger-Compatibility"

• Room-Key ____-
• Salt-Key ____
• Hash-Key ____

Otherwise it's a paradigm learning that preferences - or capabilities of minors - do not overwrite abc- oders! Is that discriminating Smoke? Who cares!

Thanks! Sam

[textbrowser]

Someone did not read the documentation.

[textbrowser]

The Fire activity is one of three messaging activities. From this activity, one may communicate with
one or more groups of anonymous participants. Fire is compatible with Spot-On’s Buzz. 256-bit AES-
CTS-NoPadding along with SHA-384 HMAC provide encryption and authentication.
The Send button is enabled if at least one network-ready neighbor is available.

[textbrowser]

Java lacks most or many or some or all of the newer cryptographic algorithms included in Spot-On. Bouncy Castle supplements the dwindling Java people.

[textbrowser]

I know that you know that I know who you are.

[Sammysupport]

GuessWho, I am Sam.

[textbrowser]

And it would be illogical to curtail Spot-On because Smoke does not have an adequate Java version. They are complimentary, nut rudimentary. They are compatible, not identical. They are aware, not a pair.