News for hackers. Stuff that matters.
[dead]
Re:How I cracked NQ Vault's “encryption” by jxcl on Friday April 03, 2015 @01:18PM (#9317114)
People are downvoting you, but I totally agree. Stop requiring javascript to let me read text: literally the first thing ever put on the world wide web. Fancy your page up with javascript if you must, but let me choose to consume the text how I want.
Re:How I cracked NQ Vault's “encryption” by jasonlotito on Friday April 03, 2015 @01:47PM (#9317271)
> People are downvoting you, but I totally agree.

Since you are new here, I'll explain why I and others most likely have downvoted his comment, and why it's acceptable to do so, regardless of whether I agree with the sentiment or not: it's off-topic, and adds nothing to the discussion in the linked to article. Most importantly, it's essentially complaining that the content is inappropriate.

Re:How I cracked NQ Vault's “encryption” by tomjen3 on Friday April 03, 2015 @02:32PM (#9317538)
I can sorta agree with the both of you, but this is really off topic.
Re:How I cracked NQ Vault's “encryption” by MasterXen on Friday April 03, 2015 @01:05PM (#9317012)
Re:How I cracked NQ Vault's “encryption” by bshimmin on Friday April 03, 2015 @01:17PM (#9317102)
Or slightly nicer to read: https://github.com/ninjadoge24/ninjadoge24.github.io/blob/ma...

I have no idea why the blog is fetching a Markdown file via JavaScript from GitHub and then using JavaScript to render it... but at least you get the nice "doge" if you don't have JavaScript enabled.

Re:How I cracked NQ Vault's “encryption” by cbd1984 on Friday April 03, 2015 @06:23PM (#9318953)
> I have no idea why the blog is fetching a Markdown file via JavaScript from GitHub and then using JavaScript to render it...

I can guess: Make pushing changes out to the blog one step (upload fixed Markdown) instead of two (compile Markdown to HTML, push fixed HTML).

It's not the smartest thing in the world to do, but it's comprehensible.

Re:How I cracked NQ Vault's “encryption” by gohrt on Friday April 03, 2015 @01:05PM (#9317014)
[deleted]
Re:How I cracked NQ Vault's “encryption” by task_queue on Friday April 03, 2015 @01:27PM (#9317168)
The publishing platform and hopefully the author should care.
[deleted]
Re:How I cracked NQ Vault's “encryption” by task_queue on Friday April 03, 2015 @02:19PM (#9317465)
I beg to differ. A vocal minority of users who are aware of the JS dependency speak up for the unknown subset of users who can't read the page due to an error and don't care enough to investigate.

If a page starts to lag when I'm scrolling on a phone, it isn't worth the CPU cycles, battery life or my frustration to continue using it.

Re:How I cracked NQ Vault's “encryption” by thoughtpalette on Friday April 03, 2015 @02:57PM (#9317697)
Deleted as the comments are off-topic. You didn't address my points regardless. I do agree with you on your last sentence completely though.
Re:How I cracked NQ Vault's “encryption” by task_queue on Friday April 03, 2015 @04:04PM (#9318095)
True, it isn't a publishing platform. I assumed it was blog platform du jour. I missed your last point, for that I apologize.
Re:How I cracked NQ Vault's “encryption” by sp332 on Friday April 03, 2015 @01:07PM (#9317031)
It doesn't even load anything from another domain, so what's the problem with it? That link says that it's "dead to history" which has nothing to do with reading it right now.

Edit: "curlable" https://github.com/ninjadoge24/ninjadoge24.github.io/archive...

Re:How I cracked NQ Vault's “encryption” by theandrewbailey on Friday April 03, 2015 @01:17PM (#9317104)
The link you gave requires knowledge of the Github API. The original HN link does not give useful page content when cURL'd, and is the same stuff seen when you view source in any browser:

  > curl https://ninjadoge24.github.io/#002-how-i-cracked-nq-vaults-encryption

  <!DOCTYPE html>
  <html>
  <head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <meta name="google-site-verification" content="-YcMCt3q4z8rSKghGahhaHxy8W-gHY5339-YUMfSlHA" />

    <title>ninjadoge24's blog</title>

    <link rel="shortcut icon" type="image/ico" href="favicon.ico">
    <link rel="stylesheet" type="text/css" href="assets/css/lib/pure-min.css">
    <link rel="stylesheet" type="text/css" href="assets/css/style.css">
  </head>
  <body>
    <a href="#"><header title="ninjadoge24"></header></a>
    <small class="info"></small>
    <article></article>

    <script type="text/javascript" src="assets/js/lib/jquery-min.js"></script>
    <script type="text/javascript" src="assets/js/lib/markdown-min.js"></script>
    <script type="text/javascript" src="posts/index.js"></script>
    <script type="text/javascript" src="assets/js/script.js"></script>

    <script>
        (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
        (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
        m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
        })(window,document,'script','//www.google-analytics.com/analytics.js','ga');

        ga('create', 'UA-55807298-1', 'auto');
        ga('send', 'pageview');
    </script>
  </body>
  </html>
Re:How I cracked NQ Vault's “encryption” by diminoten on Friday April 03, 2015 @01:12PM (#9317070)
From a decision standpoint, wouldn't sites that require JS to render content be more important to read now, while they're correctly rendering? It's transient information that may not exist tomorrow -- why would you choose to not read it?

Because presumably you're "NR" as a method of punishing the author of the page, but surely you can't think this act is in any way consequential.

Re:How I cracked NQ Vault's “encryption” by sp332 on Friday April 03, 2015 @01:14PM (#9317087)
The author wants people to read the content, so refusing to read it is meaningful.
Re:How I cracked NQ Vault's “encryption” by diminoten on Friday April 03, 2015 @01:24PM (#9317147)
That puts too much emphasis on any individual reader.

I'd argue the author wants to get an idea out, and if one person does or does not read the article, the idea will still be propagated by/to others.

Re:How I cracked NQ Vault's “encryption” by djfm on Friday April 03, 2015 @03:00PM (#9317711)
Wouldn't say the original comment was so useless (even being from just one reader) after all: see the conversion thread it spawned!

That being said I don't care about this JS issue.

Re:How I cracked NQ Vault's “encryption” by emodendroket on Friday April 03, 2015 @01:35PM (#9317207)
Who even cares whether you read something or not. I don't.