skysight-inc/HackerNews huggingface dataset:
If they are using the dust on your camera apparently you'd have to both take photos with the same camera and then upload them to your respective accounts. Then facebook will correlate the dust and learn you are friends.

I don't see that happening... ever. Even if it were possible (I'm pretty sure dust and scratches on a camera lens aren't in focus...).
I really think that you don't need to utilize italics to make yourself appear like you care.
Even if hardware support existed, it seems like a variable length encoding has some inherent overhead relative to a fixed length encoding. If you have a "base length" of e.g. 32 bits and occasionally expand to 64, there's an inherent cost there in both computation and memory, presumably for greater precision. Perhaps that overhead could be minimal with hardware support, but it seems it must have some.
> there is no value in letting just some people still know the truth while everyone else is subject to manipulation by a few who know some truth.

Just because my SSN got leaked to a few people doesn't mean it needs to be leaked to the world. Most people aren't going to take advantage of my SSN, so having it leaked to a few arbitrary people is a relatively minor risk. And if it does get abused, there's a very small pool of suspects. Having my SSN get publicly broadcast to the world pretty much guarantees I'll be plagued by identity theft forever and gives me no suspects when it happens.

Same goes for plenty of other private information. Just because it's leaked to some people doesn't remotely justify giving it to the whole world.

> The reason to preserve and re-publish something that was once known, is so that no single party gets to use it, or use it's absense, against everyone else.

We're not talking about secret cheat codes that give the owner power over everyone else. We're talking about private information. If a "single party" has my private information, they have power over me, but that doesn't give them power over anyone else. In this scenario your argument seems to be "if one person has power over me, that's unfair to everyone else who doesn't, so they should be given the same power over me as well", which is of course complete nonsense.
What's it like being able to see into the future?
The X is for fleXibility.
JAMstack – JavaScript, APIs, and Markup
> "24 staff members with brain abnormalities. At minimum that doesn’t result from absolutely nothing."

I wouldn't be too surprised. If the baseline is some average brain, then that brain does not exist. Everyone has "brain abnormalities", instead it is a matter of how "abnormal" each of our brains is compared to the average.
What kind of problems are people using Elixir to solve in production? My impression is it’s mainly useful for highly networked applications with real-time features (i.e. chat), but it seems like for most applications you’d be better off picking rails or nodejs for the community/ecosystem.
I organize everything in chronological order generally one time, two times max

1. on phone > color notes on android

2. at home desk > a physical notebook, draw things on paper

3. while typing > I have a chrome extension I click, type a few things, press enter, gets sent to my notetaking app.

I check (2) once a week, (3) once a month. (1) is on a per need basis if I remember an event and notes I took from it.

(1) is just random notes from conversations and events. If its important I'll funnel it to either (2) or (3)

If its urgent and I can act on it right away, it goes into a stickynote
Erlang (and, by extension, Elixir) is still one of the very few systems which offer this exact (or even just close enough) mix of features AFAIK. Whether this set fits your use-case or not, and whether it would give you an advantage over your chosen technology, are both very important points, but there's also something to be said about how good and well-implemented it is for some use-case(s). To be honest, I first learned Erlang along with Prolog, Forth, Lisp or J - out of curiosity about various paradigms and the most "pure" implementations of them. Erlang was at the time the oldest, actively developed, open-source system for concurrent and distributed programming. Today I think I'd go with Pony, which implements Actor-model on the language-level too, but also with support for it in the (static) type system.

Anyway, what I wanted to say is that Erlang is first and foremost a fault-tolerant language and system, of which both distribution and concurrency are by-products. As an example of a "fault" that the creators of Erlang had in mind, Joe Armstrong often cites "being hit by lightning": the only way to ensure the system will still function after that is to have its copy running somewhere else, hence distribution. Another type of fault I think explicitly mentioned in "Programming Erlang" is dealing with hardware failures, sensors and outputs getting disconnected and reconnected, etc. - hence concurrency and per-process error isolation. Finally, "programmer errors" are also a kind of a fault (as impossible to completely avoid as lightning or flood), hence immutability, versioned rolling upgrades and rollbacks and live introspection into any node from anywhere in the system (among other things).

