skysight-inc/HackerNews huggingface dataset:
Biggest problem I have with Persona is one of it's main selling points; if you log in to one place you're logged into all the places. That may sound great, but it really isn't. It means that you can log out of a site because you don't want people sharing your machine to have access to it. You then log into a different, lower-security site. Instantly that first site is accessible again.

I wrote a whole thing on Persona a while back ( http://lepidllama.net/blog/trying-out-mozilla-persona-browse... ) but that ended up being the killer for me. It might be fine for activities like posting comments on a blog, but any site which stores or presents some aspect of who am I to the world needs to be a bit more secure than that!
I put a tiny Truecrypt container on my file hoster (HiDrive, Skydrive, Dropbox, etc.) in which I store the KeePass keystore. The keystore itself can't get decrypted, but in case AES has weaknesses one first needs to crack the triple encryption of AES+Serpent+Twofish of the Truecrypt container.
IMHO Clojure's omission of reader macros is sensible: it prevents proliferation of custom syntax, which makes it harder for a human to read code and reason about reader behaviour. The Clojure reader also already has its own literal syntax for vectors and maps [] and {} (which eliminates the most common use cases for reader macros).

If you believe that standards are helpful, then surely one standard reader behaviour is a good thing?

Regular macros are a different issue: they allow creation of custom control structures that aren't possible with normal functions. That's a powerful and useful feature, as many Lisps have proved over the years.

So Clojure rejects the former (unnecessary syntax sugar, potential for confusion, dubious value of reader proliferation) and accepts the latter (additional semantic power, proven utility). I personally think that's a good trade-off. YMMV of course.

Of course, there's nothing stopping you from implementing a custom reader in Clojure if you really want reader macros. So far, nobody (to my knowledge) seems to have cared enough to do this.

NOTE: I'm not bashing Common Lisp: just pointing out that language design has real trade-offs. For me, Clojure gets the majority of these design decisions right. For others, maybe reader macros are an essential feature and Clojure therefore doesn't work. No problem, use whatever works for you.
I don't think, on the net, large companies lobby for regulation more than they lobby against regulation.
Any way to transfer LastPass passwords? I've got a huge deal of entries in Lastpass
Apache communication with lisp process
i am trying to use apache in front of my lisp environment. for the intercommunication i use mod_lisp2.c and i try to listen apache by hunchentoot. i have made changes to my httpd.conf as stated in the mod_lisp2.c publisher's site. but i cannot make it happen. on browser i see internal server error when i point to apache.

What is the problem there? Is anything abnormal or missing. (freebsd 9, apache22, clozure cl, hunchentoot)

I want to be up and go and build my project and use lisp for it. but this gives too much hassle. no problem with the availability of libs to use there are plenty awesome in quick lisp. but with respect to lisp implementation or apache configuration there are options with each missing parts. should i change my idea of using lisp and switch to another environment, like Python, Ruby, PHP?
Sorry to be that guy, but I would never refer to stack overflow as a great community.

It might be a great site to get questions answered, but I feel no sense of community from there.

I'd sooner ask Kim Jong Un about how to build strong familial relationships.
Routing is only as good as the data it is run off from. To do routing correctly for cars, you need direction of segments (one way, two way, only certain kinds of traffic like cars vs trucks, etc), some way to measure the cost it takes to transition the segment (like speed), in some cases number of lanes for "bear right or stay left type of directions" and even more difficult, z level connectivity (for example the Bay Bridge in SF has a set of segments that go above in one direction and another set of segments that go below - exactly in the same direction - right on top of each other).

Search for Navstreets Reference Manual for an example of Navteq's complicated schema for routing: https://www.google.com/search?q=navstreets+reference+manual

I really wish OSM was good enough for those two things... right now, it is not there yet.
I definitely don't think there's anything wrong with using them, but my experience has been more pleasurable without in general. I'm also not entirely sure you can ever really understand the benefits of using a CC, or the reasons they impose the limitations they do, if you've never even attempted to go without one. And I think that when you're first learning about parsing you'll probably be learning more at a faster pace doing it yourself than trying to learn your way around the rather frustrating tooling built around CCs.

I guess if I'm trying to be more clear I'm glad to see this perspective expressed, since it's a relatively rare one to see expressed authoritatively. There are a few topics in parsing that I don't think get enough discussion.

Like, my pet peeve is people thinking a naive implementation of the packrat parser is guaranteed to perform better than a plain recursive descent parser. In reality you might just be trading explosive memory growth for algorithmic steps. In a lot of cases that's actually slower.
We're just targeting that market to start.
It doesn't look so flash using my dark theme unfortunately (Gnome 3, Blackbird theme):

http://i.imgur.com/NQYDBQ8.png
I've dealt with number three so many times. It just seems like a trivial fix to make the npm search more useful. It needs some kind of rating system combined with sorting by recently updated, and popularity.
>>Dell has had a reputation of being the place to work if you wanted a high salary with minimal responsibilities here in Austin. I've heard the politics are brutal, though.

When you can't justify yourself by demonstrable quality output, office-politics comes in.
Less 1.6.2 Released
I forget how I came to KeePass, but I've been using it since around late-2006.

I like how it [the .kdb file, really] can be accessed//written_to in both Linux and Windows, and that it has a usb-portable version.
The hotels have been downgrading the quality around their brand names for years now, cramming people into tinier and more cookie-cutter spaces. Plus the average Airbnb has always had more livable space (not to mention a kitchen!) than a hotel. For 190 a night, you're probably getting the whole Airbnb unit to yourself.

Take that, and SF's 14% hotel tax, and I think they're reaping what they've sowed.
There are two major competitors to the Von Neumann architecture, and then a few speculative ones. The most popular one is Harvard architecture, where code and data are in separate memories (improves security and performance, but makes loading code difficult). Most modern processors operate like a Harvard architecture machine when they are running directly from cache, but they act like Von Neumann machines when they have access to RAM. This means that they get some of the performance benefits, but you need hacky things like W^X to get (partially) the security benefits.

The other one is dataflow architecture, which involves representing programs as a digraph where nodes represent instructions. Data flows through edges from one instruction to the next non-deterministically. This was popular research material in the late 70s and early 80s, but there were efficiency concerns.

IBM (and Von Neumann) also dabbled with making computers that resembled neural networks, but VN passed away before he could dedicate a lot of time to it. AFAIK IBM's neural computer is still in research phase.

I'd say Von Neumann machines "won" for a few reasons. First, Von Neumann consulted for IBM in the department that developed their first commercially-sold computers, so he got a lot of creative control. Second, as Hennessey and Patterson wrote in Computer Architecture: A Quantitative Approach, advocates of Von Neumann computers regarded HA machines as reactionary, implying there was even some religion back then. Third, Von Neumann architecture machines are significantly easier to load programs into. My guess is that a combination of business/political concerns on IBM's part in the 50s and 60s combined with momentum and switching costs is the main reason VN machines continue to win.
Ah, of course, I should have remembered that. I don't quite see the connection, though -- unless there was a backdoor and the crackers got that backdoor password, or some such.
Done ... so pretty now. :)
When will it ship to Canada ? I just tried buying a chromecast on amazon and it wont let me.
A couple obvious questions:

- Is it possible to design a Git-like VCS with only two or three "places" instead of five?

- What would be the downsides of such a system?
GoPro is hiring for several Full-time roles in San Francisco.

-Director of Engineering, Platform:(go to: http://www.thesourcery.com/jobs/641)

-Software Engineer: (go to: http://www.thesourcery.com/jobs/643)

-Sr. Software Engineer: (go to: http://www.thesourcery.com/jobs/644)
Just as ID is a pseudoscientific attempt to cast doubt on evolution, motivated by ideology but dressed up as science, so too is denial of AGW an attempt to discredit climate science, motivated by ideology (or profit) and dressed up as science.

Climate models are tough and it's very difficult for us to forecast what the results of global warming will be, especially at local scales. That doesn't change the fact, well supported by science and not seriously doubted by any meaningful number of climate scientists, that the Earth is getting warmer and it's almost certainly due to our burning of fossil fuels.

There are two groups who try to make AGW seem less certain than it is: energy companies who have a financial interest in not seeing government action against carbon emissions, and libertarians who feel threatened by the reality of AGW as it would seem to mandate large-scale, international government regulations. That would call into question deeply held libertarian beliefs about the ability of the free market to achieve societal goods and avoid evils. Just as religious people (rightly) view evolution as a threat to their beliefs and respond by attacking evolution, so too do libertarians view AGW as a threat to theirs and respond in the same fashion.
git is NOT hard iff you understand the data model. Don't use it until you understand the data model.
I'm not sure that would be the case based on http://blog.agilebits.com/2013/12/31/the-nsa-can-do-what-to-... (scroll to the Miscellany section)
Ethereum compiler is up
How A Simple New Invention Seals A Gunshot Wound In 15 Seconds
I've not had success using Calibre on Linux, even for backup purposes.
Closed as not constructive.
I question its truthiness. It's not as if there's some shadowy cabal conspiring to force people to put operators in the middle, we developed the infix notation over a long period of time and it seems likely there are good, though possibly not entirely logical, reasons for it. We humans have funny brains, after all.

And if you really want to dive down that rabbit hole I think you have to establish that prefix is better than suffix as well. I'm somewhat dubious of even this claim, since I find suffix easier to reason about. But maybe that's just me.
Looks like the menu widget and icons are not using GTK for whatever reason. It may be worth pinging the KeePass developers with a screenshot showing that the GTK theme is not being respected properly when rendering the menu - the menu even looks odd using a light-colored theme like Clearlooks because it doesn't match the theme.
"First, your data is stored on Google servers — essentially the same servers as Gmail. This means your secrets are as safe as your email."

Well, if David says so…
Why not use postfix notation, and make a stack based language like Forth? Even less parsing to do.
Of course it is political action! It happens all the time, for private developments (eg casinos) as well as government developments (eg, local governments enacting laws to make putting sewage treatment plants or nuclear waste treatment plants in their areas)

It is effective because it adds friction. Things seldom change from one action, but lots of things add up.
Incredibly fast prime number visualization
I recommend OneShallPass (http://oneshallpass.com) over KeePass. It's open source and auditable like KeePass, but:

1) It doesn't have to be compiled or installed, since it's just a monolithic HTML page with all JS/CSS inline.

2) It has a free, optional hosted service that stores encrypted passwords with pure client-side decryption, so you can get your passwords from any web-enabled device without having to trust the host.
Minor point: the stash, the local changes, and the staged changes are all very simple to grasp. In fact, you don't have to use the stash at all and you could even forego the staging area since you can just get git to commit unstaffed files directly. Sure, there is a reason those things exist, but if you are still in SVN world and are using git for the first time, these are not the places likely to trip you up. What you are likely to get confused by is things like rebasing, and the fact that your local repo can be modal, such as when there is a merge conflict while rebasing.
Parkinson was an optimist.
The title is misleading. If any, it reinforces the fact that python is a good language for solving puzzles, writing scripts, and may be small projects.
That does indeed sound like it solves the problem. Bravo, can't wait!
Corollary of YADSL, Yet Another Domain Specific Language.
I was hoping I could find exactly this. Thanks.

The source[1] is also on GitHub too. As a non-c++ programmer, I found it pretty easy to follow along.

[1]: https://github.com/keepassx/keepassx
KeePass 2 is built on C# and works in Mono. It doesn't use Gtk# but WinForms, which on Linux doesn't follow theming well.
It's interesting, though I can't say how significant, that the (pretty tiny) tabletop-RPG publishing industry, which went electronic in a serious way much earlier than publishing in general, largely abandoned DRM at a very early stage in the process.
Well said. I feel that complaints from users should always be taken seriously. The fact that a piece of software is better than what came before doesn't mean that it can't have flaws, and can't be improved upon. I don't think git's command-line interface was designed poorly or to make things difficult. What I think is that the command-line interface was created as an afterthought, since git was originally supposed to be a low-level component and not a full-fledged VCS, and so the commands were cobbled together rather than planned.
I'm a long-time user of pass (http://www.zx2c4.com/projects/password-store/). I prefer tools that integrate well with the command-line, but there's a few things I didn't like about pass, so I started my own password manager, called passman (https://github.com/manicolosi/passman).

I wouldn't recommend using it yet, but any feedback would be super helpful.
Because it was created by Linus for Linux, a systems kernel. Very few people need to interact with a kernel. And the ones who do are so technically advanced they put up with the steep curve inherent to using Git. The fact that Git has gained popularity outside of Linux kernel development is secondary.
2.4 M in 85 years? That is 28 mm a year increase - current observations are about 3mm per year. That is an exponential growth that is unlikely to occur.
I do something similar.
I have a keyfile that I copy over manually so that people need to get more than just my password + .kdb
I've personally found that even when working with parser generators or handwritten parsers that don't need the separation it still helps to consider them separate. Having a stable and solid set of fundamental tokens makes the resulting language easier to understand. Whenever I see a language (usually made with a PEG generator) that blurs these lines everything feels very shifty. Yes I know these are very touchy-feely attributes I'm describing, and you can obviously avoid them without that separation as well, but these things are important as well.

It's an interesting accident, to me at least, that this separation turned out to be both optimal and useful.
I've added some more detail to the landing page:

http://www.cointouch.com/
Betteridge's law of headlines states: "Any headline which ends in a question mark can be answered by the word no."

You have to modify the law a bit with this article but you get something like "Git is not hard". That is the answer to this article.
Show HN: Android app to quickly add faces to images
That is exactly why sites shouldn't provide password reset by email. Email shouldn't be used for authentication in any case. It's really insecure solution.
Git provides some amazing tools in a very accessible way:

1) A great way to find regressions which is easy to automate (bisect)
2) light-weight branches
3) nice tools for dealing with patches (am, format-patch)
4) rebase (squash, amend, fix bitrot)
5) Super-simple submodules (compare this with gclient DEPS to get around SVN
limitations!)

