Recent submissions

Comment · 9 years ago
I like the analogy to de-noising autoencoders; that's a good way of thinking about this.

> In the limit, you might even have a neural network generate increasingly harder types of grammatical corruptions, with the goal of "fooling" the corrector network.

Very interesting. I wonder how many constraints would need to be added to the corruptor model to ensure the corrupted sentence retains the same meaning as the original. Somewhat related to that, I've thought that a more basic curriculum learning setup could be deployed quite effectively here, and am hoping to try that out soon.

Comment · 9 years ago
Yep, it definitely has room to improve. The work thus far has primarily been a proof-of-concept for the methodology used to generate training samples (i.e. starting with grammatically correct text and introducing errors). Next step is to try to include more high quality data, after which I may try out comment data from HN, etc. I think it would be interesting to see what the effect of somewhat noisier data like that would have on the model.
Comment · 9 years ago
Thanks for the links! I'll have to try out some of these. The data is definitely the limiting factor at this point.
Comment · 11 years ago
Comment · 11 years ago
Author here, feel free to ask me any questions.
Comment · 13 years ago
It seems like this would be much more useful if the front and back of the card were OLED screens, or something similar, so that you could toggle the appearance of the card. I feel like that would solve most of the problems people are suggesting here - i.e., it could replace driver's license, photo id's, wouldn't be a problem at bars that hold on to your CC, etc. Personally, I'm going to hold off on getting this until there's some functionality similar to what I outlined above, because currently this could only replace 2 out of the 5 cards in my wallet.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton