skysight-inc/HackerNews huggingface dataset:
> Most websites don't have secret token URLs that will log you in, right?

That's what they are proposing. Every time you log in they send you a one-time secret token URL by email.
This argues equally well for completely supporting the family indefinitely for any reason. The only difference between paying medical bills and paying for the whole lifestyle is a matter of cost, and medical bills can be really expensive.

Doesn't it bother you that an even-handed application of this principle leads to absurdity?
It seems the whole brunt of the article is, "Eh, it's good enough the way it is." It's just lazy and useless.
You put an e-mail in the box, click Submit, it sends you an e-mail with a link to click. You click the link, it brings you to a page that sets a cookie for you (key '_logged_in', value 'SOMEKEYSPECIFICTOYOUREMAILADDRESS'). Browse the site with the temporary key linked to your e-mail address. When your browser closes the cookie is gone.

If you want to log in again, repeat the process.

Now, here's why this is a bad idea: e-mails are not secure. They are sent willy-nilly around the internet in plain text through multiple mail relays. All one would need is to sniff traffic on a network segment that the mail travels over and you'd have a hell of an easy time collecting login info. This is why the passwords sent over e-mail are supposed to be temporary, and why most good password reset forms ask for additional confirmation details before they let you reset the password.

You might think the above process would be secure if the link they send you is de-activated the first time you click it, but anyone could just keep sending more e-mail login requests and collecting the e-mails. The whole thing is pretty not-secure.
Woah, you're way off when talking about sciencebasedmedicine.org. That's Steve Novella's site - and he's about as respected as you get in the sceptic community. If you want to claim that it's mostly industry propaganda, you'd better have some good evidence to back up the claim!
Opera does support web sockets: opera:config#UserPrefs|EnableWebSockets

They are not enabled by default, that's all. So it's not just that the message is snarky and insulting, it reflects ignorance as well.
My position is that a 100% culture, 0% biology explanation for group differences is highly unlikely given the fact that statistically significant biological differences do exist between "races" (groups that were geographically isolated from one another until several thousand years ago). Yes, I'm just criticizing, but it's a criticism that needs to be heard. We've allowed ourselves the comfort of believing that there are no inherent differences between groups of people for too long, and, basically, science says otherwise.
hell no, it's been a breath of really fresh air for us, we've been building all sorts of things, no problems so far. (including logging several millions of requests per day and performing distributed map reduce for all sorts of statistical models on a tiny 3 machine "cluster" we run on AWS, I hope I never have to go back to modifying schemas again, so much simpler to run and build with this mindset)
Makes me wonder, if emails and SMS messages start to carry more and more plaintext passwords (and links) providing direct access to everything, how will their security hold up in the long run? I don't think they are inherently very secure channels.
Kiva.org helps us support micro-startups by GetViable
Now, cue the browser plugin to which you give access to your gmail (via OAuth), that handles this transparently.
Best practice for serving .css files is gzippped? Is this at the file level or on-the-fly by the web server? In any case, why is this considered best practice? (I ask as a sysadmin, not a web developer.)
First, what's being taught should be applicable to the real world. That means that if you are to produce useful and productive graduates, getting them familiar with ARM is much better than anything else out there.

Second, even if you had a similarly performing architecture, unless some major manufacturer with deep pockets picks it up and fabricates a chip around it, there's not much you could do with it outside of FPGA experimentation (for something that can mimic the power and peripherals of the Pi, with all its shortcomings, you're like to need a multi $k Virtex FPGA).

Third, ARM is friendly enough to its partners and the ecosystem that it won't be going away for a long, long time. It's a reasonably open company as far as documentation goes, and do their share of community contribution. ARM was smart enough to grant architectural licenses to the only companies rich and smart enough to make their own architectures (Marvell, Qualcomm, Apple, Samsung and a few others), so they can spawn their own variants while still retaining standard ARM compatibility.

