skysight-inc/HackerNews huggingface dataset:
John does a good job of explaining the difference between software patents and traditional hardware patents to the layperson. He notes that while hardware patents are usually very specific, software patents can be so general as to cover ideas that the patent holder "had never even dreamed of". He also strongly implies that the US Innovation Act <http://en.wikipedia.org/wiki/Innovation_Act>, after being passed by the House, was killed in the Senate by lobbyists representing trial lawyers.
The problem with investment culture is twofold.

1) A lot of European money is Old Money, as in really old. You don't get to hold on that much money for hundreds of years without being on the conservative side when it comes to overly-risky investments.

2) Effective redistributive policies in the richest Northern countries have historically reduced the concentration of money to the benefit of society as a whole, but they kept low the number of people with "money to burn", a requirement for bootstrapping a healthy VC ecosystem. As a "leftie" myself, I honestly wouldn't know how to fix this without screwing up a lot of other (arguably more important) elements. Southern countries didn't redistribute as much but their elites tend to "run with the till" as soon as they can, which obviously does not help investments at any level.

Overall, I think trying to ape SV is a waste of time; each country or district should try to leverage its own cultural elements that can bring success, which might not include the requirement for VC backing.
I don't see why you equate working on Open Source projects as something "loved" and the rest as "slaving". I personally prefer working on internal code than writing patches to larger projects, since the latter often linger for weeks or months, while the former code gets into production much faster, and with less BS.

(I'm assuming the distinction is based on OSS projects vs company code. Almost all the code I write is freely licensed anyway)
Lenovo Y560 (i7 4GB RAM )
Has been running smoothly for 5+years.
The only problems I faced was a broken hinge, rest of it works perfectly, I am using Fedora on it.

Recently I purchased MSI GE60, I hope that it lasts atleast 5 years :)
Now we all need is this as a SAAS (rest API) and create a jQuery plugin that given the parameters returns the corresponding CSS
Not sure why someone has edited the title, the point of posting this release specifically (we release every quarter) was that the binary packages are now signed by default - an important requirement these days - and I wanted to emphasise that.

Anyway, enjoy! Happy to answer any questions.
hey, i'm a student of 42, would like to clarify a few things.
About the teaching assistants : we do have a few students helping the pedago team, but they aren't TA, they are in the "bocal" to help the team in place to create new projetcs, maintain the school servers and the intranet, that sort of things. Except if you encounter a bug or if there is something wrong with a subject or some hardware you are not suppose to expect any help from them, at all.

Yes 42 is a bit of a fork of epitech, but they don't have the same program anymore, the basic program is the same (projects for the beginner) but new projetcs are totally new, and students are encourage to create new projetcs too (we actually have some, like a project including docker, a student is preparing a OcamL pool etc...).

"All of École 42’s projects are meant to be collaborative, so the students work in teams of two to five people"
This is not true, the main concept of the school is the peer learning, you are not suppose to do solo projects with other peoples, you are suppose to learn how to do the project with other people, this is actually a different concept, we do have group projects though but it's a minority.
Loved this book when I was a kid, as well (and there were sequels, I think?).

It's curious -- nowadays the summary of the plot only rings a vague bell, and "Camazotz" is not a name I recognize at all. I don't think I'd have remembered this passage, had it not been cut.

But the name of the protagonist's little brother -- Charles Wallace -- gave me a delicious little shiver. I doubt I've thought of this book much in 30 years, but there's a whole section of pathways in my brain that unlocks.
...and all I can think is:
"It's a lot easier to accidentally click an ad on mobile."

Not just in the sense that they are cleverly disguised, a clumsy scroll attempt often ended up triggering an ad click for me.
I've been trying this concept for a few days and it's not that bad. It just forces me to stop typing and looking at my screen, not stop thinking or working on my problem, so it doesn't really affect my flow or concentration. It's actually kind of helpful to have to stop and think about what I'm doing.
Most arguments I've seen against HTTPS everywhere seem to fail to realise that it's not just the data confidentiality that's important, it's the integrity too.

If you don't care about the data you're getting back from a server being wrong, why bother requesting it in the first place? If you do care about it being wrong, HTTPS isn't a bad way to help ensure that what you're getting is what the server is giving out. It's not perfect, but nothing is.
Fair enough; I work in an open plan office, but conference calls and meetings are held in separate rooms.
This was done on purpose? I have seen paracetamol/tramadol combinations to get a synergistic effect (not sure that it works though). But what is the rationale here? "You got an addiction problem, so we're going to fuck your liver while we're at it" ?
First, proxies are certainly not one of the necessary principles of REST. Even without proxies, there can be REST. More importantly, most REST APIs can't take advantage of proxies anyway, because most responses must not be cached.