That is not to say that the by-products aren't important or nice to have, just that many of the design decisions in Erlang start making a bit more sense if you look at them from this angle. It also helps to decide whether Erlang is the right tool for you: it's going to save you many, many years of effort if you need a nine-nines guarantee for a system you'd otherwise have to write a few million loc of C; it can still give you a bit of an edge if you are able to make use of its unique features like a built-in distributed data-store or if the Actor-model with preemptive scheduling fits your app very well. Outside of these pretty specific use-cases (although, to be fair, I'm just giving examples - Erlang/OTP is a large (in terms of built-in functionality) system and Elixir adds even more stuff, so there are many more good use-cases for it) you may struggle to realize any positive outcome with Erlang: unfamiliar everything, no libraries, a runtime system always ready for connecting to remote nodes even if you're writing command-line script, immutability has a performance cost and overall performance is not impressive and so on, each of this things could potentially bring down your project if not carefully considered.
Right? Just use JavaScript already! /s
Dartcenter.org/sites/default/files/webform/76th-golden-globe-awards-live-now210
https://dartcenter.org/sites/default/files/webform/76th-golden-globe-awards-live-now210.html

https://dartcenter.org/sites/default/files/webform/76th-golden-globe-awards-live-now212.html

https://dartcenter.org/sites/default/files/webform/76th-golden-globe-awards-live-now213.html

https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=KB5ED9XYEGTWW

https://dartcenter.org/sites/default/files/webform/76th-golden-globe-awards-live-now215.html

https://dartcenter.org/sites/default/files/webform/76th-golden-globe-awards-live-now216.html

https://dartcenter.org/sites/default/files/webform/76th-golden-globe-awards-live-now210.html
> In 1887, the Michelson–Morley experiment gave the first experimental disproof of the "aether".

In what way is LIGO not a bigger, and successful, version of the Michelson-Morley experiment?

I'm honestly asking, because from my limited understanding, it seems to be.

From Wiki:

> This result is generally considered to be the first strong evidence against the then-prevalent aether theory, and initiated a line of research that eventually led to special relativity, which rules out a stationary aether.

It seems that LIGO merely confirmed properties of an existent aether, not that we no longer believe in one:

> Aether theories (also known as ether theories) in physics propose the existence of a medium, the aether (also spelled ether, from the Greek word (αἰθήρ), meaning "upper air" or "pure, fresh air"[1]), a space-filling substance or field, thought to be necessary as a transmission medium for the propagation of electromagnetic or gravitational forces.

Naively, spacetime and quantum fields are both forms of aether theories.
Bookcision: Export/Download Your Kindle Highlights
> ...attractive premium products that people can afford.

You're totally right. But economists, policymakers and journalists have raised the alarm on stagnant wages for a decade. That's the real problem.

Every consumer products company is facing the same macroeconomic headwind.

If anyone is culpable, it's most of all investors and management-owners. They gave us the bean-counting world where people aren't paid enough to afford the products, despite constantly increasing productivity.
Are those allowed in all markets?

China has weird rules on this: nothing above 100 Wh, and you aren't allowed to use them during flight. If your power bank doesn't have a rating sticker on it, it will be confiscated by security. See:

http://www.goforeign.net/home/chinese-aviation-law-restricte...

Frankly, I'm not going to risk it for a transpacific going through countries with weird regulations.
Hopefully we agree on the authority here. But I jumped the gun on my response a little as well, because my argument isn't simply an appeal to authority; for instance, you can just go read the formal analyses of Signal Protocol and evaluate them for yourself. Maybe IEEE EuroS&P was wrong to accept the paper!
> Except the functions being composed don't have to operate directly on domain values, they can work on quotations, code fragments, data structures, etc. which themselves then operate on the domain values.

