Personally I would love it if every channel went the way of the 'premimums'. That is, you pay for it, and lose the ads.
There's oodles of benefits, just think about it
- the programming quality is usualy better
- its a much more direct 'vote-with-your-wallet' business model
- stations could focus more on their audience than bending to the advertisers presure to appeal to everyone (like get this, TechTV could actualy get... dare I say it... technical!
- The FCC pretty much sits on the sidelines
I have digital cable right now with something like 200 channels, but I've only tagged about 25 of them as my 'favorites' and those are the only ones I even flip through.
Yes but...people already know Flash, they've gotten years of practice and make lots of money off of it. Despite potentially better technology, will they switch from what is familiar?
You're mixing Flash with Flash. Macromedia makes that rather easy, what with the naming and all.
My point is, Flash the sort of vector-graphics-IDE is what people already know, and will stick with. However what Macromedia will do is give you the option to simply 'Save as' an SVG file. Old developers get to use interface they're used to, new developers get to use XSLT and every langauges XML abilities to dynamically generate the heck out of them.
Its a win-win situation for Macromedia and 'the rest of us'. The only threat is if Microsoft breaks's SVG the way they broke(with NS's willing help) HTML. By flooding the market with a crappy implimentation that allows for such god awful developer mistakes that people actually begin to believe its OK.
If Macromedia wants their Flash product to survive this, they need to get on SVG as soon as possible, so that by the time MS comes out with longhorn there's so much pre-existing material out there that very strictly conforms to the standard, that MS will have to at least start off adapting to fit in.
However, if the wireless network is left wide open without WEP enabled, it's potentially arguable that there's implicit permission to use the network
So if I leave the door to my back-deck open for my dog to come and go while I'm upstairs reading, am I giving you "implicit permission" to come in and quietly nick my DVD player?
Well this is open source, so what would it take to take CowboyNeal up on his offer and go nuts on slashcode?
I'm an xhtml 'pusher' (I won't say zealot) and would love to use this as an opportunity to turn my half dozen perl script experience into a genuine skill with the language. But there's no way I could just dive in. I need somebody to lead, give me a manageable piece, explain the perl bits that are beyond me, etc.
So how do we go about organizing a group of developers to web-standardize slashcode? Who's in!?
On the one hand stuff like this scare's the hell out of me, but on the other hand I'm very reasurred by how the debian community handles it. Full disclosure, detailed explanations, and very conservative thinking (exibited by the "3.0r2 is fine, but we're not releasing it anyway just to be anally sure").
At this point I would like to see the debian team develop some written policies and procedures for how they intend to prevent this sort of thing in the future. I checked the site and while there's security info for how to secure your box, there's no policies on 'how does the debian project secure itself'.
Lastly, one concept you have to keep in mind, we have no idea how often other OS's key servers are cracked because they'd never tell us.
One thing is for sure, if they could get the spim's out, they would work.
digging deep into my 14-year-old-loser-in-his-parents-basement history, I remember the days when you could run a "phish"ing program in AOL. It would scrape the screen names from a couple dozen chat rooms, and mass-IM them a message saying "AOL billing has lost your password, just reply with it or your account will be disabled". I know we're talking about aol-ers here, but those retards would reply about 1 in 50. Eventually AOL added little red text to the bottom of every IM saying "we will never ask you for your password" but even then it was still very effective to just IM about 2000 people. The thing is, it only took three people "reporting" you for your account to get disabled.
So AIM now seems to have this mostly under control with the rate-limiting. Getting people's IM names will happen much the same way emails are harvested, forums, personal web pages, etc.
Here's an annoying little brain teaser. Imagine every ISP had standardized on something like Jabber and we didn't have this proprietary mess we do now with AIM/MSN/Yahoo. How would we provent spim then? Wouldn't it be just as subject to being raped as SMTP?
Everything I've read says you get 1-year of up2date service with the purchase of AS, ES, or WS. However you also claim that each release will be supported for 5 years. How much are those other 4 years of up2date gonna cost me? Is there any way I could pay for just up2date on ES with no support whatsoever?
Stuff like this is good for us/.'ers once in awhile. It helps us snap out of the whole 'ibm-is-a-good-guy/on-our-side' romanticism. There are parts of IBM who's goals line up with ours very well, and there are parts that don't even come close. IBM is too big and diversified to have any sort of character assigned to it.
...to Acquire Leading Enterprise Linux Technology Company SUSE LINUX
Novell/SUSE LINUX to become the world's ...agreement with Novell/SUSE LINUX to support... ...expertise of SUSE LINUX and...
entered into an agreement to acquire SUSE LINUX
Linux is not a fuggin acronymn!!! I really gets on my nerves when I see it in straight-caps.
I didn't realize how cheap WS is. I was all set to give up on my RH after my trusty 7.3 w/up2date was end-of-lifed. But for $179 to get a distro with that much spit and polish.. I might just get it for my home gateway/webserver/etc box.
Netscap 4.x or lower make up less than 4% of web users. Its actually around 2% average, but opensource sites and academic sites (the two many of us deal with most) can get up to 4%.
In the case of that browser, you're way better off doing what espn.com or wired.com did, show them a "for the love of god upgrade your browser" page.
Y'know what would rock? If they didn't just give him some little background/cameo part, but if they took the video footage of him, edited it deftly to put him in the proper costume, and then just spliced him into some fight scene flailing about like a fattard.
Like the part where he trips and slams into the wall, I want that to be him giving a shoulder-but to some bad guy.
Slashdot Mirror
There's oodles of benefits, just think about it
- the programming quality is usualy better
- its a much more direct 'vote-with-your-wallet' business model
- stations could focus more on their audience than bending to the advertisers presure to appeal to everyone (like get this, TechTV could actualy get... dare I say it... technical!
- The FCC pretty much sits on the sidelines
I have digital cable right now with something like 200 channels, but I've only tagged about 25 of them as my 'favorites' and those are the only ones I even flip through.
You're mixing Flash with Flash. Macromedia makes that rather easy, what with the naming and all.
My point is, Flash the sort of vector-graphics-IDE is what people already know, and will stick with. However what Macromedia will do is give you the option to simply 'Save as' an SVG file. Old developers get to use interface they're used to, new developers get to use XSLT and every langauges XML abilities to dynamically generate the heck out of them.
Its a win-win situation for Macromedia and 'the rest of us'. The only threat is if Microsoft breaks's SVG the way they broke(with NS's willing help) HTML. By flooding the market with a crappy implimentation that allows for such god awful developer mistakes that people actually begin to believe its OK.
If Macromedia wants their Flash product to survive this, they need to get on SVG as soon as possible, so that by the time MS comes out with longhorn there's so much pre-existing material out there that very strictly conforms to the standard, that MS will have to at least start off adapting to fit in.
Actually I was thinking more along the lines of 'Karma whoring'.
da da, ding
I'd be curious to hear peoples experiences with OpenNMS compared to Nagios.
So if I leave the door to my back-deck open for my dog to come and go while I'm upstairs reading, am I giving you "implicit permission" to come in and quietly nick my DVD player?
I'm an xhtml 'pusher' (I won't say zealot) and would love to use this as an opportunity to turn my half dozen perl script experience into a genuine skill with the language. But there's no way I could just dive in. I need somebody to lead, give me a manageable piece, explain the perl bits that are beyond me, etc.
So how do we go about organizing a group of developers to web-standardize slashcode? Who's in!?
Huh? The Food and Drug Administration needs to approve pets?
At this point I would like to see the debian team develop some written policies and procedures for how they intend to prevent this sort of thing in the future. I checked the site and while there's security info for how to secure your box, there's no policies on 'how does the debian project secure itself'.
Lastly, one concept you have to keep in mind, we have no idea how often other OS's key servers are cracked because they'd never tell us.
This crap is lamer than ricers.
digging deep into my 14-year-old-loser-in-his-parents-basement history, I remember the days when you could run a "phish"ing program in AOL. It would scrape the screen names from a couple dozen chat rooms, and mass-IM them a message saying "AOL billing has lost your password, just reply with it or your account will be disabled". I know we're talking about aol-ers here, but those retards would reply about 1 in 50. Eventually AOL added little red text to the bottom of every IM saying "we will never ask you for your password" but even then it was still very effective to just IM about 2000 people. The thing is, it only took three people "reporting" you for your account to get disabled.
So AIM now seems to have this mostly under control with the rate-limiting. Getting people's IM names will happen much the same way emails are harvested, forums, personal web pages, etc.
Here's an annoying little brain teaser. Imagine every ISP had standardized on something like Jabber and we didn't have this proprietary mess we do now with AIM/MSN/Yahoo. How would we provent spim then? Wouldn't it be just as subject to being raped as SMTP?
Everything I've read says you get 1-year of up2date service with the purchase of AS, ES, or WS. However you also claim that each release will be supported for 5 years. How much are those other 4 years of up2date gonna cost me? Is there any way I could pay for just up2date on ES with no support whatsoever?
And then when it is, someone exploits a security vulnerability in it.
Stuff like this is good for us /.'ers once in awhile. It helps us snap out of the whole 'ibm-is-a-good-guy/on-our-side' romanticism. There are parts of IBM who's goals line up with ours very well, and there are parts that don't even come close. IBM is too big and diversified to have any sort of character assigned to it.
Novell/SUSE LINUX to become the world's
entered into an agreement to acquire SUSE LINUX
Linux is not a fuggin acronymn!!! I really gets on my nerves when I see it in straight-caps.
Thats some cart-before-horse logic there.
[cough]bullshit[/cough]
I didn't realize how cheap WS is. I was all set to give up on my RH after my trusty 7.3 w/up2date was end-of-lifed. But for $179 to get a distro with that much spit and polish.. I might just get it for my home gateway/webserver/etc box.
Of course this is another headache for admins still patching for last month's RPC flaw." Kudos to admin's still patching one month old holes.
Those who live in glass houses... http://validator.w3.org/check?uri=http%3A%2F%2Fwww .rmpmusic.com%2F
Y'ever played counterstrike, or for that matter dealt with Steam?
Good for them, it Validates, and looks a lot nicer. I'm glad to see they took the navigational links out of images, I hate that practice.
No that landed in the Yucatan Sand Trap. Made God miss par that round.
In the case of that browser, you're way better off doing what espn.com or wired.com did, show them a "for the love of god upgrade your browser" page.
I doesn't, but if you look closely you'll see that it comes extremely close. All but one of its errors are because it uses
instead of in its URLs.I forget exactly which, but some browsers don't interpret the &blah codes in URL's, so using them makes all links broken in the site.
Like the part where he trips and slams into the wall, I want that to be him giving a shoulder-but to some bad guy.