jvdh

It was resolved? In the 'Timeline: The Speed Run' section they list:

"Day 1, same day: RBI fixes everything faster than you can say "code red""

If you don't want to spend $1400 on a clock, but still want to read time in words, there's another option. You can build it yourself for about a 20th of the cost:

https://bitbucket.org/vdham/wordclock

That one's in Dutch, but it's pretty easy to get a stencil in English and adjust the code.

From what is currently known it seems plausible that Marcus Hutchins should at least be under investigation. Some of the things he has done in the past were murky. Stopping a large ransomware attack (by accident) does not change that fact.

I have not seen remarks in the security community that people were afraid of being arrested out of the blue like Marcus Hutchins.

Not to mention that he retired three years ago.

The point of the letter is that there is something as being polite.

Intel telling him about it at some point would have been polite.

This is earnest in that he would have liked someone from Intel to tell them.

It is completely earnest in the sense that he is not expecting any money from it. Likewise he has never expected anything from Linus Torvald when MINIX was used as the primary source of inspiration for the Linux kernel when he started out with it. Although they did have some pretty serious discussions about it, but nothing more than that.

It should be noted that Minix is code that was developed by university researchers. Researchers who are payed for by (primarily) European and Dutch tax euros.

Also note that many of that time, energy and money to modify GPL code is not just programming time, but also a lot of legal advice time. With BSD-like license it should be immediately clear what you can do with the code (i.e. almost everything).

I'm guessing they are also going after the "fitness club" like profit idea. That is, get a subscription, use it frantically in the beginning. Then slowly you go less and less, but still keep the subscription because you never know when you might want to be healthy again. Or cancelling it is too much of a hassle for just $10/month.

They had a perfectly fine businessmodel. 1Password has been running for years without the SaaS model:

> P. S. Please don’t think our excitement for memberships has anything to do with money. We’re completely self-funded so we don’t have any investors forcing us to make changes by looking solely at our bottom line. We were doing just fine selling individual licenses and AgileBits was already steadily growing before 1Password Teams was even introduced.

https://blog.agilebits.com/2017/07/13/why-we-love-1password-...

The headline is misleading. They are not planning to fingerprint all children. They are lowering the age at which refugee children are being fingerprinted (from 14 to 6). This is part of the EU process of making sure that refugees are handled properly.

Things have progressed quite a bit since 2008 fortunately. Vulnerability disclosures have become much more acceptable, and are handled in a much better way.

Lots more information about disclosure:

* https://www.ee.oulu.fi/research/ouspg/Disclosure_tracking

* https://www.ntia.doc.gov/blog/2016/improving-cybersecurity-t...

* https://www.thegfce.com/initiatives/r/responsible-disclosure...

this raises an interesting question: does one side have an advantage with an incorrectly oriented board? Googling it doesn't really seem to give an answer.

Most results that I found note that it probably does not affect the game that much. If you're planning to write down moves it may become confusing when someone with a correctly set up board tries to replay it.

`It's interesting to note that the PS4 OS is also a forked FreeBSD variant as well.`

Here's a nice talk at CCC last year which explains some bits of FreeBSD in the PS4. It's mostly about hardware and how to run Linux on it, but FreeBSD gets a nice mention there too.

https://www.youtube.com/watch?v=QMiubC6LdTA

The naming of "private key" versus "secring.pgp" is very valid criticism.

Also the fact that it crashes on first use, and that it is all not very user-friendly are all valid criticisms (still!).

PS. please don't down vote because you disagree.

Encrypted email for this user group is certainly not over, and there is still no realistic alternative for it. So PGP is not going to go away completely.

Keybase.io is the best solution that has been put forward to solve this problem.

They don't because GPG is ancient, and there was no proper way to do email validation back then. It is sort of better now, but still very hard to do.

If you have realistic worries that someone can intercept your email, then email validation of your GPG keys is not going to help.

The author probably exaggerates, but identifies a very valid point. You really don't want to have this kind of confusion about something that you are planning to trust your secrets to.

There is still very much a set of users in the incident response community that relies on PGP. These are professional teams that need to communicate with each other. They talk about upcoming disclosures, current abuse, upcoming operations or patches, et cetera.

This stuff is almost all short to mid-term secret. Most of this will become public in a month or so. Leaking meta-data is an assumed risk (or too much hassle to avoid, take your pick).

If you mean "logging" as in web server logs, then it completely depends on the configuration of the server and there is nothing the client can do about it..

If you mean "transferring over the network", then yes, HTTPS only shows the server you are connecting to, but not the specific URL.

Then again, that can be deduced from the transfer sizes that are still shown.

Although with most TLS implementations they will see the size of your transfers, thus still giving away which URL you visited....

.onion addresses are like a public key. The server needs to have a private key.

Vanity addresses, ones that have a name at the beginning, require some processing in order to find the right public key.

Fortunately it is really easy to print it in other formats. Which is certainly not the case for the standard datetime library.

Finally an actually useful application for AI! No perfect result is required and this is also not something you want actual humans to do.

In this case the reason is that not only the sync service costs money, but also the custom font they use costs money. So just letting it sit there would still cost money (on top of the fee for the app store itself).

Windows handles a lot of abstractions, to hide users from the nitty gritty details (OS X does the same thing). One of those things is hiding as much of the file system as possible.

Unix usually has users engaged at a lower level, adding a startup daemon means moving a file to a certain place. That shows that filesystems are much more the direct interface for the operating system.

Also, it is possible to have a Unix operating system, but have a completely different filesystem underneath. This is just not possible for Windows users. So there is no choice, so it is nothing Windows users think about in general.

He completely forgot his laptop, moved away from the security check and only later figured out he was missing his laptop.

With hundreds of people moving through those checkpoints, I do not blame the TSA agents for handing stuff out to completely random people.

Alternative title: Guy forgets laptop at security checkout and blames TSA for his stupidity.

> I emerged from the scanner without any problems, collected my 2 bags and incidentals, and proceeded into Terminal 5. After awhile, I looked into my backpack and realized that I didn’t have my computer. My heart skipped a beat! I turned around and rushed to the security area.

The life and the work back then is very different from the life and work that we have now. A big factor is that there is no war to motivate people to work hard. Another is that labour circumstances are very very different now than what they were previously.

Finally almost nobody who reads HN does repetitive manual labour. Manual productivity is very different from mental productivity.

From my own experience, I'm not even productive for 40 hours per week. Let alone working 50 hours consistently every week.

The best information is at the very end of the report where all the tables and graphs are. They show that munition workers are at peak production at around 50 hours or so. There are many many caveats for drawing conclusions from these results:

  * The collected data is from 1915-1920
  * The collected population is very very small 
    (most sets are less than 50 individuals, one is ~100)
  * The work performed by the population is extremely repetitive manual labor

With these caveats, it is safe to say that most of the audience of HN has nothing to gain from the results of this study.