skysight-inc/HackerNews huggingface dataset:
Gradberry Spamming GitHub Users
Gradberry appears to be mass-spamming contributors to various github repositories. See http://pastebin.com/mmjkUY0w for one example, and https://twitter.com/jacobian/status/585287293860093952 for another.
The stack overflow page is disappointing because in my opinion all of the answers miss the point: Yaml is designed to be readable and editable by humans. Json is only designed to be human readable - and intentionally does not have features to support editing by people.

Json intentionally does not support comments. Think about that for a bit and you'll realise what Json is for and what it isn't for.

As SeoxyS said: use yaml for config files, Json for APIs.
I wish Linus would now turn his attention to:
1) make (ought to be a simple concept but never seems like it's quite been done right)
2) init (only he has the clout to solve the pid 1 controversy)
Will check back in 2025 for progress report.
Fintech 1,000: B2C Payments will be be 10x cheaper but volumes will increase 10x
Java 8 Concurrency Tutorial: Threads and Executors
Is compression rate nowadays still a factor? If so, is the performance of YAML worse than JSON?
In a somewhat ironic way I agree with you. However I am speaking from the perspective of what I want the US government to be more like instead of what it is right now. When you have no faith in your government I think you want no leash at all. Put all the details in the laws if you want more power than you already have.

But when you have sufficiently capable and competent actors in government I would lean on the side of trusting and giving the leash.

EDIT: And come to think of it, enormous weight of huge bills / laws I imagine could become a hindrance to a government's ability to do its job. Think about it. What if you inherited a highly complex legacy application that you were not allowed to rewrite from scratch or even refactor it, but were stuck maintaining it. And all that you ever get to do is add more code on top of the old (alot of times bad) code. It seems a cycle of futility. Instead given limited resources of a government I want a lean system where people are allowed to use their judgment and intuition.
Show HN: FlowTime – pomodoro-driven timer
We don't need two different languages for this.
Linus is not a magician, he is however very good at working with systems and spotting exactly where those systems need improvement.

I respect this quality immensely.
I am looking forward to the day Rust is available out of the box in XCode, Visual Studio, Android, QtCreator.

Until then, it is going to be "Modern" C++ for the lower layers/common code, with the platform vendor languages for the upper layers, regardless how Rust improves over C++.

I am a big fan of the type safety of Pascal and ML language families, but eco-systems have more weight than just the language.
Show HN: GoGetter New Tab. Collection of Cards with To-Do Lists for Chrome
And it might just be confirmation bias, but I've seen far more exploits in YAML parsers than in JSON parsers. YAML might be okay for configuration files, but I would never use it for data exchange…
Actually, after finding out about TOML[1], I would suggest to look at it. It is a lot simpler than YAML, explicitly does not support dangerous features like deserializing arbitrary data structures, while being very readable. Spec is not entirely stable yet, though.

1: https://github.com/toml-lang/toml
>voters cannot vote anonymously

Is it information-theoretically impossible to devise a cryptographic protocol that allows all the desired properties of voting (verifiability, anonymity, preventing double-votes, ....)?

I recall that there exist some protocols that provide at least some of those.

If it's not impossible then it's not unpatchable. Someone just has to come up with the right method to do it.
Correct! For me a better political statement would have been to wait for the People to remove the statue. I want to know whether enough people who care about the memory of the Prison Ship Martyrs to organize the removal compared to the memory of Snowden. If someone removes it, it's a strong political statement that the People want this. If no one removes it, then the People has chosen new heroes.
It is a fact that the longer a page takes to render affects the number of users who stay on that page. That would be pretty damn important for a company who makes most of their revenue from web advertising. Which is why Google will continue to push ANY technology e.g. SPDY that makes web pages faster.

VP9 does not fit in with their goal of getting more eyeballs on ads which is what makes it odd for them to push. There is no evidence what so ever of H.264 has resulted or will continue to result in a lack of adoption of video on the web. All evidence is to the contrary. In fact it is the strength of YouTube that has resulted in a lack of diversity in video sites.
Chrome plugin spying on Swedes' surfing habits
Do they actually have a good way to monetize android

