daeken

62 ms·

631.
by daeken 12y ago
From the guidelines: > Please don't submit comments complaining that a submission is inappropriate for the site. If you think something is spam or offtopic, flag it by going to its page and clicking on the "flag" link. (No
632.
by daeken 12y ago
> I'm all for faster rendering, but I wonder how well PDF.js protects against malicious content. It doesn't need to; that's what the browser is for. PDF.js doesn't need to -- in any way -- concern itself with securit
633.
by daeken 12y ago
Woah, I was designing a system just like this for the Vectrex a while back. Great execution on this project -- love to see clever hardware hacks.
634.
by daeken 13y ago
We tend to think of technology with the "a rising tide raises all boats" line of thinking, or at least I do. But this is a pretty clear case of technology dragging everyone down. Yes, it may be an equalizing force, but we don&#x
635.
by daeken 13y ago
That fretboard (well, 22-fret version) is going on a PRS-style single cut with no magnetic pickups, just a Graphtech Ghost wraparound piezo bridge. Cocobolo fretboard, sapelle body (I think), curly redwood top. Should be a nice one.
636.
by daeken 13y ago
The fret placement was, slightly surprisingly, the absolute easiest part of everything. 99% of my time was spent on the math for producing the base fretboard shape (the fingerboard() function in fret_worker.js if you're curious). Bet
637.
by daeken 13y ago
Also working on that! I've been playing 8- and 7-strings mainly, and everything out there sucks. Doubt I'll post it here, but if you follow me on twitter/github, you'll see it there. (daeken in both places)
638.
by daeken 13y ago
I'll see about throwing in some STL examples. As it stands, though, you can use the built-in viewer on the app with a (any?) WebGL browser. Edit: Here's a 24-fret board with the 'wave dots' inlay. Looks great in their
639.
by daeken 13y ago
This is a project I've been working on the past couple days. My goal is to CNC an entire guitar, and a big part of that is making a fretboard that doesn't suck. So I decided to make use of the CSG.js library ( https:/&#x2F
640.
Fret.js: Procedural Fretboard Generator(demoseen.com)
12 points by daeken 13y ago|10 comments
641.
by daeken 13y ago
I'm not surprised to see them in a compiler. When you're parsing and want to treat it as a big state machine, gotos are your best friend.
642.
by daeken 13y ago
Bear in mind, this is from a year ago, from early in its development. I'm not positive how much of this is inaccurate, but I know that omega-3 and other ingredients were added to round it out. I'd take this article with a grain o
643.
by daeken 13y ago
100% agreed. I had the pleasure of working with Andreas (and you, if you're the Fabrice D. I think you are) on the Boot2Gecko project, and he was a great project leader. He's technically adept, he knows how to work with people,
644.
by daeken 13y ago
> I also think the real name policy is one of those things that we give too much weight too in analyzing the service. Lacking pseudonyms is not the reason "average" people have not used it. I don't think that anyone will a
645.
by daeken 13y ago
From the technical side of things, where do you see the biggest challenges today? Where do you see the biggest potential wins? What are we not looking at deeply enough? This is a field that deeply interests me, but my knowledge is effecti
646.
by daeken 13y ago
While I personally agree with you that this particular story may not be HN-suitable, the rules are clear on this. 1) If you dislike a story, flag it and move on. Don't comment on its suitability. 2) Don't complain about downvot
647.
by daeken 13y ago
For the last 6 months or so, my life has been dominated by musical instruments, both playing them and modifying them. Ended up building a workshop for guitars because of it. Lately, I've been doing research into CNCing all the wooden
648.
by daeken 13y ago
https://gist.github.com/daeken/11123897 I pulled it out of an OCR'd PDF that someone linked from the forums.
649.
by daeken 13y ago
I discovered HN Special for Chrome a week or two ago, and I'll never go back. It adds every feature I've ever wanted (better, higher-contrast design; foldable comments; user info hovers, etc). https://chrome.google.com
650.
by daeken 13y ago
> As part of Heroku and our parent company Salesforce.com’s commitment to philanthropy, if you are interested in donating your bounty to a recognized charity we will match it dollar-for-dollar. Kudos to the Heroku folks for this. I have
651.
by daeken 13y ago
I don't see why not, especially because you already have the old key signature/fingerprint to use when pushing it into the Bloom filter. Seems like a perfect case for it, actually.
652.
by daeken 13y ago
My issue with the Cloudflare Challenge can be summed up in: no matter what the results are, it will give people a diminished impression of the bug's actual impact. I can't fathom any way in which the Cloudflare Challenge was bene
653.
by daeken 13y ago
Fair point -- you're right that it's extremely configuration dependent. For many (especially in the Apache realm) it's trivial and very likely; others (especially Nginx) it's quite a bit more work. But even if he was 1
654.
by daeken 13y ago
No, he didn't. He said that it's unlikely, and he's right. It's unlikely that I'm going to get heads 100 times in a row if I'm flipping a coin, but it suddenly becomes likely if I try it a couple million time
655.
by daeken 13y ago
I'm not disappointed by a fairly uneventful report, but quite honestly, I'm always a little bit worried when nothing horrible is discovered in the course of testing. It's not that I want there to be bugs, but that in a large
656.
by daeken 13y ago
For what it's worth, I think that the patch you guys threw out there (and have been using for a while) is a great idea, and I really hope it ends up in mainline OpenSSL. I think you guys have acted 100% properly from a tech perspectiv
657.
by daeken 13y ago
If the Heartbleed bug was still viable against your service, I'd say that he made the wrong call and should've emailed your team about it. But here, we're basically talking forensics. I've written at length about the de
658.
by daeken 13y ago
> I believe their actions are honest and completely reasonable. If they had known they still had an issue I seriously doubt they would have publicised the patch and risk the issue they now have. I completely agree that their actions are
659.
by daeken 13y ago
> If I have legitimate reason to believe that an exploit does not affect me (especially if it's because I acknowledged its possibility and programmed defensively against it), why would I automatically act as if I were breached too?
660.
by daeken 13y ago
When a company says "we're not changing our potentially compromised keys because we're protected by this magic box" and you punch a million holes in the magic box, your goal should be to make it well known that the prote

More ›