pepve

There is actually a straightforward way to export data from your Spotify account, try this:

https://developer.spotify.com/web-api/console/get-current-us...

Well, I'm in the EU, I celebrate π day. I'm not going to let the questionable origins of a perfectly good day ruin it for me. I even installed a new keyboard on my phone to be able to type π.

I celebrate christmas too.

The logic here is that it doesn't reduce security by much, but it significantly reduces password resets. Facebook does it too (and more) which we talked about two months ago: https://news.ycombinator.com/item?id=13426544 . Some good points were brought up.

You're not missing anything. But a bunch of us didn't figure it out before and we're just now learning about it. So we're excited, we're learning something new!

(Please, please, don't be condescending to people who are learning something new.)

Yes, that's called a length extension attack: https://en.wikipedia.org/wiki/Length_extension_attack

It's why you don't use a bare hash as authentication, but instead use a HMAC.

That list contains domains where the bug was triggered. The information exposed through the bug though can be from any domain that uses Cloudflare.

So: all services that have one or more domains served through Cloudflare may be affected.

The consensus seem to be that no one discovered this before now, and no bad guys have been scraping this leak for valuable data (passwords, OAuth tokens, PII, other secrets). But the data still was saved all over the world in web caches. So the bad guys are now probably after those. Though I don't know how much 'useful' data they would be able to extract, and what the risks for an average internet user are.

That's a great defensive technique. But even when you do that, the underlying bug should still be fixed. I don't think the equality operator is the underlying bug.

Consecutive pointer increments without a bounds check in between sounds like a bug to me. But I don't really know Ragel, and perhaps the compiler doesn't have enough information to determine this is what's happening.

Maybe he's a GNU zealot, they exist. The type to refer to Linux as GNU/Linux. ;-)

The article confuses two things. First there is voting by paper ballot and manually counting them. We have been doing that for about nine years now. Second is aggregating the votes from all the polling stations, this used to be done with software, but with this decision it will be done manually. The immediate reason for this is an investigation into the security of that software which concluded that it was not safe, and the resulting media attention.

It is yet unclear what "manual aggregation" exactly means. Electronic calculators and Excel were suggested.

Thanks, I was scanning the article for a mention of this but couldn't find it. I see now they also have retouched versions available when you click the "Full image and caption" link. I wonder why they didn't lead with those, I'm kind of used to images from/of space being (heavily) processed.

I think for SQL their sample includes just ".sql" files, which tend to contain schema definitions and data dumps, hence CREATE and INSERT. Most of it not handwritten also.

From the article, not exactly the statistic you're looking for but close:

> in 2012 suicide was overall the most common cause of death in Colorado among those age 10 to 44

X-ray does not actually kill film. It will just slightly increase the esposure. But on the films I took through X-Ray scanners I never noticed this. Also you can take the film with you in your carry-on and ask the person at the scanner to let your film pass unscanned. Worked for me back when I was concerned about this. :-)

Oh and film also doesn't die after its expiry date, I made enlargements of some shots from ten-year-past-expiry film recently, not technically perfect but I love the look. Try a roll and see what you get!

That LinkedIn thing scares me too. But it might be rather simple. Person XYZ has your email and phone number in his address book, and then shares all of his contacts with LinkedIn (which they pester everyone about).

Alternative for the cartesian product (instead of the nested loops):

    join <(sed 's/^/1 /' set1) <(sed 's/^/1 /' set2) | cut -d ' ' -f 2-

Edit, someone in the comments there has a far better trick:

    join -j 2 set1 set2

What you're saying may feel and sound rational. But it is victim blaming.

Or this one: https://xkcd.com/1489/

> it's all about status and perceived value

Yet the author of this post taped off the lettering to make it look like a generic camera.

You can edit cookies with the "Developer Toolbar". It's under "Tools -> Web Developer" and reachable with the shortcut "Shift+F2". It's not brilliant but it works well.

There's also sshfs: https://en.wikipedia.org/wiki/SSHFS

How would you do error handling for the binary data? Let's say you expect something to match but it doesn't, what are your options then?

See also πfs: https://news.ycombinator.com/item?id=6698852

I like Redis as an example in this category.

I also think this ties in with the law of leaky abstractions, in that a good understanding of that law will make ui designers choose lesser/thinner abstractions over bigger/leaky ones.

"White" light sources are generally not really white. For example compared to sunlight ordinary light bulbs are a bit orange and fluorescent tubes have a green hue. Our brain mostly ignores these differences, but a camera sensor does not. The author might have turned up the saturation on these images though, I don't know how strong the difference is supposed to look.

I think his issue might be with "enjoy the good life while it lasts". That attitude might work well if you're alone. But if you have kids, you generally want them to have a good life too.

It seems you still don't want the advertised tool though, because you prefer to just send SIGKILL immediately.

Environments differ though, the software I run will do worse on power failures/SIGKILL than on SIGTERM. I would prefer it to be more resillient, embrace a crash-only design, etc. But my world suffers from practicalities, so I deal with it by being careful with SIGKILL.

I personally prefer utilities like this just do one simple task and perform it well. And adding a timeout would just complicate things unnecessarily, compared to the alternative of pressing Ctrl-C when you feel you've waited long enough.

Methane outside of earth is more common than I thought it would be (after reading the article): http://en.wikipedia.org/wiki/Methane#Extraterrestrial_methan...

I really want to like this. But SIGKILL is such a special instrument in the administrator's toolbox that I don't want it automatically sent after a short timeout. Moreover I don't think anyone should want that. This tool will hide or allow you to ignore important issues with your system.

I do unequivocally like the blocking behaviour though, I might implement that for myself.

Edit: so just something like this:

  function killwait() {
    kill $1
    while ps -p $1 &>/dev/null; do
      sleep 1
    done
  }

On modereately fast networks, instead of -z which uses a single threaded gzip implementation, parallel gzip may still give big improvements: http://zlib.net/pigz/