Second, HTTPS is MITMed using self-signed certificates (signed by custom CAs which are installed in browsers on the network) by proxies all the time. This is very common in corporate networks. Therefore, HTTPS currently works with proxies.
> I think most stuff people do nowadays is things that's not cache-friendly anyway

So you're OK with throwing away a perfectly fine and proven internet protocol which has survived for several decades, on a vague notion you have that "it's probably not that cache-friendly anyway".

That sounds solid.

> HTTPS is not a security improvement for the hosts. So what?

Reduced performance. Increased latency. Increased complexity. Increased attack-vector size. But indeed: so what?

> HTTPS is frequently implemented improperly. Non-argument.

Yes. Who cares about the real world, anyway?

I'm awfully sorry, but I honestly don't think your post counts as a very good counter-argument to those very valid points which were raised in the reported issue.
Complex answer, but simplified the answer would be yes.

The primary reason why it would be enforceable is that you need a license to run a program (copying to ram, as per https://en.wikipedia.org/wiki/MDY_Industries,_LLC_v._Blizzar...). A build program's license could thus include any type of conditions which dictate terms for usage, including what kind of license that project has.

The only limits are those inherent to copyright itself (https://en.wikipedia.org/wiki/Limitations_and_exceptions_to_...), and consumer protection laws. Consumer protection law would be the best guess as to limit what kind of conditions a product has after sale, but so far most legal system has chosen not to do so, and it get even more complex area when the product is given away for free.
This "how will you earn money" and its follow up "You honestly think people would spend hours upon hours of their free time infront of a keyboard and screen and doing what was it you said building boxes and stuff with lego like pieces!? Why would anyone play games thats not productive".

In general, entertainment, never passes these nay-sayers.
Better POP flow now than POP eyes later.
What's the cost of not having the OSS code to power your startup, and having to reimplement it from scratch or paying a huge license to some commercial vendor?
Because your initial premise is flawed. Equal GET requests will often have different results based on the user doing them. Either because they are requesting their "own" data or because they have different privileges and see different results. While not perfect, it's the reality.

This throws out all possibilities of caching. And why intermediates should differentiate more than that I cannot see. So https is in no way limiting REST.
I think SAP would beg to disagree.
Non-sensitive web traffic does not exist. Every request is sensitive in the sense that it's another piece of data that can be used to build a tracking profile of the computer that sent it. You might not care that a particular request is tracked, but that doesn't change anything because you may decide you do care at some unknown point in the future. Using HTTP takes that choice away.

There's countless use-cases where plain HTTP is not only OK, but probably the simplest and best option.

That doesn't mean HTTPS everywhere is a bad idea. There definitely are use-cases where HTTP would be faster/cheaper/easier/simpler/etc, but the move to ban HTTP takes all that in to account, and argues that banning it is still a good idea because the implications for privacy are simply more important than any of those issues.
> Overall, I think trying to ape SV is a waste of time; each country or district should try to leverage its own cultural elements that can bring success

This way of thinking is so terribly wrong. Early-stage investment is absolutely crucial to tech startups. It is not "copying silicon valley" to say that early stage investors are crucial, any more than saying that having snow or mountains is crucial to creating a ski resort. Same for many other factors.

No more excuses. No more "not invented here syndrome" of cities saying that they shouldn't copy successful parts of silicon valley, just because they don't want to feel like imitators. This attitude that every city can be special in their own way while ignoring what really matters is hurting founders.
> If you don't care about the data you're getting back from a server being wrong, why bother requesting it in the first place?

If that's the argument, it reasonably applies to everything, everywhere, and we should scrap TCP alltogether.

Instead we need to implement a replacement which ensures everything everywhere at every level of every stack does crypto as well. Let's call it STCP!

Or does that suddenly sounds zealous? It just follows from your base argument.
Really?

Depends on how much you are into it, and the type of exercise

Running in a treadmill is very different from running into a park, for example. Or where you have to overcome different hurdles and the situation changes every minute.

People usually think lifting weights is boring, I disagree. It is boring if you do it mindlessly and with low weights compared to your 1RM
Interesting - what country are you in? It is available in Denmark.
This is a current trend, I don't see a problem to have closed source, Microsoft built an empire with closed source-code and solutions, nobody complained with it. Now we are in the sharing economy era, so it makes sense to open when possible.

The big 3 problems in Europe are the lack of investors a "Siliconvallish" mind, the lack of a certain amount of money for so called "experimental" technologies and REAL exit-strategies opportunities.

Why I pointed these 3 factors? Having a right investor believing in hi-tech and experimental products, you get the money to start is also someone that bring the right kind of network. With the second factor you can scale, scaling in Europe is VERY expensive (different languages, VAT, cultures, etc...) and the amount of money required is very high. The third factor is required to get the first and the second one, we don't have a working acquisition schema. Investors are too scare to put money on hi-tech in Europe just because exits are REALLY difficult. In the Valley, if your company has a great product, you can end up bought after just 6 months, in Europe this is extremely rare.

That's point of view, I would real like to get some statistics about it and write an article, if you know a good and reliable place where I can find some valid data, they are welcomed.
So why not have the TLS applied at the edge of your network of machines that provide the service, and plain comms between them? Or is it somehow important that everyone, everywhere be able to read the stuff?
> So you're OK with throwing away a perfectly fine and proven internet protocol which has survived for several decades, on a vague notion you have that "it's probably not that cache-friendly anyway".

Don't do straw men, please. I said that it's not as big an issue as the author said it was. Nothing more, nothing less.

> Reduced performance. Increased latency. Increased complexity. Increased attack-vector size. But indeed: so what?

Not that much increased complexity in most cases. But the performance is a potentially good argument. The author should have used that instead.
and i would have gotten away with it if it wasn't for you meddling rain forests and 3rd world hungry people.
QuickBooks to be discontinued – Timescale for discontinuation
Should Every Business Have a Blog? Definitely Not
This counter-argument fails because HTTPS is much easier to implement and web servers already use it. Whereas TCP is much lower level and to make "STCP" we would have to recode servers entirely to handle both TCP and STCP requests from clients.
Or Google calls it QUIC [1]. And it's exactly that, a replacement for TCP with TLS.

[1] http://blog.chromium.org/2013/06/experimenting-with-quic.htm...
That's what I was thinking too reading the article. At least half of his points are non-arguments and and the other half is stuff like "but we've always done it this way! why change that?!"

Please. Don't forget you can actually be infected with malware through plain-text connections. It's not just a privacy thing.
> There's no reason that the majority of people would need or want drugs

Alcohol is far far more dangerous than a lot of the illegal drugs, and used by a majority of people.

That we've drawn a line where one of the worse drugs we have are on the "ok" side, while many of the milder, safer ones we know of are on the "horrible, illegal, immoral" side certainly does nothing to good.

Part of the problem of the education here is that if it was honest, then explaining current drug policy would be a big issue. How do you explain why drugs like marihuana or lsd that are near impossible to overdose on are illegal when a drug like alcohol that causes tons of death are not?

How do you explain why codeine sales is legal over the counter in many countries now, but can only be sold adulterated with paracetamol/acetaminophen or ibuprofen in doses that means abuse or accidents of them are now a leading cause of liver failure, to the extent where the illegal prescription opioids they can get hold of on the black market is now vastly safer than some of the non-prescription over-the-counter drugs they can by at their local pharmacy?

Current drug policy makes honest education impossible without admitting that the drug policy itself is not based on harm reduction or public safety. Nobody will accept drug education that explicitly admits that the policy is beyond broken.

E.g. you want to "guide future users towards safer choices"? Then one of the things drug policy should do would be to recommend cannabis over alcohol if you have first made the decision to take a drug. How many places do you think that would fly when many countries still insist on depicting cannabis pretty much as evil?
A vibrating pen helps Parkinson’s sufferers write correctly
This is a nifty find, and might make a little bump in the popularity of an acknowledged classic, but faking it would hardly be worth risking her career & reputation.

The granddaughter's job is managing L'Engle's estate.

Plus, it seems to me that a fake would be quite possible to expose -- the age of the paper/ink, uniqueness of typewriter characters etc.. It's one page of an entire paper draft of the novel, typewritten (presumably on a single machine) 50 or so years ago.
I might manage to go at WebIT Bulgaria[1] the 22nd for a couple of hours. Send me an email, we might catch up.

[1] http://www.webit.bg
Cryptography cannot be separated from authentication, and only the application can know how to do authentication. E.g. emails are designed to be forwarded between servers and not care about the exact path they take, so it would be foolish to apply hostname-based encryption to emails; instead emails are (or should be) encrypted using S/MIME or OpenPGP, to the specific intended recipient. It's then fine, indeed desirable, for these encrypted emails to be passed around over cleartext transports such as TCP.
Show HN: Seomator – Website analysis and SEO audit tool
TCP is a transport level protocol. It's job is to get messages from A to B in a way that tries to guarantee delivery (amongst other properties). HTTP is an application level protocol, it's job is to encapsulate messages and commands between two applications that may be remote. We have already built mechanisms that secure traffic on the transport layer (see IPSec) and they actually work well when they're needed/useful. It turns out that right now, securing data on the application layer is much easier / cheaper than trying to do IPSec everywhere.

Finally, HTTP is a bit of a special case, because much of the time data delivered over HTTP is code that's going to be executed on a client's machine. If anything, this makes it much more important that the integrity is preserved.
Flexbox does it for you.
http://codepen.io/kowdermeister/pen/mJbGdr
> Yet I never see one acknowledge the existence of the other, which threatens it. In fact, I'd see people religiously support both, unaware of their cognitive dissonance.

Are you sure you're not just seeing different groups of people support one or the other? I support HTTPS-only and am more or less anti-REST.
HTTP: here is the length (response header) and here is the payload transfered with checksums (tcp).
HTTP has quite good integrity of the data you requested.

If you mean HTTPs is great to check if it's coming from the right server (identity/authority) then well, see how well the CA system works and how weak certificates really are (e.g. "Ron was wrong, Whit is right").
You can work around that by doing certificate pinning (see google chrome for example) and stuff like that, but in that case I'd already be better off signing the payload and sending that as part of the response.

The scientific institutes of germany worked around all the CA headaches by becoming an intermediate CA (see who signed https://www.pki.dfn.de/ ). I'd just expect more intermediate CAs popping up as a result of HTTPs only which will weaken HTTPs even more.

(And yes, I'm using https everywhere and would enable https for just about every site, except e.g. for linux iso downloads and alike)
Researcher denied flight after tweet poking United security
Trying to shut down discussion by abusing that rule is a terrible thing to do.
This was my thought too, how far can an overpowered FM radio station on a high antenna reach? Anecdotally 50km-100km is not unusual.

In the old days there were high powered AM stations (also known as border blasters) such as Radio Luxembourg http://en.wikipedia.org/wiki/Radio_Luxembourg_(English)
There's actually a crypto IP replacement out there: https://github.com/hyperboria/cjdns
Google Search Change Tomorrow Could Cause 'Mobilegeddon'
The thing is, shared killfiles predate twitter by decades. It's not a new idea and it's not a new controversy.

If a communications medium doesn't have functioning anti-spam, it drowns in spam. If it doesn't have functioning anti-abuse, it now appears that there will be a wave of harrasment and abuse.

The most recent victim of this I can name is Sue Perkins, after the rumour went round about her being a replacement presenter for Jeremy Clarkson on Top Gear. This was nothing to do with her and had no truth in it, but nonetheless resulted in a misogynist hate campaign.
> If you don't care about the data you're getting back from a server being wrong, why bother requesting it in the first place

Perhaps I'm not overly concerned with the prospect of someone altering a gif of a cat falling over because someone put ham on its face.

People can send me fake letters and post can be intercepted but it's still useful.

I'm not saying that security isn't important or that we shouldn't be securing more than we are but the argument that it's vital everything is secured is clearly false. There is traffic that I simply do not care if it is public, and the risk of it being modified (and the consequences if it is) are so low that I think the added time and stress of worrying about it would be more detrimental to me.
First of all, the 46/LTE require some bandwidth for upload and download. The lowest bandwidth for LTE is made to match the frequency spacing for DAB (It's actually prepared to replace DAB) with 1,4 MHz channels. FM slots for broadcast is regulated as slots with 100 kHz.

A slot with only 100 kHz bandwidth will give you modem speeds, like 24,4 bits/s. So there's just not revenue to make so small speed for modern broadband networks since everyone need to share the channel.

The other issue is that the band 88-108 MHz have so big coverage, so there will be problems with the cell spacing.

So 4G via FM is not a business case. However, the DAB channels are already planned for 1,4 MHz LTE. So guess what will happend in the near future?
As I said in another thread - yes, there is corruption. But it is mainly in government spending, EU funds, big corporations. If you hire someone in IT, or work in IT I doubt you will face corruption yourself. Also, there are currently very real Parliament efforts for constitutional changes aiming at fixing this.
Shitty first commits
How to Setup Virtual Private Network (VPN) in Linux Ubuntu Based Distributions
Occams razor says OP has a point.
I know our governments are fucking our internet, but please don't help them. If we encrypt, we change the personality of the internet. It goes from a "hi let's talk" system to a "prove you are who I think you are before I say anything" system. If that sounds like a win to you, then we're going to disagree on a lot more than internet policy.
HTTP is very useful for caching and mirrors for Linux distributions because signatures are checked by package managers outside of the transport protocol.
Discussion: https://news.ycombinator.com/item?id=9402336

Other submissions, some with a few comments:

https://news.ycombinator.com/item?id=9394364 : 4 comments

https://news.ycombinator.com/item?id=9397675 : 2 comments

https://news.ycombinator.com/item?id=9394147

https://news.ycombinator.com/item?id=9397814

https://news.ycombinator.com/item?id=9394147

https://news.ycombinator.com/item?id=9403338

There may be more ...
AAAAaaand we're back to 7 solutions to a simple problem
They are transmitting public radio from Ingøy in Finnmark on 153 Khz. This is long wave transmitter to cover the Barents sea. And Svalbard/Spitsberge we can find a mediumwave transmitter on 1485 Khz.

Even Svalbard/Spitsbergen is a part of Norway - FM and AM will continue on this islands.