As far as I understand, the initial motivation is to avoid being locked out. Suppose that iOS held 80% of the market, they could change the default engine, replace Google Maps with Apple Maps (like they did), etc. Given that smartphones and tablets are now commonly used to access the web, Google could have lost a serious chunk of traffic.

In other words, Google does not have to monetize Android directly, it exists to keep people in Google's ecosystem.
Two things would help online voting tremendously:

1) Open-source code. That's how you find the bugs and build confidence.

2) Opt-in privacy. Ballots could be like Facebook-posts - public by default, with optional privacy. After the election closes, the results would be posted on the web where everyone who voted publicly could verify that their own vote was counted correctly.
In 2015, nobody should still be hiring developers who don't know how to use Git yet. It's a massive warning that they're not keeping their skills up to date.
> XML was originally simple too with just DTD as Schema.

The complexity of XML has not changed since its inception.

> Then they come up with XML-RPC, XMLSchema, XSLT, SOAP and many other complex concepts that in the end more or less failed.

This doesn't really has any bearing on the specification of XML itself. XML is simple (with some caveats like entity expansion), and extremely flexible. The problem is that it is designed to be read and written by machines, while still being debugable by people. It is extremely verbose. It shines in some use cases, eg for documents with a complex structure and a lot of semantic metadata. But it is even less suitable than JSON for configuration files, for instance.
Fred Wilson: How to Be Your Own Boss
By "TV industry" I assume you mean the manufacturers of TVs. Since most of them support Android TV (which requires VP9), or want 4k Youtube as a ready source of content for their 4k TVs, and are often brands that already make Android phones, or re-use chips intended for those that do, I'd guess they'd have to do more work to avoid VP9 then to use it.
Thank you for putting this together. I like your approach of news and journals. Please keep it up!
The leashes are the words of the law and their ultimate interpretation. Everything follows from those words.

Transparency and good faith are ideals that are rare in powerful bureaucracies. Expecting those with the most power in the world to act in good faith is a scorpion and frog tale.
Sony: Smile to Unlock Your Smartphone
Why is it a better serialization format compared to yaml?
> Ansible and YAML

I am searching for an replacement of / alternative to Ansible written in Go or Rust that uses JSON or INI as config format.

(Ansible is written in Python. Both Python and YAML rely on outline indentation which causes many headaches)
As an aside, back in the early 2000's the NSW Government contracted ERG (a Perth based technology company) to implement a Smart Card system for public transport. ERG had already successfully rolled out Smart Card systems for other local public transport systems worldwide to much success, most notably for the Hong Kong public transport system, the MTR (Octopus Card), in 1997, which is still the largest such deployment to date with tens of millions of transactions daily.

Unfortunately the NSW contract ended in lawsuits back and forth with the NSW Government trying to reclaim the project cost and eventually (arguably) led to ERG's demise. Sad that a successful Australian company, a leader in it's field, able to deploy complicated systems worldwide was (in part) taken down in it's own backyard by a (in comparison) pretty straight forward project.
Normally I would agree with you, but only if we insist everything has to be completely over the internet. If we make it so that voters have to collect a random token from a box (ie you stick your hand in and take one) and that they have to show id to get to pick one then there is no way to vote twice (at least not without a fake id) and no way to connect the voter to the vote. It does require on site access but that could be allowed over a period of several months if need be.

We already have voting by mail, of course, but this way you get to wait until election day to cast your actual vote and it is too easy to connect the vote to the voter.

The issue with a gun being pointed to the head could be solved rather easily by issuing every voter a random number of votes and marking on as special (perhaps it comes in another envelope). All none special votes are automatically ignored, so you would gain nothing by pointing the gun at somebodys head.

This also solves the software trust problem: allow an open specification and an API test endpoint and somebody will write an open source voting program. As a bonus the software could submit the votes to an api at all the registered parties and any news org so that everybody could agree on the count.
We find that due to raised salary impacts for Ghanaian police officers relative to customs agents causes the police to increase the value of bribes taken at each individual stop by between 20-40 percent (~$0.20 - $0.40), increase the total amount taken on the road, even while they reduce the number times they receive a bribe.

Bribe size is increased, frequency is decreased, which is what you'd expect from increasing salary of a public official for the purpose of reducing corruption.

Take it to the extreme and increase their salary to USD$1m per year, and the frequency could drop to 0 or 1, and the price could be $10m, so fewer instances of corruption would happen because fewer people can afford it.

Public officials are also people. Most people have the same inherent desire to be good, and yet most are vulnerable to same temptations. The reality is not dictated by law.

Of course, good enforcement and punishment of corrupt behaviour is also required.
AMA with Kiran Jonnalagadda, Founder of HasGeek and Hasjob
Discouraging hacking domestically it will widen the skill gap between foreign hackers and domestic white hats.
Whats to prevent the government from checking who voted what then later on then?
RAD Studio XE8 (Delphi XE8, C++Builder XE8) Are Available Now
it's more explicit.
We recently moved much of our application's schema definitions and configurations out of code/JSON and into YAML files (we generate JSON during the build process in placess where it is necessary). A pleasant side effect was that the YAML file set began to double as basic documentation.

e.g.

name: user
plural: users
label: User
...
primary_key: uid
display_key: full_name
unique_keys:
- username
- uid
client:
storage:
type: IndexedDB
...
actions:
create:
label: Save
permission: create_user
...
server:
storage:
type: mysql
...
api:
create_user:
url: /users
method: post
fields:
username:
name: username
label: Username
type: string
length: 20
required: true
editable: false
Agreed. After using both YAML and TOML, I'd say that TOML is much more readable as compared to YAML.
I think there might be different definitions of "enforcement in good faith" here. Your perspective, if I understand it correctly, is "The purpose of this law was presented as fighting terrorism and now it's being used for other purposes, which constitutes bad faith enforcement".

Another perspective is, "Law enforcement isn't doing anything that it shouldn't be doing, therefore they aren't acting in bad faith". Whether they're going after terrorists or drug dealers or money launderers, it's all the same to many (if not most) people. As long as there's no evidence that government officials are abusing the provisions of the PATRIOT Act to settle personal scores or persecute those with unpopular beleifs, most people will see them as acting in good faith. This assumes that actions taken are within a reasonable interpretation of the letter of the law, of course.

I get where you're coming from, or at least I think I do. I just don't think that the issue is so black and white. This may be a case of "The current government isn't doing what I want it to do" as opposed to "We should change the way that the laws are written". And the solution to that is pretty simple: Vote.
Can you do that even now? I can trivially bring a cellphone into a voting booth and take a picture even now.
Think again if you really want that for every service.

I've encountered many poorly written services where I would have been happy if there were a schema to be at least sure what kind of messages are exchanged.
I'm OK with something like, 'the people who targeted the site had an agenda to find a hole, they found one, and they were happy to find it. I'm happy to hear about it from them via responsible disclosure and to have fixed it promptly. That would be close enough to ideal for me, and it seems like that's pretty much what happened.

If they denied the hole, or tried to cover it up, or did anything other than fix it immediately upon learning about it, really, that's the most we can hope for.

Did they slander the researchers?
Life with the iPhone 6 Plus
I have had a similar experience with spaces handling in yaml: the application configuration was producing error because of tabs were being used instead of spaces ....
I've heard of YAML, it seems ok, but it'll never catch on. JSON is too established.
Putin photo 1
Genode works on a variety of L4-based kernels, probably what you want to look at.
I do have one.. I'm using it for my blog, portfolio and my email address..
the problems with xml (as in "outside the XML-RPC, XMLSchema, XSLT, SOAP stuff") IMHO arises these two / three points