I don't see any company seriously threatening ARM's dominance for at least a decade. If you want to do embedded systems or mobile (and soon servers) low-level, you need to know ARM.
Because it's only a website, not REAL engineering! Let the intern do it!
Um... the (short) article was filled with substance. There's a big block quote from Kawasaki right in the middle where he talks about all the specific things he likes about Android.

Now, those are all high level things everyone here will be familiar with. So maybe the article is mis-targetted. And the headline is clearly designed to inflame. So you can argue about that if you want.

But saying that Kawasaki's opinions have no value is just weird, and sounds like sour grapes to me. The guy was the official Mac evangelist for literally decades. Clearly his opinions are newsworthy.
Letters From Anthony Flew Made Public
You are absolutely right about the complex user interactions. In that case the responsive design could just be informational only (hiding all the complex features that would otherwise be very hard to use on a mobile screen).
Maybe they did that right after writing it clear text in http logs stored in publicly accessible files.
This feels like it's arguing for limitations, and i'm never a fan of that.

The argument that responsive design is not worth it, because some people do bad responsive design (or even most do bad responsive design) is pretty odd. To carry that same sort of argument out into anything in life would land you in serious life lessons.

Yes, responsive design takes more time (no matter how you slice it). And, yes, sometimes it's not needed. Those should just be obvious to any developer worth their salt. Like everything considered when developing a website - weigh it all, figure out what's best for the project and it's users. Most definitely - time/money will be a factor in those considerations sometimes.

All I can think is the writer of this article hasn't seen how powerful responsive design can be?
It would seem that the conclusion of this article can't be drawn from the quotes Schmidt gave.

"Reuters has softened the tone of its original report which is now disputed by Bloomberg. Bloomberg says that Schmidt declined to say whether Google submitted its Maps app for Apple approval. Instead it quotes him saying, "We haven’t done anything yet with Google Maps," adding that Apple would "have to approve it. It’s their choice." The updated Reuters piece now quotes the Google chairman saying that Google and Apple are in constant communication at "all kinds of levels," while appearing to say that the decision to remove Google Maps from iOS was Apple's alone." [0]

[0]: http://www.theverge.com/2012/9/25/3386598/google-maps-app-st...
Possible misleading headline:

Google Executive Chairman Eric Schmidt confirmed on Tuesday that his company has not submitted a mapping app of its own to Apple's App Store, though he didn't entirely rule out the idea.

Just because they haven't submitted one, doesn't mean they're not working on a new one.
Does not mention OStatus; flagged.
I want to add the fact that it works just fine when spoofing the user agent. "Identify as Firefox" setting in Opera.
Libertarians do overlap quite a bit with anarcho-capatilism and randism. You might not define libertarianism that way, but many do. The best you might say is something like, 'libertarianism, as espoused by [X], hold that a government should be in place.' As a counter example, I can easily find self-identified libertarians who are anarchists.

edit: grammar and clarification.
> Yet, this is the exact stuff the kids are interested in! They want to learn how it works.

Speak for yourself! When I was a kid I was more interested in computers than anyone I knew, and I was the first kid I knew to own my own computer, and yet most of the educationsal stuff I could find on computers was the sort of stuff that explained all about registers and CPU cycles and the like. I had ABSOLUTELY NO INTEREST in that stuff, other than a quick overview of how a computer is even possible. In fact, I found all this low-level stuff being foisted on me as incredibly tedious. I also had a motorcycle when I was a teenager, and I found all the nonsense about registers and CPU cycles to be like trying to explain to me how a carburetor works when what I had asked was how to do wheelies.

I was much more interested in high level languages because they let me see how I might potentially accomplish amazing feats. I found Basic to be tolerable, but the first thing that I found to be truly inspiring was APL, due to its mathematical elegance and its providing a vision of amplified productivity. And you can't get farther away from the hardware than APL!

On the other hand, later in life when I went to college, I did find it very interesting and inspiring to learn how to build (and to actually build!) a micro-controller out of nand gates and an EEPROM. Registers, CPU cycles, and the like, are the monkey in the middle. Too low level to be fun, and too high level to let you feel like you really understand things at a fundamental physical level.
his SafeSet implementation exposes functionality as exported fields instead of exported methods. That should be a red flag to anybody with any real-world Go experience. Exposing functionality through channel fields obviates the possibility of generalizing the functionality as an interface. It also creates subtle traps, where the caller must now know whether they're expected to set these channels to be buffered or unbuffered.

If you're dead-set on implementing this with channels, those channels should be unexported and hidden:

http://play.golang.org/p/zRSco7MpMl

In reality, it's far more sane to just say `type SafeSet struct { d map[string]bool; mu sync.Mutex }`, again exposing all the functionality through methods, and just locking and unlocking the mutex as necessary. If using a mutex makes the implementation more clear and is semantically equivalent, then use a mutex. That's not typically the case, because typically the case involves more than just locking and unlocking. In this particular example, all you need to do is lock some resource, so it's ok to just use a lock.

And the claim that there's no data privacy isn't correct, it just assumes a data privacy model that Go doesn't have, namesly the "public" and "private" notions. Go instead opts for the notion of "exported" and "unexported" fields and methods; i.e., fields and methods that may be used only by code within the same package. It's a different mechanism for hiding data, but it does exist.

Anywho, if you want to see a completely absurd, lock-free (not strictly nonblocking), threadsafe queue in 51 lines of Go using higher order channels, just for kicks, see here: https://gist.github.com/3668150
Web-based SVG Editor
I felt that way three years ago.
At this point, I'm starting to think the omission is intentional.

Similarly with home-screen widgets.
Though I think lock screen/notification center widgets might be incoming.
> make them really miss Google

Presumably this will also lead to a number of iOS to Android converts - it's not just about making Apple look bad, it's demonstrating on a large scale that "Android is better, see?".
Did anyone else think of opening their own charging station(s)?

I think the big news here is that someone is creating a distributed electric plant with social benefits to attract customers to buy their cars, pretty brilliant and world changing ideas. Why not join the fun?

Even if there's not enough Tesla or other electric vehicles coming to your station you'll at least be making your money back on solar energy generation and selling coffee, internet, etc. to customers that come in.

Tesla doesn't have to be the sole provider for the free charges.
I like it. Especially because theoretically it can be
mixed with other, conventional authentication schemes, so it can be made completely optional and used at will, just like sites currently mix password + several OAuth providers.

It's pretty much the ideal scheme for all those sites you don't visit regularly (and many of us, despite knowing better, use the same password for...).
I was not aware of that at all, thanks for pointing it out. Looks like this could actually be a solution to something.
If it is the kind of site for which you are willing to keep a cookie around, then you'll only have to get a new link from your email whenever your cookie expires or if you explicitly log out.

Otherwise, you are correct.
We've been using MongoDB in production for our main content store at Conversocial for over a year now. We've gone from 1.8 to 2.0 to 2.2 and we're happy. We have ~400gb of data, 220 million documents all on Amazon's SSD instances.

We have definitely had our moments where we've screamed that we hate Mongo and are going to rip it out. That's normally where we've overlooked a detail of how it works... and we've had this same experience with every database technology we use - including MySQL and Redis.

The day after, when we've cleared our heads... we're happy again. The same as the other technologies.

I think that with all technologies you're going to get bitten by some detail you didn't know about or had forgotten. The trick is to mitigate these disasters by thinking about your failure cases.
While I haven't gone full production with MongoDB yet, it has been a struggle to hear the signal through the noise.

I'm glad that there are proponents of MongoDB like ServerDensity, it's nice to hear the other side of things from people who understand the issues.

Out of all the issues mentioned, I'm particularly interested in a fix for uncompressed field names.
The new MySpace: a mix of Pinterest, Metro, and Justin Timberlake
Actually that's quite easy in Opera. There is a dropdown box to select different user agents called "Browser Identification".
Helpful Resources and Webapps for New Web Developers
That's my exact thought. An idea solution is to check your mail on your phone, open a link that is essentially a second layer of authentication where you can login by clicking on the link in your mobile device, then refresh the page on the desktop and you'll be logged in.

I still see this cluttering up my inbox, they would need to be deleted right away...for me it's just easier to type in a password.
>These days there is just simply no suitable platform to actually play around with

http://www.redferret.net/?p=33596
Really weak article. This actually makes me look down on ManageWP as a brand.
You cannot be an entrepreneur if you do not cut the ropes
> Comments: The 32 bit limit is noted (perhaps it should be a warning) on the download page but the main problem was the author did not know when writes started to fail. MongoDB uses unsafe writes by default in the sense that from the driver, you do not know if the write has succeeded without a further call to getLastError. This is because one of the often cited use cases for MongoDB is fast writes, which is achieved by fire and forget queries.

(in reference to I’ll Give MongoDB Another Try. In Ten Years, http://diegobasch.com/ill-give-mongodb-another-try-in-ten-ye...)

I read the referred article and the HN discussion...but wasn't quite able to tell how much of the debate was focused on the reasonability of this default rather than "developers should read the docs, or accept catastrophic failure" attitude (which is not inherently wrong).

What immediately comes to mind is the Rails ActiveRecord update_attributes vulnerability...the default was to allow the updating of all specified attributes with the assumption that no competent developer would trust unsanitized input from the browser. After a good Samaritan performed a spectacular hack on Github, the Rails team immediately changed the default.

Is that the situation here with the 32-bit silent fail default? That it is a sensible default, but could be changed if it's shown that competent devs will nonetheless screw it up?
Quite interesting though, as far as "useless" ideas go.
Google "Hacker News collapsible".
Why hasn't someone just used the Google Maps API to mock up a quick app and submit it? Would Apple simply reject it?
I'm not sure you can call that "strategy" if a prerequisite is that your competitors customers are unhappy. :)

Apple's hubris (and a not inconsiderable amount of hype by the media, no doubt related to some PR misteps by Apple) gift wrapped this for Google. All they need to do is write an app.
"He's about as respected as you get in the sceptic community"

Ever look up how respected skepticism is within the larger philosophical community?

I mean look at my pastebin post: http://pastebin.com/cniysd82

And this encompasses only a small fraction of the corruption within the pharmaceutical industry, because I wanted to make it readable. There are literally dozens of book published on this.

But does SBM actually address any of the criticism? Not a single point of it, because there is no defense; in fact, it's all coming from high-level 'insiders' in the medical community -- JAMA, NEJM, the IOM, etc. Instead they just spin it in order to trick people who are predisposed to have faith in modern medicine. (And I use the term faith, because if you're familiar with these issues then it's unmistakably clear that this is really what it is.)

What science-based medicine does (again, the blog, not the concept) is really no different than what the evangelical megachurches do, it's just dressed up in different language.
The original article wants the equivalent of an open source Z80/65xx/68k, fuse settings for all the ULAs, schematics for all custom-designed chips, and open source ROM disassemblies.

1980s home computers didn't come with these, even though they had (for the time) very powerful custom graphics and sound chips (eg. Amiga [1]). Of course, some of it was reverse engineered, and some of it has been released long after the fact.

[1] https://en.wikipedia.org/wiki/Original_Chip_Set
They're not secure. SMS and e-mail are sent unauthenticated and unencrypted and can be intercepted in many different ways.
I did replace the # with %23 in my testing, it works on the S2 but not the S3. You can view for yourself at: http://kristofferr.com/samsung.html
The thing is, those channels are already used by most services for password reset.

So, a user could implement this workflow themselves already.

Basically, create a password for the site that you don't even know yourself when you sign up. Make sure you select the appropriate "keep me logged in" option.

Now, if you ever get logged out, go to a different computer or otherwise clear your cookie, you just "reset" your password... which generally involves sending you an email that lets you login to the site based on the link or code provided.

This approach is simply making that the norm and doing away with the (probably insecure anyway) password for the site.

If email and SMS aren't secure for password recovery, what alternatives do we have that scale and provide for a quick and user-friendly experience?
>None are or claim to be based on libertarian principles.

I think part of the argument is that if libertarianism is so good / efficient / other desirable criteria, why don't societies naturally evolve into those societies?

Again, I don't think that this is the entire argument, or even a particular good one (in the case of somalia). I'm just pointing it out.
I wish you would write about some of these issues that you faced so we all can keep them in mind when using MongoDB in the future.
Bookmarked. This is really useful.
This article makes no sense. We know Google Maps won't be the built in mapping solution already, but it sounds to me like google did/will submit an app:

>[Eric Schmidt] said any decision on whether Google Maps would be accepted as an application in the Apple App Store would have to be made by Apple.
It's actually not an uncommon behavior for a sick bee to leave the hive. They do this so that they will die outside and protect the rest of the colony.

http://peacebeefarm.blogspot.com/2011/01/protection-by-behav...
As many people, I find a long text (like a blog post sometimes is) easiest to read if it is about ~80 characters wide. My laptop has a 16:9 display, and I usually have my browser in full-screen mode with tabs in a sidebar on the left. This leaves plenty of space for a website to put a sidebar and text side by side, so I don't really mind it on the desktop.

Obviously, if the sidebar does not add much (like on many blogs), I wouldn't mind if it goes away entirely.

edit: Columns seem to be problematic when there is no well-defined "end-of-page", as on paper.
From the article it doesn't sounds like it was anything to do with the db.

Looks like they were processing the logins using GET instead of POST, unaware it was logging all the requests. Then the log files ended up on an ftp server for anyone to download.
There is a greasemonkey script that does this. Just google it.
Show HN: streamplayer.js
Made a pretty simple Flash+HTML5 video player controlled by streamplayer.js
webgl can be much faster because you can draw many primitives with one call. there's a lot of overhead from js down to gl.
Read what I wrote, I wasn't talking about the S3 :)
The consequences of an attacker getting access to my Dropbox are less grave than an attacker accessing my email account.

Can you be specific as to why? If you use Dropbox for personal information, I'd assume it would be similar.
This is cool for simple use cases, but why not just use Core Data? Just check a box when you're making a new project and you're done (well, kinda). That said, for projects that just need a simple straight forward db framework this seems cool.
Well, someone has to. The alternative is having the authors pay, and that creates the wrong kind of incentives.
For this reason, the link/code being sent should have an expiration attached to it, as well as being single-use.

This doesn't avoid any number of different scenarios.

Too bad we don't all use PGP for email...
I have hurt my nose before with a hardcover book. Clearly, those things should never be printed. That's supposed to be the reason to go for one or the other - nap-friendliness? People are becoming ridiculously spoiled.
And to a lesser degree: "It was his job to shill the first Macintosh, and he did a pretty good job." "Job" twice is redundant. It's not a huge deal but it's just kind of lazy and sloppy.
Definitely a neat idea. Could also just email them a reusable link except that would leave the credentials in your browser's history unless there is a way to avoid that.
They're not particularly exciting. Example: we accidentally left detailed logging enabled on a secondary server and weren't monitoring the space left on the drive for logs. The disk got full and the secondary failed. Annoying that it failed but it was our fault for not monitoring that space and also leaving detailed logging on!
You mean WP? It's not really an alternative, it's iOS in different clothes. It's even more closed and walled than iOS, and most fruits in that garden are rotten.

Only way to succeed with walled garden is to have the best fruits in there.
No giveaway needed. It's got the MarketWire logo fairly large at the top, and look at the byline:

Press Release: Tesla Motors, Inc.
Alexa Ranking: Facebook overtakes Google to claim the top spot.
RoboHornet: independent browser benchmark
And if you was a freelancer instead of an employee? or a coworker?