I’m having problems doing js/history.back. It crashes inside react somewhere. As I am using Accountant, I was hoping to find some support there for this, but it has not and I conclude that I am thinking about this the wrong way. Someone here knows how to go about it?

@pez have you tried using the same code outside react? can you give us some sample code?

@hugobessaa: basically it was just [:a {:on-click js/history.back}]. But as I’m using Accountant there is HTML5 pushState involved and such.

have you tried #(.back js/history) ?

I’ll try it now. 😃

@hugobessaa: That worked of course. Thanks! I have some reading up to do on interop.

@hugobessaa: js/history.back yields #object[back "function back() { [native code] }”], so why the need for wrapping it? Is there a difference between javascript functions and cljs functions?

Quick one: what do people use to hash passwords in Reagent (or CLJS in general) or otherwise stop them from being transmitted in plain text over network?

@grav: I'm not sure. maybe @mikethompson can answer

@hjrnunes: I don’t know if there’s anything Reagent- or ClojureScript-specific, but when I Googled for “clojure bcrypt OR scrypt” this came up: https://github.com/weavejester/crypto-password (plus I think highly of a lot of @weavejester’s stuff in general).

(In today’s world, the only decent password hashing systems are bcrypt and scrypt. Which is why I did not just Google for “clojure password hashing”.)

Has Argon2 been found to be weak?

(x-posting from #C0MDSV2LW) Please vote if you're interested https://twitter.com/mihaelkonjevic/status/708318966863761408

@smw: Huh, I haven’t heard of Argon2 until now. Thanks for the pointer! I’m not a crypto expert, so I go by what I read from the likes of https://www.nccgroup.trust/us/about-us/newsroom-and-events/blog/2015/march/enough-with-the-salts-updates-on-secure-password-schemes/ (which was written before Argon2 existed).

(though that article did mention the Password Hashing Competition, which Argon2 won)