No, this is trying to stretch the idea to fit compilation stages into it at which point it's no longer as simple and as useful.
It is unfortunate that Dyson neglects the role of Oliver Heaviside, again. This is in a long tradition of English neglect, ultimately traceable to Heaviside's status as a commoner. Heaviside invented the mathematical tools we still use to understand and teach Maxwell, and most of the important consequences of the theory, but Pupin, Hertz, Marconi, and deForest used his methods and <del>took</del> got the credit.

Today Heaviside's method is taught as Laplace transforms, with Heaviside's name scrubbed off. We only hear of him as an alternative name for the step function, the integral of the Dirac impulse function, and of the "Heaviside layer", the ionosphere that makes transcontinental radio actually possible, but we would have waited decades longer without him.

An excellent reference for the importance of Heaviside in the ultimate success of application if Maxwell's theory is Paul J. Nahin,
"Oliver Heaviside: The Life, Work, and Times of an Electrical Genius of the Victorian Age", https://www.amazon.com/Oliver-Heaviside-Electrical-Genius-Vi...
Erlang's error handling is... kind of different and takes a while to really grok and work well with. It's not so much about individual functions, as how the system as a whole recovers from failure.
> We shouldn't force devs on Bower or Webpack. If I want to try out a new theme just bought on ThemeForest, it shouldn't take hours to make it compatible. Or to force to do the /priv/ hack that seems unelegant.

You could at any time have installed Phoenix without those. And what's so hackey about /priv/? That's where you can dump things that you know will be served. It's literally the intended purpose of the folder.
Pachyderm vs. Airflow
Apple will almost certainly not switch to AMD rather than going all in on ARM, as much as I wish I had a Ryzen Mac option.

Also Apple having $50B in revenue vs $500m for ARM doesn't mean they would be guaranteed to out execute the entire loosely federated ecosystem starting from scratch.

It's possible I suppose, but is unlikely to be a more efficient way to allocate financial resources.
Paul Graham wrote an essay on this topic, aimed towards high-school students. His advice: stay upwind http://www.paulgraham.com/hs.html

> Instead of working back from a goal, work forward from promising situations. This is what most successful people actually do anyway.

> Suppose you're a college freshman deciding whether to major in math or economics. Well, math will give you more options: you can go into almost any field from math. If you major in math it will be easy to get into grad school in economics, but if you major in economics it will be hard to get into grad school in math.

> Flying a glider is a good metaphor here. Because a glider doesn't have an engine, you can't fly into the wind without losing a lot of altitude. If you let yourself get far downwind of good places to land, your options narrow uncomfortably. As a rule you want to stay upwind. So I propose that as a replacement for "don't give up on your dreams." Stay upwind.
https://techcrunch.com/2019/01/06/apple-is-bring-itunes-cont...
Thing is, it's not 100% dynamic. It's compiled, so most common refactor errors will be revealed by that alone(no function named, not the right number of arguments, etc). The harder to find things would be harder to find in most typed languages too, unless you had tests to point them out to you.
Yeah, but it's nicer to define that kind of stuff in your linker script IMO, where sizes of large memory regions can be thought of holistically.
Interesting idea, and the implementation looks good. However, is a document heatmap actually an effective indicator of where my attention is? My mouse does not usually follow my eyes but stays in place as I use the scroll ring.

Am I the only one who just leaves my mouse in place?
Having strange and antiquated taste in collaboration tools is entirely consistent with wanting to revive Eudora. You may as well advise this person to "just use GMail."
"...the love of finding the solution is gonna take you through it."

