Your symmetric cypher plan means that the FBI or similar could read all the criminal communications by catching one guy in the ring and offering him a plea bargain in exchange for the symmetric key.
Public / Private keys pretty much solve the problem of key exchange and make it easy for everyone in the ring to have their own key. If everyone has different keys, then compromising one guy in the ring only discloses messages sent to him.
Ok, the problem goes a little deeper than I originally pointed out. If we disregard the risk of method collision there are risks to extending an inappropriate class. Composition is a safer and more defensive strategy when you're using code under someone elses control, even if inheritance looks appropriate.
There are even examples of poor inheritance inside the java api - the java.util.Properties class extends Hashtable instead of containing one. As a result, it inherits get and put methods that let you insert any object to the underlying hashtable. Since Properties should only contain Strings this causes problems when you come to store the properties as a flat text file.
So, I think most people would agree:
Properties is a Hashtable.
but that isn't all of the story:
Properties is a Hashtable that should only contain String data.
In this case composition would have been a safer choice.
When you extend a class you don't control, you delegate control of the class contract. The superclass author can add methods like these that break your code in subtle and unexpected ways. Those methods will become part of your public API and you won't be able to get rid of them without breaking compatibility.
In the case of Properties, java still ships their broken design because there is a lot of code out there that uses the hashtable get and put methods directly.
That's actually a good thing, inheriting from classes you don't maintain is a risky business.
If you subclass and add methods in your class there is nothing to stop the original class adding new identically named methods in a subsequent release.
It is generally much better to favour composition over inheritance unless a class specifically documents that it is intended to be subclassed - eg/ abstract classes.
Bitpass have a payment card system, people with visa or paypal can buy (currently virtual) top-up cards, similar to those used for pay-as-you-go mobile phones.
Each card has a unique number on it. You enter the top-up card number on the site and the money is credited to your account. The first person to enter the number gets the money, once entered the card/number is useless.
Parents could buy a 3 dollar card for junior and leave him surfing bitpass porn until his money ran out.
Ximian's artists work full time and contribute to a lot of projects outside Ximian Desktop, including doing a lot of work for the core gnome project. It's rare to see a major gnome project that doesn't credit jimmac or tigert.
Pretty much all the stock gnome 2 icons were produced by Ximian - so gnome's default good looks are down to them.
Ximian are a major Gnome community player and are pushing it fast in the right direction. Red Hat are doing the same. For Gnome development to carry on at the current rate we should wish both companies success with their plans.
Still, I think the article calculated that Google would make $350,000,000 a year, so they'd be able to afford a refresh every month even without a some kind of built in discount deal. There would likely be some kind of special deal for spiders.
I guess they'd have to think about costs vs income, but so do the rest of us:)
Come on, whatever far, far away galaxy you live in, you'll have to admit there is a massive contrast between "The Empire Strikes Back" and the by the book kiddy movies you're talking about.
Empire is dark! The rebels get their asses kicked repeatedly, Luke gets his hand cut off and discovers Vader is his father and Han gets frozen. SW was cheesy fun. ROTJ was an ewok merchandising exercise. Empire kicked ass.
If a $25 million bounty was placed on the head of any foreign leader to declare war on the states, then it wouldn't take long for someone close tot hem to turn traitor. I'd imagine you can burn through that kind of money in a few hours of tomahawk bombing.
I'm actually surprised that this hasn't been tried. If the bounty isn't collected then there's nothing to lose. +++++
So, to conclude - there is no extra security risk from running X apps remotely. The programs are still running on the remote machine, they're just displaying on your local X server.
Unless the X client - server communication is encrypted (maybe tunnelled through ssh?) there is an additional security risk. All user input on the server machine has to be transmitted to the client and this most likely includes keypresses and mouse events in a sniffable format.
All input to an xterm X-client could be sniffed, including passwords to ssh accounts, su passwords etc. This would be bad.
Ximian packaged Nautilus has the spinner replaced with a glowing blue radar-gem.
Now the services are dead, there is no eazel branding in gnome at all.
Also; since there is no longer a branding motivation the name of nautilus (at least in the desktop) can be changed to something more appropriate. Making the confusing cognitive leap from a deep-sea crustacean to file management serves no longer purpose.
I really don't think there is anything nasty going on. I'm installing Ximian 1.4 on RH6.2 with KDE 2.1.1 and it hasn't asked me to remove any KDE packages.
I suspect the package removals in your case followed a Red-Carpet style verification of your rpm database. Maybe one of the packages kde depends on had to be replaced or had installed badly and the rest followed it because of the dependency removal.
What was the point of releasing that beta channel?
All the packages were beta 1 -- a week later beta 2 was out for testing. Red Carpet didn't supply the upgraded packages.
I'm stuck running the beta 1 packages til ximian wrap up 1.4 - it's been out for a week and I'm still running unstable packages from a month ago! +++++
Slashdot Mirror
Your symmetric cypher plan means that the FBI or similar could read all the criminal communications by catching one guy in the ring and offering him a plea bargain in exchange for the symmetric key.
Public / Private keys pretty much solve the problem of key exchange and make it easy for everyone in the ring to have their own key. If everyone has different keys, then compromising one guy in the ring only discloses messages sent to him.
Ok, the problem goes a little deeper than I originally pointed out. If we disregard the risk of method collision there are risks to extending an inappropriate class. Composition is a safer and more defensive strategy when you're using code under someone elses control, even if inheritance looks appropriate.
There are even examples of poor inheritance inside the java api - the java.util.Properties class extends Hashtable instead of containing one. As a result, it inherits get and put methods that let you insert any object to the underlying hashtable. Since Properties should only contain Strings this causes problems when you come to store the properties as a flat text file.
So, I think most people would agree:
but that isn't all of the story:
In this case composition would have been a safer choice.
When you extend a class you don't control, you delegate control of the class contract. The superclass author can add methods like these that break your code in subtle and unexpected ways. Those methods will become part of your public API and you won't be able to get rid of them without breaking compatibility.
In the case of Properties, java still ships their broken design because there is a lot of code out there that uses the hashtable get and put methods directly.
That's actually a good thing, inheriting from classes you don't maintain is a risky business.
If you subclass and add methods in your class there is nothing to stop the original class adding new identically named methods in a subsequent release.
It is generally much better to favour composition over inheritance unless a class specifically documents that it is intended to be subclassed - eg/ abstract classes.
What if the development time for the application is halved and the barrier for entry for new developers is greatly lowered?
If performance is good enough using a high level language there is no reason to waste limited resources coding at a lower level.
Bitpass have a payment card system, people with visa or paypal can buy (currently virtual) top-up cards, similar to those used for pay-as-you-go mobile phones.
Each card has a unique number on it. You enter the top-up card number on the site and the money is credited to your account. The first person to enter the number gets the money, once entered the card/number is useless.
Parents could buy a 3 dollar card for junior and leave him surfing bitpass porn until his money ran out.
Ximian's artists work full time and contribute to a lot of projects outside Ximian Desktop, including doing a lot of work for the core gnome project. It's rare to see a major gnome project that doesn't credit jimmac or tigert.
Pretty much all the stock gnome 2 icons were produced by Ximian - so gnome's default good looks are down to them.
Ximian are a major Gnome community player and are pushing it fast in the right direction. Red Hat are doing the same. For Gnome development to carry on at the current rate we should wish both companies success with their plans.
There's no point trying to poke technical holes in something that doesn't exist yet!
Besides, if the spider deal was done with domain lookup your spoofing script wouldn't work.
If they can get away with it they'll probably cut prices and steal dial-up users.
If they don't, their competition will.
Domain access actually seems a lot more reasonable.
It would encourages people to get paid for providing a services over pages and that's what this is all about really.
That's the best point I've seen so far :)
:)
Still, I think the article calculated that Google would make $350,000,000 a year, so they'd be able to afford a refresh every month even without a some kind of built in discount deal. There would likely be some kind of special deal for spiders.
I guess they'd have to think about costs vs income, but so do the rest of us
Nobody mentioned credit card payments for each page!
Payments would probably be aggregated and traded between ISPs and hosting services -- you'd only pay 2c extra on your monthly bill.
In addition, paid for web content would mean more content, which would mean more subscribers and cheaper broadband fees.
Read the article!
The whole point of "penny a page" is that every page costs the same flat rate.
Without everyone participating it would be a micro-payment system, which has different pros and cons.
If you got paid for hosting the content you'd be able to afford better bandwidth or some kind of akamai system.
Come on, whatever far, far away galaxy you live in, you'll have to admit there is a massive contrast between "The Empire Strikes Back" and the by the book kiddy movies you're talking about.
Empire is dark! The rebels get their asses kicked repeatedly, Luke gets his hand cut off and discovers Vader is his father and Han gets frozen. SW was cheesy fun. ROTJ was an ewok merchandising exercise. Empire kicked ass.
You're wasting keystrokes. You can shave 0.3 seconds from your development cycle with echo ;)
+++++
How about a government sanctioned form of Assassination Politics?
If a $25 million bounty was placed on the head of any foreign leader to declare war on the states, then it wouldn't take long for someone close tot hem to turn traitor. I'd imagine you can burn through that kind of money in a few hours of tomahawk bombing.
I'm actually surprised that this hasn't been tried. If the bounty isn't collected then there's nothing to lose.
+++++
So, to conclude - there is no extra security risk from running X apps remotely. The programs are still running on the remote machine, they're just displaying on your local X server.
Unless the X client - server communication is encrypted (maybe tunnelled through ssh?) there is an additional security risk. All user input on the server machine has to be transmitted to the client and this most likely includes keypresses and mouse events in a sniffable format.
All input to an xterm X-client could be sniffed, including passwords to ssh accounts, su passwords etc. This would be bad.
+++++
head != boobs
+++++
Ximian packaged Nautilus has the spinner replaced with a glowing blue radar-gem.
;)
Now the services are dead, there is no eazel branding in gnome at all.
Also; since there is no longer a branding motivation the name of nautilus (at least in the desktop) can be changed to something more appropriate. Making the confusing cognitive leap from a deep-sea crustacean to file management serves no longer purpose.
Even the Mac's "chooser" makes more sense
+++++
Your competitors are trying to make profit from the same market as you are. That market is made up of a finite number of individuals or companies.
In short: if a competitor gets your customer's dollar then you don't.
+++++
After you get off the flight from tokyo?
+++++
I really don't think there is anything nasty going on. I'm installing Ximian 1.4 on RH6.2 with KDE 2.1.1 and it hasn't asked me to remove any KDE packages.
I suspect the package removals in your case followed a Red-Carpet style verification of your rpm database. Maybe one of the packages kde depends on had to be replaced or had installed badly and the rest followed it because of the dependency removal.
+++++
Photoshop has really great accelerators - it takes a while to use them, but I could do what you describe with:
;-)
ctl + (zoom in) (hold space anywhere and move the mouse to scroll window at all times - MUCH quicker than scrollbars.)
OR
z (zoom tool) and drag out a zoom marquee
THEN
m (marquee tool), ctl c (copy), ctl n (new doc - bash return for default settings), ctl v (paste).
There you go - 5 gestures, no menus
Because each gesture is a real world key press it works out 3 times as fast as casting a spell in black and white...
If you like keyboard shortcuts, photoshop is a dream to use.
+++++
What was the point of releasing that beta channel?
All the packages were beta 1 -- a week later beta 2 was out for testing. Red Carpet didn't supply the upgraded packages.
I'm stuck running the beta 1 packages til ximian wrap up 1.4 - it's been out for a week and I'm still running unstable packages from a month ago!
+++++
The old default gnome widget set was pretty bad. AFIAK it took most of it's uglier features from Motif.
You shouldn't really be crying over it though - you could always change it with gtk themes, see http://gtk.themes.org/
The default gtk theme is now much nicer. Radio buttons and check boxes are easier to use.
+++++