skysight-inc/HackerNews huggingface dataset:
This conflation is made too often. I think the problem with the assumption that if someone made something public willingly they don't care is if people knew they are under surveillance they may not speak their mind, or speak at all.

If people who use the internet expect all their activities to be logged and mined for patterns that can potentially be used against them, they may behave very differently.

Since we all act in self interest this means no one will speak freely. This is what surveillance does, this is what the chilling effect is.

This reduces the value of the internet for the free exchange of ideas and discussion. People who seek this will have to resort to encryption and other tools and forced to behave in a secretive fashion as if they were doing something wrong.

Protests and activism are supposed to be normal part of every democracy and its disconcerting the see the strange discomfort our 'democratic societies' show to activism and the sheer amount of effort devoted to managing it from infiltration to surveillance.
That sounds right to me. I really wanted to avoid a definition of art debate. My original post is subjective, but honest.

In case you're interested this is where I was coming from:
http://artnews.org/artist.php?i=613

The site works, I didn't see any issues, and I think it does a good job staying out of the way of the product.
Upvoted for thoughtful phrasing, even though a wild-ish animal deciding to go domestic for retirement does seem interesting.
Does it really need a separate TL;DR when the article's subtitle says the same thing? That's not a TL, it's just a DR.
I feel like now is a the first time in a long time where the emerging technologies of today are looking to have a dramatic impact in the near future, and this probably gives birth to a lot of people thinking about tomorrow. I think this is a good thing.

Peter Thiel talks about this in his book, which was published in 2014, saying the 60's was the last time people were optimistic about tomorrow, illustrated by the professions people were getting into.

That was two years ago and I feel like two years later we're just starting to see the proverbial jet packs at the end of the tunnel. To start I'm sure that's bound to have more people entering machine learning rather than web development
Stolen IoT data is the perfect way to case a house. That's a market waiting to happen.
It always makes me think Brave New World in the way it subordinates a sense of humanity to a specific design, and also in the way that design isn't as clever or durable as those who promulgate it imagine it will be.
I find it interesting how they conflate "finding comfort" with "finding truth." In my experience, in the existential sense, the latter is the antithesis of the former.
Biggest wart we have is that it randomly picks a machine to run migrations on, if it's a deploy with migrations.
Ok fine, but then how far off of the mean should they then be? They aren't all super smart nor are mentally deficient as they have to be able to function in society to make money enough to pay for the service. At most this is what, an IQ mean of 75-125. So that then means at the low end, TT chat-bots can fool human males of IQs of 75. That's pretty darn good and that was 4+ years ago.
ummh... have you ever been on any of those subways?

Paris is a marvel for its density and well-planned routes. But some of the lines are more like underground light rail compared to e.g. the Lexington line, which on its own carries like 1/3 of the passengers of Paris or London.

The London Tube trains I've been on felt like a subway for midgets compared to the 10-foot wide BMT trains. They stop running at night. One of the only times I've missed a flight was due to a London Tube delay.

The new Chinese subways really put the US to shame, quiet, double glass doors, video screens everywhere, cell phones work everywhere, very cheap, very dense and very crowded.

The NY subway is pretty reliable and fast. Apps like Moovit and Citymapper make it pretty easy to get where you want as quickly as possible. Train Time coverage and wifi coverage could be better, the latter is improving. It could be nicer but all I can say is if you think the New York subway is bad now, you should have tried it in the 70s.

Edit: I'd add that an Oyster-type payment system would be nice. Also, a couple of MTA alumni have led systems in London, Hong Kong, Toronto, other cities, so NY is probably not at the very bottom in best practices. Bottom line is you can get anywhere quickly and reliably at all hours, if not always in luxurious style, and you don't need a car to live here. So I'll take it, until your driverless taxi can deal with NY traffic and get there faster.
Compared to what followed, I think I'd pick brutalism. Downtown buildings in cities that mostly grew up in the 80s and 90s are just boring. When I google brutalist building images, I'm struck by how wildly they vary. I don't love them all. But, they've got real personality and originality. Sure, sometimes it is overblown...big shapes in weird places just for the sake of showing off.

I find architecture that slaps old forms onto new buildings to be...gross. There's a couple of skyscrapers just outside of Houston, for example, with fucking red shingles on it, like it's an adobe house in the desert or or something. So much architecture glues on a bunch of columns, ornamental lintels, fancy molding, etc. When placed on a structure that is huge, particularly one that is much taller than it is wide, they look ridiculous.

I think there are good buildings that were built in almost every era; but, some eras are less ambitious than others. Brutalism was, at least, ambitious. I think there's a reason so much scifi and futurist imaginings feature brutalist architecture. It is an architecture that screams "there are no limits to what we can build!" I think that's pretty cool.

It's all subjective, of course, and we all have our preferences. But, calling it "objectively wrong" seems hard to defend. It is only objectively wrong if it fails to function as a building for people to live or work in. If it leaks, if it falls down, if it is difficult to heat and cool, if it inaccessible to the people who need to use the building. Those are ways to measure architectural wrongness objectively. It's safe to say that some brutalist buildings failed to live up to their purpose, but that's true of many architectural projects. Having the style fall out of fashion, due to a reactionary response to the new and very different, and the buildings fall into disrepair because of it, is not really the fault of the architecture. Old buildings get renovated every 20-30 years, or they stop being relevant. This is true of even iconic buildings like the Empire State building.

Anyway, I quite like brutalist architecture; I don't mean I like it with no discrimination. I still just buildings on their own merit and being in the right style doesn't mean I'll like it, any more than me saying I really love punk rock means I would ever listen to Green Day or Bad Religion. But, there are brutalist buildings that I find beautiful. And, a lot of stuff that followed that I find horrible.
Ahem! The problem is not the NULL array start address. It's the array length being zero, and thus equal to the number of file descriptors that poll() fails to add to the kqueue, also zero. Read everything referenced by the headlined article, and you'll find this.
ISIS suspect charged with researching encryption, encrypting website
So you have nothing to say about this weird claim you made about launch costs (or my other points you dismissed), which seems to be contradicted by Wikipedia:

>> No, mostly because the 600 $ per lbs. figure touted quite often as the target was never actual the target, it was the based on differential payload costs when launching a crew only mission vs a crew + payload.

[Edit: 600$/lbs is in "modern" dollars. In early 70s dollars it was ~ 110$. The real costs were somewhere between one or two orders of magnitude larger, depending on what year you select the dollar. The differential costs can only be a fraction of that.]

>> the Air Force wanted it

As far as I've read, NASA sold the Shuttle to the air force with unrealistic promises. That is why they wanted it. It isn't so?

>> No this isn't what he said

That full paper contained e.g.: the expense of owning and operating [the shuttle], or any similar system, is simply too great. Any new system, to be successful, must offer a much, much lower fixed cost of ownership.

And this was from someone that was as tied to not making NASA look bad as anyone can be!

[Edit: I really can't see that Wikipedia misrepresent Griffin's position, as you claim? Please be more specific about that claim. You really need to show quotes to dismiss wikipedia today.]

>> NASA got stuck with [the shuttle] and yes in the later years it fought to keep it alive not because NASA was stupid but because it had no other option since there were no alternatives on the table.

The Shuttle ate a large part of the NASA budget (30% at least some years), which contained lots of aviation and other programs. The shuttle was a gigantic job program -- that gave NASA, with a big weight to throw around, an incentive to kill off all competing launch systems! There was probably a reason not much happened in launch systems until the Shuttle died...

[edit: The point was, there were no other launch systems not just because the Shuttle took such a gigantic amount of the total budget but also because NASA had motivation to keep the job program going.]

[edit 2 on this: If you put your foot in a trap and can't afford the tools to get the foot out of the trap, because the trap was so expensive -- you're not "stupid"? :-) ]

