Go buy a Nokia E-Series phone. You can have 3G, VoIP for free calls and, yes, you can run putty to ssh in to your computer and restart the webserver. I haven't used Windows Mobile, but I'd expect most of those handsets can do likewise. Be aware though that if you buy a network subsidized handset some or all features maybe disabled.
Why are you using a decade old phone and then complaining about other phones not having features that have been available on some handsets for at least 2 years?
Yes, but anytime anyone googles anything, google has to do processing.
I'd have thought they'd use a caching solution just like wikipedia. After all, just as Wikipedia has some very popular pages and some less so, Google has many popular searches and many less so. Wouldn't they cache these? After all if you're dealing with millions of searches for 'george carlin' you wouldn't want to go query your entire DB every time, would you?
Don't worry - this is just/. making sure the facts don't get in the way of a good scare story.
The actual law in Japan requires a waistline above the specified figures and a weight related ailment. See link and link
If someone is fighting fit and as a result has built body mass causing a larger waist, they're still not going to see any penalty unless they develop a weight related condition of some sort.
They explicitly don't do that, but the submitter ignored that for the sake of creating drama.
As others have said, the EULA basically says Novell claim copyright over the package of all these apps. You can go ahead and distribute the whole package, or modified versions of any OSS software included. If you modify anything, you need to remove Novell's branding. Just like CentOS has to remove all the RH branding from their distro.
As for the benchmarking clause. It applies only to software companies and their agents, and says you can't benchmark this without authorisation. If you do so, we have the right to benchmark any competing software made by yourselves. In otherwords, if RedHat had a no benchmark clause and benchmarked their SuSE v RedHat and published the results, by doing so they'd be giving Novell the right to carry out and publish its own benchmarks on RedHat
Actually you don't need a certificate signed by a CA for SMTP over TLS.
We have used a self signed certificate for years and hundreds of other MTAs connect to us and happily set up a encrypted session to transfer mail.
Of course this has issues, by making it harder for the other end to be sure we are who we say we are, but given the alternative is simply to failover and send unencrypted that's not really a major concern.
This is with Postfix. Do any of the other big MTAs actually look to check the certificate is trusted before sending an encrypted message with default TLS settings?
Any spot where I can travel at a dangerous enough speed (20mph) also has low pedestrian traffic.
Well no wonder. Who would want to walk on a sidewalk with bikes passing at 20mph.
A bike's place is on the road with the other vehicles. Those riding bikes should obey the rules of the road, as should those driving any motorised vehicle that wishes to pass them. Most of the rest of the world has managed this for decades.
Yes, The Register had a much more balanced article too: http://www.theregister.co.uk/2008/06/06/virgin_media_bpi_deal/.From that article, 'At this stage there will be no "three strikes" process; customers who continue to fileshare illegally will not be disconnected.'
Virgin are also quoted as saying it was unwilling to disconnect customers who don't stop accessing illegal music. A spokesman said: "It's a bit of a judgement call for us to be making threats of disconnection or account suspension. We weren't willing to do that. There are now so many lawful cheap and free music services out there that we believe an education campaign in partnership with the BPI is the best way forward."
Seems Virgin aren't quite being the bad guys the summary makes out.
A possible solution would be opportunistic encryption. It would allow some sites to serve encrypted traffic without changing anything at the apache/squid end of things. No change is needed at the browser level either, and cache's can still be used.
There's still a cpu overhead, but at least we don't lose all the other methods needed to keep http traffic flowing quickly.
The CPU requirements of serving large numbers of encrypted pages are massive in comparison to non encrypted pages.
You need to spend CPU cycles encrypting each page for each browser rather than just firing the same data in response to multiple requests,often from a cache.
To make matters worse, browsers for good reason won't cache data received over SSL, so each page view sees much more data having to be served.
Does it occur to you that the UI developers might not be the best set of folk to be fixing a proxy/dns resolution bug?
Not that I think the bug should take that long to squash, but it's a crap argument to say they shouldn't develop any other part of the application while they wait for it being fixed.
Older than that - it built on work by Alexander Bain who received a patent for "improvements in producing and regulating electric currents and improvements in timepieces and in electric printing and signal telegraphs" in 1843.
Or you could use something like a kurobox or hacked buffalo linkstation to serve webpages. Then you'd only be powering your router and a USB/network drive overnight.
In my opinion it would be unfeasible to maintain two sites, one for narrow band users and one for high speed users.
It might be extra work, might even be a pita, but 'unfeasible'? Most modern websites of any size separate content from presentation through some sort of content management system.
With a decent CMS it should be trivial to offer a 'light' version of your site - I think someone else mentioned the low graphics version of the BBC news site as an example.
It is possible that a lot of the content that is increasing page sizes are flash adverts - if I fire up internet explorer there seems to be an ever increasing number of these animated adverts (can folk actually read a web page with three animated adverts amongst the text?). I'd hazard a guess that the reason many sites don't offer light versions of their pages is the threat to revenue through decreased ad views and has very little to do with the complexity of serving up two variants of a website.
I certainly do - my first SSL cert from Thawte cost a fraction of the $900 an EV SSL certificate costs from them, and required utility bills, bank statements etc to verify my identity.
Identity can, and has, been validated in the same fashion as EV-SSL certificates for a fraction of the price in the past. If they wanted to establish identity they could, and for less than an EV-SSL cert costs at present.
I've used several of the super cheap providers in recent years and all have delivered pretty much instantly via email after the telephone verification.
In the past I've dealt with Verisign and Thawte in the days where they wanted to see bank statements and such like - certificates then could take days or weeks to arrive. These days I'd only expect that to be the case with EV-SSl certs.
I'm not clear what the issue the original poster is having. All the providers I've used in recent years have provided detailed instructions to make the certificate request. Assuming it's Apache or IIS, it seems hard to see what could go wrong?
Do they need a large number of certs quickly - then maybe a wildcard certificate or a root certificate (and spending $$$) is what they need.
There's not enough detail in the summary to define the question that needs answering.
It's horses for courses. If you're serving web pages and running database queries from a well tuned database, the Sun Niagara chips are fast and very well suited. They serve the pages a little slower, but can serve many more at a time.
If, on the other hand what you're doing is not easily threaded then IBM probably have the upper hand. Say you're doing some mathematical analysis, where you have to do everything in sequence. IBM's faster processor can complete each stage quicker, moving on to the next part and delivering the result faster than a chip with more threads but slower speed.
I have three DVD players at home, do they think I'm actually gonna dump them and go for Blue Ray and fork over $400 for another player?
I doubt Sony expect you to. However, once you have a BD player, are you going to buy a DVD or a BD of the latest movie. I'd hazard a guess that most folk would opt for the new technology.
I know I stopped buying VHS tapes as soon as I had a DVD player, even though I still owned a couple of VHS players and plenty of old tapes.
As others have commented, they need to get the player price down to encourage adoption, but I think that once the players are out there, the disc sales will quickly follow. Assuming they make a decent royalty off each disc, it may even be in their interest to subsidise the player cost to boost uptake.
make Google a bank there and users account holders (with a zero balance of course)
Crazy idea. They should make all the account holders with a balance like their gmail quota. That way, I could sit all day with online banking open watching my balance increase!
The number and availability of competitors is irrelevant. The iPod maintains circa 90% of the MP3 player market. That is almost certainly a monopoly.
Now there's nothing wrong with that in itself. Apple won that position. The trouble is, once you win yourself a monopoly in a market, you have to be very careful not to abuse that position to extend your reach into other markets. It sounds like this is exactly what Apple are trying here.
Slashdot Mirror
Go buy a Nokia E-Series phone. You can have 3G, VoIP for free calls and, yes, you can run putty to ssh in to your computer and restart the webserver. I haven't used Windows Mobile, but I'd expect most of those handsets can do likewise. Be aware though that if you buy a network subsidized handset some or all features maybe disabled.
Why are you using a decade old phone and then complaining about other phones not having features that have been available on some handsets for at least 2 years?
I'd have thought they'd use a caching solution just like wikipedia. After all, just as Wikipedia has some very popular pages and some less so, Google has many popular searches and many less so. Wouldn't they cache these? After all if you're dealing with millions of searches for 'george carlin' you wouldn't want to go query your entire DB every time, would you?
You'll notice I covered this when I said it's harder for the other end to be sure we are who we say we are.
However, as I also pointed out, in the absence of TLS, SMTP servers just failover and send in plain text. I know which one I'd rather have.
Don't worry - this is just /. making sure the facts don't get in the way of a good scare story.
The actual law in Japan requires a waistline above the specified figures and a weight related ailment. See link and link
If someone is fighting fit and as a result has built body mass causing a larger waist, they're still not going to see any penalty unless they develop a weight related condition of some sort.
They explicitly don't do that, but the submitter ignored that for the sake of creating drama.
As others have said, the EULA basically says Novell claim copyright over the package of all these apps. You can go ahead and distribute the whole package, or modified versions of any OSS software included. If you modify anything, you need to remove Novell's branding. Just like CentOS has to remove all the RH branding from their distro.
As for the benchmarking clause. It applies only to software companies and their agents, and says you can't benchmark this without authorisation. If you do so, we have the right to benchmark any competing software made by yourselves. In otherwords, if RedHat had a no benchmark clause and benchmarked their SuSE v RedHat and published the results, by doing so they'd be giving Novell the right to carry out and publish its own benchmarks on RedHat
Actually you don't need a certificate signed by a CA for SMTP over TLS.
We have used a self signed certificate for years and hundreds of other MTAs connect to us and happily set up a encrypted session to transfer mail.
Of course this has issues, by making it harder for the other end to be sure we are who we say we are, but given the alternative is simply to failover and send unencrypted that's not really a major concern.
This is with Postfix. Do any of the other big MTAs actually look to check the certificate is trusted before sending an encrypted message with default TLS settings?
You might want to read this from Microsoft. In particular, take a look at the setting for DefaultFileTypeRisk
Let me guess, you own a Motorola?
The UK has certainly forced those wrongly convicted to pay for their time inside as in the case of the Bridgewater Four: The Times and The Guardian
Well no wonder. Who would want to walk on a sidewalk with bikes passing at 20mph.
A bike's place is on the road with the other vehicles. Those riding bikes should obey the rules of the road, as should those driving any motorised vehicle that wishes to pass them. Most of the rest of the world has managed this for decades.
Yes, The Register had a much more balanced article too: http://www.theregister.co.uk/2008/06/06/virgin_media_bpi_deal/.From that article, 'At this stage there will be no "three strikes" process; customers who continue to fileshare illegally will not be disconnected.'
Virgin are also quoted as saying it was unwilling to disconnect customers who don't stop accessing illegal music. A spokesman said: "It's a bit of a judgement call for us to be making threats of disconnection or account suspension. We weren't willing to do that. There are now so many lawful cheap and free music services out there that we believe an education campaign in partnership with the BPI is the best way forward."
Seems Virgin aren't quite being the bad guys the summary makes out.
A possible solution would be opportunistic encryption. It would allow some sites to serve encrypted traffic without changing anything at the apache/squid end of things. No change is needed at the browser level either, and cache's can still be used.
There's still a cpu overhead, but at least we don't lose all the other methods needed to keep http traffic flowing quickly.
The CPU requirements of serving large numbers of encrypted pages are massive in comparison to non encrypted pages.
You need to spend CPU cycles encrypting each page for each browser rather than just firing the same data in response to multiple requests,often from a cache.
To make matters worse, browsers for good reason won't cache data received over SSL, so each page view sees much more data having to be served.
Does it occur to you that the UI developers might not be the best set of folk to be fixing a proxy/dns resolution bug?
Not that I think the bug should take that long to squash, but it's a crap argument to say they shouldn't develop any other part of the application while they wait for it being fixed.
Older than that - it built on work by Alexander Bain who received a patent for "improvements in producing and regulating electric currents and improvements in timepieces and in electric printing and signal telegraphs" in 1843.
Isn't that the whole point of these things? They use ePaper and reflect light.
Or you could use something like a kurobox or hacked buffalo linkstation to serve webpages. Then you'd only be powering your router and a USB/network drive overnight.
It might be extra work, might even be a pita, but 'unfeasible'? Most modern websites of any size separate content from presentation through some sort of content management system.
With a decent CMS it should be trivial to offer a 'light' version of your site - I think someone else mentioned the low graphics version of the BBC news site as an example.
It is possible that a lot of the content that is increasing page sizes are flash adverts - if I fire up internet explorer there seems to be an ever increasing number of these animated adverts (can folk actually read a web page with three animated adverts amongst the text?). I'd hazard a guess that the reason many sites don't offer light versions of their pages is the threat to revenue through decreased ad views and has very little to do with the complexity of serving up two variants of a website.
I certainly do - my first SSL cert from Thawte cost a fraction of the $900 an EV SSL certificate costs from them, and required utility bills, bank statements etc to verify my identity.
Identity can, and has, been validated in the same fashion as EV-SSL certificates for a fraction of the price in the past. If they wanted to establish identity they could, and for less than an EV-SSL cert costs at present.
I've used several of the super cheap providers in recent years and all have delivered pretty much instantly via email after the telephone verification.
In the past I've dealt with Verisign and Thawte in the days where they wanted to see bank statements and such like - certificates then could take days or weeks to arrive. These days I'd only expect that to be the case with EV-SSl certs.
I'm not clear what the issue the original poster is having. All the providers I've used in recent years have provided detailed instructions to make the certificate request. Assuming it's Apache or IIS, it seems hard to see what could go wrong?
Do they need a large number of certs quickly - then maybe a wildcard certificate or a root certificate (and spending $$$) is what they need.
There's not enough detail in the summary to define the question that needs answering.
I seem to remember quite adequately reading email and surfing the web on an Acorn RiscPC with a 33MHz ARM 610.
I'd suggest things could get more efficient still.
It's horses for courses. If you're serving web pages and running database queries from a well tuned database, the Sun Niagara chips are fast and very well suited. They serve the pages a little slower, but can serve many more at a time.
If, on the other hand what you're doing is not easily threaded then IBM probably have the upper hand. Say you're doing some mathematical analysis, where you have to do everything in sequence. IBM's faster processor can complete each stage quicker, moving on to the next part and delivering the result faster than a chip with more threads but slower speed.
I know I stopped buying VHS tapes as soon as I had a DVD player, even though I still owned a couple of VHS players and plenty of old tapes.
As others have commented, they need to get the player price down to encourage adoption, but I think that once the players are out there, the disc sales will quickly follow. Assuming they make a decent royalty off each disc, it may even be in their interest to subsidise the player cost to boost uptake.
The number and availability of competitors is irrelevant. The iPod maintains circa 90% of the MP3 player market. That is almost certainly a monopoly.
Now there's nothing wrong with that in itself. Apple won that position. The trouble is, once you win yourself a monopoly in a market, you have to be very careful not to abuse that position to extend your reach into other markets. It sounds like this is exactly what Apple are trying here.