* it's a little too verbose (<xml></xml>.. while even S-expressions use just ')' as terminator)

* there is no obvious way to transform any xml to an object (pojo is the best aproxymation, but how do you differentiate between a sub-tag, a text node, and an attribute?)

* it's essentially typeless (how do you serialize a number? how to differentiate it from a string? from a boolean?)
If you happen to be a welder reading this, either in training or in work, I have a small seed to plant: Practice best practices for 5 years and then come to the developing world. Practical, visionable, safety-first, disciplined skills are what moderately developed countries are shouting for, and you can call your price.
Yes, we know.

But adding new keywords instead of reusing/overloading old ones for newer features would have been nice. Writing new code in C++11 isn't the problem, reading old ugly C++ code and trying to understand it is. I think the clean break is Rust and it already looks promising. Sure some of its syntax is influenced by non-C languages and looks a bit weird, but I can live with that.
ESCORT COUPLE KELLY KATERINA – Golden Diamond Escort
I was really surprised to view the comments, and find the attitude expressed in the GP's post #1.

If anything, I read this and thought something along the lines of, "I wish some of the subjects I learned in college were explained this way, at least to start."

Now, I fully appreciate understanding fundamentals, and not black boxing things (see the ongoing framework debate posts), however I didn't read that article looking to be spoon fed a black box for ML or anything...I was just bored and curious. So it made for good reading.

Perhaps I'm generalizing too far, but it reminded me of when I was presented with the classic Lamport paper on "Time, Clocks, and the Ordering of Events in a Distributed System" in undergrad. This would have been around 2004. I had been working (i.e. coding for money) for some time by then, but back then, you could still build a lot with a relatively stock LAMP stack (or similar.) MongoDB, Riak, Redis, Cassandra, DynamoDB, etc. were not all commonplace (much less things you could have a cluster ready to play with by means of a simple 'vagrant up'.) So when I was given the paper, without much context, I had a hard time really "getting it", or how it applied to me. I'm pretty sure I eventually got some commentary on it from the professor in class, while hurriedly going through powerpoint slides, probably anxious to get back to his research. Then a test question or two about it later.

Years later, after working more, and "distributed systems" becoming more of a tangible thing, I re-visited it, and it made more sense. Anyway, my point is that had I gotten some sort of a, "and here's what the paper is talking about, and how it applies to something tangible, in plainspeak", it would have been useful - so we shouldn't groan about an article like this. Someone out there is going to understand the subject much better thanks to that post.

[Note to the reader that's very familiar with the vector clocks paper - I realize it's not written with that much jargon, and DOES do a decent job in the introduction section of using plain language, but the purpose was just lost on me. I mean, it makes reference to ARPA Net, and then goes on to determining event ordering. It just didn't equate to any thing in my world view, and I had done a decent bit of multi-threaded/process programming by then too.]
Good identification of some common fallacies and misconceptions. If anyone finds the fallacies hard to read, here are restatements of some of them as straight advice:

• If a technology has flaws, that does not render the whole thing worthless.

• New technologies that you haven’t tried are not perfect, and will still require hacks.

• You have worked with some technology for a while, and built up a corpus of specialist knowledge and hacks. That does not necessarily mean that it is more flawed than some newer technology that seems simpler. That apparent simplicity is probably just because you haven’t worked with it and therefore only understand it in a shallow way.

• Old, widely deployed technologies are not over-complicated. It just seems that way because people have built more complex systems with them than with new technologies, and thus have been forced to tackle more complex requirements.

• Acquiring specialist knowledge is not bad – it is the reason you are paid to do what you do.
China does not have extradition treaty with US. There couldn't be any extradition embarrassment then.
> There is nothing illegal about having a monopoly. What is illegal is forming cartels and collusion to create restraint/constraint of trade.

That sounds like a description of a somewhat sane legal system, but it's not a description of United States "antitrust" law. See, for instance, United Staes v. Alcoa.

http://en.wikipedia.org/wiki/United_States_v._Alcoa
Could you elaborate a little bit more on those protocols that you mention? Massively interested in those!
Accident Detection service to detect auto accidents using smartphone sensors
CamStudio Audio and Video Software
I wished the author would have _not_ used flash for the buttons.
Rebranding the Business of Farming
Thanks! Fixed. Also learned something really scary about JavaScript in Firefox

https://gist.github.com/greggman/15b5285fab6e0ca0a799
If you can't pratice defense / train on your grounds, isn't it giving your enemy an advantage ?
I like the idea. I like that you even round-trip comments. I suppose that doesn't add too much complexity to the implementation?

Have you ever been bitten by the dwimmy typing of numeric and true/false/null data?
A curated catalog of websites to submit your startup
The conciseness of XML with the power of JSON!
YAML IS INSECURE.

Your parser might not support instantiating arbitrary objects, but those your programs interact with might... :(

Anyone else recall the problems with YAML vulnerabilities? An old blog post by me: http://williamedwardscoder.tumblr.com/post/43394068341/rubys...

So never ever use YAML for tainted input.
7 Minute Workout App Success Story
K-pop fans are more relevant consumers than foreign anime fans, because they spend tons of money that goes back to the original producers, and tend to live in other Asian countries where the agencies will can more easily communicate with them (or are even capable of realizing they exist).

Meanwhile anime's business model relies on selling less than 10,000 copies of any one series at about $30 an episode. Nobody outside Japan is going to put up with this, and they're afraid of going out of business if they change strategies, so growth is not very good.

Manga does well worldwide and is healthy, though. America can't compete in this market because our comics industry is a monopoly that only produces one genre[1], whereas the main genre in manga[2] is much more relevant to any reasonable person. I feel Japan has no fundamental advantage in this area, though, and other people will eventually figure it out.

[1] Weird cosmic fantasy stories about people wearing underwear over their clothes getting in fights all the time.

[2] Waifus.
Making a sport game in Unity: model and prototype
> As for doing a technical interview? If asked I would never do one, I am a professional. No one asks a Lawyer...

I'm thinking exactly this, just wanted to make sure this practice of refusing to tech interviews exists, and it won't be considered as being rude... Thanks for the detailed answer!
Ok, but only if he first turns his attention to a proper git submodules/multiple reposities kind of thing
I got my own small language too: https://github.com/Cirru/cirru-json
I'm suprised nobody mentioned that JSON lacks date data type.

This is annoying as not everybody using ISO 8601 strings as dates.
I guess you are talking about the plan to have the data of one shard only on one disk (see https://github.com/elastic/elasticsearch/issues/9498)? This does not necessarily mean that you will end up having only one shard per datapath - only if you have just one shard per node. But you are right, the change might lead to unbalanced disk usage in some scenarios, where increasing the number of shards would solve the problem.

There are two options:

1. (Recommended for now) Export the table with COPY TO ( https://crate.io/docs/stable/sql/reference/copy_to.html). Drop the table and then import it again using COPY FROM (https://crate.io/docs/stable/sql/reference/copy_from.html ).

2. Use insert by query (see https://crate.io/docs/stable/sql/dml.html#inserting-data-by-... ) if it is ok for you to copy the whole data to another table (with more shards).

1) is recommended, since it allows for throttling on import time (see https://crate.io/docs/en/latest/best_practice/data_import.ht...) and also does not require a rename of a table, which is currently not implemented but is on our backlog. However i think once ES 2.0 is out we will have table renames and also throttling in insert by query, so option 2) will be recommended then.

Our genreal recommendation to the fixed number of shards limitation is to choose a higher number of shards upfront (number of expected cores matches the most use cases) or to use partitioned tables (https://crate.io/docs/en/latest/sql/partitioned_tables.html) where possible since those allow to change the number of shards for future partitions.
Are you open-sourcing your systems so that others may benefit? Or keeping them locked down to extract maximum profit?