Read the parent again - he's using the terms correctly. It doesn't need full merging, as the chances of two people working on it at the same time are low - just as long as they're working on the same copy, it's fine.
Though if google spreadsheet had versioning that'd be pretty cool.
They have their own box; why wouldn't they just throw in a h264 decoder chip and get massively reduced bandwidth costs? The only real reason to use MPEG-[12] these days is for backwards compatibility, or dealing with slow software decoders. People can be retrained for the new tech easily enough.
Post DHT hashes on usenet. Find peers using kademlia. It's impossible for users of the DHT to filter effectively, so they should (IANAL) not be held liable for distributing peer info (unlike tpb, they don't get the metadata, just the infohash - so they don't know whether a given file is legit or copyright infringement).
Framing will of course need to be used regain sync. If the encryption operates in CBC mode, then any error will cause only the next block to be damaged, providing outer framing protocols handle resyncing. After that, it's up to MPEG (or whatever) error recovery to minimize the screen corruption. Once the next B frame comes (no more than a few seconds or so, or seeking will be nigh-impossible) the compression context will be reset, and playback can resume normally. All without compromising that so-very-vital DRM:p
The vast majority of sites, I'm afraid, require a host header - that's how shared hosting works. Maybe this'll change when ipv6 rolls around, but for now, that trick only works if you add it to/etc/hosts.
However, fusion reactor technology is not useful in creating a bomb (except the fuel, I suppose). Additionally, in order to build a H-homb, you first need to build a fission bomb to trigger it.
If you mess with the UI, the elements the theme used to control may no longer exist, or the theme may fail to apply to all the needed elements. Thus, it's sensible to break themes over UI changes, to ensure someone will go in and check that the theme still works properly.
Better, use a private key, but don't indicate which in the message.
The recipient tries every key they have; if you don't have the private key in the message any test is inconclusive.
Just because a copy may remain does not mean it's easy to find. Google's Bigtable technology might retain deleted data for days, but finding the data could be nearly impossible.
What makes you think they index deleted emails? Most likely they're just floating about with a bunch of ad-hoc indices for cleanup purposes, and purged on an arbitrary schedule.
Google's bigtable presentation gives some clues onto this. Bigtable purges deleted information in a batch manner, not as the delete requests are given. It seems they'd need such a CYOA term to use such a system.
As an odd suggestion: why not build all your code into objects and distribute those with a little script to link them on the client machine into an executable. That would fix the problem right?
Nope. If it was that simple, it'd just work anyway. Problem is, if structures in header files or whatever change, then the old object files are no longer compatible with the new library, and a recompile is needed.
As I understand it, it's basically that if the program has a feature which causes it to dump its source, you can't disable or remove that feature without getting approval from everyone who touched the code since it was added.
What makes you think the email is kept forever? Just because they can't go and scrub the emails from all their backup tapes instantly doesn't mean they keep them in a vault forever to use against you.
Slashdot Mirror
Read the parent again - he's using the terms correctly. It doesn't need full merging, as the chances of two people working on it at the same time are low - just as long as they're working on the same copy, it's fine.
Though if google spreadsheet had versioning that'd be pretty cool.
They have their own box; why wouldn't they just throw in a h264 decoder chip and get massively reduced bandwidth costs? The only real reason to use MPEG-[12] these days is for backwards compatibility, or dealing with slow software decoders. People can be retrained for the new tech easily enough.
Post DHT hashes on usenet. Find peers using kademlia. It's impossible for users of the DHT to filter effectively, so they should (IANAL) not be held liable for distributing peer info (unlike tpb, they don't get the metadata, just the infohash - so they don't know whether a given file is legit or copyright infringement).
You're probably right - I'm just vaguely remembering avidemux status displays for the B frame terminology...
10G is a hell of a lot more than two movies if you use a decent codec.
Framing will of course need to be used regain sync. If the encryption operates in CBC mode, then any error will cause only the next block to be damaged, providing outer framing protocols handle resyncing. After that, it's up to MPEG (or whatever) error recovery to minimize the screen corruption. Once the next B frame comes (no more than a few seconds or so, or seeking will be nigh-impossible) the compression context will be reset, and playback can resume normally. All without compromising that so-very-vital DRM :p
The vast majority of sites, I'm afraid, require a host header - that's how shared hosting works. Maybe this'll change when ipv6 rolls around, but for now, that trick only works if you add it to /etc/hosts.
Would you mind clarifying the Lawrence J. Fogel bit? A google for him doesn't explain what you're referring to here, alas.
However, fusion reactor technology is not useful in creating a bomb (except the fuel, I suppose). Additionally, in order to build a H-homb, you first need to build a fission bomb to trigger it.
Sign-ups are quite slow, but after that it seems to mostly work okay. I've heard invitation and reminder emails are having problems, though.
Which book is this? I'm not finding it on amazon or google books; what is the ISBN?
If you mess with the UI, the elements the theme used to control may no longer exist, or the theme may fail to apply to all the needed elements. Thus, it's sensible to break themes over UI changes, to ensure someone will go in and check that the theme still works properly.
Better, use a private key, but don't indicate which in the message. The recipient tries every key they have; if you don't have the private key in the message any test is inconclusive.
SSL is available if you go directly to https://mail.google.com. Of course, emails to or from non-gmail users aren't encrypted over SMTP.
Just because a copy may remain does not mean it's easy to find. Google's Bigtable technology might retain deleted data for days, but finding the data could be nearly impossible.
What makes you think they index deleted emails? Most likely they're just floating about with a bunch of ad-hoc indices for cleanup purposes, and purged on an arbitrary schedule.
Google's bigtable presentation gives some clues onto this. Bigtable purges deleted information in a batch manner, not as the delete requests are given. It seems they'd need such a CYOA term to use such a system.
Obviously, just rip the files off the CD again to some lossless format. Voila, unlimited copies.
Nope. If it was that simple, it'd just work anyway. Problem is, if structures in header files or whatever change, then the old object files are no longer compatible with the new library, and a recompile is needed.
As I understand it, it's basically that if the program has a feature which causes it to dump its source, you can't disable or remove that feature without getting approval from everyone who touched the code since it was added.
There's a library class for accessing ZIP/JAR files. All in all it sounds rather simple.
Why keep it, is the real question. If news of that kind of thing leaked, it would destroy their reputation. the rick would be far too high.
What makes you think the email is kept forever? Just because they can't go and scrub the emails from all their backup tapes instantly doesn't mean they keep them in a vault forever to use against you.
Don't essentially all ACID-compliant databases do this?
Note, however, the defense is not allowed to inform the jury of this right.