thesumofall

29 ms·

301.
by thesumofall 12y ago
Usability also has taken quite a dive with recent iterations of OS X. iOS, Windows and Android are all not only much more obvious to use for the average user but are also much more pleasant to look at. For a lot of basic stuff I need additi
302.
by thesumofall 12y ago
That's exactly what I'm talking about: Distracting formatting codes, too wide text width (by default), mono-spaced fonts (by default), ... Yes all of this can be dealt with but it would still be great to see a LaTeX editor that as
303.
by thesumofall 12y ago
What's still missing in the LaTeX ecosystem (to my knowledge) is a visually pleasing writing environment. The end result might look great but code editors are simply not made for prose. Even editors specifically designed for LaTex do n
304.
Efficiency Comparison of Document Preparation Systems – LaTeX and Word(plosone.org)
73 points by thesumofall 12y ago|60 comments
305.
Would You Implement Passwordless Login?(sitepoint.com)
2 points by thesumofall 12y ago|1 comments
306.
Antifragility, Evolution, and Entrepreneurship(florianheinemann.com)
1 points by thesumofall 12y ago|0 comments
307.
by thesumofall 12y ago
Yes, can only second that. Absolutely painless. Generally, I'm very pleased with how easy SSLmate makes it to get HTTPS up and running for your domains.
308.
by thesumofall 12y ago
Exactly what I was looking for! Thanks!
309.
by thesumofall 12y ago
Nice demo. Hopefully the time will come when we will finally have a proper Latex editor that is easy to use and has an editor that makes it a joy to write with (think of iA Writer)
310.
by thesumofall 12y ago
It does and it's designed for it. Found this example online: https://github.com/rbudiharso/smsauth-example Basically you can use any delivery mechanism with it you'd like
311.
by thesumofall 12y ago
Someone just made me aware of www.cotap.com - It's probably using a different middleware, but I think a perfect example of where passwordless login makes great sense!
312.
by thesumofall 12y ago
Almost :-) The tokens are one-time only. Afterwards the session is keeping track of the user. Another login requires a different token. Regarding the emails of Facebook, etc.: Great example, actually! I guess the problem really is that they
313.
by thesumofall 12y ago
It's not a Mozilla solution, though, says the developer :-) Hacks is simply publishing about it
314.
by thesumofall 12y ago
It is not necessarily linked to an email account. It's up to the lookup middleware that has to be programmed by the implementer how to translate the login into an email address / phone numbers
315.
by thesumofall 12y ago
Passwordless would allow you to do that quite easily. Only risk are the shorter tokens (can be balanced by shorter validity, though). There is a short description of how to do it in the documentation
316.
by thesumofall 12y ago
Yes, password managers are absolutely the better solution, if we can convince every person to use one :-)
317.
by thesumofall 12y ago
Yes, I'm a developer of passwordless. Persona is great and similar to passwordless in a way with the only downside being the reliance on JS.
318.
by thesumofall 12y ago
b.) wouldn't make a difference if the account is compromised
319.
by thesumofall 12y ago
There is a fully fledged implementation for Node.js https://passwordless.net (Disclaimer: I'm leading the development)
320.
by thesumofall 12y ago
I guess most larger companies pay their employees taxi trips to/from the airport.
321.
by thesumofall 12y ago
And for those who missed it, there is a free chapter here: http://www.gatesnotes.com/media/features/books/Bill_Gates_Jo...
322.
by thesumofall 12y ago
Yes, stuff happens. But as said: Most services use long-lived sessions. It's a choice: Trouble people with either insecure passwords and password resets, or take the risk that sometimes when a session was closed people might in rare c
323.
by thesumofall 12y ago
Good point. My thoughts: - Email is not the only option to deliver tokens. You could also go for SMS, or both - For most registrations such emails are anyway commonplace. Combined with long sessions (where possible), I think the risks of de
324.
by thesumofall 12y ago
With the risk of repeating myself: https://passwordless.net I think we often overdo the simple things such as authentication.
325.
by thesumofall 12y ago
Depends on the email address you use :-) Gmail, etc. are directly supported - for any other email provider (or your self-hosted one) you'll need a password.
326.
by thesumofall 12y ago
Also, Persona still relies on passwords which are usually too weak and re-used across the web
327.
by thesumofall 12y ago
I think Persona is great and can be the right choice for many scenarios. Browser support, the JS requirement, and the reliance on email (whereas tokens can e.g. be distributed via text message) might however be points that convince develope
328.
by thesumofall 12y ago
For [11]: I think it makes sense to also highlight other approaches than OpenID such as https://passwordless.net which is a sort of way in the middle (disclaimer: I'm the author)
329.
Show HN: A token-based authentication system for Node.js/express(passwordless.net)
3 points by thesumofall 12y ago|0 comments