Hacker Newsnew | past | comments | ask | show | jobs | submit | more phpnode's commentslogin

Long sales pages convert. There are a few reasons, one is that long pages give you the chance to pre-empt and answer each and every question or concern that the customer might have. The other reason is that merely by spending a long time reading your sales page, that person has made an "investment" (of their time) in what you're offering, and now they want to get something for that investment.


I think that just comes down to numbers. There are only about 40 million people in Australasia compared to 740 million people in Europe and 312 million in USA.


By saying "australasia" I'd also include Japan (130mn), South Korea (50mn) and India (1.3bn) -- not China, which is notoriously insular on most levels. They sum up to a sizeable contingent that doesn't seem to be represented in HN posts (note: i'm not saying they should, this is not about political correctness).

I noticed the occasional post about Indian matters, but it looks like the other Asian communities are just not interested in HN at the moment.


If you've ever tried to do this you'll know that while it works in theory, getting it working in practise is much harder than you'd think. In the past I've tried to create acapellas using a song and its instrumental (both digital recordings taken from the same source) using this technique and even with the highest possible quality digital audio the results are mixed at best.


Honest question - what can you do with bytecode that you can't do with javascript? Modern javascript is fast and ubiquitous and is clearly not going away anytime soon. Isn't the human readable nature of javascript more suitable for debugging anyway?


Some features typical of VM languages, like "goto" makes it more appropriate as a compilation target, because lots of higher-level control structures kan be compiled to gotos. Of course goto could also be added to the JavaScript language as is, but then we have a conflict since goto is nice in a low-level language, but discouraged in higher level languages. This conflict of interest in language design does not exist when the user language is seperate from the VM-language.

I agree with your point though.


The Relooper is good enough that the lack of goto isn't an issue in a practical sense these days.


The Emscripten Relooper algorithm "takes basic blocks of code - chunks of simple code, at the end of which are branches to other blocks of code - and generates high-level structure from that using loops and ifs."

http://mozakai.blogspot.com/2012/05/reloop-all-blocks.html


That's my point. The Relooper does a good job with vast majority of code that you might conceivably want to compile to JS, making the lack of goto not a problem in a practical sense for these compilers.


Hah, sorry, I didn't know what Relooper did, so I posted a comment describing where to find out about it for other people.


or you can literally write the whole sentence, which is even more secure and you don't have to remember any special rules, just the sentence itself. Of course it's more typing:

    Guess what? Back in 2009 I saw a uniquely attired man traipsing round local places with a high number of legs, necks and shirt collars.
136 characters or 14 Gigayears to crack. Wow today I learnt that there's such a thing as a Gigayear.


I just went through the process of changing passwords to sentences. You'd be surprised at how many sites do not allow sentences.


I use a password manager, and I have a unique password per site. I generally try to use an MD5 hash resulting from a "ps waux | md5" at the time of registration. I've encountered sites that rejected this due to lack of upper characters (oracle.com, which then allowed me to use "Abc123"), having no special characters, being too long (often forcing me to down-size to 16 or 8 chars). The worst are sites that silently truncate long passwords (I'm guessing due to code errors), so your password is invalid the second you register and must immediately proceed with a password reset.

Big sites are generally good about allowing long/strong passwords. Many mom-n-pop sites are often hit-or-miss.


What irks me is when they reject special characters like ?!#$@", etc.


Well, to be fair, 14 Gigayears in terms of an attack geared towards a totally different case. I wonder if we can optimize an attack on sentence passwords using hidden markov modeling, or other natural language processing methods. The entropy at the character level decreases if we assume the password is an english sentence [1], and my gut feeling is that we can apply this same thinking at the word level as well (this may very well have been demonstrated already in research).

[1] http://www.nd.edu/~busiforc/handouts/cryptography/cryptograp...


I thought about that, but presumably since so very few people use sentence based passwords, crackers don't optimize for this use case yet. Regardless it's quite a long sentence and that should afford some additional protection against this kind of attack, i can imagine 3 or 4 word sentences being defeated by this kind of technique, 30 words seems a lot more difficult


This is purely a thought experiment at this point, but it would actually be a pretty interesting project. I wonder if it's true that longer sentences would be more secure -- or perhaps entropy decreases with larger inputs that give more data to analyze. In the cipher world this would be true, but for O(1) hashes, I'm curious how this could be tested.

Edit Ultimately security from these types of attack would be with unusual/non-sensical adject/noun, adverb/verb pairs etc -- which your example does reasonably well. Picking a bible verse (for example) would be bad, though.


The problem is that you have no hints about what is correct or not because presumably a one way hash is being used, so even if you get the first 29 words right, you don't know that.

Assuming the cracker just uses a wordlist containing 200,000 terms and unsophisticated brute force, this thing could crack a 3 word password in a day and a 4 word password in 800 years[1]. It would certainly be an interesting project, but I honestly think this is a safe approach for now.

[1] http://www.wolframalpha.com/input/?i=%28200000**4+%2F+63+bil...


I know we've pretty much made our points by now, but my argument is that brute forcing at this level might be more feasible than what you suggest here (if we assume the sentence is correctly using a particular language).

Say we choose one word from the 200,000 and it's a noun. Then we can make assumptions about the next word (eg it's likely a verb) and immediately the number of options for the next word collapses from 200,000 to a subset of some smaller cardinality. In fact we can use our knowledge of common English to restrict the next options down further -- to only verbs that make sense to this particular noun and that agree with the noun's plurality.

So unlike current password brute forcing, where every character is independent of the others -- thus having exponential complexity -- brute forcing a sentence using current NLP methods could be much less expensive. Perhaps a hierarchical method exists that would scale at O(n log n).

Anyway, this is just fun thinking. You're right that current password strategies are a long way away from making this type of cracking worthwhile.


I agree that you could potentially reduce the search space based on rules, but English especially is not well known for it's adherence to rules, see http://en.wikipedia.org/wiki/Buffalo_buffalo_Buffalo_buffalo...

Conversations like this are why I come to hacker news.


I think most of the responses here regarding the crypto are missing the point. It doesn't matter if the key is not totally random. It just has to be good enough so that they can plausibly deny that they know anything about the file contents. It is their attempt to absolve themselves of responsibility for the copyright issues concerning the content. It is not about making your files more secure.


How is this new service supposed to be viable like the last MU? If the point of this "encryption" is supposed to provide plausible deniability, then the whole point of distributing warez via this site "legally" will have to be that the decryption keys are kept secret or underground.

But for this site to be popular enough to allow for downloads supported by ad revenue, then the file links and decryption keys will have to be widely distributed to drive traffic. If someone files a takedown notice with a file and decryption key that proves the data contained therein is copyrighted then won't MU be in the same boat they were in previously?


they could be doing something as crazy as putting the key in the "share this" URL. If they put it after the fragment then it doesn't get sent to the server and they can continue to deny having the ability to read file contents. Someone did a "Show HN" with a site that did something similar a month or two back.

Presumably mega then don't offer a site search but instead rely on google to index warez forums with links to the site that include the decryption key. I don't know.

Edit: found the site that did this: http://news.ycombinator.com/item?id=3852649


Yep, that was me. I strongly suspect that this may be what he is up to. It occurred to me at the time that there may be a way of doing it with files.

Ultimately I shut down the site as it got very little traction.


I don't think this encryption is supposed to provide plausible deniability in the most general sense. Stuff was DMCA'ed from megaupload all the time, but that was never a problem. There were many many many uploads of the same data and you could always find a working copy. There was a lot of friction because some people wanted all copies to be deleted, not just the link removed. This encryption allows for plausible deniability against deduplication. Mega can't possibly know what are all the copies of some content, so even if they comply with DMCA requests as before, nobody can force them to delete all provided copies.


Has to or wants to? Guido has chosen to focus on building an awesome language rather than maximising his personal wealth. Some people just like programming, and I'm sure he's extremely well compensated and does not have to work 9 - 5.


I'm currently finishing off a project that would have seriously benefited from html5 webcam support. The current state of things is really frustrating, in the latest chrome and firefox you can access a webcam and take pictures, but it's not possible to actually do anything with the video stream, you can't broadcast it to the server without horrible (and slow) hacks, so it's really crippled. That's the frustrating thing about html5 generally at the moment, it's eventually going to be awesome, but you can't actually use a lot of it yet.


This should hopefully change as WebRTC gets more fleshed out support. It's something I aim to try and tackle in my own webcam library (that was posted here a short while ago), but yeah. Finding an efficient way to even send a single frame is a bit awkward, and there's more than one way to do it.


As much as I am excited to see such hacks, a lot of the HTML5 goodness is just reinventing what Macromedia Flash did 5 years ago. The page turn JS, the audio recording JS, webcam js, etc have all been possible before with Flash quite easily in 10 or 15 lines. Not to mention it has been more reliable (no audio sync issues, no video drivers issues, etc) and it works with 99.3% [1] of the browsers in the market instead of just a few.

Proprietary or not but Flash still fills this need better than anything out there and it is sad to see that the so called better alternative is still in such a dismal shape (even in the latest release version of browsers).

[1] http://www.adobe.com/products/player_census/flashplayer/


I think the point is that the web platform should be able to do all these things natively.

Right now, the implementations aren't perfect - and cross-browser support is definitely lacking. But ultimately, I think it's hard to argue that the end goal of having this stuff baked in to HTML and JS is better than relying on a proprietary 3rd-party plugin.


Yes, I had to use flash, but of course that means I can't broadcast from mobile devices.


only if the cost of supporting <noscript> is less than the benefit, which for a lot of sites it probably isn't. The people who turn off javascript are in the extreme minority


that's "only" $18mm a year, so yes and a whole lot more


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: