skysight-inc/HackerNews huggingface dataset:
Not an explicitly enumerated right in the USA, but a "right" in the same way freedom to walk down the sidewalk is a "right": you're not endangering peoples' lives & it's not explicitly prohibited so you "have a right" to do it. If someone attempted to prevent you from walking down the sidewalk they would be denying you that "right."

Driving a motor vehicle does endanger peoples' lives, so we (society) decided you don't have the "right" to do it, but you can be granted the privilege to do so pretty easily provided you have the $$ for administrative fees & can pass a test demonstrating basic competency.

Your question is totally reasonable, but I think it's fair to say one has a "right" to bike on public roads (barring interstates) but not a "right" to drive on public roads as this requires a license & is subject to many strict regulations.
What Is The Company Culture Of Path Like?
I realize this will not typically be the entry point for a user, but it took me a bit of clicking to actually figure out what pedestal-app even is (a Closure web app framework, by the way).
So are you just syncing entire truecrypt .tc files to Dropbox? Does that work incrementally or does the entire .tc file have to get resent every time you modify a file within?
Doesn't resize very well.

Oh wow, the actual app itself is pretty neat. The landing page looks pretty bad, I would have instantly closed it if it was posted anywhere but HN. Once I started playing with it, it's pretty nice. I would probably just make that the base page, and advertise your book marklet in a dialog box or something.

The logo looks a little pixelated and reminds me of 90's free clip art pages.
"Any city that has resources for this ought to take a hard look at the size of their police force."

Aren't tickets usually a source of revenue?
All three of the cities you've lived in are notorious for sprawl. It would be reasonable to strive for improvement in those cities, but don't make the mistake of thinking that the problems those cities have is representative of the rest of the country.

It's like living in rural Idaho then complaining that America needs to learn how to pave roads because packed dirt just isn't cutting it.
This doesn't seem to be responsive. Your kids (or mine), no matter how heart-tugging a debate example they may be, will still be hurt less from a collision with a bicycle than the cyclist will be from a collision with my car. To argue otherwise, as Yver did above, is silly and counterproductive.
Nothing in that paper talks about people being killed as far as I could see. Higher event rates != higher deaths. Running into another bike was considered an event, but that's not generally deadly.
If you really want low cost and no frills, just run redis locally.

I still don't understand the point of third party redis - I'm not aware of a service that is more lightweight and CPU friendly than redis.
> ...have issues live streaming to youtube and twitch. Each requires special (different) encoding parameters for streaming, and youtube needs each resolution streamed separately. This, along with separate streams for twitch and youtube...

This isn't a sales pitch so much as an offer to chat about it and see if we could help turn a service we provide into a product that meets this need.

For years we've provided this as a "private label" service to major media companies that need to provide one single broadcast quality live stream and have it delivered to thousands or hundreds of thousands of end users on Windows and OSX (RTMP), Android (RTSP), and iOS (HLS), in bitrates ranging from 300 kbps to 6 megabits, while also pushing the full array of bitrates to YouTube, Hulu, etc.

The problem is that this is not cheap. Pulling it off with low latency and across a full array of formats and protocols tends to require dedicated hardware (depends on the source material, talking heads easier than sports, for example). But our approach does cost significantly less than trying to use AWS instances, and if the community of broadcasters or viewers was large enough, it might make sense for us to open up this private label service to individuals.

Feel free to ping me if someone wants to talk about it.
It doesn't look like this tragedy had anything to do with respect for bicyclists; the driver, who could likely at minimum be charged with manslaughter, drove off the road to avoid traffic and fled the scene of the accident.

I don't disagree with what I think is the spirit of your comment, which is that there's probably a policy response to this tragedy. To me, it highlights the all-to-lax nature of our moving violation enforcement laws; every American who gets behind the wheel (myself very much included) subjects their neighbors to tremendous risks, and the penalties and risk of detection don't create meaningful incentives.
Your reply contains nothing of substance, and very little that is even of relevance.
Looks like they got too much traffic...
This is definitely true. Bicyclists on public roads have (most of) the same responsibilities as drivers, which means penalties for breaking the rules.
I played around with firebase and AngularJS over the weekend. Had a lot of fun, firebase was really easy to use (once I understand how the data was structured).

I open sourced the code as well: https://github.com/hswolff/bringthesalsa . Direct link to the app here: http://bringthesalsa.hswolff.com/#/ . Blog post here: http://harrywolff.com/weekend-project-bring-the-salsa/
Be awesome if the online code editor included Emmet http://docs.emmet.io/ like jsFiddle. :}
what is smaller: a string of bits, or a compressed string of digits?

What are you talking about? You could have had something on your mind, but this is a terrible terrible juxtaposition of words...
Your point being? Driving or biking on the road makes you a vehicle, all vehicles follow the same set of laws. I don't care if your "I'm a bicyclist" superiority complex makes you think you're above the law; you're not.
I'm not quite sure why I was hellbanned. I guess that's the point of it though.

