There are plenty of ways to save the movies to your hard drive. One way is to get it from your browser cache. There are other tricks, too.
Re:No Repeating Recordings? (i.e., TiVo Season Pas
on
Mac PVR Coming Soon
·
· Score: 2
If you had read the links, you'd know that this box uses an external service, titanTV, for scheduling. SO perhaps you could check out titanTV for more information about what can be done.
Well, it is USB, so it is not a card, which means it will work with iMacs, iBooks, PowerBooks that don't have capability to use cards. Other than that, probably not too much different, though I don't know card specs. It mostly just captures the video, converts to MPEG-1, and is controllable via software to some extent (to change the channel or input source, for example), apparently. I sure want to play with one...
Um, but the key used to sign the signature is known by the updater, which has the public key locally, and so the signature file would need to be used with a different key, which the client program would recognize as different. The whole point of PGP/GPG is that the key of the signer is known and trusted. If you could hack the client to recognize a different key, then that would be a problem. Otherwise, the only way would be to crack the GPG key... oops.
There was no such implication. As two others noted, I was implying -- nay, stating:-) -- that the Big Brother in the parody was a caricature of the specific Big Brother from the 1984 commercial.
No, there is no OSA Perl, on either Mac OS or Mac OS X. There once was an experiment years ago to have an OSA Perl on Mac OS, but it failed.
MacPerl allows access to the raw IAC API under Mac OS, including the OSA* and AEGizmos APIs, and can compile and execute raw AppleScript (or any installed OSA language, via the Mac::OSA or Mac::OSA::Simple module), but is not itself an OSA language. On Mac OS X, perl can call out to the osascript and osacompile command line tools... there's also CamelBones for doing Cocoa with Perl inside of ProjectBuilder, but it still isn't an OSA language.
I couldn't get a movie of mine to play under QuickTime 6 on Mac OS X with this codec, but it worked fine under Mac OS 9. I didn't spend much time trying to figure out why though.
I stopped running MSIE on Mac OS 9 because it kept corrupting my system Internet Preferences file. It would add crap into the file, crash, and corrupt the file, and I would lose all of my preferences. Yay!
I am a registered user of VISE, and use it for the MacPerl installers. It does not require you quit all applications. That is a preference the builder of the installer may choose. It certainly is not necessary to quit all running programs when installing Mac OS 9 software. Sorry, but the blame is not MindVision's, nor Apple's, unless there is something we don't know about Mac OS X itself that requires Microsoft to enable this feature, which is unlikely.
This does not mean UFS is more secure. Your example doesn't work anyway; I have a "private" directory on my Mac OS X web server, and Apache won't let me access it as "Private". Even if it did, you could use one of the *Match directives instead (which would be a pain, but thankfully, it's unnecessary).
I meant to respond earlier, but didn't get the chance. There are several ways to go about this. One is to the oft-mentioned CamelBones, which is in initial stages, but is a great start for Cocoa bindings. For Carbon, there is a vaporware project I've played with, a SWIG-based glue for Perl, Python, Tcl, Ruby, and maybe more, and more details of it will be forthcoming when it's ready.
Right now there is also the Carbon-based MacOSX::File, which offers much of the same functionality as the Mac::Files module included in MacPerl, and there is OSXMacPerl, a basic clone of the MacPerl module (DoAppleScript and more are provided).
And some day I would like to port the Mac:: modules to Carbon, if I get the tuits.
Chapman explained that, because of the Mac's age, some of the first viruses ever written were for a Mac and some writers still target the platform specifically.
There's even a release of the infamous Sub7 Trojan in Alpha development at the moment, he added.
It sounds to me like Symantec is developing the virus, or at least knows the people who are. If the former, they are criminals, if the latter, they are obligated to tell the appropriate legal authorities.
OK... so? That is just admitting that real-world experience is such that Mac viruses are less prevalent, which is what I said. Sure, market share is a big reason why. But the "experts" -- who exist in this story only to scare Mac users into buying their product -- said the opposite, that the risk for both platforms is the same. It's untrue, by any measure.
I am eagerly looking forward to Chimera being as good as (and in platform-specific ways, better than) Mozilla. I can't really use it for now unless it gets faster (my G3/500 box that runs Mac OS X can't handle it well, and my primary G4/667 box runs Mac OS for now), but someday I surely will have a fast enough Mac OS X box to use it, and it's the most promising browser I see today. All the good things about Mozilla and Mac OS X. I love Mozilla in theory, and it's my primary browser on the G4 box, but it has a lot of platform-specific problems. I just wish there were a "Chimera" for Mac OS, based on Carbon instead of Cocoa.
Of course. That's why the title has a question mark, the dept. line read "have-some-conspiracy-with-your-coffee", and the final sentence was "Who knows?" Those are strong hints that this is all just speculation.:-)
I did get it to save the password in the Keychain. But it would disappear after awhile.
I could not even get it to work with hardcoded username/password. AEServer kept dying and leaving zombies behind, and I think osascript was trying to talk to zombies, because I kept getting authentication denied errors, even with a hardcoded username/password.
My current method is to run a background AppleScript in my login session that dumps the data I need, once a minute, to a file in/tmp, and then my cron job reads from that data, instead of calling an AppleScript directly with osascript. This doesn't work for controlling anything, and it doesn't work for immediate access to data, but all I am doing with it is putting a "Now Playing" on my home page.
If I had the time, I would port the Mac:: perl modules, including Mac::AppleEvents and friends, to Mac OS X. Though, I am not sure if a program that executes raw Apple events has similar limitations to osascript; that is, I don't know whether these limitations are built in to osascript, or are built in to the AppleScript software. So that solution might not help me anyway. I still wish I had the time to do it, though.
Um... actually, this is making it more Unix-like (as if Unix can be made more Unix-like)... on Mac OS 9 I have no way to set up an ssh-agent (although NiftyTelnet does cache your ssh passphrase in memory, and MacSSH can cache it in the Keychain). On Linux, when I log in to my graphical UI, I set up one ssh-agent for all my terminals etc. to use. It's the same thing. ssh is made for this. All this does is make it so the ssh-agent is started automatically and your key is added to it automatically, by using the Keychain. Sure, the Keychain or SSH could have security flaws in them, but is that's the case, there are far bigger problems than merely this.
There are plenty of ways to save the movies to your hard drive. One way is to get it from your browser cache. There are other tricks, too.
If you had read the links, you'd know that this box uses an external service, titanTV, for scheduling. SO perhaps you could check out titanTV for more information about what can be done.
Well, it is USB, so it is not a card, which means it will work with iMacs, iBooks, PowerBooks that don't have capability to use cards. Other than that, probably not too much different, though I don't know card specs. It mostly just captures the video, converts to MPEG-1, and is controllable via software to some extent (to change the channel or input source, for example), apparently. I sure want to play with one ...
Um, but the key used to sign the signature is known by the updater, which has the public key locally, and so the signature file would need to be used with a different key, which the client program would recognize as different. The whole point of PGP/GPG is that the key of the signer is known and trusted. If you could hack the client to recognize a different key, then that would be a problem. Otherwise, the only way would be to crack the GPG key ... oops.
There was no such implication. As two others noted, I was implying -- nay, stating :-) -- that the Big Brother in the parody was a caricature of the specific Big Brother from the 1984 commercial.
No, there is no OSA Perl, on either Mac OS or Mac OS X. There once was an experiment years ago to have an OSA Perl on Mac OS, but it failed.
... there's also CamelBones for doing Cocoa with Perl inside of ProjectBuilder, but it still isn't an OSA language.
MacPerl allows access to the raw IAC API under Mac OS, including the OSA* and AEGizmos APIs, and can compile and execute raw AppleScript (or any installed OSA language, via the Mac::OSA or Mac::OSA::Simple module), but is not itself an OSA language. On Mac OS X, perl can call out to the osascript and osacompile command line tools
I couldn't get a movie of mine to play under QuickTime 6 on Mac OS X with this codec, but it worked fine under Mac OS 9. I didn't spend much time trying to figure out why though.
I stopped running MSIE on Mac OS 9 because it kept corrupting my system Internet Preferences file. It would add crap into the file, crash, and corrupt the file, and I would lose all of my preferences. Yay!
I am a registered user of VISE, and use it for the MacPerl installers. It does not require you quit all applications. That is a preference the builder of the installer may choose. It certainly is not necessary to quit all running programs when installing Mac OS 9 software. Sorry, but the blame is not MindVision's, nor Apple's, unless there is something we don't know about Mac OS X itself that requires Microsoft to enable this feature, which is unlikely.
Jeez, and now I see they put an installer log file in my document root!
Is there no end to the madness?
They changed my browser preferences, without asking me, back to MSIE as my default browser. Jerkfaces.
MSIE 5.2 won't install without quitting my running apps.
So, it won't be installed for some time.
Maybe Microsoft is just jealous, wants to bring everyone else down to its OS level.
This does not mean UFS is more secure. Your example doesn't work anyway; I have a "private" directory on my Mac OS X web server, and Apache won't let me access it as "Private". Even if it did, you could use one of the *Match directives instead (which would be a pain, but thankfully, it's unnecessary).
I meant to respond earlier, but didn't get the chance. There are several ways to go about this. One is to the oft-mentioned CamelBones, which is in initial stages, but is a great start for Cocoa bindings. For Carbon, there is a vaporware project I've played with, a SWIG-based glue for Perl, Python, Tcl, Ruby, and maybe more, and more details of it will be forthcoming when it's ready.
Right now there is also the Carbon-based MacOSX::File, which offers much of the same functionality as the Mac::Files module included in MacPerl, and there is OSXMacPerl, a basic clone of the MacPerl module (DoAppleScript and more are provided).
And some day I would like to port the Mac:: modules to Carbon, if I get the tuits.
No. MP3 is for "MPEG Layer 3", not "MPEG-3".
I wrote ".0" in the context of "Perl 5". The meaning was clear, no matter how you read it. You're being overly pedantic and hypercritical.
Actually, you're only half-right. There is no OS/X or OSX, but there also is no OS X. It's Mac OS X.
:-)
If you're gonna be a pedant, at least be unassailably correct.
Chapman explained that, because of the Mac's age, some of the first viruses ever written were for a Mac and some writers still target the platform specifically.
There's even a release of the infamous Sub7 Trojan in Alpha development at the moment, he added.
It sounds to me like Symantec is developing the virus, or at least knows the people who are. If the former, they are criminals, if the latter, they are obligated to tell the appropriate legal authorities.
OK ... so? That is just admitting that real-world experience is such that Mac viruses are less prevalent, which is what I said. Sure, market share is a big reason why. But the "experts" -- who exist in this story only to scare Mac users into buying their product -- said the opposite, that the risk for both platforms is the same. It's untrue, by any measure.
I am eagerly looking forward to Chimera being as good as (and in platform-specific ways, better than) Mozilla. I can't really use it for now unless it gets faster (my G3/500 box that runs Mac OS X can't handle it well, and my primary G4/667 box runs Mac OS for now), but someday I surely will have a fast enough Mac OS X box to use it, and it's the most promising browser I see today. All the good things about Mozilla and Mac OS X. I love Mozilla in theory, and it's my primary browser on the G4 box, but it has a lot of platform-specific problems. I just wish there were a "Chimera" for Mac OS, based on Carbon instead of Cocoa.
Of course. That's why the title has a question mark, the dept. line read "have-some-conspiracy-with-your-coffee", and the final sentence was "Who knows?" Those are strong hints that this is all just speculation. :-)
My current method is to run a background AppleScript in my login session that dumps the data I need, once a minute, to a file in /tmp, and then my cron job reads from that data, instead of calling an AppleScript directly with osascript. This doesn't work for controlling anything, and it doesn't work for immediate access to data, but all I am doing with it is putting a "Now Playing" on my home page.
If I had the time, I would port the Mac:: perl modules, including Mac::AppleEvents and friends, to Mac OS X. Though, I am not sure if a program that executes raw Apple events has similar limitations to osascript; that is, I don't know whether these limitations are built in to osascript, or are built in to the AppleScript software. So that solution might not help me anyway. I still wish I had the time to do it, though.
Um ... actually, this is making it more Unix-like (as if Unix can be made more Unix-like) ... on Mac OS 9 I have no way to set up an ssh-agent (although NiftyTelnet does cache your ssh passphrase in memory, and MacSSH can cache it in the Keychain). On Linux, when I log in to my graphical UI, I set up one ssh-agent for all my terminals etc. to use. It's the same thing. ssh is made for this. All this does is make it so the ssh-agent is started automatically and your key is added to it automatically, by using the Keychain. Sure, the Keychain or SSH could have security flaws in them, but is that's the case, there are far bigger problems than merely this.
Damian is usually joking, about something. :-)
He said "this article," not "an article much like this one" or somesuch. So, he was wrong. *shrug*