jbri

36 ms·

331.
by jbri 16y ago
I would actually lean the other way. If your system is far more secure than another identical system, people are less likely to bother targeting your application when they break open the other one much more easily. It's only when you bring
332.
by jbri 16y ago
And then all the people who pirated your app deride it as "buggy" and you lose your paying customers, because who would buy such a buggy piece of crap?
333.
by jbri 16y ago
The challenge then is to write a script that automates the cracking.
334.
by jbri 16y ago
Yes, but the attacker can not get the browser to silently fetch the page (regardless of whether Javascript is disabled) just by sticking, say, an <img> tag somewhere.
335.
by jbri 16y ago
Are you suggesting that the health risks of asbestos were known when it started to become widely used? If not, you missed the point of my comment.
336.
by jbri 16y ago
The lack of understanding about possible adverse effects of asbestos worries me... Oh wait, it is actually pretty nasty stuff. Now, while the "20 years down the road" thing is a bit silly, a lack of understanding about potential adverse e
337.
by jbri 16y ago
Nanoscale silicon material with desireable physical properties? Sounds a little asbestosy to me.
338.
by jbri 16y ago
What is a company going to do if you break an NDA? Call out a hit squad? Break your kneecaps? Oh, that's right, they'll get the government to step in. With regards to your second issue, you're making the classic mistake of conflating a user
339.
by jbri 16y ago
Private individuals and businesses cannot do anything to prevent free speech. At best, they can petition the government to do so on their behalf. Hence the first amendment issue.
340.
by jbri 16y ago
In fact, once the 486 hit, 0x90 was an explicit NOP (1 cycle instead of the 3 that an XCHG usually takes, won't stall the pipeline even if other stuff touches AX, etc.). Similarly, on x64 0x90 is a true no-op, while stuff like XCHG EBX, EBX
341.
by jbri 16y ago
Right. Because the current price they're charging is going to be all that they're ever going to charge until the patents expire. Or, you know, what's actually going to happen is the price being kept low until H.264 is well-entrenched, and t
342.
by jbri 16y ago
Dropping Flash for video playback would be nice, yes. But making the shift from plugin-based playback to HTML5 video is an opportunity . And it's really the only chance that the web as a whole is going to get - if Flash video dies and H.26
343.
by jbri 16y ago
Right. Because end users are the only people who matter, and it's not like the MPEG-LA could start charging ridiculous fees to anyone who, I don't know, wants to build a decoder from source or something. Oh wait...
344.
by jbri 16y ago
You know, Flash. A browser plugin that allows execution of SWF objects. Which is an open, non-patent-encumbered format.
345.
by jbri 16y ago
Do you feel that WebM is patent encumbered? Can you point to any pre-existing patents that you feel it is covered by?
346.
by jbri 16y ago
In a similar vein, anyone who cares about being build their own encoder or decoder for web video (or even just anyone who wants to compile from source their own build of a codec) is happy about having an unencumbered web video format instea
347.
by jbri 16y ago
Yes, good design is more than visual aesthetics. But you seem to be saying that the aesthetics are then not important, which is completely false. If it looks terrible, it's a bad design. Period. At best, top-notch effort in other areas can
348.
by jbri 16y ago
Totally! I mean, it's not like you can offer people the svelte, clean, fancy option and fall back to HTML POST if that doesn't work or anything. Nosirree.
349.
by jbri 16y ago
The problem isn't the buffer being full, it's a problem with the buffer being <em>large and full</em>. Buffering less and just dropping packets when your smaller buffer fills (or even before then) lets the congestion control
350.
by jbri 16y ago
Best case would be your router/modem dropping/ECNing packets to keep below that cap, which would fix the "multiple computers" issue. You've still got the problem of buffering in your ISP's network screwing you up if it can't handle the rate
351.
by jbri 16y ago
This could work ... if you only have one machine on your local network and your outbound link can sustain that data rate 24/7. It's not really a practical solution for 99% of cases.
352.
by jbri 16y ago
Not at all. Transistor density keeps marching on - it's clock rates that have stagnated, and they did so quite a while ago. So we're getting more and more transistors on a chip, but it's prohibitively expensive in terms of power consumpti
353.
by jbri 16y ago
Should the people who's work you "built upon" get to decide what you do with your own work too?
354.
by jbri 16y ago
This is primarily about what's known as "first-sale doctrine". Basically, if the copyright owner gives you a legitimate copy of a work, you are free to pass on or resell that particular copy without needing to ask permission from the copyri
355.
by jbri 16y ago
Not anything significant, I don't think. This particular case says nothing about technological protection measures, which is the real issue with regards to resale.
356.
by jbri 16y ago
Keep in mind that content isn't created in a vacuum, and any content that an artist creates draws significantly from prior works.
357.
by jbri 16y ago
It seems that, once again, the best position is somewhere in the middle, rather than on either extreme.
358.
by jbri 16y ago
We can get some idea by looking at the vast body of works created when copyright was significantly limited compared to today. While there may be a handful of "artists" who wouldn't end up creating works if they could only profit from them
359.
by jbri 16y ago
Actually, unpublished works are still copyrighted. The issue here is that you have to show that you created the work if you want to make a copyright claim, which is difficult if the work is unpublished and not registered.
360.
by jbri 16y ago
This all sounds similar to the argument that Google should stick with search instead of moving into email. Or stick with Search + Email instead of moving into mobile devices.

More ›