Not to mention the main point of Git, the distributed nature, and the ease of moving code between two repositories.

These basics are easy to learn, not demanding at all, and just feel good to use. I have trouble comprehending when people say it's difficult, especially compared to things like Mercurial (and the mq extension), or SVN.
Uh, tech's not really a great reason. The tech behind 20 year old games is hardly an arcane mystery. The Games industry in general is pretty good at sharing techniques, perhaps because by the time they're shared, they're already old.

You don't need a game to enter the public domain to deconstruct ideas and craftsmanship either. You DO need it to legally play the majority of games for free, or to resell without paying royalties.
When did blogspot break the back button?
They sell more than computers though. Monitors, printers, servers, storage, support, etc etc.
> Also it won't take "years" to get a working prototype. You can get something working in less than a month.

It all depends on the language. Tiny domain specific languages might only take hours, under the right circumstances (for an experienced language implementer).

When someone says "years", I assume they mean an industrial strength general purpose language.
I dunno, SVN has had great integration with the Windows Explorer, at least when I learned it a decade ago. It really was pretty intuitive. (Now, granted, SVN had many other imperfections, but it worked pretty well for smallish teams.)
It'll be interesting to see if they stick to this globally.

The distinctly American prudishness regarding sex is almost a mirror image of large parts of the world with respect to cinematic violence. It's part of why you can be so sure these west coast companies will never monopolise the market in Germany, for example.
I built a similar hosted service on AppEngine called KeeStand (http://keestand.appspot.com). Code is on Google Code (https://code.google.com/p/ariwilson/source/browse/#hg%2FKeeS...).

Additional features:
- It works offline.
- You can import or export your passwords in CSV form.
- If you choose to delete your account, it is immediately and irrevocably destroyed.
You can buy write-once, use-only SSL modules. Look for "SSL Offload".
Life is too short, drink better coffee
I've been having it on my various systems (Windows, Linux, Android) in the sidelines for a couple months, and after initial fiddling, still haven't actually started using it.

This is mostly because I don't want to have to deal with copy-pasting my password between the KeePass app and the browser (where most of my passwords are needed). Luckily, there are autofill plugins that exist for Chrome [1], Firefox [2], and Android [3].

However:

- said plugins work with KeePass2 which on Linux the GUI theme to the point of being almost unusable (as a C# app using WinForms, it doesn't respect GTK/Qt themeing well).

- getting the KeePass2 plugin needed for the browser plugins requires jumping through hoops on Linux and I haven't gotten it to work (yet?).

- I'm sharing my KeePass database on DropBox (with its own security considerations...) to synchronise between the different systems and...

- The Android app just won't open the shared database.

So it feels like I'm 60% of the way there, but I still don't have a usable system. Hints appreciated.

[1] https://chrome.google.com/webstore/detail/chromeipass/ompiai...
[2] https://addons.mozilla.org/EN-us/firefox/addon/passifox/
[3] https://play.google.com/store/apps/details?id=com.hanhuy.and...
I'll admit that is an interesting feature honestly the first thing on the list? It's certainly a cool and interesting idea, but I'll admit it's not a super important feature in my view. Thinking back on all the research I've done I can't think of a single time where I would need such a feature. I never use any data strucures beyond matrices, which Matlab handles by default. Since 1x1 matrices are just numbers, every function that works for matrices, works for single numbers.

I do use Python, but it came into it late on my project. Future projects will definitely use Python since it's good enough for data processing stuff. Hard core numerics will still be done in Fortran/C.

I definitely do see Julia being the better version of Matlab but it certainly has a ways to go.
> We'd love to go abroad, the only prohibition to that is the cost of passports.

? A US Adult Passport costs $110 and last 10 years; that's $11 a year. (Kids are less.) Are you in a country where it costs a lot more than that?
Why the heck is Git so hard? No?
I use both Mercurial and Git. Mercurial is just as powerful but does a much better job at hiding the underlying model and doesn't make it as easy to shoot yourself in the foot. You can see a comparison of the concepts here: http://mercurial.selenic.com/wiki/GitConcepts (maybe a little biased but I think it does a good job)
The 'storing hashes properly on the server' problem is the biggest problem with website authentication right now, as seen by the number of breaches resulting in weak-ass hash dumps.

With SRP the derivation of strong keys using a KDF is done by the client. Not only is this more scalable, it means users don't have to trust web developers, who are almost never cryptographers, to get the 'storing hashes properly' bit right. Not having to trust is great. Not having to trust websites with our chosen passwords also means most of the risk of reusing passwords across services just goes away. In short it's epic win for users, but it's extremely difficult to get people to see that the real problem is a bad trust model.

Another reason to like it is it's safe to use over vanilla unencrypted, unauthenticated connections, which could be important because certificate authority integrity is, imho, the second biggest trust issue on the web right now.

Persona and OpenID etc are flawed because they copy that very same CA trust model.
How do you know if it is a time saving abstraction or a time wasting abstraction without knowing how it works?
Yep because porn will bring the world to an end... unbelievable.
Kentucky lets Computer Programming satisfy their foreign language requirement
... Except the Fed is mainly buying Treasury debt. It actually encouraged loaning out for "risky" investment by pushing down interest rates. That's why there's the fear in emerging markets as the program winds up.
Exactly. The first thing I tell people when moving over to git is to forget SVN ever existed. Thinking in terms of SVN (or another non-Dvcs) is what I find trips people up over and over again in git.

This isn't to say the git cli is perfect, but once a person understands how a DVCS works the typical git use case is easy. And then when someone needs an advance feature they can look it up. Git continues to surprise me with its code wrangling abilities.