skysight-inc/HackerNews huggingface dataset:
Thank you for the detailed write-up! I have some questions, I would like to understand it better. You are a real expert and I appreciate your taking the time to understand my question and help me understand better.

1. Why do you say cash-rich founder's offer of $500K is within 10%-20% of the market price of the shares, when in fact the market has just priced the company at $7M, half of which the market has therefore just priced at $3.5M? It seems to me that $500k is 1/7th of $3.5M, so the offer is only 14% of a fair offer...

For example, what if one partner is greedy and wants to buy out the less greedy, but also poorer, technical founder, after they have some huge windfall that gives huge value to the company. (Some of which is reflected in the $7M valuation they've received - which is not at all low.)

2. You write "that's exactly why investors insist on vesting schedules, first rights of refusals, tag-alongs, bring-alongs, etc". Would you say under the typical clauses offered by VC's, they would allow the remaining founder to spend an unexpected and large amount of money from the company coffers in order to buy out the other partner? (Or repay a debt investment they had raised to do so)? Why would the investors allow that? Especially if it was not envisioned explicitly under "use of funds" and, of course, they'd rather have two partners work on it than one. (But the greedy, cash-rich funder would prefer to own and have the company by himself.)

3. You write - "he might not have access to lenders/investors, which could get him treated unfairly". Would the company be able to raise debt to finance a buyout of one partner by the other or is that not something a company can raise debt for?

Thanks for your answers. I'm pretty shocked at everything you've said. (As you noted at the top of your comment, I misinterpreted you also.) By the way, this does not apply to a situation I am in - and I hope won't apply in the future. I simply do not really understand the clause and its implications in the real world, that well. Thanks for your help.
They were poisoned. After living an the aquarium for years, right before this "vote" came to the park board.

Not a lot of direct evidence, but a shitload of smoke.
Looks like Kotlin will soon be skyrocketing to the top of the TIOBE charts.
* How does one realistically protect against these new attack vectors?*

Do not install unsigned software is a good start. Does that dialog need a secondary 'Are you really really sure?' absolutely .. but the basic defence in this specific case was in place.
I feel like if tech announcements should just be basically patch notes. Why all the pomp?
Interesting, also hadn't heard of pushcrew (which it asked about), that also looks interesting.
$300k at the end of retirement not at the start. Having $300k more than you actually need isn't what I would call rich, but it's also not marginal.
Self-Hosted “SQL-Not-required” Data Analytics and BI Tool. Inspired by Looker
Potential North Korean missile would hit San Francisco in 30-34 minutes
Interesting; 101domain.com charges $160 for 2 years (2 year is required through them). I'm assuming they're getting some sort of discount?

That is an interesting avenue to go however, so thanks!
No one to threaten to make the ship stop either. There's a fair chance a would-be pirate would end up in Hamburg.
Is hiring ML talent in that industry any more difficult than generally?
Great writeup!. I think a lot of developers would do well to understand both the 'right' way to respond to this sort of event, and the tools you need in order to do so. Most importantly being detailed loggging and processes for re-keying everything.

I've participated in, and run, exercises where such damage is inflicted on purpose to surface gaps in the the response processes and to fix them. I was inspired by the Google DiRT (disaster recovery) and NetFlix Chaos Monkey exercises. Both of these create not simply review processes but simulation by action, or actually doing the damage to see the process work. Setting up your systems so that you can do that is a really powerful tool.
"The U.S. Coast Guard has estimated that human error accounts for up to 96 percent of all marine casualties."

But if we somehow manage to account for 90% of all eventualities when programming, how are we going to be safer?
IBM doubles power for quantum systems, developers execute 300K+ experiments
> it's admin interface is by far the best thing since sliced bread for internal/backoffice applications.

By the way, some best practices here that I've discovered:

- Use the Django admin for performing actions closely tied to specific models that don't involve any business logic. E.g. changing which one of a user's email addresses is their primary address.

- For admin business logic that spans multiple tables, (e.g. inactivating a user's email address and logging that action in a different table), just create an app called admin_api or something similar and then create DRF endpoints for performing this sort of admin logic.

The benefit of having your admin business logic wrapped in REST endpoints is that you are writing and testing all your admin logic the same way as you write and test all your other endpoints. And since all your admin business logic is just another Django app, you can create models for your admin business logic, e.g. for logging the results of your database integrity checks. And then you can use the standard Django admin on top of those tables, so you're basically putting an admin on top of your admin.

And because all your admin logic is encapsulated in rest endpoints, you have the option of either hitting those endpoints from Postman or some custom admin front end, or else hitting the service methods that perform the business logic for those endpoints directly from the Django admin actions dropdown list[1].

[1] https://docs.djangoproject.com/en/1.11/ref/contrib/admin/act...
Multiverse: have astronomers found evidence of parallel universes?
No it doesn't allow you to make an informed decision. It only indicates the presence of offensive words from a list you do not know, but trust anyway.

To keep an eye on my son, we just mirrored the TV and stereo signals from the living room to the kitchen. We actually see and hear everything he does. THAT'S how you stay informed!
I don't think it would be that much of an asshole to sell the data so that a user starts to see ads for their local gym in their Facebook feed all of the sudden.

You'd be making the world a better place by encouraging the act of exercising. And the lower cost of healthcare. It's pretty much up to you now!
I suspect it's the opposite. TensorFlow in source will never be as fast as the TPU cloud with custom processors, so it won't be as suitable for serious high volume production stuff. It's more like a hook into the TPU ecosystem.
I think one of the things that get people excited about Go on desktop is it is one of the few well supported GC langs that compiles to an exe. There isn't anything else super compelling about it.

On android, everything gets AOT compiled on install already.
The thing to keep in mind is that this is the Wal-Mart model: drive prices as low as possible (and maybe sell in bulk). It squeezes/kills the little suppliers (such as indie developers), drives down the notional market value of goods, but feels like a good deal for consumers.

At least in current society there isn't anything overtly wrong with "the Wal-Mart model" as it stands, but recognizing a Wal-Mart model is the first steps towards trying to figure out if it is long term healthy for the community. (Which brings us back to the article at hand, questioning the long term health of the community in the face of a Wal-Mart like Steam.)
you should replace 'always' with 'foreseeable future'. its plain wrong otherwise.
>Nobody, not even Marx, is claiming this.

You're quoting me out of context. Marx claimed:

lv = lw + p

With lv being labour value, lw being labour wage, and p being profit.

He alleged that the capitalist is expropriating the p from the worker. What you quoted is out of context because it leaves out the "+ the profit earned by the employer" part of the equation.

>The employer does not actually buy labour, this is a popular misconception. He purchases the capacity to perform labour, which is measured usually in hours (though it can be measured by other metrics too).

No, the employer is buying labour. Labour means work done. That's what an employment contract stipulates the employer is buying.

This is why I call Marxism quack economics. It misdefines and mischaracterizes basic terms and concepts to validate its story of exploitation. It's pure intellectually dishonest demagoguery.

>Nobody denies that the direction itself is applying labour to the products; for if it wasn't, engineers or project managers wouldn't be applying labour.

I'm not talking about workers directing other workers. I'm talking about directing the financial capital that hires the workers. Investments require analysis, and that is work. The actual process of saving and safekeeping capital is also work. This is all ignored in the Marxist analysis, so that you can arrive at the verdict of exploitation, where the "capitalist not only receives the fruits of his own labour, but also the fruits of others' labour".

Which is absolute nonsense on so many levels that it's clear that the intelligent advocates of the theory, like Marx, are being disingenuous.
If part of the value of the source code is its secrecy, then its value decreases when it's made public.

It's not necessarily true that part of the value of source code is its secrecy, though. We'd like to believe that, but it's difficult to come up with evidence to support it. Most instances where source code is leaked result in no damage to the owner, for example.
They did get together to sort the mess out. They did so in the 1980s. Where do you think the idea of "ANSI function prototypes" came from?
Prior HN coverage: https://news.ycombinator.com/item?id=14315036
The author took the time to write a blog post, but not trying the code for anything else than that bogus() function. Had they done that, they would have realized their mistake.
Sophie+Sofa+on+Saturn+by+Lenny+Nobrega+
.ai is a ccTLD that is run by, I believe, a single person in Anguilla. I do not think it is run on a platform that supports EPP, the standard protocol that is used by registries and registrars to handle automated purchasing of domain names. Given that, it would not be possible to handle .ai domain names on Google Domains. 101domain.com is likely doing a manual process for registering .ai domain names that goes through https://whois.ai/

(Source: I am the eng lead of Google Registry, which run's Google's TLDs.)
I'd like to see a language available at the item level. You can derive the language from the http headers but if you're dealing with linkblogs it would be nice at the item level to help with filtering.

I think that images and urls would do well as order lists rather than as individual values. at the top level you have 3 urls and an array for hubs. with type and url you could have an array for hubs and the urls. same could be done for images at the top level and both again at the item level.
As to why they implemented the killswitch, a simple guess will be a slip up or poor personal security leading to your lair being raided by some unforgiving 3 letter agency that doesn't mind meting out a few harsh knocks until you cease the spread.

However I agree with you on the poor implementation of the killswitch. The first thing that came to mind was, why not use an .onion instead? It might mean bundling the malware with TOR but I've seen enough of these use cases to know it's not a challenging thing to implement.
Better to have the entire computing might of the world struggle to crack your private key instead of some lucky researcher registering your domain and halting your spread.
Probably most notable case is https://en.wikipedia.org/wiki/Brandon_Teena (the story was made into the movie Boys Don't Cry). You can find quite a few more on https://en.wikipedia.org/wiki/List_of_unlawfully_killed_tran....
http://www.popsci.com/high-salt-diets-might-make-you-hungrie...

>The more salt you eat, the thirstier you get. Right? Wrong, according to two studies released today in The Journal of Clinical Investigation. The research found that as salt consumption increased, people actually drank less water. And the high-salt diets seemed to make study subjects hungrier, too.
TESLA V100 is apparently ridiculously expensive at 65,0000$.

In fact to an extent even NVidia has realized that there is more money in creating a GPU cloud from scratch rather than selling GPUs.

I think the net losers are Apple, Amazon/AWS (I believe NVidia is responsible for their lackluster GPU offerings.) & Intel (Who are still hoping for Multi-core to work. And are on track to be disappointed just like they lost mobile market to ARM hoping for Atom to be eventually adopted.)
I like writing Go, and it's my go to (pun intended) for writing web API's. Building a framework around it for Android apps would be a mighty task. Kotlin makes more sense considering it's connection with the JVM.

I'll keep writing Java to build Android apps though. I'm sure it's "more fun" or whatever, but Java's worked just fine for me thus far. I'm used to the verbosity, and have no desire to start from scratch with another language. If some huge benefits were presented, I would. But, I'm failing to see any.
San Francisco sues Uber in battle over driver privacy
No, Android does not support JavaFX or Swing for that matter.
How many Android 5 devices are still receiving security updates?
Google shut down my apps for work because one of our devs had multiple sign-in enabled and he had a banned play account. Google uses its bots for the ban hammer so just be careful
For example: "Trading on Private Information: Evidence from Members of Congress" (2016) https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2712297

EDIT: Also "Abnormal Returns From the Common Stock Investments of Members of the U.S. House of Representatives" (2011) https://www.cambridge.org/core/journals/business-and-politic...
That's my point though – it doesn't have anything to describe metadata, so therefor trying to cram in additional semantics is futile if you still want to call it JSON. Call it something else and you can attach whatever semantics you'd like, but they think it should be served up as `application/json` which means all those semantics go out the window.
I can see myself using this for simple communication on 3D geometry work to my colleagues (I work a lot with 3D rendering). Hand drawing is so hard sometimes :). However, for that it would need at least a transparency option so I can layer boxes and all.

Otherwise, it feels really smooth in my browser. Good job there. I can see more shortcuts in the future but as I have very basic needs these are not a showstopper for me.
Agreed. Greater efficiency, lower power and data usage... are those not things that premium phones can benefit from also?

I suppose you have to give up some features, but given how few of the features on most apps I do use, I think this could be an acceptable tradeoff.
This relies on the security of my phone OS, which I trust much less than my desktop's.
Couldn't they ransom the cargo?
Honest question. Have you ever been in the engineering spaces in a ship/offshore rig/etc.? Do you have any idea of the diverse type of work a ship's engineer and his various reports do?

I don't mean to pick on you too much but the idea that you can have little Hueys, Deweys, and Louies tooling around a container ship doing whatever maintenance is required is ludicrous.

And the other suggestions about having crews that you transport from ship to ship isn't quite as unrealistic but is needlessly complicated in the way that software often is. Among other things--have the people suggesting this sort of thing ever been in the North Atlantic in bad weather?
If you're already familiar with Android dev, using the built in Convert Java to Kotlin feature in Android Studio is invaluable, especially in the beginning.
dude, that doesn't mean scam. It just got used by some scammers.
Seems very likely given that the Russians have hacked the White House in the past:

Even after spending millions of dollars on security, the White House admitted in 2015 that it was hacked by Russians.
Why do you think that Handbrake is only for ripping DVDs?
I read it more as "I hope this isn't used as an excuse to lock down execution of arbitrary unsigned binaries".
Oracle winds up killing another golden goose they aquired from Sun. That's what they do though. They buy innovative technology companies who have committed customer bases and then slowly squeeze all the money out of them until they can migrate off. By then they've aquired another set of victim customers.
Um -- as someone who has bought Swheat Scoop for my cats for almost 20 years -- I can assure you it's not the low-cost option. Clay is much cheaper.
I'm in New Zealand in case that matters. The interface is horrendous - and it has numerous checks it requires before you are allowed to pay and each step takes a long time to accept, and it hates "fill" as an option (rather than say $50) - Do you have any discount receipts (from supermarkets)? Have you an AA card? Do you authorise payment up to X? Are you sure? Hold being placed... Waiting to process....
If you pick up the pump at any stage before it's ready it all breaks.
> without stopping to wonder why HandBrake would need admin privileges, or why it would suddenly need them when it hadn’t before

Seems like it's completely random that an app needs admin or not. Blender3d? No admin. Unity3d? admin. etc.
I'm slightly skeptical at the moment because there was a lot of buzz at the time of the press release, and then it's total silence for more than a year now. I tried to find any sort of hands on commentary to confirm that it actually works and exists, but no luck.

Still, if it were a total scam I wouldn't think the Mayo Clinic would put their name on it.
It's unfortunate that XML has fallen so out of favor that well-made, strongly-schemad formats specified in XML, like Atom, are suffering in turn -- although reasons for feeds' demise go well beyond its forms-on-the-wire. This trend frustrates me, but it's undeniable that a lot of web data interchange happens with JSON-based formats nowadays, and the benefits of network effects, familiarity, and tooling support make JSONification worth exploring.

But even more frustrating is when a format comes out that's close to being a faithful translation of an established format, but makes small, incompatible changes that push the burden of faithful translation onto content authors, or the makers of third-party libraries.

I honestly don't intend to offer harsh targeted critique against the authors -- I assume good faith; more just voicing exasperation. There have been similar attempts over the years -- one from Dave Winer, the creator of RSS 0.92 and RSS 2.0, called RSS.js [1], which stoked some interest at first [2]; others by devs working in isolation without seeming access to a search engine and completely unaware of prior art; some who are just trying something unrelated and accidentally produce something usable [3]; finally, this question pops up from time to time on forums where people with an interest in this subject tend to congregate [4]. Meanwhile, real standards-bodies are off doing stuff that reframes the problem entirely [5] -- which seems out-of-touch at first, but I'd argue provides a better approach than similar-but-not-entirely-compatible riff on something really old.

And as a meta, "people who use JSON-based formats", as a loose aggregate, have a serious and latent disagreement about whether data should have a schema or even a formal spec. In the beginning when people first started using JSON instead of XML, it was done in a schemaless way, and making sense of it was strictly best-effort on part of the receiving party. Then a movement appeared to bring schemas to JSON, which went against the original reason for using JSON in the first place, and now we're stuck with the two camps playing in the same sandbox whose views, use-cases, and goals are contradictory. This appears to be a "classic" loose JSON format, not a strictly-schemad JSON format, not even bothering to declare its own mediatype. This invites criticism from the other camp, yet the authors are clearly not playing in that arena. What's the long-term solution here?

[1] http://scripting.com/stories/2012/09/10/rssInJsonForReal.htm...
[2] https://core.trac.wordpress.org/ticket/25639
[3] http://www.giantflyingsaucer.com/blog/?p=3521
[4] https://groups.google.com/forum/#!topic/restful-json/gkaZl3A...
[5] https://www.w3.org/TR/activitystreams-core/
the steering wheel

https://www.youtube.com/watch?v=d3pQ0oO_cDE
You forgot another criticism: The repeated plug for Mathematica every 3-4 pages.

I couldn't get past 10% of the book before I got sick of the "Look how great Mathematica is for describing these algorithms!"
2nd out of 2 results. That's pretty funny.
My interpretation: 1) they always charged for SSL overhead; 2) they introduced a bug in late 2016 that underestimated SSL overhead; 3) that reduced charges for SSL overhead, and also broke flagging of Spark and Flame plans with too much SSL overhead; 4) they just fixed the bug, restoring normal estimates of SSL overhead; and 5) that restored accurate charges for SSL overhead, and also restored flagging of Spark and Flame plans with too much SSL overhead.

I'm guessing that OP's SSL overhead spiked after the measurement bug was introduced. Maybe also Firebase wasn't enforcing their limits before introducing the measurement bug, because they weren't confident about the data.
This is clearly a better part of the petrol pump world than mine.