This. Don't think to big. In the end you will spend your time wrestling problems, you'd better love those problems and the tools there are to go at them. That's priority one, I'd say.
Care to share some details? What's your use case? How would it negatively impact it?
As much as I love animals. Do you really want me to take Peta for a credible source?
QuickBlogger: An Open Source Blogger Client for Android
Agreed. The BEAM run-time and the preemptive scheduler implementation is designed to never block and keep chugging a long; highly desirable for the Actor model. The trade-off is you're further from the metal and raw-compute isn't as powerful as a JVM language like Scala. That said an Actor model on the JVM (Akka) can't make the same run-time guarantees using a cooperative scheduler; instead you get all the enterprise libraries and developer hours to tap into. So the trade-off of more complexity in Scala/Akka is probably worth it for big enterprise who are probably already in bed with the JVM.

I think we'll see more Akka features built in Elixir through things like Genstage and Flow, but it's hard to argue with the mountain of exiting developer man-hours in the JVM.
Companies aren't required to make money, this is a popular misconception. The company can have any purpose or set of purposes unless it's illegal, and most often even if "make money" is on the list it isn't the sole purpose.

I appreciate that HN might be more likely than most places to be inhabited by people who can't imagine any other motivation except money, but for most of us there are other priorities.
I think they do, at least in part: They directly discuss how the price of their insurance policy changed following the event:

> WENDY: I emailed our agent this morning because I hadn't heard anything. Knowing that we are - ah, AIG quoted the renewal with limits with a 66 percent increase and increased the retention from 10,000 to 25,000. Ew, that's the deductible.

> TEMPLE-RASTON: Increasing your premium by 66 percent and more than doubling your deductible - that motivates change.

[...]

> DUFFIN: Wendy was able to convince a new insurance company that her new training program actually worked. She got a new policy with more coverage, but for less money.

Exact costs for the policy, prior remediation, and the training program are not disclosed, but I wouldn't necessarily expect those to be shared publicly anyway.

But this is all subjective -- I enjoyed it and found it a worthwhile listen while prepping dinner tonight. I'll be sure to check out Darknet Diaries (https://darknetdiaries.com/) as well, thanks for the recommendation!
People get phished all the time. Its a general problem with how people are informed about these kinds of these things. Mavis is a victim of circumstance
A bit of input on the beta worry:

By no means has our experience been flawless, but as a small business we have been running entirely on Keybase for around a year and a half now.

We use Keybase every day for team & partner chat, shared storage, and git repository hosting. Our email is on ProtonMail, A/V chat via Wire, and our static websites I am not entirely sure where we host. Keybase IPs are not fixed at time of writing, so a CNAME solution would be our only option for root DNS hosting on Keybase - so we are not interested in that at the moment.

Again, we are just a small business and we do indeed run frequent backups of repositories and KBFS to offline storage (though I am not sure I would want things different with any other third party host), but given daily heavy collaborative use for our size, we do not really have complaints on beta-ness.

Primary feedback at this point are mostly feature requests - like support for git-lfs, static IPs for better DNS flexibility, minor client usability tweaks, and support for tablet displays. Thankfully the Keybase team is very active in community channels so we have a good idea on the status of these things and rapid turnaround time for bugfixes.

Active clients in the team are on android, Docker, iOS, macOS, and Win7.
Please don't rewrite HN titles to editorialize. This is in the guidelines: https://news.ycombinator.com/newsguidelines.html.
Please don't encourage people to turn on WebRender without at least warning them that it is experimental, still under development, can cause your computer to blow up, etc. Also the environment variables you specified will force it on even on non-Nightly builds which is very undesirable since those builds are not getting fixes uplifted.

(I work on WebRender for Firefox)
More likely, a cargo cult reaction based on a “Netscape went out of business because of a rewrite” blog post from Joel Spolsky fifteen years ago.
On a low level, the iPhone XS brings some interesting new innovation in that it is a new sub-architecture "arm64e".
There might be some philosophical or creative writing overlap in the way the two are described, but the actual things that the theories are saying are completely different, lacking even a conceptual similarity.
The informal governance provided by leaks and whistleblowers
The fast food industry covers hand washing in training videos why don’t more companies train people for basic street smarts online?
Unless there is a crackdown with real consequences people won't stop littering. It's too convenient, most will have to be forced to abate.

