donpark

Yes. Same core idea as Identicon although original intent behind that was to use it for visual distinction, not recognition.

Excellent. I am using my own pure-go lib, hacked up just to avoid hassle of binding to native code, but it supports only features I need.

Thanks Kevin.

I recommend, exploring other options. For example, work on same thing for 2-5 more years but from a remote location of your choosing, like Thailand, or full Nomad life-style.

If result improves your productivity, it may be a WIN-WIN solution.

googling "conexant keylogger" shows this is not a new problem.

Mission accomplished. Much faster without minimap enabled. :-)

opening a file takes too long, likely due to minimap. I'd disable expensive eye-candies by default.

Source code: https://github.com/silt/silt

Whiteboard should not be the focus. If interviewer just shared whatever technical problem they're trying to solve and asked the interviewer to share their insight as a peer, then it's up to the interviewee to use the whiteboard or not. Frankly, I think this is best done over email so interviewee has the time to think about the problem.

In short, companies should approach interviews like free consultations with an expert or peer.

VoIP isn't getting better because vendors are not willing to delay output for better UX.

I didn't know about Reddit Gold and don't use Reddit enough to answer this.

Even if mechanism is same, I think result will be different for Twitter.

I tweeted this few months ago:

1) Add golden heart 2) Sell golden hearts to users. 3) Reward some golden hearts daily to users, perhaps based on tiered ranking. 4) Allow advertisers to gift golden hearts to users. 5) 'Promote' tweets with golden hearts and display them in Moments.

In short, allow peer promotion. Red hearts are currently being wasted as weak social signals and nods. This change blurs the line between ads and peer-promotion.

You should inform your client of the situation then work together to resolve the problem. Best course of action might be to bring in another expert you know temporarily, possibly through subcontract if your client don't know who to hire.

Calling in another expert is not an admission of incompetence. It's just a matter of efficiency and expediency.

I'd not recommend doing what lawyers do. Best client-developer relationship is built-on trust. Follow your heart and you'll be rewarded over time.

On OAuth 2.0 token substitution threat model: https://tools.ietf.org/html/rfc6819#section-4.4.2.6

Given that OAuth is all about delegated authorization, meaning entity that uses the access token may not be the user but some third-party service using the token on behalf of the user, using it as proof-of-identity makes no sense.

This point becomes clearer with limited permissions. If access token is proof-of-identity, why limit what the user can do when you know it's the user?

A container is just changes you make to a file system to get something running. To run a container, Docker applies changes listed in its image then executes its entry point. When it stops, changes to file systems are preserved but memory is not. When removed, everything is gone so next time it runs you're starting fresh from original image.

Magic with container are: 1) those changes are only visible from code running in the container, and 2) changes can be layered on top of each other (FROM in Dockerfile).

Go's blandness is a feature to me. It's not a joy to write but pleasant to read and understand which, sadly, won't matter unless Golang gains more popularity.

I suspect it's mostly cargo-cult thing.

JWT itself, however, is a signed-JSON format with detached signature which is very useful well beyond access token use-case.

JWT as access token at large scale will require frequent key rotation so inability to revoke becomes a problem but it's not a show stopper because one can work around it using various tactics such as bloom filter I mentioned above.

You can build a bloom filter on schedule which will tell you definitely if the token has not been revoked without hitting the database.

unless I'm mistaken, this looks more like a open-source-as-a-resume project based on rehash of existing open source WebRTC projects like Muaz-Khan's WebRTC-Scalable-Broadcast [1] than a breakthrough. I seriously doubt they overcame scaling problems inherent with those projects.

Proving me wrong would be simple: just demonstrate live streaming to thousands or even hundreds of viewers without adding servers.

[1]: https://github.com/muaz-khan/WebRTC-Scalable-Broadcast

Just one thing: ability to return array of elements as result.

Better than prolonging agony. Fire the faulty chain of command, fix the problem then announce Galaxy Note 8.

nice although keywords and photos are more practical query methods than sketches which are harder to input and thus less expressive (i.e. sketch of a bear returning teddy bears and not real bears).

Have you looked into using IndexedDB? It's pretty widely supported [1] and far more performant than Files API last time I used it intensively (few years ago).

[1]: http://caniuse.com/#feat=indexeddb

I chose not to read this article. Just do it.

that is a major problem too, particularly in Asia and discrimination (race, sex, age, disabled) target groups. audio-only is also impacted (language, stutter, accent, pitch, etc) but to a lesser degree.

but then we developers would be lost without problems.

[Recent ML work on Gaze Manipulation](http://www.creativeai.net/posts/6fokKr6xuytqsnT9F/deepwarp-p...)

[Online interactive demo](http://sites.skoltech.ru/compvision/projects/deepwarp/)

try this one: https://github.com/cmcneil/board-yet/blob/master/model/item2...

I stand corrected. thx.

Unless I'm mistaken, 'protection' goes beyond AWS to include "any of our affiliates, customers, vendors, business partners, or licensors."

This effectively creates a safe harbor against not only trolls but also legit patent holders who foolishly decide to use AWS.

I disagree. While SaaS blinks in and out, requires maintenance, and most fading away over time when interest or business model dwindles, open source projects lives on even in orphaned form. Time is on open source's side.

It's not about who is right nor his right to express his opinion but what leads to better system. You can be right yet be toxic at the same time. Truth can kill. Lies can heal. Timing and situation matters. Ignore and suffer.