yeh most people still use ie as thats what comes with the comp Until that changes you need to stay ie compatible Its a pain i know but the average internet user users ie If you run a "how to make money online" blog then you might get away with it as most webmasters use FF
I was thinking that, it would be nice. Live.com might hate me, but who cares I get like 20 visitors from them a day at most.
I wouldn't ban IE users, just detect them and put a Google Firefox referral button in their face and convert them
There are many issues which could affect a website’s rankings on search engines which could be out of the site owners control. Below are some of the issues: Issue 1 – Changing a Site’s IP Address: Moving a site to a new IP (either by switching in on the server, or physically moving the site to a new server with a new IP) would affect a site’s rankings. There would be a lag time between when the DNS change would be submitted and when it would take effect and filter down to individual DNS servers. The site owner (or webmaster) would process the DNS change with a name server, and the registration would likely change within 2-3 days. However, for this change to filter down to the root name servers could take days more. The structure of the internet is based upon a series of root name servers. There are 13 root name servers that provide name resolution for the internet. The DNS registration/update is applied and forwarded to these root servers who then process the information downwards. The speed of the update to the downstream servers depends on their local settings. Most are set to refresh every 15 minutes, but some can take days to do an update. When a client (or search engine, or search engine spider) requests a site, it first goes to its local DNS server to request the listing. If it’s own DNS server doesn’t have the site, it forwards the request to the next upstream server, and so on until the name is resolved to an IP. If the name is found and associated to an IP, the IP address is then forwarded to the client who goes to that address. The DNS server has no idea if the address is correct or not, it only has the information since its last refresh with its upstream server. If the IP isn’t correct, the client will get an error. Recommendation: To solve this problem, the ideal situation would be to have the site exist in both the old and new location for a period of 1 week. This would provide sufficient time for the main root servers and their subordinates to update and refresh their information. Since most clients pay for web hosting services on a month to month basis, and generally sign a contract for a year, it would be advisable to plan a move a few months in advance, and use the last month of the contract to host the site on two servers. If this wasn’t possible, we’d need to know when search engine spiders are most active and try to move the site when they aren’t active. This would lessen the impact of the move. We also feel that sites that have paid listings would be greatly impacted by a site move, as many premium listing guarantee a regular spider visit, usually every few days. They would follow the procedure outlined above, and would likely not find the old site (if it was moved completely and not maintained at the old IP Address). The site would then likely be dropped by engines, such as Yahoo, and the site owner would probably have to re register and pay the fee to get listed. Issue 2 – IP’s being banned by Engines: An issue which isn’t necessarily server related, but can be a cause for a site not being indexed is that they share an IP with a site that has been banned, or have inherited an IP from a banned site (see http://support.easystreet.com/abuse/banned_ip.html ). If an engine finds a site objectionable, or feel they were being spammed by a site/IP they will ban it from their index. If this is the case the site’s chances of being picked up by that engine are virtually nil. If this site moves on to a new IP address that hasn’t been banned then they will probably get indexed until the engines catch up to the new site IP and proceed to ban them again. In the mean time, the banned IP gets given to a new site. The new site has no idea the IP has been banned by the engines, but finds that they aren’t getting indexed. From the site owners perspective (and probably that of the webmaster) they don’t know that the IP has been banned and won’t know why they aren’t being indexed. Recommendation: If your site hasn’t been indexed within a reasonable timeframe, and you can’t think of a reason, you could check with the webmaster to see if you have an IP that we previously given to another site, and perhaps do some searches for the other site. If it looks like a spam site to you then it may have been banned on your IP earlier by the engines. Another alternative would be to just request a new IP. Keep in mind the lag time for the DNS updates to filter down, but this wouldn’t likely affect you as much if the site has been banned because of the IP.
Wow... you clearly didn't read the thread, but I believe I have found a fix. Here's the php code if anyone wants it: <?php if (eregi("MSIE",getenv("HTTP_USER_AGENT")) || eregi("Internet Explorer",getenv("HTTP_USER_AGENT"))) { echo 'This site only supports <a href="http://getfirefox.com">Firefox!</a>'; } else { echo ""; } ?> PHP: