Recent submissions

Comment · 9 years ago

    Traceback (most recent call last):
      File "/root/routes/game.py", line 395, in get
        audio_filepath = audioSubmission['filepath']
    TypeError: 'NoneType' object is not subscriptable

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "/usr/local/lib/python3.6/site-packages/tornado/web.py", line 1467, in _execute
        result = method(*self.path_args, **self.path_kwargs)
      File "/root/routes/game.py", line 445, in get
        user=self.get_current_user().decode('utf-8'),
    AttributeError: 'NoneType' object has no attribute 'decode'
so many wrong things with this..
Comment · 10 years ago
And I thought I was pessimistic. I must be missing something, how did we go from a faulty code, to KPIs, to Comcast paving the future of the AI?
Comment · 10 years ago
Dates are available for some objects, see http://stackoverflow.com/a/39930978/1832154 for more details about what is/isn't available.

The issue is a different one, I believe you're considering one specific situation while there are others to ponder. What would happen if someone copy & pasted part of the hash, or had some tool that always reduced that output to the first few digits, or other situations like these, how would you be able to tell that the user was actually after the oldest commit? It seems much easier to indicate there's a problem, a conflict, and let the user solve it.

Comment · 10 years ago
How does it compare performance-wise?
Comment · 10 years ago
How do you apply your rules considering what's available today? Which services are you using? It sounds like it would be a big headache to orchestrate the automation among all these different providers.
Comment · 10 years ago
And who monitors your company monitors? :)
Comment · 10 years ago
My productivity increases so much when I shutdown chat apps I can only wish people responsible for setting them up at companies would stop for a minute and read this. Only the fact that the app is running is enough to reduce my output since I'll switch to it regularly no matter what.
Comment · 11 years ago
I'm aware of that but it seems specially interesting that they decided to go with a specific old version of some files. I don't think this kind of decision was ever made public, was it?

The general clean up idea is mentioned all over, but selecting old versions of specific files is not.

Comment · 11 years ago
Interestingly, looks like LibreSSL avoided the BN_mod_exp bug.

OpenSSL history for crypto/bn/asm/x86_64-mont5.pl can be seen at: https://github.com/openssl/openssl/commits/d73cc256c8e256c32...

LibreSSL is using an old version of that same file found at http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib/libssl/src/.... LibreSSL is using a version (possibly with patches on top of it) that is at least before https://github.com/openssl/openssl/commit/cf6d55961cfaa00eb1..., which introduced the bug reported.

BoringSSL patched it here: https://boringssl.googlesource.com/boringssl/+/e701f16bd69b6...

So, why LibreSSL went with a 2+ year old version of that file?

Comment · 11 years ago
Are the hardware specs available somewhere? Is it possible I'm confusing this with an interface for launching EC2 instances at a premium disguised as being actual dedicated hardware?
Comment · 11 years ago
I believe the reference is coming from http://docs.ethereum-alarm-clock.com/en/latest/overview.html...:

Guarantees - Will the call happen?

There are no guarantees that your function will be called. The design of this service is meant to provide the proper motivation for calls to be executed, but it is entirely possible that certain calls will be missed due to unforseen circumstances.

Comment · 11 years ago
About the stats: by "specially about their deployment count and usage over time" I meant the number of certs deployed by cert type (DV, OV, EV) and how has their usage progressed over time? If the second part is not clear, let's say that 5 years ago EV certs represented 2% among issued certs, and today it represents 1.4% -- I'm looking for historic data about this.

Thanks about the warranty clarification, so it only protects you if the /CA/ does something bad to you? In that case wouldn't it possible to sue the entity for, possibly, an even larger sum?

Comment · 11 years ago
I can't wait to see how this industry will change after LE is fully running -- this is amazing. Are there any stats about the different cert types, specially about their deployment count and usage over time?

One thing I don't understand about the guarantees given by CAs is the one about the warranty, like the "$1,750,000 Warranty" from Comodo. How exactly can they provide that? Or is that some sort of MUST have if you want to partner with an insurance company?

Comment · 11 years ago
I assume I'm jealous for a project that brings nothing new compared to so many other solutions and still grabs 76 stars (as I write this). It seems, after all, github stars are another way to say "I'm popular" and not so much that a project is good.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton