The realm, outbound proxy, a STUN server and/or NAT settings, DMTF protocol, the codec. Which are named different on the different softphones, and never located on the same page. And optionally the port, of course some umts providers block sip. Not to mention that several sip providers lock logins to their fixed ip.
SIP is really really great for us techies. But i'm pretty sure that at most 5% of my colleagues could configure a softphone.
I'm saying that a single proprietary network is technically better. It's just that the average person can't install or configure a sip softphone, while skype is accessible to the masses. How many people do you know, that take a laptop with a sip client with them on vacation? I know just one: myself. But I know several people who bring their laptop with skype.
That's exactly what makes skype so interesting. A lot of our customers live on other continents. Since they know how to install skype, it could save a lot of money if office users could skype through the pbx.
Okay, it's not really open source. But it does allow a whole range of new applications. For instance: sipskype bridges (for asterisk or any other pbx).
Because a truly foss voip project requires a server or open ports on at least 1 side. Skype requires only 2 clients that speak the same protocol, the skype network handles the rest.
Matt Mullenweg eloquently implored Wordpress bloggers to update more frequently.
If only Matt stopped breaking backwards compatibility, I would be up to date constantly. In the last few years I've seen several things breaking as matty decided to rename hooks and stuff. Therefore, all important functions of my sites must be checked before actually upgrading...
They really really need a new name. There's no way that thing is going to be marketed successfully. Not even if the software itself was able to power web4.0 apps, skipping web3.0 alltogether.
[q]using contact information from Whois records, sends him an email asking to confirm his ownership of the site.[/q] I've requested several SSL certificates over the years. Never ever have I received such an email to confirm ownership, nor was I pre-confirmed as the domains were registered elsewhere. Okay, so the CA was not netsol or thawte. But it sure was a CA that was acknowledged by both MSIE6/MSIE7/MSIE8/FF2/FF3
I don't see a reason why my CA wouldn't simply hand me a valid cert for paypal.com, no technical stuff, anyone can do this. Okay, my cert would probably be revoked as soon as someone finds out, but by then the damage could be millions...
But what about privacy? Internet-cafe's are required to make a copy of your passport when you're using their internet. How much will you be spied on when using the wifi service? I guess all packets are stored "against terrorism/child pornography/critisism on berlusconi". Guess the only way to be safe is to setup a vpn and redirect everything over it.
Bittorrent is quite a good protocol for this indeed, especially if you need the ability to 'resume' a down/upload. However, it's a complex protocol, if you don't know what you're doing, you could leak information I guess.
How about FTP with hash-checking. - step 1: uploader makes md5 sum - step 2: uploader uploads md5 sum to ftp server - step 3: uploader uploads the actual file to the server - step 4: a script checks the file to its sum. When done, tags it ok. When faulty, delete. How to make scripts run after upload? Well, just read: http://blog.derjohn.de/space/start/2006-11-14/1
Otherwise, you could consider writing your own software for this. A simple perl transfer script with hash checking shouldn't be too hard to write.
In my personal experience, I found mcafee asap (mcafeeasap.com) the easiest to use in such a small business. This software has "agents" which report their status back to the mcafeeasap.com website, from which the administrator can monitor all pcs.
This idea is great for small companies. The implementation however had a few problems: - Over time, I've installed all "agents" at least twice. They just stop working for no reason at random moments - Some agents 'do' have a reason to stop: they think the license has expired, while it's definitely not. - And mcafee is bloated + it uses mshtml for every single dialog and even for invisible actions like downloading updates. This eats cpu power.
I'm talking about home users, people that do not have a fulltime sysadmin. Millions of home users usually have a friendly neighbourhood kid that installed the pc, but doesn't support it after that.
Sure, for corporate sysadmins it would be very easy to keep a non-MS browser up-to-date. But those admins can install Firefox themselves and won't need a bundled firefox. It's the home user, the guy that does not know where to download a non-MS browser, who's at risk.
People that cannot manage their own updates should have computers that update all components installed in default installation, and especially any program that communicates with the outside world.
MSIE may stink and may be insecure. But still, it's a LOT more secure than any 2-year old firefox/opera/safari browser. On a lot of installations I've seen, Firefox hasn't been updating for years as the user doesn't have permission to install updates. MSIE is (by default) updated by windows update.
Therefore MSIE is a lot more secure to the average user. Hate to admit it, but when one of my family members wants a reinstall, they get MSIE.
About half a cycle is normal. This is the case in my company as well.
But here, we're speaking about 2 complete cycles. IE8 is (i'm sorry to say this as a Linux fan) a great browser. I haven't seen any instability so far, and I'm sure its stable enough for deployment in 99,9% of all companies.
The primary reason IE6 is still around, is that we do not care enough to kill it. Of course there are some corporations that refuse to upgrade their software. But in their refusal to upgrade, they make theirselves vulnerable to attacks. As sites still support IE6, home users have no reason to upgrade as well, making themselves vulnerable to attacks.
Botnets sending viruses and spam have a great benefit from this practice. Easily said:
These few companies are holding the whole internet hostage. For a few bucks saved in the company, millions of other users are at higher risk. I'd say lets all annoy the shit out of IE6 users until they upgrade.
I'm running a site that has a few thousand visitors daily. I've just implemented a oneliner that gives IE6 users a 600x100px red warning they should switch.
Congratulations! The following domains are available:
netw0rk-s0luti0ns-sucks-cock.com
[...]
Domain Names From $14.99:
netw0rk-s0luti0ns-blows-cock.com
netw0rk-s0luti0ns-sucks-dick.com
netw0rk-s0luti0ns-blows-dick.com
netw0rk-s0luti0ns-sux-cock.com
netw0rk-s0luti0ns-sux-dick.com
n3tw0rks0luti0nssuckscock.com
netw0rk-s0luti0ns-sucksballs-cock.com
well... if you insist:-)
unfortunately, the suggestions don't get registered when selected
Indeed, it is. After running Zoot (Redhat 6.2), I decided RH wasn't the distribution for me. I've run (and still are running) several other distributions after that, including Slackware 7-10, Debian Potato, SLES and OpenSuSE. Since the Novell-MS deal, I cannot trust SuSE enough, and I switched again... to CentOS. And now I'm considering the next servers to get a paid-for RedHat.
If it weren't for CentOS, i would not have bought anything from RH...
Slashdot Mirror
The realm, outbound proxy, a STUN server and/or NAT settings, DMTF protocol, the codec. Which are named different on the different softphones, and never located on the same page. And optionally the port, of course some umts providers block sip. Not to mention that several sip providers lock logins to their fixed ip.
SIP is really really great for us techies. But i'm pretty sure that at most 5% of my colleagues could configure a softphone.
I'm saying that a single proprietary network is technically better. It's just that the average person can't install or configure a sip softphone, while skype is accessible to the masses. How many people do you know, that take a laptop with a sip client with them on vacation? I know just one: myself. But I know several people who bring their laptop with skype.
That's exactly what makes skype so interesting. A lot of our customers live on other continents. Since they know how to install skype, it could save a lot of money if office users could skype through the pbx.
Okay, it's not really open source. But it does allow a whole range of new applications. For instance: sipskype bridges (for asterisk or any other pbx).
Because a truly foss voip project requires a server or open ports on at least 1 side.
Skype requires only 2 clients that speak the same protocol, the skype network handles the rest.
It's called a price tag.
The only problem with the price tag is that it stops working as soon as the price drops to a reasonable amount.
So, when do we expect a microsoft update to change te blocklist? Or will they simply rename their plugin+give it a new extension id?
Lying... but it works very well. They even got slashdot to mention their name. And remember: even bad publicity is good publicity.
Matt Mullenweg eloquently implored Wordpress bloggers to update more frequently.
If only Matt stopped breaking backwards compatibility, I would be up to date constantly. In the last few years I've seen several things breaking as matty decided to rename hooks and stuff. Therefore, all important functions of my sites must be checked before actually upgrading...
They really really need a new name. There's no way that thing is going to be marketed successfully. Not even if the software itself was able to power web4.0 apps, skipping web3.0 alltogether.
Ssssst. Don't tell them.
Less links = less income = earlier death for the dead-tree-media.
I prefer not to say, criminals are reading /. as well.
[q]using contact information from Whois records, sends him an email asking to confirm his ownership of the site.[/q]
I've requested several SSL certificates over the years. Never ever have I received such an email to confirm ownership, nor was I pre-confirmed as the domains were registered elsewhere. Okay, so the CA was not netsol or thawte. But it sure was a CA that was acknowledged by both MSIE6/MSIE7/MSIE8/FF2/FF3
I don't see a reason why my CA wouldn't simply hand me a valid cert for paypal.com, no technical stuff, anyone can do this. Okay, my cert would probably be revoked as soon as someone finds out, but by then the damage could be millions...
Make sure police officers in the rest of world get to know the site as well?
why is the windows 7 price in europe going to be 150% of the dollar-price in euro's (100 dollar -> 150 euro). That's twice what americans pay.
But what about privacy? Internet-cafe's are required to make a copy of your passport when you're using their internet. How much will you be spied on when using the wifi service? I guess all packets are stored "against terrorism/child pornography/critisism on berlusconi". Guess the only way to be safe is to setup a vpn and redirect everything over it.
Bittorrent is quite a good protocol for this indeed, especially if you need the ability to 'resume' a down/upload. However, it's a complex protocol, if you don't know what you're doing, you could leak information I guess.
How about FTP with hash-checking.
- step 1: uploader makes md5 sum
- step 2: uploader uploads md5 sum to ftp server
- step 3: uploader uploads the actual file to the server
- step 4: a script checks the file to its sum. When done, tags it ok. When faulty, delete.
How to make scripts run after upload? Well, just read: http://blog.derjohn.de/space/start/2006-11-14/1
Otherwise, you could consider writing your own software for this. A simple perl transfer script with hash checking shouldn't be too hard to write.
In my personal experience, I found mcafee asap (mcafeeasap.com) the easiest to use in such a small business. This software has "agents" which report their status back to the mcafeeasap.com website, from which the administrator can monitor all pcs.
This idea is great for small companies. The implementation however had a few problems:
- Over time, I've installed all "agents" at least twice. They just stop working for no reason at random moments
- Some agents 'do' have a reason to stop: they think the license has expired, while it's definitely not.
- And mcafee is bloated + it uses mshtml for every single dialog and even for invisible actions like downloading updates. This eats cpu power.
I'm talking about home users, people that do not have a fulltime sysadmin. Millions of home users usually have a friendly neighbourhood kid that installed the pc, but doesn't support it after that.
Sure, for corporate sysadmins it would be very easy to keep a non-MS browser up-to-date. But those admins can install Firefox themselves and won't need a bundled firefox. It's the home user, the guy that does not know where to download a non-MS browser, who's at risk.
People that cannot manage their own updates should have computers that update all components installed in default installation, and especially any program that communicates with the outside world.
MSIE may stink and may be insecure. But still, it's a LOT more secure than any 2-year old firefox/opera/safari browser. On a lot of installations I've seen, Firefox hasn't been updating for years as the user doesn't have permission to install updates. MSIE is (by default) updated by windows update.
Therefore MSIE is a lot more secure to the average user. Hate to admit it, but when one of my family members wants a reinstall, they get MSIE.
About half a cycle is normal. This is the case in my company as well. But here, we're speaking about 2 complete cycles. IE8 is (i'm sorry to say this as a Linux fan) a great browser. I haven't seen any instability so far, and I'm sure its stable enough for deployment in 99,9% of all companies.
The primary reason IE6 is still around, is that we do not care enough to kill it. Of course there are some corporations that refuse to upgrade their software. But in their refusal to upgrade, they make theirselves vulnerable to attacks. As sites still support IE6, home users have no reason to upgrade as well, making themselves vulnerable to attacks.
Botnets sending viruses and spam have a great benefit from this practice. Easily said: These few companies are holding the whole internet hostage. For a few bucks saved in the company, millions of other users are at higher risk. I'd say lets all annoy the shit out of IE6 users until they upgrade.
I'm running a site that has a few thousand visitors daily. I've just implemented a oneliner that gives IE6 users a 600x100px red warning they should switch.
Expecting fork in 3...2...1...
in a few years Google is buying Microsoft anyway.
unfortunately, the suggestions don't get registered when selected
Indeed, it is.
After running Zoot (Redhat 6.2), I decided RH wasn't the distribution for me. I've run (and still are running) several other distributions after that, including Slackware 7-10, Debian Potato, SLES and OpenSuSE. Since the Novell-MS deal, I cannot trust SuSE enough, and I switched again... to CentOS. And now I'm considering the next servers to get a paid-for RedHat.
If it weren't for CentOS, i would not have bought anything from RH...