I want to apologize to everyone who was affected by this. MyRedis was my first SaaS, and it was a learning experience in many ways (and continues to be, apparently).

I have adjusted the shutdown dates to give everyone more time.

On a personal note, here's a brief backstory to explain how I got here:

I started MyRedis as a technical co-founder almost a year ago. Since then, two other people have filled the other co-founder role. One decided to move to NZ one day without notifying me, and start working for some "dream job" company. The other, as has already been pointed out in this thread, was arrested recently.

MyRedis was starting to grow at a rate that I no longer felt comfortable saying I could manage. I was starting to fall behind in basic admin stuff, and it wasn't fair to my customers. This was the entire reason I finally decided to find someone who could take care of the MyRedis customers, and hence, where we are today.

I've spent nearly $50,000.00 of my own savings to build MyRedis, and support my family while doing so. I've learned a ton, and I'm going to pick myself up and do it again, someday.

I hope this transparency sheds some light on MyRedis. It wasn't some big company, it was me. I woke up every day and personally answered tickets, wrote code, and lived and breathed MyRedis. In the end, though. It's the customers who matter.
Tell HN: Why Internet Companies act like they have no Customers?
I recently posted a LinkedIn Ad and wanted to discuss it with their customer rep for some advice.

Here is what I got:
LinkedIn's self-service ads don't require a salesperson. You can create targeted ads, set a budget, bid, and pay with a credit card directly from your computer.

For budgets of $25,000 and above, contact us about display advertising.

Same story with Skype, try contacting Skype. I once spent an hour finding their phone number and I gave up.

Technological Advances killing jobs at an amazing rate but it seems that unwillingness to make their services more customer friendly is also one of the causes.
No. But Apple has a shockingly small number of employees relative to other big software names, and they have had historically had much fewer third-party developers than other platforms.

As a result, they have chosen to consolidate the mindshare onto one memory management technology rather than dilute the talent pool with two competing proposals. Given that iOS is much, much more popular than OS X, they have chosen to standardize on the technology that works best for the popular platform.
This smells like a desperate attempt by the TSA to justify their own existence.

Note that none of these confiscated weapons by themselves necessarily constitute an intent to use them. Knives especially are commonly carried and can easily be forgotten about.
There Is A Better Way To Legally Raise Seed, Development & Expansion Capital…
But redis doesn't really require any of that - it'll run and provide decent performance on a small instance, or even better, running on the same instance your app is running.

