skysight-inc/HackerNews huggingface dataset:
The obvious suspicion is that Atwood was merely being diplomatic when he described Gruber's email in those words...
Mr. Atwood, you may be too kind. I see this as a chance to bring Markdown to a larger audience by not only standardizing it, but also renaming it as well.

In this endeavor it would appear that you are giving too much credit to Gruber. It is unfortunate that he was not one to be more gracious in the matter.
The Enlightenment is a direct consequence of the Protestant Reformation that preceded it a few centuries prior. The key ideas of Protestantism was that faith should be a) based on reason and b) involve a direct communion with God, without intervening priests, ritual or hierarchy.

If this sounds appealing to you, you are basically a Protestant, possibly a post-God Protestant aka "atheist"/"agnostic"/"secular". In Catholicism, as with most religions, God (or gods or spirit) is intertwined with every aspect of life. The idea that religion is purely about beliefs is a Protestant idea - for most people, their religion is about community, ritual, and accessing deep emotions or altered states of consciousness. Protestantism rejected most of this in favour of a purely 'rational' faith, from where it's baby steps towards giving up faith entirely in favour of pure reason. (Evidence: atheism flourished in the traditionally Protestant countries of Northern Europe and the Anglosphere).

"People are going to have to choose to believe that their religious beliefs are "just religious" and have no serious relevance to the material world (the exact notion their religion decries as the ultimate heresy) and join the modern world"

Has no relevance to the material world === "not real"; in other words, people are going to have to give up their religions.

"Those ideas are absolutely and totally required to support the idea of coexistence of peoples of different faiths."

I.e., for people of different faiths to co-exist they have to give up their faiths (in favour of 'secularism' or 'moderate-ism' aka Protestantism).

Much more on this idea here: http://unqualifiedreservations.wordpress.com/2007/09/26/how-...

Related point: the West has 'Protestant-ised' several world faiths (in fact the concept of 'world religion' is arguably the creation of 19th century Protestant missionaries and scholars).

e.g. Buddhism: http://meaningness.wordpress.com/2011/06/24/protestant-buddh...

And Hinduism: http://mitrailleuse.net/2014/08/08/the-westernization-of-hin...
> Bluetooth is very finicky.

Is there any hope that these new wearable computers will lead to the adoption of something better than Bluetooth? Something based on IEEE 802.15.4, maybe?
Two 'searchmaps' about Linux:
1: https://app.linkwok.com/view?id=QSgnSYDj2rZ5sdxWf
2: https://app.linkwok.com/view?id=eBLZYv5m66y3jTe9k

Check them out. The idea that we seem to be failing to convey is that in most cases of casual research online it ends up taking hours and is not completely optimized. Also content ownership online is near impossible for the lay user - For e.g. Who has the time to author a wiki - but what if you could just drag and drop what's relevant and add some notes here and there, add connections to show a flow of thought and share it with someone. I used to teach engineering undergrads and signed up to work on Linkwok only cause I saw the value - Imagine lecture notes and lesson plans as Linkwok searchmaps! Where teachers and students can interact as well.

We get that search is private so by default everything IS PRIVATE on Linkwok but then content authorship is NOT generally private. So Linkwok caters to that as well.

Consider this:
1. When users search online and you're distracted or switch to a different task, it takes them a while to get their bearings with all those tabs etc. Or when you bookmark, unless you open the page you often don't know what it was. Here, every page can be stored as a visiting card - edit the name and description to something you remember
2. Users often don't remember how they got to a particular page - what they searched for when they found it. On Linkwok every page you add gets tagged with the search query.
3. There are several use cases where people need to collaborate when doing research and Linkwok directly caters to this.
4. It brings content authorship to the lay user cause it is supposed to be simple - ideally - evidently we need to fix the UI and UX a bit.
5. People search for similar things - If someone has found and curated the information for that topic why not continue from where they left off?

Finally, to my mind there's three kinds of searches that occur - broadly.
1. Where the user searches for something, the first link is all he needs and he's done. Linkwok is not for this case.
2. Where a user needs to iterate queries until he gets what he needs - Linkwok can come in mighty handy here.
3. Where one answer is not enough -one link is not enough - And here too Linkwok comes in handy

And if Linkwok searchmaps can come in handy for 2 and 3 - won't a searchmap also become a one stop for case 1 as well? That's what we're going for.

We're strangely positioned as an App. I will admit. But we do believe that there's value and hope that we can somehow convey this.

