chpio

Would doing all the crypto stuff in wasm reduce the problem? Even an unoptimized wasm should be more efficient than doing it in unoptimized js. Does the tor browser (with...

or did it just got deleted from the chrome store?

Hmm, not sure if this is even desirable. You can (and should!) use [structured concurrency](https://en.wikipedia.org/wiki/Structured_concurrency).

The same goes for *Borrow*. The Borrow trait is pretty useless as it is now. It even needs a workaround in the language to work for `&[]` and `&str` as...

He's using a Mac (I'm too) and referring to the Mac installation guide https://github.com/dino/dino/wiki/macOS

He said so: > I use a MBP 2019 with Intel Processor.

no it does not, see #30

but there are no _put_/_set_ methods in the [interface](https://github.com/joebandenburg/libaxolotl-javascript/tree/046466831f4b2a5c1a225d4db6b8a8bfab9a2adf#the-store-interface), but you defined them in [xolotl](https://github.com/joebandenburg/xolotl/blob/53634bc2c2378729ab6142ad41116c6d84191c0b/js/services/textsecure-storage-service.js). I could not understand why the _Store_ Interface is readonly, but i think it's just...

+1 https://github.com/davetayls/jquery.kinetic/issues/33

https://github.com/tkahn/Smooth-Div-Scroll/issues/160