skysight-inc/HackerNews huggingface dataset:
I found this article related to the attack in that paper https://bitcoinmagazine.com/articles/why-bitcoin-mining-pool...

While I'm not completely convinced that the countermeasure of "spy mining" completely mitigates the attack, it does appear that this is not a new vulnerability. Further, if a pool had all of the hardware under one roof, it wouldn't be possible to spy at all which would reinstate all of the problems outlined in the paper.
Pro-tip: do an "experiment" with blockchain (built in house to keep it cheap) so they can tell their golf buddies they're looking into it. Make sure it's compared to a sane solution, because then they can feel superior for having "insider knowledge" that it's pointless.
Speech synthesis not recognition.
Spoken like someone who is a true introvert who thinks before they speak:) Thanks for the read - Nina
Summary: Better building codes would help us all, they need to improve too.

They're better to live outside, but our building codes don't make them better to live /inside/.

(I mean actual refuge that provides quite private space with silence, clean air (no odd smells/smoking of various types/cooking/baby diaper pails/rotting milk trash cans), and true tranquility.)

Bad neighbors can exist anywhere though. The suburbs have streets which might be fine for small sedans but which loud motorcycles or 'MAC' trucks shoved inside of oversized pickups can ruin. It also only takes that /one/ person smoking somewhere even vaguely near-by to ruin the clean air around that house.
>"Excessive automation at Tesla was a mistake," Musk tweeted recently. "Humans are underrated."

Ironic to hear this from a company that is aiming to build autonomous vehicles.
>>Well, trying to build AI using failed papers from the 1980s have near zero value today.

I think if you had picked any other example you'd have been correct, but many current-day AI advances are based on decades old techniques. One caption from an article about Geoff Hinton states: "This publication from the mid-1980s showed how to train a neural network with many layers. It set the stage for this decade’s progress in AI."[1]

[1] https://www.technologyreview.com/s/608911/is-ai-riding-a-one...
See what Facebook thinks is in your news feed images
ChromeOS been secure since the get go. Just seems weird Google can do it and MS struggles so much.

Now you get GNU/Linux out of the box but security intact.
Build an Instagram “Pin” Effect in Python with Correlation Tracking
Yes, and specifically in the case of Premier League it seemed to cause problems with needing extra stoppage time. There was a recent match experimenting with video replay, and one side's manager complained that more extra minutes should have been added because of the video review, but wasn't (presumably because of TV advertising scheduled).
MongoDB sharding chunk
> The real question is: with the benefit of hindsight, could you define a better but similarly simple format?

I think the only answer to that question is to build it separate from JSON if you think it can be better, if it is truly better it will win in the market. There is no reason to break JSON and add complexity to the parsing/handling. It is 10x harder to implement simplicity than a format that meets all your needs that ultimately adds complexity.

The problem is when people want to add complexities to JSON. There is nothing stopping anyone from adding a new standard that does do that. But I will argue til the end of time that JSON is successful due to simplicity not edge cases.

Everything you mention can be implemented in JSON just as a string with type info, just because you want the actual type in the format might be the problem, it doesn't fit the use case of simplicity over edge cases. Your use case is one of hundreds of thousands people want in JSON.

> But sometimes one tool could have been better without giving up any of what made it useful for its niche.

Famous last words of a standards implementer. JSON wasn't meant to be this broad, it reached broad acceptance largely because for most cases it is sufficient and simplifies data/messaging/exchange of data. There are plenty of other standards to add complexity or build your own. You use JSON and like it because it is simple.

The hardest thing as an engineer/developer is simplifying complex things, JSON is a superstar in that aspect and I'd like to thank Crockford for holding back on demands like yours. Not because your reasons don't hold value, they do, but because it is moving beyond simplicity and soon JSON would be the past because it will have been XML'd.

In my opinion JSON is one of the best simplifications ever invented in programming and led to tons of innovation as well as simplification of the systems that use it.

If people make JSON more complex we need a SON, Simple Object Notation that is locked Crockford JSON and any dev that wants to add complexity to it will forever be put in the bike shedding shed and live a life of yak shaving.
I'm not going to disagree that data formats should undergo a process.... but sometimes they do undergo too much process. Most of the EDI standards, for example, are a product of a huge amount of committee that sells a lot of standards and are used extensively yet are almost impossible to write a parser for.

Edit: obviously this isn't the case, since people have actually parsed it, yet it's a non-trivial thing to do and I have yet to see a solution that isn't horribly specific or a solution that ignores something that might be problematic in non-standard solutions (of which there are a million because of the difficulty involved). A huge amount of domain specificity doesn't help either.
A Laravel inspired Python framework
One thing that seems to be not really commented on is "Play Testing / Exploratory Testing" ( and semi related, "dog fooding"). This is the manual test process where someone actually uses the software and looks for problems. Problems are then captured as a new automated test case. This is about finding undesirable unforeseen consequences ( sometimes you get desirable ones! though if it is desirable, you will want to capture it in a test also ).
mid-size coastal cities are severely underrated imo. sure you miss out on some of the glamour, but you can get a pretty nice urban lifestyle and your tech salary goes way further. personally, i love being able to drive anywhere within the city limits in under 30 mins and being able to find parking when i get there.
Tide works well with typescript, which I find better than ES whatever.
As seen in their very example: ETC exists distinct from ETH
> i’d seriously question your rationality as a member of this scientific-related community.

Speaking of science, do you know of any peer reviewed paper that concludes that the blockchain “creates trust where there is none”?
I was recently at an "Emerging Technology" conference for emerging technologies that was targeted at non-technical entrepreneurs and innovators. 90% of the conference was focused on blockchain, while the remaining was focused on AI. During the entire conference, blockchain was being touted as a silver bullet for many problems, and many of the people at the conference ate it up.

The best anecdote to summarize the conference was a speech by IBM where they covered a project which they did with major retailer to track a supply chain. The speaker mentioned some impressive results which caused a noticeable people around me to literally say "wow". However, they did not once mention specifically how blockchain was the cause of these results or give reasons why blockchain was superior. From what I could tell as an engineer, the entire application could have been built without blockchain.

I was surprised at how blockchain was being touted as the next technological revolution (and very light on the details) and was concerned at how quickly the other attendees accepted blockchain as it was being sold. I left the conference thinking that it would only be a matter of time before blockchain would be touted as a silver bullet in the larger community due to conferences like these (although I am sure they've been happening for a while, and this was my first exposure). It will not be long before a large number of software projects will be based on blockchain needlessly, and/or the engineers will be arguing with management why using blockchain is a mistake.
I had a whole week of Facebook Messenger annoying me with requests to let it access my contacts, my photos, my location, or how such-and-such a person might be a good candidate to “friend” on Facebook. Not one useful message from anyone: all the people I need to hear from use SMS or email or even iMessage. Everyone else’s messages are still there in the Facebook web interface.

So I deleted Messenger from my devices. I haven’t missed it at all in a year.
Accessing Suicide-Related Information on the Internet (2013)
So if it's a ticketed event (i.e. you can't enter without a ticket), would eventbrite need to buy a ticket to access the event to record it?
My terrible customer service experience with Audi
I'm glad you had a good experience with Protocol Buffers. (I work on the protobuf team at Google). But I would advise a bit of caution. Writing a fully-compliant protobuf implementation is trickier than it looks. I'd recommend running any new parser through the conformance tests; I created these to exercise some of the edge cases.

https://github.com/google/protobuf/tree/master/conformance

Here are some of the quirks of protobuf:

- non-repeated fields can occur multiple times on
the wire -- the last value "wins".
- you have to be able to handle unknown fields, including
unknown groups that can be nested arbitrarily.
- repeated numbers have two different wire formats (packed
and non-packed), you have be able to handle both.
- when serializing, all signed integers need to be sign-
extended to 64 bits, to support interop between different
integer types.
- you have to bounds-check delimited fields to make sure
they don't violate the bounds of submessages you are
already in.

I do think protobuf is a great technology overall. But it has some complexities too; I wouldn't want to oversell its simplicity and have people be unpleasantly surprised when they come across them later. :)
My leverage wasn’t that bad. To close I had to spend about $4,000. No down payment. It’s an FHA 30-year fixed at 3.85%, so I bought really at the bottom of the market. I’ve got a great tenant and about to renew them for another year with no increase in the rent. The income from that has been a god send and I’m net positive on expenditures. I’ve managed to get 3 months ahead on the mortgage payments to account in case I DO have a vacancy and need time to find soenone. I just got extremely lucky. I bought out of a fear of being homeless (for whatever reason) and to secure a foudnation for myself as I grow older. It’s become much more and I’ve learned a helluva lot.
Citation needed.

Banking provides a number of services and employs a bunch of other peoples. Sending money from a to be is just one of the things it does.
Well it's a bit old now but a few years ago on the Hiawatha blog a test of load under attack was done and Hiawatha was able to handle a simulated (d?)dos very well.

I'm on mobile but a quick ddg show: https://www.hiawatha-webserver.org/weblog/64
I’ve never had problems with almond milk, cashew milk, coconut milk, or soy milk not being able to stand up to coffee, which usually has a lot more acidity than tea.

For me, it’s been more about the taste of the non-bovine milk itself. And almond milk is by far the best thing I’ve found so far. I also like when it is mixed with other non-bovine milks, like cashew and coconut.

If you use cold-brewed coffee, that has a lot less acidity than hot-brewed coffee. So, it works even better with non-bovine milks.
We should've drawn the line in the sand back with 56 bit key limits
The S-expression has cleaner whitespace and field names than the JSON, which makes it harder to make an apples-to-apples comparison.

But the biggest problem with that S-expression is that I don't know how to parse it. Is SGML a symbol, identifier, a quoteless string? How do I know when parsing the 'entry' field that what follows is going to be a list of key/value pairs without parsing the whole expression? Is 'see-also GML XML' parsed as a list? How do we distinguish between single element lists and scalars? Is it possible to express a list at the top level, like JSON allows? How do you express a boolean, or null?

Of the problems outlined in the OP, S-expressions solve one: there's no question of how to parse trailing commas because there are no trailing commas. They do not solve questions of maximum levels of nesting. They have the same potential pitfalls with whitespace. They have exactly the same problems with parsing strings and numbers. They have the same problem with duplicated keys.

My point here isn't that you can't represent JSON as S-expressions. Clearly you can. My point is that in order to match what JSON can do, you have to create rules for interpreting the S-expressions, and those rules are the hard part. Those rules, in essence, _are_ JSON; once you've written the logic to serialize the various types supported by JSON to and from S-expressions, you've implemented "JSON with parentheses and without commas".
By "community" do you mean the website forum operated by Y Combinator Management LLC? That's some hubris.
I think the reference was to invisible powers controlling your news, search, social, legislative, and economic institutions.
It’s not puke inducing, but it is verbose. The language designers just took a different approach to how to write code. Just for some background, it came out at a similar time to c++. Both were designed to be a ‘better c’