And, to go back to the original subject, the Orion seems to be another cuckoo, eating up most of the food in the nest. :-(
Some good points brought up here-- we need evangelism like this to get enough public support to explore the galaxy.
So, whatever planet-killing doomsday weapon will wipe out every shred of humanity from Earth, but its operators will just happen to forget to point it at a completely independent, self-sufficient Mars?

I feel that building a 100% successful planet-killing doomsday weapon is far harder then establishing an independent, self-sufficient Mars colony... That will not be affected by it.
Concrete has a very hard time lasting more than a few decades anywhere that gets rain, and especially anywhere that gets snow.
Wait. Did you just use the word "nice" in a way that was associated with Boston City Hall, even indirectly? AFAIK (and my own experience) Boston City Hall is pretty much universally reviled as Soviet architecture set in a wind-swept brickyard--the latter aspect of which is apparently being addressed to some degree.

Speaking of Boston, I must admit that the redone, cleaned-up Brutalist modern wing of the Boston Public Library while, of course nowhere equalling the original Beaux Arts structure, actually feels open, welcoming, and airy. It was truly awful previously.
That's... really unfortunate. Have you looked into customization to potentially make them usable for you? It's fine if you don't want to, but I'd hate to see somebody unable to use such useful tools due to a lack of finger dexterity.
After an unpleasant experience with rats in a big city, I found the Youtube videos of "ratter" Plummer Terriers going to work morbidly satisfying. Although I've wondered if it's the bite or the shake that finishes the job.
No, but even if California's BPC (Bigot Per Capita) was half of Georgia's, we would still have twice as many Bigots as Georgia.
Also, this fits in with advice #3, use common options. Users aren't "blindly" adding -v for verbosity; they're expecting it as a common option. Admittedly, the verbose/version/something else distinction is not as standard as I'd like, but if I were writing this I would have explicitly said in point 3, "-v is verbose. -V is version. -h is help. -?, if implemented at all, is a synonym for --help. -n is dry run, if that makes sense for your command. (By the way, unknown flags should cause the command to fail rather than silently do the wrong thing.) The first instance of -- causes all further arguments to be blindly accepted as positional arguments rather than flags, including further uses of --. If at all possible, all command forwarding (e.g., ssh, shell, autocall) is done using multiple positional params, not nested quoting nightmares."
* Everything on one page

* Doesn't take 30+ seconds to load

* Sortable and filterable
Amazing how it expresses sheer human grandeur at the same time it reduces the human to insignificance, isn't it? I always feel like I'm in some kind of weird cross between a cathedral and the diggings of some giant alien worm.
If you want to implement the signal protocol for your own company (see WhatsApp, Messenger, Allo, ...) you will probably have to buy a license ($$$), and ask for their help ($$).

* https://whispersystems.org/blog/whatsapp-complete/

* https://whispersystems.org/blog/allo/

* https://whispersystems.org/blog/facebook-messenger/
This was exactly my reaction. The tips around Amazon Redshift were spot-on including a few obscure-but-critical ones e.g. the one about many small tables taking up a ton of disk space!
I don't believe that's an accurate analogy.

Even if the laws change, even if self-driving cars became the norm tomorrow, you should assume you're cycling through a real-life GTA. You probably weigh about 200lbs including the bike and are travelling at ~20mph. The car weighs 10x as much as you and the slowest it's going is 25mph.

It is very frustrating to have to assume everyone is out to kill you, but that goes with the territory when you're riding on the same streets as 1 ton rolling missiles. It would not be smart to relax one bit since even if the law changed, cars blow their tires, brakes give out, old people still drive, etc.
Basically, because people thought it was safe. It didn't seem significant to use the same prime since the key exchange process involves both Alice and Bob generating a secret. Solving the discrete logarithm of g^a mod p was still thought to be intractable given a large enough (1024bits) p.

As to the technical reason why the DH parameters were reused - speed and efficiency. A DH key exchange would take longer if you had to generate those parameters each time.
Undisguised concrete. All modern architecture on a large scale is defined by concrete (though apparently that's changing), but the difference is in how much it is on display.
Five surprises in the latest Windows 10
Node's module system doesn't import dependencies into a global namespace. So the `x` required by `a` and the `x` required by `b` will have separate namespaces and won't conflict, or even know of each others' existence. There are pros and cons to this approach, but it definitely does work. Flow, at least, (and presumably Typescript) understands the module resolution logic and handles this very common situation without issue.
That's totally fair, but I hope that each of those organizations has a vested interest of exposing each other; at the very least it's in the NSA's charter to protect American businesses against attacks, I have no idea if they feel this is an effective way though. So yes, it's risky.
But Microsoft has all those disadvantages too, even though it's harder to get moles inside it's easier to have their stuff undetected (and in the case of the NSA it might even be done with full cooperation). Plus, the market share makes them a bigger target.

Outside probably hypotheticals, what we know for certain is that microsoft is attempting to monetize their new windows on the back of user's data.
If you think the internet is the world wide web as well, then sure, it's changed a lot.

But the actual internet infrastructure is still the same, this paper discusses the protocols and architectural problems. I challenge you to name something that has changed. Even IPv6 was formalized 15 years ago.
you can manually delete and import root CAs in the windows 10 CA trust store:

https://technet.microsoft.com/en-us/library/cc754841(v=ws.11...
What about electronic shifting?
I love using Signal and will continue to make modest donations, but I would really appreciate an improvement in audio call quality. I still use Silent Circle for calls because it is so tiring to talk when the bitrate is low.
Nice to have it directly in DropBox since folks probably already have their PDF there anyway. No need to separately upload to DocuSign, HelloSign, etc.
I don't think it meets the low latency requirement. It's a CAP theorem joke. Can't have strong consistency across multiple data centers with low latency because you have to read/write from a quorum of DCs in order to maintain availability in case one DC goes down.
Cool feature, though it'd be nice if Signal fixed the message delay and message dropping problem. But Signal uses the proprietary GCM service (because "it's impossible to do message sending correctly, so let's force people to use proprietary software") so they probably can't fix it...
You'd find the same things with careful reading and consideration for a shallow article too.
Redis Pub/Sub: Intro Guide
I love Signal and this seems to be a stab at Wickr since from what I've heard that is the reason people prefer it to Signal sometimes. Having said that, it has a couple of problems:

1. Images are downsampled without warning. There should be some sort of warning or mini info box for the times when the images are downsampled and there should be information about the changes in resolution.

2. If one uses it as the main messaging app, one has to search through history sometimes. But there is no chat search feature. I am forced to scroll all the way up and copy the message data to an editor. Even really basic case insensitive search would be great.
Time Doesn’t Kill All Deals.  but It Puts Them at Risk
What good is a seatbelt if the person sitting next to you can stab you? The blog post makes a point of this not being secure if the person you're messaging is malicious and that's not what it's for.

I think these two comments make good points:

I just had an interesting conversation with a friend who was recommending that I use Telegram/Wickr, and I told him that Signal was where it's at. Then he asked me if it had self-destructing messages, and I said "Why bother? That can be easily circumvented". His reply was that in some countries phones had been confiscated, and even though one person had enabled local encryption, the user with the confiscated phone had not enabled it; thereby implicating everyone who had communicated with that person (even though the messages were delivered secure over the network). So while self-destructing messages are in many ways a flawed guarantee of privacy, they can perform a very useful function in cases where the users are not malicious, but rather are security ignorant (i.e. most people with a phone).

https://whispersystems.discoursehosting.net/t/automatically-...

I've always been thinking that the critique of such a feature is based on a false underlying premise.

Yes, it's true that the recipient can make a screenshot of the message. But the recipient in the absolute majority of cases is not a "threat" in a classical sense, not someone with bad intentions or someone who is not supposed to know the contents of that message. After all, the sender trusts the recipient, as he is the one sending the message to the recipient in the first place.

The usual scenario is a recipient who is not that security-aware and doesn't think about those things that much if at all. Personally, I'd say most of my contact are that way.

The sender might send this recipient a message containing something especially critical, say, a user name and a corresponding password, and doesn't want to see that information in the wrong hands if e. g. later on, the recipient loses their phone, the phone gets stolen, etc. Also note that this kind of recipient is unlikely to use a general passphrase for Signal as this lessens convenience.

So what's essentially happening here is a security-minded sender taking security measures for or in place of a thrustworthy, albeit forgetful, non-security-minded, etc recipient.

https://whispersystems.discoursehosting.net/t/automatically-...
Anything is possible if you pay the price (motivational)
I apologize for making an unwarranted assumption about you. There has been so much talk about "Twitter censorship" where it really seems to mean "Milo Yiannopoulos and Breitbart should be able to continue trolling even when their methods violate Twitter's ToS".
I think we're using very different terminology here. An event in our world may contain thousands of metrics as part of the same event.
Can't view page without logging in.
I'm wondering if your opinions on the difficulty of introducing new protocols have changed over the past decade. For example, Bittorrent has taken off, and while I used to have to manually configure ports on my NAT to allow Bittorrent to pass through, I no longer need to do so. Universal PnP seems to have taken care of that (at the cost of some security).
If you can automate testing, especially on mobile, I highly recommend it. Building a testable app makes testing easier, whether you actually automate the testing or not.

Mobile testing kind of sucks, automated or not. Manual testing requires an ever increasing number of devices, and the actual testing is slow, monotonous work (aka good testers get bored and move on).

Maybe this approach... Automate what you can, making sure it behaves right. Use manual testing to verify it looks right, and as validation the automated tests didn't miss something.
Yeah, there was another one [1] built with the same name later. It's a 2/3 scale model of a battleship which is still on display in Point Loma (in San Diego). I used to work around there and it seemed like they were refurbishing it recently.

1: https://en.wikipedia.org/wiki/USS_Recruit_(TDE-1)
Energy  a Desert Full of Tomatoes, Thanks to Solar Power and Seawater
Also, -- (two dashes) in the command line means "end of the options", which allows, e.g. rm to delete a file starting with dash.
And this is happening as soon as Microsoft makes it so that you can't pick and choose updates anymore. Yeah, it doesn't look suspicious at all.

https://krebsonsecurity.com/2016/10/microsoft-no-more-pick-a...
developers use node to compile whatever version of javascript they are using with a version that will run in most browsers without issues. It's also useful when concatenating and minifying assets. It's called an asset pipeline where you build a release, just like when you compile and package your Java,.NET or Go code before deploying it. Now of course javascript is a dynamic language and should not need all that stuff ... in theory ... but for some reasons developers love complexity. You can design the most simple system the most simple language, developers will find way to add layers of layers of complexity one way or another ... before going back to square one. It's interesting you are talking about Go. right now Go is quite simple, You bet your ass it will look like Java in 10 years just like Javascript is becoming more and more complex with tons of tools, transpilers and what not.
This analogy won't make sense to (most) younger people but I think that in order to make new insights you need to take the pressure off. Metaphorically speaking, to "change gears" you need to push the clutch in.

For me, I "load the machine up" like a dishwasher during the day and when I wake up, a lot of times, the machine has come up with the answer overnight. It delivers the answer during my morning shower.
The peaceful times also generally don't make the history books.
Could not agree more. Reading "A Case for Mars" by Dr. Robert Zubrin, esteemed aerospace engineer and founder of the Mars Society, explains - in every possible detail - the why and the how of settling Mars. Anyone interested in this topic should check it out. I would not be surprised if that's what got Elon Musk excited (and convinced that it's quite possible) in early 2002.