skysight-inc/HackerNews huggingface dataset:
The Palo Alto equivalent (which I've seen) is "the bartender gives 3D printing pitches"
Maybe html was wrong phrase. I mean the distributed nature as typified by everyone having their own domain - with attached storage. This was the default back in the dial up days (side thought is that Apple could bring that back - iCloud is nice as storage and all but how much will it take to go from iCloud to paulsdomain.com/photojournal - that’s almost a Facebook killer and at some point is much much easier to distribute)
Did you patent your IP first?
Google did something similar to me as I have detailed in this thread below....

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

It's very relevant to this story and I think it's important for it to be told to warn other inventors how Google treats the little guy/girl!
That end is called raising the interest rate. When the rate hits some magic phase transition number where enough people believe you can invest in safe liquid accounts for more than the return on risky assets then the whole thing collapses.

But then it'll get propped up again afterwards and everybody believes that now.
I believe the core devs agreed to make a proposal, and then the proposal got rejected by the other devs.
WHY IS IRAN NUCLEAR PROJECT TRUMP’S NIGHTMARE?
Thats funny, after working with most major device manfacturers on digital video for 2 years (2009-2010), I submitted a similar concept to YC in late 2010 but received no reply. My core point was mobile device manufacturers desperately need a USP and this would work nicely combined with some DSP based nearby device playlist remixing and possibly a heartbeat sense and some GPS smarts. You know for shared sports like cycling and jogging and rowing and stuff. Perfect sync not required, since everyone is on earbuds. Vary the music as you go over the hill, the sun sets, tempo manipulation, auto-transitioning between tracks, etc. Would work just as well for smarter playlists while driving. Tech's all there these days, still not aware of anyone who has done it. If you make millions on it wire me 100k. :)
Thank you. This should be the link in the title. Better still, we should reassess https://news.ycombinator.com/item?id=13434938 and ban direct links to pay walled sites.
Can someone ELI5 whats the core tech behind Project Genie or Flux? What I've found are some vague descriptions like "Flux provides seamless data exchange between industry design tools such as Rhino and Revit".
I recently turned down a job offer citing an overly broad IP clause. I had a call within minutes offering me a choice of how else it could be worded.

I still turned it down and decided to go freelance instead because the contracts I had read had raised all kinds of personal questions.
No, he really is against the tools. He is on the record as being opposed to static typing, optionals etc.

And by the way, noone is making the argument that tools solve all the problems developers deal with. But to say that actually, they solve none of them, is foolish. Optionals, to take one example of something Uncle Bob is against, prevents a large proportion of what is probably the most common runtime error, namely dereferencing a null pointer. And yes, Uncle Bob is right that it comes at the small expense, which is having to think more carefully up front about your data and your abstractions, and there is no doubt he is right that some programmers will feel constrained and will find and use whatever mechanisms exist to bypass the safety that this feature offers. But in much the same way, there are also some people who feel constrained by seat belts, hard hats, helmets, dust masks etc. and choose not to wear them, yet you don’t find many people who would argue that this makes them pointless and generally a bad idea.
Go mobile is pretty decent for building SDKs, I am always wary of solutions which abstract the native APIs as you can get pinned to a particular iOS or Android version while waiting for updates.

Go Mobile allows you to use the Go standard library and packages to build an SDK which integrates as a library by exposing C interfaces. With Android it creates the JNI stuff for you, iOS ObjectiveC bindings. As long as you avoid / be aware of any other C based dependencies it is pretty safe and maintainable.

Building an iOS framework still requires a mac as it needs to shell to xcodebuild but it does work pretty well.

With all of these tools you have to consider the Software Application Development lifecycle. What is the lifecycle of the application, are you prepared to completely re-write if the tooling disappears, can you suffer not being able to use the latest native framework while waiting for tools to update compatibility or are you prepared to pitch in and update the tooling yourself.

For me the main complexity with native apps is the UI, these APIs require specialist knowledge and can often wildly differ between platforms. React Native does a good job of abstraction and maybe this coupled to GoMobile is a dream partnership.
I think in many ways Trump and Sanders had the same appeal to very different demographics.

We've all come to understand that politicians are mostly liars. And I think Trump represented what was seen as a break from the mold because he seemed authentic. He said things that you're not "supposed" to say, he acted in a way you're not "supposed" to act. In general, he seemed to be being a person and not a politician. He made lots of promises as all politicians do, but I think his behavior being far outside of the mold gave people hope and optimism that he was being genuine - that he would actually fight to bring jobs back, work to curtail foreign competition for what jobs there are, and so on.

Sanders similarly broke the mold of a politician. Polls show socialism focus tests somewhere near the apocalypse, yet Sanders openly called himself a democratic socialist. And he talked about many things that have become completely taboo in politics including the corrupting influence of banks paired with a completely myopic monetary policy, single payer healthcare systems, corporate tax avoidance (something Trump also hit on), and more. He said things you're not supposed to say, and so I think we also viewed him as breaking the mold of a politician - and being somebody that might genuinely work to do the things he is talking about.

The behavior you're describing is why it's particularly tough for the two sides to ever see eye to eye. Imagine you were one of these disenfranchised poor living threadbare and barely getting by ever since the day you were born --- and the national discussion was on how to try to treat individuals who came into the country illegally better. That sort of thing breeds resentment. That resentment in turn is then characterized as racism. And that perceived racism in turn denigrates their own position even more, which results in even more empathy for immigrants leading to even greater resentment, and so on. It's a vicious cycle.

I wish there 'domestic exchange programs.' Have a substantial number of individuals living in one side of the bubble temporarily join a family living on the other side. I think peoples' eyes would be opened if they could see we all really just want the same thing - and that's a better life for the people. The only thing we disagree on is how to get there. But somehow in this process instead of seeing eye to eye we've instead characterized those that disagree with us as something less than rational humans capable of being swayed. And as both sides refuse to communicate to the other sides rationally this sort of inhumanity becomes a self fulfilling prophecy.
Interesting to note that dollar adjusted the market has actually been going down for months.

http://ei.marketwatch.com/Multimedia/2017/10/04/Photos/NS/MW...
> Seems like it would be hard to get Haskell to run 8/9 as fast as C.

The typical factor mentioned in the Haskell world is 1/2 the performance of C.
> And incur legal liability? Businesses will gladly do lots of manual work to avoid thousands of lawsuits.

Pretty sure that forcing thousands of businesses to upgrade their systems to avoid defrauding users is grounds for a lawsuit itself.

Imagine if Google, Apple, and Microsoft teamed up to make an incompatible change to web browsers that broke all existing websites and exposed all of the users of those websites to risk of finical loss of the website admins did not perform an upgrade.

Who is liable? The admins who didn't even realize an upgrade was required, or Google, Microsoft, and Apple for creating the situation?
People who write these articles I think learned from the last crash that those who "predicted" it became famous ("Did you hear, so and so called it, smack on the nose, they must be a good economist. Let's have them write a book").

So now nobody wants to be left out, and so they predict crashes every week. Eventually when a crash will happen they'll say "see I predicted it, where is my book deal".
EU to implement electronic ID to accelerate adoption of e-government services
I use the dialpad all the time. Not for numbers, but it also supports T9, searching through your contact list by names.
If I find a bug on my own I can do as I please with it. I have no obligation to inform the vendor. I can write an exploit and publish it, share it with my friends, or sell knowledge of it to whomever I please. The vendor has zero right to my work or to dictate what I do with it.

There are few things more frustrating than dealing with a vendor that doesn't understand this.

On the other hand, if I find something while being paid to look then I must tell only the client and hope that they are responsible enough to disclose it instead of silently patching.

I don't these are minority views.
SRE consultant here.

I was dissatisfied with Linux and FreeBSD, seL4 seems much more robust, in terms of system reliability and security. (seL4 is not an OS, but a framework to build an OS on top.)

Then I was dissatisfied with all the crap in the x86 ISA (bucket of modes, 4 rings, many deprecated features, insecure SMM and zillions of feature flags), the mostly failures of RISC and the over complexity of many versions and variants of ARM (but it’s nice that it’s available as IP).

It seems there ought to be an architecture that can make writing OSes easier and more secure:

- handle task/context switching much faster than x86

- IPC (zero-copy both register and page borrowing, maybe copy if source page is locked or if async.) This enables L4-fast CSP in the ISA.

- resource limits / counters

- memory page allocation

- capabilities management

- transparent page compression and encryption

- OS bookkeeping (kernel-specified privileged data: per task/core/etc.)

in addition to the usual suspects (MMU, FPU, SIMD, etc.):

- virtual memory

- paging (including possible unprivileged page-fault handler)

- hypervisor (VM lifecycle)

- interrupts / faults / exceptions

- TLB

- tiers of caches / cache coherency protocol

- memory controller

- standard I/O controllers

- clock throttling w/ spread-spectrum and thermal management

- micropower standby

- JTAG

- at least one system-wide atomic operation (compare&swap or ainc/adec)

much more rigidly, faster and less clunkily that most OS gunk tends to be. Not CISC overload, but healthy facilitation of fast AND secure OS and user-mode program constructs that are batteries-included.

Also, SystemVerilog looks doable (I’m reading the whole IEEE spec for SV2012) and there’s always MOSIS should a Kickstarter be in order to make actual ASIC dev kits. EDA looks manageable but there’s a definite learning curve to testing, verification, behavioral design, RTL and DRC.

Plus, opaque firmware blobs and chips aren’t conducive to trusting the end-to-end security of the supply chain of a finished product. End customers are almost praying that some fab hasn’t slipped in malicious microcode or RTL changes or the parts stuffers didn’t insert a backdoor into unsecured firmware.
Here’s a thought experiment. Yes Bitcoin is global but like all other distributed systems, the CAP theorem applies. When there is a network partition, you can only choose between consistency and availability. Now what if tomorrow the Chinese government decided to totally block Bitcoin traffic, just like they block Facebook, Twitter, NYT, Tor and VPNs? Losing either consistency or availability would be a heavy blow. It’s either going to stop working at all, or fork into a Chinese and non-Chinese version. I don’t see how either of them inspires confidence.
>"It’s even worse than just using the proprietary information — they actually then claim ownership through patent applications,” Buether said.

Why didn't Attia patent everything already? He'd been working on it for 50 years.

I suspect Google is really just getting into the building design software space but not using Attia's work and Attia thought he was now a part of any effort by Google in building design software.
The Art of B2B – applying UX and CX Thinking Strategies
For a few years I used a 34" ultrawide next to a 27" monitor (they're exactly the same height).

Recently I switched to a single 38" ultrawide (a xr382cqk) and I've taken down the second monitor.

Windows and OS X both have good enough tiling that I can use the single monitor without the distraction of bezels, and there's much less ceremony to hooking up one monitor

I think the same thing would work with a ~40" TV, and I e seen people do it, I just prefer the space efficiency of the ultrawide
That's simplistic. Why would they go to the trouble of "cutting out the people who originated these ideas" if they are already at X Labs and the project was to continue?
Show HN: Free Advertising on Dust
From Edison to Jobs its the American way..
So according to Bell Labs testing, the telephone layout (123/456/789) beat calculator layout (789/456/123).

That raises some questions.

First, why is there a difference? For any given sequence of numbers both of those layouts requires the same amount of movement, just mirrored around the 456 line. There should be no physical reason for one to work better than the other, so it would seem it is something mental. What is that?

My guess is that it has something to do with our left to right then top to bottom reading order. If someone speaks out loud the digits from 1 through 9 in order and you are asked to write them down in a 3 x 3 matrix as they say them you will probably fill them in reading order, giving 123/456/789.

Second, it would be interesting to see what would happen if the order within the rows were reversed, 321/654/987 vs. 987/654/321. My guess is that the latter would beat the former. It gives a less complicated sequence when accessed in reading order.

Third, I wonder which layout would have won for calculators if the calculator makers had tested like Bell Labs did. Let's assume it is a given that we have to go with either 123/456/789 or 789/456/123, and just need to determine which works best in a calculator.

With the phone all you need to operate it are the digits (the first touch tone phones did not have the '#' and '*' keys).

With the calculator you also need the decimal point, the operator keys, and '=' [1]. The layout of the digit keys needs to fit well with the layout of the non-digit keys.

I'd guess that '=' is the most used key, with '+' the second most used. Third is probably '-', although I'd not be shocked if it was 'x' because it will see a lot of use in percentage calculations which might be common enough to put it ahead of '-'.

Because '=' and '+' are so important, it makes sense to put them somewhere that can be identified by feel, and the best place for that is probably one of the bottom corners.

If that's where we put '=' and '+', then I expect calculator order in the 3x3 digit grid would win, because of Benford's law [2]. Calculator order would put the smaller digits closer to '=' and '+' than telephone order would.

[1] or 'ENTER' if you are civilized.

[2] https://en.wikipedia.org/wiki/Benford%27s_law
Another recommendation for Enpass. I started using it because they had a great desktop Linux version which worked perfectly with their Firefox & Chrome plugins. After that, paying $10 for the Android version was a no-brainer.
It's somewhat obvious by the content of his post. (I do actually really appreciate when people do disclose their conflicts here. Thanks to those of you who do.)

theDoug is also not wrong, to be fair. There's no situation in which a Google employee who is not a lawyer publicly commenting on a lawsuit against Google works out well for the employee. Anything he says could get his employer in additional trouble, and as an employee, commenting on a legal case is really, really easy grounds for termination, pretty much anywhere. Whether he agrees with the article or not, nothing he says ends up beneficial to him, so it just makes sense to not comment.
> they are really just TXT with an API

No, they're really not. An SRV record points to a hostname, not an arbitrary string. You can do lookups in one RTT, not two.
I just hope it doesn't collapse when anyone looks at it.
> Use with non-OSS modifications, as a component of non-OSS, or to develop non-OSS (the most controversial) falls outside L0-R's license conditions, after a grace period.

I'm trying to understand your "controversial" clause. I have doubts this is compatible with any existing definition of FOSS, but maybe I'm misunderstanding.

Does that mean everything I create with a software under that license is under the same license?
To put this into a concrete example: If I have a text processor under that license - does that mean if I use it to write my emails I have to disclose my emails to anyone who is asking, because they're now under a copyleft license?
> You can't equivocate the n=1 case and the n=10000 case.

Fair enough, but the comment I was replying to was equivocating those cases too. I was simply pointing out that maybe, just maybe, a service like this might have some value above and beyond a 5 minute script and a cron job. And indulging in a small rant against the "i could do that in a script/i could write that in a weekend" etc mindset.
Url changed from https://qz.com/1095294/2017-nobel-laureate-jeffrey-hall-left..., which points to this.
Simple, because then they'd have to share the profits with them.
Just for fun, check out all the variants Nokia has tried out: https://i.pinimg.com/originals/ca/41/48/ca4148e6aeba457a6abd...

They have tried almost all the concepts from that bell study.

Especially interesting is 7610 optimized for thumb reach. Other funny ones are 7600, 3200, 3650 and Ngage QD
> There are few things more frustrating than dealing with a vendor that doesn't understand this.

I think they do understand this very well; they just want to brainwash people into thinking it's a civic duty to do what they say. It's not. Ethical security researchers' responsibility is to the users, not to the vendors.
Thanks for your suggestion, but I am not sure how to implement this in practice? How do you generate different email addresses for different websites for a typical user who uses gmail?
Not sure how Apple deprecating a transitional tech is a valid comparison to Swift. You might as well say APFS is a passing fad that some manager might cancel and we'll all be back on HFS+ soon.
Mall developer rebrands amid rising vacancy rates
Violetear – The journey to achieve 0 allocations
You might be wrong. Rust is as fast as C and creates binaries as small as C.
Seems to me like SSN is missing an open free (as in paid for by taxes) 2FA service.

When I obtain a drivers license or passport (or some other process to confirm my identity at a government facility) that I should be able specify my 2FA medium (email address or phone number [text or call]).

Any organization that wants to prevent identity theft should be able to do a 2FA challenge. As an individual I would receive a phone call or text or email "Acme Co. is processing a request to open up a new line of credit under your SSN. Did you initiate this action?"

There should then be regulatory requirements on banks, insurance, etc that require 2FA confirmations before associating an SSN to your account.
Are you on Windows? If so, Bazel now bundles the JDK so you should not have to worry about Java.
>But it isn’t easy to ...

Surely that's a significant understatement. Once mega copy dev has planted that idea in one's mind it must be hard to kill off. So maybe one needs to have thought about the possibility of an unwelcome approach and have a plan to kill it.

Maybe:

1. Ask mega corp to authenticate themselves - maybe by posting a pre-agree shared secret on their corporate blog.

2. Post the approach from mega copy dev on one's own blog telling them to go away. Eg. "I received the following unwelcome approach from a large Mountain View search company - details redacted (snark) ..."

Comments?
This article is about a security flaw, and yet the website is leaking database error information. Seems safe.
Our tools & materials are constantly changing... not to mention that every project is different in various ways (though many developers delude themselves into thinking their project is unique i.e. the snowflake effect). I've found the most success when I stick to tools/patterns/strategies that I've had some degree of success with in the past.
> > Plenty of FOSS is well funded
> For example?

Is that a serious question? Ok...

I heard Google pays its employers quite well. Plenty of FOSS is developed by Google, for example large parts of Chrome.
I think Linus Torvalds gets a reasonable salary. So do many other kernel hackers - payed by all kinds of companies.
Red Hat seems to be doing well, they have plenty of people working in all kinds of FOSS projects.
I already mentioned OpenSSL.
React is developed mostly by Facebook employers. I guess Facebook pays good salaries.
I'm surprised by the resistance of some of these iOS developers. You would think that after years of developing in a language that looks like diarrhea they would have gleefully switched over to Swift.
Personally I’m of the opinion that Bitcoin is already “too big to fail”: there are so many interested parties and stakeholders who want it to succeed that it will be kept alive through sheer will, despite internal politics.
Have fun dealing with ALL the 16 Landesdatenschutzbeauftragten taking a very close look at you.

Considering that all this tracking has to be opt-in under German law (I talked with the Landesdatenschutzbeauftragte of my state about your "experiment" here already, and they confirmed it), I’d say you can expect quite some trouble with the way you’re running this shit.
Calculus is a low level tool that you need to know in order to effectively think and communicate about problems that deal with numbers. Signal processing is probably a big chunk of these problems. That can be things like, computer vision, audio DSP, etc.
Google is big and has plenty of money. It sounds more like politics than anything financially motivated.
The line is crossed if you attempt to market and sell it for illicit use, or a prosecutor thinks they can demonstrate that you did effectively that. See: recent case about the guy writing the remote system control software then became a popular hacking tool / RaT.