skysight-inc/HackerNews huggingface dataset:
> You can't just call it "malvertising" when it's just not what you wanted...

It's an advertisement which seeks to get users to download software from an unofficial source. The site does not provide links to the official sources.

The advertiser has paid money to get users to go to their site instead of the official source. The advertiser seeks to misdirect users into visiting their site (which is loaded with ads) instead of the official one. I consider this misdirection to be malicious.
To me, the supposed benefit of using blockchain was so obvious as not to require stating: Removal of any central authority over connecting customers to service providers. And you might not want Uber tracking your travels, for example.

There are good arguments for centralization, too. Not saying the blockchain argument win out. Just saying, the benefits are the same as for every other blockchain application, and well understood.
We detached this subthread from https://news.ycombinator.com/item?id=10946398 and marked it off-topic.
I suspect the 3 month certs is to make sure you have to authenticate your domain 4 times a year with Let's Encrypt to make sure that you can't hold a valid SSL key for the domain for more than a few months after you transfer it. Also, if someone manages to scam Let's Encrypt, the resulting cert is only valid for a short time.

The local client is there to make sure that the authentication process can be automated and not require your manual intervention.
My advice is to be realistic about how much change you should handle all at once. You've been at this place 10 years so a job change alone would be a huge change for you, bring stress, uncertainty, doubts, regrets, etc. And you are going to be welcoming a child at the same time. This will be physically and emotionally exhausting for you and your partner.

I went through almost the exact same situation except we had twins. I had a very tempting offer on the table when my wife disclosed that she was pregnant. I ended up staying and received paid leave and was able to stabilize myself after about 10 months such that I could move on to a new job.
Ok I see now.
I think both methods have a place going into the future.

What I've understood from Relay/Falcore/etc. is those technologies are great for something like Facebook or Netflix, hence why they made the frameworks, but for many other cloud/web apps, it may not make sense. A single atom app state works really well. Is that along the lines of the right thinking? I'm using React+redux along with websockets and haven't had any problems with large state trees, but the whole state can be sent to and from the server very fast as it's not too big.

I'm sure Elm will have something comparable to Om Next/Relay/falcore as well then, to solve those use cases.
> - Why do we need a local client app to issue certificates? Is there a web interface in development? Is there a technical reason for it to work this way?

The client takes care of solving the ownership challenge, provisioning the certificate and configuring your web server (if you want it to). It also helps with renewal, in a way that it can be automated completely.

The entire process uses an open protocol (ACME), and there are a number of alternatives out there. If you like web-based ones, look at https://gethttpsforfree.com/

> - Why does it issue 3 month certs? Beta period? (This is reason enough to pay btw, If I did not screw something up to end up with short term certs)

This is likely to stay even after the beta. The reasoning behind it is that Let's Encrypt makes it easy to automate renewal, and shorter renewal periods will encourage users to configure and use automation as opposed to doing it once a year and then forgetting about it. It also reduces the time frame in which you're vulnerable in case your key is exposed at some point. (CRL and OCSP solve this only in theory.)
This doesn't seem quite right. Did you maybe mean "#undefine FOO" or "! defined(FOO)"? Whether BAR gets expanded or not, in your example it looks like it would always evaluate true. Or am I misunderstanding the ambiguity?

It might be telling that I also don't understand the Clang bug report as written. I think there are typos in the examples. Is the switch from "HAVE_FOO_BAR" to "HAVE_FOO" in the first example intentional? Is the construct "#defined" (with a final 'd') intentional in the second?
57km (35.4 miles) may sound impressive enough in isolation, but it's not until you start putting it into real-world context that you realize just how monumental a tunnel this is: Imagine driving any of these commutes entirely underground:

- The Chicago Loop to Naperville (31 miles)

- SF SOMA to Palo Alto (33 miles)

- Midtown Manhattan to Perth Amboy (32 miles)
I can't even figure out how to get on the property sometimes - see the old EDS "Mothership" in Plano! [1] Amazingly, the front desk was on the 4th or 5th floor archway - which you could not get to without getting past a badge reader. (that's the way I remember it anyway)

Street signs, entrances, etc should be optimized for both first time users and everyday users; which is difficult, but without that traffic goes slower and you have more accidents, people get frustrated and hate you.

[1] https://h71044.www7.hp.com/campaigns/2011/events/POD/images/...
Why? AWS is issuing certificates. They happen to be doing that through their new Certificate Manager service, but the more interesting news is that AWS is issuing publicly trusted certs.
The goal with letsencrypt is to get everyone using SSL, even the layman. With that in mind they aim to automate the process as much as possible so you don't need to remember to update your cert or worry about it expiring. The client will handle all this for you in the background.

They are even considering shortening them to less than 3 months. I think the goal there is to ensure people automate it who would otherwise try and do it manually.
> I've never been openly been discriminated against

Yes, I always walk around with my head in the sand too.
A 3-year wildcard cert from rapidSSL is only 200 bucks when purchased through a reseller. If going in that direction saves you even a couple hours over the course of three years, it's more than paid for itself.
I honestly can’t wait for VR products to be easily available. I finally went to my 1st CES 2 weeks ago and theres a bunch of cool VR headsets heading our way this year.

One of the big ones I tested was the 3Glasses D2. They’re supposed to be shipping to North America this year for $399. SO much cheaper than the other ones I tried. Still has a great latency, FOV and refresh rate. I spoke with them for a few minutes when I was there … apparently they have a standalone headset coming out later this year too. (Saweet!). Anyways - they were my biggest surprise from CES. Definitely one to keep on your radars.

I also checked out some of the bigger named-VR sets at the show (Oculus, Samsung Gear, HTC Vive). There were a few glitches (as expected with young tech), but there’s some really good stuff coming out to look out for. Great English content too - gaming and videos.

I also heard about Deepoon - a Chinese knock off of Oculus. Apparently they’re trying to use Oculus’ content on their VR headsets and sell for less. Cool idea, but there’s got to be some issues with intellectual property/compatibility. No objection Oculus? It’s an interesting convo about innovation vs. straight up copying successful competitors.

Anyways - can’t wait to see how the industry changes this year as products/content actually enter the market. Think it will become mainstream? #hereshoping
There's a basic start to a remote syncing tutorial here: https://github.com/omcljs/om/wiki/Remote-Synchronization-Tut...

Basically, you specify a query as a remote query and it calls a `send` function that you specify, and you manually pass the query to the server to execute, which will return results and automatically be merged into the app state (and of course, re-render components that depend on that query).

For the part where they stop making that request, they must do custom lifecycle code so that when the component unmounts, they are able to access current open requests (probably indexed by component manually) and cancel it. That part is not builtin to Om Next.
Should You Use Deliberate Practice… or Just Practice?
Certainly! I'm currently working on the case sensitive search issue, but afterward I'll try to see what it'll take to make a feed.

Can you create an issue? https://github.com/iankronquist/y-cloninator/issues
A very interesting article. It is always good for world cuisine when a culture participates in international trade. But the article gets a few details wrong, in forgetting the occasions when the Persian language took in loanwords from other languages, for example "tamarind," which comes from Arabic and means "Indian date."

https://www.google.com/search?q=etymology+of+tamarind&oq=ety...
The local client app is needed to verify that you actually own the domain.
3 month certs are actually more secure since there is shorter amount of time in which they can be stolen & used.
The goal of letsencrypt is to make re-issuing certificates automated, so even a 1 week certificate is no problem since you can run a nightly cronjob to refresh it.
I'm using Let's encrypt for personal and work stuff. The official client stinks. The first time I tried it I had to shut down my web server to get the cert? It was my personal stuff, so I did it, but moved on to find a new solution for work. I'm using this: https://github.com/diafygi/acme-tiny. It needed a bit of a tweak to get the challenge files to show up on all of the EC2 instances that hide behind the ELB since you don't know which one will be hit.

As for the 90 day limit, we aren't too worried. We'll add domains often enough we shouldn't have to worry about it. and it can always be automated.
By splitting the addition up into two discrete calls, the ordering is made much more explicit, there's no room for ambiguity.

In C#, the largest part of a TimeSpan is a day, you can't have a TimeSpan of "one month and one day", because adding that to a DateTime would add a different amount of absolute time depending on the DateTime. You can have a TimeSpan of "32 days", and adding that to any DateTime yields a consistent result.
Buffy the Vampire Slayer, A.k.a Sarah Michelle Gellar, Launches Food Startup
The New Way to Code Python
> (oh god, I’m doing it)

What a wonderful bit of meta-defensive writing.
This is why everyone hates working with time and date functions. :-)
I couldn't find the answer to my question on that registrar, but does anyone know if this will be recorded?
Jim Louderback's Predictions: Big Media Developments of 2016
Yep. "Assuming the initial odds are right, these guys may have cheated". That's one hell of an assumption. The odds moving is one of the strongest indicators of the initial odds not being right. Market efficiency etc.
> Why does it issue 3 month certs?

IIRC, it is to encourage automation, and short term certificates are somewhat more secure (shorter period of use if one leaks and it isn't revoked; shorter period to attack the keys [shouldn't be an issue in any reasonable time period, but it can't hurt to limit it] etc.)
Thanks for sharing your experience!

I think that not having fun (I know this is rough simplification) is terrible. What worries me is more that I have weird sadness in the evening when I have finished my work and have not touched any side project or did some learning. I don't have any energy for learning and that makes me feel worse...
Traveling through time with 'Braid' creator Jonathan Blow
Has something actually changed? I mean, appreciably in just a few months time?

Just goes to show angel investors, while an essential component of the startup ecosystem, can be emotional, illogical, and volatile.

If you're unable to accurately value what you invest in and prone to getting swept up in hype, you shouldn't be investing in startups (or maybe anything).

The ones who suffer in all this aren't the investors -- they're already rich. It's the employees who get shitted on, forced to work harder for less, or loose their jobs because of the whims of the market and other people's faulty thinking.
Comments moved to https://news.ycombinator.com/item?id=10945219.
Would you bring your electric car inside your home?
I mean, ATX (or other standards like MiniITX) boards are still really nice for initial embedded development. Even past that, it's really nice for a test farm for CI of embedded code. The weird boards are just them cheaping out. When they pass the savings onto you ala the Raspberry PI it's great; when they don't ala most FPGA dev boards, it really sucks.

That's why ARM has the Intergrator/Versatile series of dev boards. Back in the day, MIPS had the Maltas.
I really like this play - GM can undercut other organizations that are forced to purchase their vehicles, as well as realizing savings on maintenance. Over time, they can slowly strangle competitors in the car manufacturing business - users lower their usage of personal vehicles, due to easy access to Maven vehicles. Then they switch away to Maven permanently.

It also sets them up, in the long term, to run a self-driving car organization. It establishes the brand, service, and the maintenance organization.
We picked the other one because it contains more background info. If people disagree, we can swap the URLs.
It looks like this is free (the pricing page isn't up yet), as I was able to issue a certificate and not have any charges show immediately.
Yes, but I'd ideally go to a licensed, brick-and-mortar store for the reputation and reliability over either eBay or Craigslist, if it weren't for the prices and availability of items. My point is that the benefits of centralized, non-blockchain solutions can outweigh what you lose when you go decentralized, and that's something that should be questioned of every new blockchain application.
What's frustrating for me is this obsession governments have with the encryption aspect of cryptography, and the carelessness they have with the authentication (signing) aspect of cryptography. If they break the former, they break the latter. The authentication aspect should assure sender and receiver both their mutual identities and the veracity of message content. If any portion of that authenticity goes away, massive trust is lost. Signed digital documents, legal or even everyday emails, is then broken. Both current and historical documents are affected. Voice conversations and voicemail can be recorded, modified, and rebroadcast - my conversation with a bank, a broker, reciting my SSN, all of that can be used with a copy of my own voice in ways that hurt me or other people and implicate me.

I'm convinced elements in governments are playing with matches. I don't know that it's malicious, but at the least it's obliviousness.

It may be inevitable that this gets severely broken, and that's the thing to plan for - the aftermath - not dissimilar to compsec practice of preparing for infiltration by better protecting data itself rather than relying solely on the idea of an impenetrable network.
I have nurtured the secret belief that the reason that Letsencrypt renews certificates ("automatically") every three months is not a feature... but a forced limitation by the guys who own the root cert chain.

If I'm a startup, why should I shirk away from paying 9.99 for a RapidSSL certificate from namecheap and have it working reliably through Ansible/Puppet/Docker... and rather muck about with the chance that my server SSL cert may go down because my letsencrypt client was outdated or something.

Or worse, I have a wordpress site running on a PHP host - the best case scenario is that they agree to use a certificate I buy. Running a python based client ?
"You are the enemy, and are not be trusted.

Every time I've been pulled over, the police office has walked to my passenger side window with their hand on their sidearm. I'd say the subtext starts way before mentioning any actual rights I might have (and that the Supreme Court has stated that must I explicitly use in order to keep)
No, cost is not a reason. The infertile male mosquito method isn't the best one we have.

Geneticists have discovered ways to drive terminal genes into entire populations. A mosquito species could be wiped out in no time with a gene drive.

https://en.wikipedia.org/wiki/Gene_drive
I don't think it's that's simple. It's not that it works better for hugely complex apps. It just works better for certain kinds of apps, even if they are small. The project I'm working on is small, but Om Next is far better suited to it (the complexity of using Redux+Redux/etc on it would be far greater).

The question is, are the majority of apps better suited for a tree-based state or a queryable graph? I'm not sure, but it's at least even.

I've heard Elm is working on something similar, so I wouldn't be surprised if that happens.
How about non-engineering applicants?
Why is there also little or non-existing black non-engineering (accountants, lawyers, project managers) staff in SV?
You're proving my point for me. They're the middlemen who over the last few decades managed to make themselves indispensable. The law is that complicated for a reason, and it's not just because humans are messy.

Speaking about your example - somehow, many otherwise civilized countries manage to handle DUI cases without lawyers getting involved.
Buying SSL Cert through Bluehost (my domain registered, and blog hosted) and figuring out how to apply it my web-app, zejoop.com, hosted on AWS was far and away the most annoying and difficult chore in my development/deployment process as a relatively junior SW developer. If I could solve all inhouse within AWS (at reasonable cost) is be very happy. My cert just renewed, so until I roll change to AWS my https:// is down. If update is as difficult for me as original install was, then I guess it will be about 18 hours of aggravation. So I'll look into this, if the OP title is a reality.
Yes, I didn't know "Honor" was the name of the startup (Which focuses on Elder Care) until I opened the article.

On an unrelated note, it's interesting to see that the decision to do this was less related to the current contract vs full-time debate and more related to Honor's specific industry and business model.
That's just about the only possibility, I think -- both forms should generate the same sequence of uops.
I am talking about very early employees. What is the typical dollar amount in RSUs or stock a new engineer after MEng is getting in Google?
Not really. For instance I work for a retail company. let's say someone wants to find out all the products on a weekend that made over 10000$. This can of info can be generated by the AI which can query that companys database.
> Solving this impedance mismatch

The solution seems now to get rid of the REST paradigm(GraphQL ...).

While I have no opinion on what should be the right solution, I welcome the idea of questioning the usefulness and the significance of REST, especially in the era of fat web clients.
As to Mexico, language barriers are still a thing.

However, the real cost is the content that's not created. If an author is paid by the book then they tend to be of reasonable length. When paid by the page, you get content that never really ends. Compare MMO's with single player games and generally MMO's last much longer, but are less fun while your playing.

Advertising driven content is similarly insidious. You don't want people to spend a lot of time reading or thinking, just click click click.
Mirage uses OCaml's strong types to generate secure, fast and highly specialised code. It's also very succinct and with LWT, almost as good as Haskell for lightweight concurrency and nonblocking IO. Why would you want to use Python? This is a golden opportunity to learn and use a superior language.
This one actually isn't Mike Bostock. It's just "hosted" via his `bl.ocks.org` service. The code itself lives in a Gist[0].

The original author is blacki[1][2].

[0] https://gist.github.com/blacki/ebba08223eba20b56b62
[1] http://bl.ocks.org/blacki
[2] https://github.com/blacki
SaaStr – Your VP of Sales Shouldn’t Be Perfect
The presence of both "so obvious as not to require stating" and "Not saying the blockchain argument win out" suggests that it's probably not as obvious as it seems. :)
It's about damn time, I'm up to my amigaut in manuscripts!
As an EU citizen let me assure you that it is indeed a sales tax. The French guy who conceived it just thought to give it an innocuous name to better sell it to the public. Sure, if you are a company you may offset part of it but for private individuals that makes absolutely no difference whatsoever.
I'd like to know this too. I can't spend an entire day watching this but I certainly would like to view the talks over time at my own pace!
Time Inc. Is in the Midst of a Replyallpocalypse
IMHO, working on timestamps in code like this is just asking for edge case to bite you in the ass.

The only sane way I've found to work with time is to convert any timestamp into a seconds-since-the-epoch value when doing any internal work and then covert back to the timestamp format for display. As an added bonus your code won't get super messy when you start getting timestamps from different sources that are formatted differently. Everything gets normalized to the internal representation before you do work on it.
> As usual, SEC Consult Vulnerability Lab communicated this issue according to our responsible disclosure policy. Initial contact and exchange of the security advisory was performed through the European sales team at AMX.

My stance with these things, is if it's a backdoor, "responsible disclosure" is out the window.

Just expose the criminal to the public.
> Induction defines that line

Really? How?

> the onus would be on the skeptics to explain WHY they think the sun won't rise tomorrow

You've just contradicted yourself, and sided with Deutsch (and hence with Popper) here by admitting that if a skeptic can explain why the sun won't rise tomorrow that the skeptic might be right. That's Deutch's (and Poppers) whole point: it's not about induction, it's about explanations.

BTW, it's a question of when, not if, there will come a day when the sun will no longer rise. The best estimate at the moment is about 5 billion years from now.

A better example of the failure of induction is this: Barack Obama has been the president of the United States for about 2500 days now. And he will almost certainly be the president tomorrow, and the next day, and the day after that. But I can nonetheless predict with 100% certainty that, one way or another, he will not be the president one year from today.
Personally I don't find using npm shrinkwrap a chore at all. If npm 3+ notices a shrinkwrap file in the project it'll update it automatically, so most of the time you don't even have to think about it.

We've been using npm 3 on multiple large projects spanning frontend and backend, being worked on by many developers, pushing code through CI into production many times a day and npm installing fresh in every environment. There are probably many thousands of nested dependencies in some projects. It works, nothing bad happens, it's fine.

Npm comes with some trade offs, true, but also a long list of plus points as well. No system is perfect, but you're painting some calamitous disastrous picture here which simply isn't reflected in reality.
Then they just sell their car if they don't work for Uber anymore. It's not like cars will suddenly become worthless.
It could change in the future, but there are a plenty of languages that got pretty mainstream while closed source -- in terms of working with numbers and data, I'd definitely call matlab and sas mainstream, stata and mathematica are nearly mainstream, R of course is open source which is a huge reason for its popularity, but it's a clone of closed-source s+ which was fairly popular already. In the general-purpose world, c# and swift got most of their traction while still closed source, etc. Surely there are more examples in other domains... But yes, there is definitely a very welcome trend to open source stuff.