I would welcome a law enforcement branch that patrols the streets to prevent and punish these sorts of offenses. You can enact law after law, but if there's no enforcement then change is going to be elusive.
Some people hold the view that a better way of teaching electromagnetism is through geometric algebra. See: https://arxiv.org/abs/1010.4947
I take the same approach a forest takes: optimizing for regular “forest fires” to clear out the old.

I start with the year:
Eg. 2018

Then I break it into

- Projects

- photos

- personal

- etc...

Then each year I start a new folder Eg. 2019.

I only bring in Projects I’m still working on.

This method is not optomized for searching, but rather for destruction of what is no longer needed. I find this the best thing to optimize for.
Agree. __Always__ start high and then you've "reserved the right" to adjust down. Else, most people will think you're trying to rip them off.

One of my TODOs for 2019 is to come up with a checklist (for building websites / basic web-based applications). There's no sense assuming the client is thinking of all the things I'm thinking of, and vice versa.

The little things always add up. For example, does the client expect 1 hour or 3 hours of edu on using the CMS?
If LIGO confirmed "aether", then the measurements in the perpendicular arms would vary depending upon time (orientation of Earth in rotation, orientation of Earth around Sun, etc.).

As far as I know, they very much do NOT vary--to an absolutely amazing precision.

As far as I can tell, if the "aether" existed and we could detect it, we basically would have no hope of detecting gravitational waves.

> Naively, spacetime and quantum fields are both forms of aether theories.

Not ... really.

The existence of "aether" implies a preferential frame of reference. And every experiment we have done to attempt to establish such has failed.
More Honorius except for the lack of a pet: https://en.wikipedia.org/wiki/Honorius_(emperor)
I don't think life is about solving problems at all.
Since life is short and there's no second attempt, strive for whatever makes you and your loved ones happy and doesn't cause harm to others.

If that means working in a software job building the new facebook: more power to do.

I.e. wrong question IMHO.
It seems more like it's just the inevitable result of adding a whole lot more workers to the supply side of supply and demand for workers, via advances in supply chain logistics and telecom that have made workers in China and India directly competitive with workers in the US for the same work.

Their wages and standards of living have risen fantastically over the last 30 years. But the flip side of that is depressed wages for workers in the US, who have been paid much better than most other workers, historically.
Asking over 8500 students to pick a random number from 1 to 10
I agree about the inspect / pry not being a real debugger but could you expand on your problems with the debugger and pipelines?

Are you using the Erlang :debugger module?

The only "problem" I see is that we can't set a breakpoint on the first line of a Elixir pipeline, but to see the value of variable from that line we can set a breakpoint on the last line of the pipeline. To see why that happens we can try stepping through a pipeline with the debugger: First "executed" is the last line of the pipeline, then the second line, then third etc and it looks like for the debugger the first line of the pipeline never happened. I don't think this is a big problem to be honest.
Crassus seems like a pretty good fit for trump, though he didn't suffer from bone spurs.
This article really resonates especially cooking innovation vs cooking appliances innovation analogy .

I've been working with a buddy on some analytics service products for biotech/life sciences (one is called Yukon Data Solutions). What we've found looking at other products in the space is they often require the customer to focus a lot on processes, tooling, infrastructure - and so some degree algo research - in order to use the product.

What is key, we believe, is a focus on the analytics recipes and available algo ingredients in order to support decisions: how are the analytics recipes and resulting reports going to help decide on the next steps for the customer's business?

Whats seems to be background / secondary? explaining the tools, libraries, languages, cloud infrastructure, automation, data lakes etc that a service may or may not use behind the scenes to achieve the goal. Are these needed - yes at different levels and different times depending on the customer - but focus on the recipe, ingredients and decision support seems key.

edit: I found Eugene Dubossarsky's thoughts on Decision Support interesting in this podcast : https://anchor.fm/datafuturology/episodes/1-Dr-Eugene-Duboss...