You asked for links, I know I have said more. But I did feel the need to add all that explanation cause we're obviously failing with our communication.
Pascal Costanza exemplifies a lot of what I love about Lisp. It's interesting to note that not too long before this was written, he was highly opinionated about the language in a very different way:

> I have participated in one of the first Feyerabend workshops, organized by Richard Gabriel, one of the main drivers behind the original Common Lisp effort. I have also read his book Patterns of Software around that time. Later we had a small discussion in the patterns discussion mailing list. He tried to promote Lisp as a language that has the "quality without a name", and I made some cursory remarks about Lisp's unnecessarily complicated syntax, just like anybody else who doesn't get it yet.

> To me, the most important comment he made in that discussion was: "True, only the creatively intelligent can prosper in the Lisp world." The arrogance I perceived in that comment annoyed me so much that it made me want to learn Lisp seriously, just to prove him wrong and show him that Lisp is not as great as he thought it is. As they say, the rest is history.

[http://lisp-univ-etc.blogspot.com/2012/04/lisp-hackers-pasca...]

Once you begin to peek under the hood of the language, there's no end to the secrets it starts revealing and no end to the intellectual rewards it brings to curious (and yes, even arrogant) newcomers. P-cos has since gone on to do some of the most interesting work in Lisp since the ANSI standardization, such as ContextL. It would be interesting to see a substantial update to this guide in light of his more recent work.
Check for New Courses and enroll for free
This is a pretty elegant solution for delegated authority, too. If you have client-side code as well as server-side code that both access an API, JWTs can give you a uniform way of handling authorization at the API level.

Client side access is pretty well understood. A JWT can be stored in a cookie and then added to Ajax requests as a bearer token, for example.

The server-side code will typically have some way of validating the client, such as an encoded cookie. This will be used to build a user object of some sort, which can be used to run authorization checks. When the server side needs to access the API, the user object can be serialized into a JWT and added as a request header, similar to typical client-side access. If it's done well, the API can use a very similar user object to check authorization. Another option is just to do JWT pass-through. If this is done, the signature should at least be checked to avoid facilitating an impersonation attack.

JWTs have built in signing to ensure that the user object is intact. All that is left is to encrypt the channel with SSL.
Thanks for the feedback guys. We put in a temporary fix without the whole grid nav. We thought it was pretty cool. But good UI is always an iterative process and we're working to improve this.
Anyone remember reading an old article about the relationship between safety equipment and risky behavior? The idea was that the more safe you feel, the more likely you are to engage in unsafe behavior. The example given was that cyclists with helmets were much less cautious of traffic than bicyclists without helmets.

So I'm not sure if this has to do with cars feeling more safe or just the prevalence of smart phones, but driving down the interstate and paying close attention to what other cars are doing is terrifying. Literally every day I see a number of people driving 70+ MPH and slightly drifting over the lines or driving with their phones perched in front of them on the steering wheel. And it is not just teens or other classes of people typically associated with risky behavior, it is everyone.

This transition from smart-cars to self-driving cars is scary. As the cars become more attentive it seems we get less attentive.
Sorry to hear that! And we didn't mean to override the scroll. We just wanted to draw all the focus on what Linkwok is and get users to the app faster. In any case we have put in a temporary fix without the whole grid layout until we do an overhaul. Thanks for the feedback!
In trains they have busywork to test your attention. (I rode a simulator once, it's like a flight simulator but for locomotives.)

There's a deadman pedal that you need to keep pressed to keep the train moving. Once every half a minute, you need to lift your feet of the pedal. If you fail, the train will soon break and come to a halt.
We'd love if you gave the app another go now. Would love some feedback. Thanks.
If you look around the site a little bit, you find that this is actually just a maritime-oriented rendering of data from OpenStreetMap. Not as usable as professional, commercial maps, but still not too bad.

Hopefully this encourages more mapping of features not on land for OpenStreetMap, just as OpenCycleMap has helped the availability of cycling data.
Well it's fair to say that experiment shows causation but no I don't think you can say the correlation shows it works. I think it goes against the definition of the word.....

I found the article too dense to get as well, but I do think 'perhaps' we could use correlation more to assume causation. I think we are too cautious and certainly the haters always bring in correlation to stop science articles they think don't follow their beliefs. Not sure if that's compatible with the OP or not, it hurt my head.
Not quite what I meant - no I don't think cops were writing SQLi but they learnt enough to laugh at Little Bobby Tables, just as they can learn enough to follow the money through 17 bank accounts.

This is the equivalent of is the FBI allowed to search my trash if the trash is in a trashcan on my property or on the sidewalk, being pulled by a street cleaner or knocked over by a fox. We can make it as complicated as we like but the law needs to draw some lines somewhere and stick to them.
and share?
The age is not an issue, people thought the iPhone 4 was wicked fast at the time, the speed seems adequate for a smart watch I would contend the software is too bloated - Java is not the fastest tool in the shed. However the fact that it's power hungry is a deal breaker in a watch.
I wonder if the "vehicle-to-vehicle" technology could be implemented faster if it was included in GPS mapping apps. Sure, your GPS can't slam on your brakes but it could warn you of hazards, and your data might be used to slam on the brakes of the car behind you (and prevent you getting rear-ended!)
> A good poker player knows they got lucky and shouldn't have won the hand.

Possibly nitpicking, but a good poker player is unconcerned with whether or not they won the hand (from a strategic standpoint).

They're worried about the expected value of the course of action they chose, and how to maximize EV at every decision.

Poker players actually do commonly report on this phenomena, however they report on it inaccurately--most report that they made their poor decision (which ultimately won) for a particular reason. Some intuition if they made a lucky guess about their opponent, perhaps, or a feeling if they had a lucky outcome, or (unknown to them) miscalculated "pot odds."

I've found that in the same way that most people believe they are good poker players, or above average drivers, people tend to believe that they are good at anything where skill and talent is not directly obvious (basketball, for instance), or start believing that long before they are actually good at it.

Looking up local photographers on FB is one of my favorite pastimes for this reason.
Please refer my answer here: https://news.ycombinator.com/item?id=8283554

As for the name - The idea was that it's a wok(cooking pan) for what you find on the web.

And the video - I agree entirely. Any app should be simple enough that when you get there you know what to do. Unfortunately either we need to find a new UI/UX and Interactions guy or more likely it's a process to get a completely intuitive UI and we're working towards that. I'm just glad we hadn't posted the last version on HN - I'll admit it was appalling! As one commentator on Twitter said - it's like Prezi for research so please give it another go. There's a feedback button in the app that you can use. Thanks.
Theft under the guise of, "oh this must be drug money". I think the article mentions the average amount taken is something like ~$8k. That's 8-10months of legal fees.

AND IF YOU DON'T LIVE where they took it, you'd have to GO THERE to go to court.

That's why in places like Missouri they love pulling over out of state licenses because they know if you live in California you aren't going to be coming back to contest their shenanigans.
Could you please add "US-only" in your title? Thanks.
E-ink doesn't update fast enough or well enough for a watch. Have you ever used a Kindle? The Pebble uses an "E paper"[1] display which doesn't use a backlight and that watch can last a week. Battery life is proportional to how often the display is updated.

[1] http://en.wikipedia.org/wiki/Electronic_paper#Wristwatches
World's first manned flight with an electric multicopter[video]
Show HN: Disco – Easy GitHub Browsing
Disco is tiny app I built over the weekend to try and make browsing git better.

Inspired heavily by Tower, it also adds pull request integration and is run in the browser. It's only for public repositories.

Checkout:

http://disco.88cartell.com/#/rails/rails

http://disco.88cartell.com/#/emberjs/ember.js

http://disco.88cartell.com/#/angular/angular.js
"what happened was basically that the Islamic world came up against the Crusades, and with Catholics murdering them with terrible savagery..."

I think you mean the Mongols.
https://en.wikipedia.org/wiki/Siege_of_Baghdad_%281258%29
Gen X had a lot more to do with the useful parts of the Internet, along with pre-Baby Boomer scientists, than the boomers (and thus hippies).
I'm agreeing with "qq66". If you wanna make a real business out of this, you should follow qq66's advice and get yourself the producers on board. They however would wanna see prospected sales pipelines and some forecasts. In addition to that, you might need to agree on fixed sales per year in order to be recognized as a distributor. Alternatively, you could go with a luggage full of money to some small Asian trade fairs..
The thing is I don't believe the court will find this to be violating any laws.
It's interesting how most of the comments focus on the technical aspects of what the guy built.

What I found interesting and inspiring is the time and passion that he puts in what he does. I really hope to still have something that makes me so passionate when I will be 72. It's a great way to live your life.
Show HN: Avaza, a Free Business SaaS with Projects, Timesheets and Invoices
There's one thing I'm curious of from the perspective of a lawyer, which is the part I didn't describe clearly. If someone were to post some piece of software online with a description saying, "go ahead and use it for anything you want" but then also include a LICENSE.txt that says it's only licensed for non-commercial use, would that original statement of "anything you want" make it harder to sue a commercial user?

In this case, Bukkit and CraftBukkit are effectively the same project. Bukkit is the collection of plugins, CraftBukkit is the essentially the abstraction layer to allow those mods to run in the memory space of the Minecraft server.

Regardless of what FSF thinks is a derivative work, and really regardless of what really is a derivative work under the law, everyone contributing to Bukkit seemed to be acting as if they thought plugins in the same memory space communicating over APIs was a perfectly legitimate use of their code, at least until this squabble.
How to Succeed in Silicon Valley Without Really Trying (YC S12)
the Pebble does not use e-ink, they use Sharp's "Memory LCD" technology which is a low power black and white LCD.
The pattern I've seen used most commonly is the latter situation you described. The user authenticates, and is issued a signed JWT which includes their user ID and (optionally - I actually talk about this in my comment here: https://news.ycombinator.com/item?id=8283530) an expiration. You can also delegate roles and permissions through the JWT, which makes for a really slick authorization pattern if you've got a case where you'd like to easily change a user's permissions. I mean, you can add whatever you want to a JWT - I guess I'm just offering suggestions based on my own experience. IMO, user ID is the best way to go, because it's only a single field you have to maintain. If you start adding too much information in there you might end up with a bunch of tokens with old property names etc. Personally I just tried to closely follow what OAuth specified should be added to OAuth JWTs. I think I've got "issuer", "audience", "expiry" and "id" in my current tokens, but adding a list of permissions would be a good choice too in my opinion.

I think what everyone needs to remember is that SSL is a must for these things. If you're issuing non-expiring tokens over non-SSL you're just giving the keys to the castle away. Another thing that should be considered is token storage. I'm using local storage right now which works for me, but it just means I need to be more careful than ever about XSS exploits, because there's no "HTTP only" option for local storage!
I am intimately familiar with your work on scalac, and that's all I can bring myself to say about that.
Women in Tech is looking bright
The OAuth way of doing things is to have two tokens: an auth token and a refresh token. The auth token is the one you send with your requests to authenticate them (and can be a JWT), but it has a very short expiry time (say an hour). The refresh token is typically a random string that's stored in your database and can be used in place of a username/password or other credentials to get an auth token.

This way you can store (in an app, or a browser) the less sensitive refresh token (which might expire after a week or so) instead of the highly sensitive permanent auth credentials.
You can go back further by modifying the startTime parameter in the download link.

https://maps.google.com/locationhistory/b/0/kml?startTime=14...
I just wanted to point out the "Marine Traffic" layer, which appearantly shows real-time positions of vessels. For example, off the coast of NJ I spotted this tug: http://www.marinetraffic.com/ais/details/ships/368468000/ves...
I worked at Google for 3 years and GM for 5 years (including engineering in Cadillac) so when I see news about the companies, my ears tend to perk up.

A few things should be set straight. Google was not (and by a long shot) the first to think of and try to develop self driving technology. I'm disappointed to see technical people in silicon valley not think a bit more critically. All OEMs and many tier 1 suppliers have thought about and (especially larger players) tried to build self driving cars. When you're a company like Denso or Bosch, this is a massive opportunity and not to aim a few people of your hundreds of thousands of employees to the problem is hard to imagine even if you know nothing about automotive. To be clear when I worked at Bosch from 2004-06, this tech was in development.

Secondly, the HN crowd specifically is notably biased. Check out Google self driving announcements vs GM (or any news about automotive manufactures other than Tesla). Having worked at both companies in product and engineering - yes they are of course different. But not nearly as much as you think. The single most notable difference is that Google is a very margin rich business. That allows the company to attract and retain top talent but it doesn't mean engineers that doesn't work at Google are bozos.

Thirdly, the technology that traditional OEMs have tried to develop is around 2 axis - cost and safety. Google is approaching the problem differently. Google's approach of a $x0,000 LiDAR system might prove to work if LiDar costs fall but thats a big risk. Also, Google admits that their cars don't work in things like rain. I'm not saying Google won't win this space - the contrary, I think they have a great shot. What i'm saying is this is significantly complex tech and its complexity is hard to understate. There can and will be different solutions that work.

Lastly, GM and Google are not the only ones in the game. Nissan and Mercedes have announced they will have cars with similar tech in 2017/18. Ever single automotive player is investing huge amounts of resources.
Looking forward to reading some more answers on this since proud moments seems to vary tremendously (social vs. monetary). Keep going. :)