"yum -y install redis" then "service redis start" and it just works. I'm not sure there is an easier service to use than local redis.
I agree - I think a little more than the instrument landing system was offline during that period of time. Surely ATC had them on radar and could have easily seen them coming in way too slow to properly land.
I'm finding it a little annoying how people seem to like to defend every aspect of the flight - the pilots were fine, the plane was fine, the runway is fine (two of those I believe, BTW), as if that makes it better. The plane crashed and two people died, something was
_definitely_ wrong.
Anyone interested in making a HN team? (possibly a few given that it's limited members/team)
If the acquisition is for the customers the correct way to do this would be to handle the transfer for the users. Move the data for them and even keep the existing connection hostnames etc working. So, no change would have been needed for the users.

If the parent company has the same service why ask the users to do switch manually? I think with the excitement of the acquisition they have simple not thought through things.
Well, I haven't earned my downvote wings yet, but I'd wager you did yourself in with "typical apologist bullshit". They're not silencing your opinion, they're disapproving of your tone.
Here's another: http://www.youtube.com/watch?v=zY7UK-6aaNA

But keep quiet about it.

A video that simply showed a timer counting down four minutes and 33 seconds would be even better.

Live performance on every viewing.
> (1) opening an issue in the wrong forum and (2) failing to familiarize yourself with the previous discussion threads

OK. Fair enough, but I did look for an existing issue on the matter. There were none.

> You know this is a controversial topic, please act more maturely in the future.

Personally, I find attempting to lock down open internet-protocols by transforming them into some sort of binary obscurity rude and against everything the internet was built on.

I don't think everyone is aware about that happening right now. and I see nothing wrong with attempting to bring focus to the issue if that is what needed. Seeing how this draft still outlines a binary-protocol, this clearly still is in need of attention.

Just because some Google-heads somewhere decided that by completely ignoring everything the internet has taught us so far, and in the name of pre-mature optimization can shave off 2ms on their page-load doesn't mean the internet should pander to their interests.

If anything is controversial it is how this is all being done without any documentation showing us what benefits we get from the costs associated with a binary protocol. That is amazing. Completely and utterly amazing.

But OK. Let's say I listen to your guidance: Where would be a good place to raise this issue? Where would I take my "childish" issues to ensure they get the attention they so much deserve?
Girl Learns to Dance in a Year (TIME LAPSE) [1min51s]
I thought I had read in one of those that PG really wants to replace banks and credit cards. Or maybe it was someone else. Either way, that's one of the things I'd love to get into as far as "big picture" stuff (along with a cloud-based "space station" on venus, but the bank thing might be slightly less difficult). I'd completely revamp the entire purchase process, as much as legally possible (and realistically doing that would also require lobbying to change any outdated laws we can that aren't being protected by the other banks. You'd have to go after all the peripheral laws first I feel like, or else the banks would crush you with their influence). The entire transfer of funds and the documentation of the purchase would be re-done based on what we can actually do with this kind of data. It's insane that my bank only tells me things like "AMAZON MKTPLACE PMTS AMZN.COM/BILL WA 06/26" for an amazon purchase. Mint tries to parse that and just has no idea how to classify it. The truth is, the bank should only get sufficient information for facilitating the transfer, and there needs to be a simple system of reporting detailed purchase info directly from the store to the user. Getting this to work with many vendors would be a pain, but it doesn't help that currently I don't know anything about those systems. I have some ideas on how to kind of abstract that out...
Those sepia toned filters might actually make me rethink my opinion of the TSA. They should get plaid flannel uniforms and change their motto to "We were groping old ladies before it was cool"
Hospital creates bidding war by posting pricing online
The thread that initiated the hellban seems to have been plucked right out of Reddit. A case study of how not to behave on HN.
No, it can't. Not in any physical sense. If a car swerves and hits a cyclist at 30kph, the cyclist is almost certain to be injured, if not dead. If a bike swerves and hits a car, they might scratch the paint. When will the false equivalences end?
While I feel that most of the article is little more than reaching for straws, he does make some good points about memory management in Javascript and on mobile.

Garbage collectors should be optional. I would really love to be able to handle my memory directly if possible, and while there are some things I can do related to object pooling, I lose control over that with closures and a more functional approach.

I guess to counter my own argument here I will say that for most resource intensive things like simulations (call them games if you will), an object-oriented approach does a better job of modeling than a functional one. Game loops, sprites, bullets flying around... go OOP... and then use an object pool and limit your use of closures. Is it a pain in the ass? You bet, but so is having to manage the heap on your own.

Now, as for the rest of the article, the author did a LOT to discredit himself insisting that JS performance will not increase over the next few years... dude, come on, winning isn't as important as learning and discussing, and you're clearly just trying to WIN an argument.

This article is not very balanced. It is basically just saying that all software written for a VM is stupid. That the concept of Garbage Collection is an abomination.

The truth is that VMs are incredibly successful and aren't going anywhere. I mean, look at the rise of VPS! Now compiled C and even machine code aren't running as fast as they could be! Run for the hills!

Performance is not the be-all, end-all of computing. We're a social species and the reason that JS is the so successful has more to do with the fact that it is hosted in a VM based on open standards than anything else.

So why have we moved to virtualization? Because it makes a LOT of sense. It's the same reason we invented compilers and higher-order languages in the first place... we're human. We are the ones writing and reading source code... the machines don't, they just blindly follow instructions. We choose to sacrifice speed for a more humanistic interaction with our machines, and that applies just as much to programmers as to the people who just use programs.

These are very early days for mobile computing. You say you want to raise the level of discourse? Well then do it by writing articles that are more about discussing solutions than winning. For example, HTML5rocks.com (and yes, I am fully aware of the HTML5 marketing machine..) has been writing some good articles on memory management in Javascript, and that approach actually raises the level of discourse.
isn't dropbox built on top of amazon?

Isn't it a platform on a platform at that point?
If ctf365 wanted to keep the playing field level, they could sandbox the entire network so that attacks originate from another device on the network. So you have:

-----------------Network-----------------------------------
my_fortress <- targeted by: competitors_command&control_box
my_command&control_box :targets -> competitors_fortress
-----------------------------------------------------------

No shady traffic ever needs to traverse the public internet. Only ssh access to my_command&control_box and my_fortress is required. This has the added benefit of normalizing the attacking horsepower of the entrants.
Interesting concept, but how does that scale?
If you have modest needs of it, just run it on the same machine.

The whole point of redis is low latency data queries, which running on some third-party service you lose.
Five things every front-end developer should ask up front
Only Friend People Who Know You Personally On Facebook. #Fail
There needs to be more of this. As a relatively new biker in NYC (since the bike sharing program launched) I've been amazed at the suicidal tendencies of my (non-bike share) brethren. At a red light? Just pedal out into the middle of the road to see if you can cross anyway. Going the wrong way? Sure!
This article is weird. It starts off with a strong premise -- we need more fact-based arguments when discussing technology choices. Yes, agree!

There are a fair amount of good points here, particularly about ARM's potential but he's very dismissive of counter points and seems to believe having lots of quotes is a substitute to a good argument.

The section about garbage collection is especially unconvincing and, again, dismissive of counter points. He never really addresses Android or Windows Phone (which, by the way, he repeatedly mistakenly calls Windows Mobile -- which is right in line with the extreme iOS focus the article has). He mentions them, but then seems to think that a few quotes that show that, under some extreme circumstances -- mostly games -- the GC can be a problem on those platforms. But which is it, are all Java and C# Android/Windows Phone apps unacceptably slow or are some types of apps not really doable in those GC languages?

This is important because a large part of his argument centers on GCs not working on mobile.

I'd conclude that the article is overly defensive. To the point that the author repeatedly poisons-the-well of anyone who might potentially disagree.

> we need to have conversations that at least appear to have a plausible basis in facts of some kind–benchmarks, journals, quotes from compiler authors, whatever.

This is where I think the article falls apart. Appearing to be based on facts is what this article is about, but appearance just gets you talked about. It doesn't really move the conversation forward at all.
Oh wonderful, it appears to use SPDY-like header compression. Why don't we just create a new compression algorithm and predefine common HTML tags and words to improve compression of the response body too! But we shouldn't base it on any known compression scheme and only use it for the case where the content length is less than 220,498 bytes but more than 8,494 bytes to optimize the behavior of today's more common MTU settings for PPPoE in Scandinavian countries minus of course the most common size of compressed headers today. It will be particularly optimized for the kind of responses Google sends back to minimize their own server load and common adwords will of course be included in the predefined list of compressed tokens.

/sarcasm

What happened to simple protocols? Seriously, per-hop flow control (which works best with which of the dozen version of TCPv4 or TCPv6 flow control?)? TCPv4-like framing with weird limits (16383 bytes)? Keepalives/Ping? Truly ridiculous specialized compression for headers which ignores the role of HTTP proxies? QoS?

Why not just implement the whole protocol over a raw IP connection and stop pretending like we're operating in layer 4+? I get that multiplexing is difficult without flow control, but good lord does this thing look overdesigned for what few benefits it offers over HTTP/1.1.
UK residents - please consider signing the .gov.uk epetition [1] for the government to implement the "Get Britain Cycling Report" [2]. Report Summary [3].

The petition is close to 70,000 signatures and should be debated in parliament when it gets to 100,000.

RIP

[1] http://epetitions.direct.gov.uk/petitions/49196
[2] http://allpartycycling.files.wordpress.com/2013/04/get-brita...
[3] https://allpartycycling.files.wordpress.com/2013/04/get-brit...
John Cook has some interesting material on testing PRNGs in his chapter for the book Beautiful Testing. His material is (was?) online free, here: http://www.johndcook.com/blog/2010/12/06/how-to-test-a-rando...
Intro to A New You
Good WIRED article. For the Minority Report (movie) style of your data available everywhere, we need a bit of hardware also for authentication. The only physical thing I always have with me is my wedding ring - it would be neat if small RFID or other security/auth gear could be easily put into existing things, like wedding rings. An alternative would be something under the skin, but I am not so keen on that.

Not to wander off too far afield here, but: secure auth is required to move further forward in user convenience, but in a world where most major companies and most large government organizations get hacked into, having a secure and unobtrusive "single sign on" to all services is tough.

In anycase, I think Dropbax really gets a lot of stuff right. I was just helping a friend and his wife deal with data on different devices and I kept pushing Dropbox. For me, the $100/year is a no-brainer buy decision because I get much value from Dropbox, but they were not convinced.
Bikes are threats to pedestrians. I've never hit a pedestrian on a bike but I've come close. I've also been hit by a car while on a bike (at a low speed, enough to trash the bike but I was able to hop off in time) so I have sympathy here.
> As the author mentions, once you get to 3x-6x more physical ram than what you absolutely need, the garbage collector no longer slows down your device - in fact, it speeds it up. So I'm not sure that this is really that big a problem. RAM is one of the areas where mobile devices really are improving rapidly

That's not generally true. GC performance decreases with the number of objects that have to be collected. More objects (and real-life experience shows that as soon as there is more of a finite resource -- memory in this case -- users' demands will quickly lead to ti being depleted again) actually means worse performance, not more.

GC also depends heavily on the memory's speed, and on the speed of the CPU-memory interface. If those remain constant (and, again, real-life experience shows that, while they don't, they tend to get faster slower than the CPUs do), GC performance hits will actually become heavier with increased memory.

This is particularly important if you consider that you can't actually force GC in most web environments. It's up to the system to decide when it starts cleaning. If that's done on a worst-case basis (i.e. postpone collection until the memory use becomes, or looks to be on a track of becoming dangerous), increasing the amount of memory won't help for memory-intensive applications.