<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;DkMERX07cCp7ImA9WxNUGEo.&quot;"><id>tag:blogger.com,1999:blog-24069595</id><updated>2009-11-10T09:33:24.308-08:00</updated><title>The Real Blogger Status</title><subtitle type="html">What Blogger won't tell you</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://blogging.nitecruzr.net/" /><link rel="hub" href="http://pubsubhubbub.appspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>992</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/Nitecruzr-Blogging" type="application/atom+xml" /><feedburner:emailServiceId>Nitecruzr-Blogging</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry gd:etag="W/&quot;Ck4ESHg8cCp7ImA9WxNUGE0.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-1008219927952302594</id><published>2009-11-09T08:50:00.000-08:00</published><updated>2009-11-09T13:08:29.678-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-09T13:08:29.678-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Custom Domains" /><category scheme="http://www.blogger.com/atom/ns#" term="Custom Domains Setup" /><category scheme="http://www.blogger.com/atom/ns#" term="Custom Domains Problems" /><title>Custom Domains And The Chair To Keyboard Interface</title><content type="html">A Google Custom Domain is an elegant solution for &lt;a href="http://blogging.nitecruzr.net/2009/04/so-why-are-custom-domains-setup-so.html"&gt;alternately addressing a blog with a BlogSpot or a non BlogSpot URL&lt;/a&gt;, and having the current search engine value of the BlogSpot URL transferred to the non BlogSpot URL.  There is no other DNS based solution for doing all of that, and doing that so elegantly.&lt;br /&gt;&lt;br /&gt;It's so simple to setup, too.&lt;ol&gt;&lt;li&gt;You start with &lt;a href="http://blogging.nitecruzr.net/2008/12/your-blog-custom-domains-and-righteous.html"&gt;a righteous DNS configuration&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;You &lt;a href="http://blogging.nitecruzr.net/2008/05/google-custom-domains-two-step-domain.html"&gt;publish the blog to the primary address&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;You &lt;a href="http://blogging.nitecruzr.net/2008/05/google-custom-domains-two-step-domain.html#DualAddresses"&gt;redirect the secondary address to the primary address&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;You are done with the setup.&lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;&lt;br /&gt;For all of it's simplicity, it has a major flaw in the way it's implemented.  This flaw, in Computer Security, I describe as a &lt;a href="http://networking.nitecruzr.net/2005/05/please-protect-yourself-layer-your.html#Layer4" target="_blank"&gt;Chair To Keyboard Interface Fault&lt;/a&gt;.  A CKI Fault is a frequent factor in computer security problems, and similarly, in &lt;a href="http://blogging.nitecruzr.net/search/label/Custom%20Domains%20Diagnoses%20Not%20Acceptable"&gt;custom domain problems&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Yet the bloggers, who generate the faults, are not the sole cause of the faults.&lt;br /&gt;&lt;br /&gt;Custom Domains depend upon DNS, and DNS is not a user friendly infrastructure.  DNS, or &lt;a href="http://en.wikipedia.org/wiki/Domain_Name_System" target="_blank"&gt;Domain Name System&lt;/a&gt;, is buried so deeply in the guts of the computer operating system, that very few bloggers know - or care - how it operates, or that it even exists.  Yet, what are they greeted with, when they decide to &lt;a href="http://blogging.nitecruzr.net/2008/12/your-blog-custom-domains-and-righteous.html"&gt;try publishing a blog to a non BlogSpot URL&lt;/a&gt;?&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;&lt;br /&gt;&lt;a name="SymmetricalDNS"&gt;&lt;/a&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Symmetrical DNS Configuration&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;The most obvious configuration uses &lt;a href="http://blogging.nitecruzr.net/2008/03/diagnosing-problems-with-custom-domains.html"&gt;a symmetrical DNS structure&lt;/a&gt; -  dual "CNAME" referrals.&lt;br /&gt;&lt;pre&gt;mydomain.com. 3600 IN CNAME ghs.google.com.&lt;br /&gt;www.mydomain.com. 3600 IN CNAME ghs.google.com.&lt;/pre&gt;&lt;br /&gt;This is the simplest to explain.  Both the domain root, and the "www" alias separately use a "CNAME" referral to "ghs.google.com", which provides a second referral to the current Google server that is available for use.&lt;br /&gt;&lt;br /&gt;With a symmetrical configuration, you may publish to either "mydomain.com" or "www.mydomain.com", at your convenience.&lt;br /&gt;&lt;a name="ASymmetricalDNS"&gt;&lt;/a&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Asymmetrical DNS Configuration, aka "Google Apps"&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;If you have a domain with email, FTP, and other possible auxiliary services, you use &lt;a href="http://blogging.nitecruzr.net/2008/03/diagnosing-problems-with-custom-domains_29.html"&gt;an asymmetrical structure&lt;/a&gt;, which &lt;a href="http://blogging.nitecruzr.net/2008/06/custom-domain-publishing-and-google.html"&gt;use Google Apps&lt;/a&gt; to let you add auxiliary services, with &lt;a href="http://blogging.nitecruzr.net/2009/09/your-blog-custom-domains-and-quadruplet.html"&gt;quadruple DNS server redundancy&lt;/a&gt;.&lt;br /&gt;&lt;pre&gt;mydomain.com.  3600 IN A 216.239.32.21&lt;br /&gt;mydomain.com.  3600 IN A 216.239.34.21&lt;br /&gt;mydomain.com.  3600 IN A 216.239.36.21&lt;br /&gt;mydomain.com.  3600 IN A 216.239.38.21&lt;br /&gt;www.mydomain.com. 3600 IN CNAME ghs.google.com.&lt;/pre&gt;&lt;br /&gt;Look &lt;span style="color:rgb(255,0,0); font-size:85%; font-weight:bold;"&gt;carefully&lt;/span&gt; at &lt;a href="http://blogging.nitecruzr.net/2009/09/your-blog-custom-domains-and-quadruplet.html"&gt;the IP addresses in the 4 "A" records&lt;/a&gt;, before concluding that the 4 records are identical.&lt;br /&gt;&lt;br /&gt;With an asymmetrical configuration, you may not publish to the domain root.  Your only valid choice is to publish to "www.mydomain.com", and select "Redirect mydomain.com to www.mydomain.com".  If you publish to "mydomain.com", you will eventually see&lt;blockquote&gt;&lt;span style="font-weight:bold;"&gt;Blogs may not be hosted at naked domains.&lt;/span&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;a name="VirtualHost"&gt;&lt;/a&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Additional Virtual Host&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;If you wish to add an additional blog to the domain, maybe to &lt;a href="http://blogging.nitecruzr.net/2007/06/adding-your-blogger-blog-to-your-non.html"&gt;add your Blogger blog to your web site&lt;/a&gt;, you setup an &lt;a href="http://blogging.nitecruzr.net/2009/10/your-blog-custom-domains-and-virtual.html"&gt;additional virtual host pair&lt;/a&gt;.  There are several variations on this setup - &lt;a href="http://blogging.nitecruzr.net/2008/12/one-blog-multiple-urls.html"&gt;some righteous, others spurious&lt;/a&gt; - that you need to consider, carefully.&lt;br /&gt;&lt;pre&gt;blog.mydomain.com. 3600 IN CNAME ghs.google.com.&lt;br /&gt;www.blog.mydomain.com. 3600 IN CNAME ghs.google.com.&lt;/pre&gt;&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Some DNS experts state that there are DNS oddities that not even DNS experts can understand.  And configuring DNS addresses just is not user friendly, &lt;a href="http://blogging.nitecruzr.net/2009/01/custom-domains-and-third-party.html"&gt;nor is it predictable&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;If I was to instruct someone&lt;blockquote&gt;Diagnose your domain setup.  Enter&lt;blockquote&gt;dig @localhost nitecruzr.net A&lt;br /&gt;dig @localhost www.nitecruzr.net A&lt;/blockquote&gt;into a command window.&lt;/blockquote&gt;For even those whose computers would run the "Dig" command, how many would be prepared for the output?&lt;br /&gt;&lt;pre&gt;&lt;br /&gt; ; &lt;&lt;&gt;&gt; DiG 9.3.2 &lt;&lt;&gt;&gt; @localhost nitecruzr.net A&lt;br /&gt; ; (2 servers found)&lt;br /&gt; ;; global options:  printcmd&lt;br /&gt; ;; Got answer:&lt;br /&gt; ;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 25181&lt;br /&gt; ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0&lt;br /&gt; &lt;br /&gt; ;; QUESTION SECTION:&lt;br /&gt; ;nitecruzr.net.   IN A&lt;br /&gt; &lt;br /&gt; ;; ANSWER SECTION:&lt;br /&gt; nitecruzr.net.  3600 IN A 216.239.32.21&lt;br /&gt; nitecruzr.net.  3600 IN A 216.239.34.21&lt;br /&gt; nitecruzr.net.  3600 IN A 216.239.36.21&lt;br /&gt; nitecruzr.net.  3600 IN A 216.239.38.21&lt;br /&gt; &lt;br /&gt; ;; Query time: 123 msec&lt;br /&gt; ;; SERVER: 127.0.0.1#53(127.0.0.1)&lt;br /&gt; ;; WHEN: Mon Nov  9 21:48:45 2009&lt;br /&gt; ;; MSG SIZE  rcvd: 95&lt;br /&gt;&lt;br /&gt; ; &lt;&lt;&gt;&gt; DiG 9.3.2 &lt;&lt;&gt;&gt; @localhost www.nitecruzr.net A&lt;br /&gt; ; (2 servers found)&lt;br /&gt; ;; global options:  printcmd&lt;br /&gt; ;; Got answer:&lt;br /&gt; ;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 23566&lt;br /&gt; ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0&lt;br /&gt; &lt;br /&gt; ;; QUESTION SECTION:&lt;br /&gt; ;www.nitecruzr.net.  IN A&lt;br /&gt; &lt;br /&gt; ;; ANSWER SECTION:&lt;br /&gt; www.nitecruzr.net. 3600 IN CNAME ghs.google.com.&lt;br /&gt; ghs.google.com.  380000 IN CNAME ghs.l.google.com.&lt;br /&gt; ghs.l.google.com. 300 IN A 74.125.43.121&lt;br /&gt; &lt;br /&gt; ;; Query time: 105 msec&lt;br /&gt; ;; SERVER: 127.0.0.1#53(127.0.0.1)&lt;br /&gt; ;; WHEN: Mon Nov  9 21:48:52 2009&lt;br /&gt; ;; MSG SIZE  rcvd: 99&lt;br /&gt;&lt;/pre&gt;&lt;br /&gt;Which I abbreviate as&lt;br /&gt;&lt;pre&gt;nitecruzr.net.  3600 IN A 216.239.32.21&lt;br /&gt;nitecruzr.net.  3600 IN A 216.239.34.21&lt;br /&gt;nitecruzr.net.  3600 IN A 216.239.36.21&lt;br /&gt;nitecruzr.net.  3600 IN A 216.239.38.21&lt;br /&gt;www.nitecruzr.net. 3600 IN CNAME ghs.google.com.&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;With all of these details in mind, is it surprising that we have users complaining of "&lt;a href="http://blogging.nitecruzr.net/2008/12/why-isnt-blogger-solving-another-blog.html"&gt;Another blog is already hosted at this address&lt;/a&gt;" and "&lt;a href="http://blogging.nitecruzr.net/2008/11/why-isnt-google-solving-server-not.html"&gt;Error 404 Server Not Found&lt;/a&gt;", with &lt;a href="http://blogging.nitecruzr.net/search/label/Custom%20Domains%20Diagnoses%20Not%20Acceptable?max-results=100"&gt;diagnosed causes of such intriguing variations&lt;/a&gt;?&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-1008219927952302594?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/1008219927952302594/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/11/custom-domains-and-chair-to-keyboard.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/1008219927952302594?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/1008219927952302594?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/U8dwS8RE7Qg/custom-domains-and-chair-to-keyboard.html" title="Custom Domains And The Chair To Keyboard Interface" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/11/custom-domains-and-chair-to-keyboard.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU8EQn8-fCp7ImA9WxNUF0Q.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-4074383095759675557</id><published>2009-11-07T10:27:00.000-08:00</published><updated>2009-11-09T11:10:03.154-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-09T11:10:03.154-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Network Problems" /><category scheme="http://www.blogger.com/atom/ns#" term="Diagnostic Technique" /><title>I Can't See My Blog - What Should I Do?</title><content type="html">This is a very difficult question to answer, because of its almost infinite complexity.&lt;ul&gt;&lt;li&gt;There are several different causes.&lt;/li&gt;&lt;li&gt;There are more symptoms than the number of causes.&lt;/li&gt;&lt;li&gt;There are still more ways that bloggers might report the symptoms that they see.&lt;/li&gt;&lt;li&gt;The reports, and the symptoms, will vary in both accuracy, detail, and relevance.&lt;/li&gt;&lt;li&gt;Different problems can be fixed only by people with different roles, relevant to the blog.&lt;ul&gt;&lt;li&gt;Some problems can be fixed only by the blogger (blog owner).&lt;/li&gt;&lt;li&gt;Others can be fixed  by the owners of the client computers or their network service providers.&lt;/li&gt;&lt;li&gt;Still others can only be fixed by Blogger Support or third party server owners.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li&gt;The epidemiology of the problems will produce different observations.&lt;ul&gt;&lt;li&gt;A few problems are occasionally observed by Blogger / Google staff.&lt;/li&gt;&lt;li&gt;Some problems will be observed by the blogger.&lt;/li&gt;&lt;li&gt;Others may be observed by the bloggers friends / blog readers.&lt;/li&gt;&lt;li&gt;A very few problems will be observed by everybody.&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;The term "blogger" can itself cause confusion - some bloggers might be the owners of the blogs, and others might be the viewers - and this, too, needs to be clarified.&lt;br /&gt;&lt;br /&gt;And let's also note the difference between "Blogger" and "BlogSpot".&lt;br /&gt;&lt;ul&gt;&lt;li&gt;The former is where you maintain your Blogger blog.&lt;/li&gt;&lt;li&gt;The latter is the native domain where you, by default, publish your Blogger blog.&lt;/li&gt;&lt;li&gt;If you're not publishing externally - either to a custom domain (on a Google server) or by FTP (to a third party server of your choice) - you'll be publishing to BlogSpot.&lt;/li&gt;&lt;li&gt;Many times, your specific problem might affect your access to one domain, but not the other.&lt;/li&gt;&lt;/ul&gt;I'm going to describe the complexity of this problem, enumerating by problem cause, to start.&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Blocked By ISP&lt;/li&gt;&lt;li&gt;Blocked By Network, or Local, Problem&lt;/li&gt;&lt;li&gt;Custom Domain Problem&lt;/li&gt;&lt;li&gt;Corrupted Content&lt;/li&gt;&lt;li&gt;Deleted Blog&lt;/li&gt;&lt;li&gt;Hijacked Blog&lt;/li&gt;&lt;li&gt;Login Problem&lt;/li&gt;&lt;li&gt;Lost Position In Search Engine Result Pages&lt;/li&gt;&lt;li&gt;Temporary / Transient Problems&lt;/li&gt;&lt;li&gt;Last Resorts&lt;/li&gt;&lt;/ol&gt;&lt;b&gt;Blocked By ISP&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Some ISPs, possibly motivated by political pressure, are blocking blog traffic, from time to time. You may see a variant of the well known&lt;br /&gt;&lt;br /&gt;   404 Server Not Found&lt;br /&gt;&lt;br /&gt;or just as likely, a completely white screen, with no error.&lt;br /&gt;&lt;br /&gt;You can frequently get around this problem, by using a proxy server.  Unfortunately, there is no guarantee that other readers of the blog will know to do that.  If your blog has significant reader population in the geographic regions affected, you're going to lose readership.&lt;br /&gt;&lt;br /&gt;&lt;a rel="nofollow" href="http://groups.google.com/group/blogger-help/web/use-a-proxy-server" target="_blank"&gt;http://groups.google.com/&lt;wbr&gt;group/blogger-help/web/use-a-&lt;wbr&gt;proxy-server&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This problem can only be fixed (worked around) by the blog readers, or the owners of the networks used by the blog readers.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Blocked By Network, or Local, Setting or Security Problem&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;There are settings and programs on your computer, and on your network, that will affect your ability (or your readers abilities) to access your blog, and other blogs.  Any of these individual items, or combinations of these items, can be relevant.&lt;br /&gt;&lt;br /&gt;* The DNS setting&lt;br /&gt;&lt;a rel="nofollow" href="http://groups.google.com/group/blogger-help/web/how-to-identify-a-dns-problem-on-your-computer" target="_blank"&gt;http://groups.google.com/&lt;wbr&gt;group/blogger-help/web/how-to-&lt;wbr&gt;identify-a-dns-problem-on-&lt;wbr&gt;your-computer&lt;/a&gt;&lt;br /&gt;* The MTU setting&lt;br /&gt;&lt;a rel="nofollow" href="http://groups.google.com/group/blogger-help/web/how-to-check-the-mtu-setting-on-your-computer" target="_blank"&gt;http://groups.google.com/&lt;wbr&gt;group/blogger-help/web/how-to-&lt;wbr&gt;check-the-mtu-setting-on-your-&lt;wbr&gt;computer&lt;/a&gt;&lt;br /&gt;* Local network or security problems&lt;br /&gt;&lt;a rel="nofollow" href="http://blogging.nitecruzr.net/2006/12/securing-your-browser-and-painting.html" target="_blank"&gt;http://blogging.nitecruzr.net/&lt;wbr&gt;2006/12/securing-your-browser-&lt;wbr&gt;and-painting.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Any of the above can cause the white screen as well.  Both DNS and MTU are settings on your computer, or on your network.  If there is a problem, the problem starts at the blogger computer, or with the Internet Service Provider.  As in the above scenario, you may be able to use a proxy server.&lt;br /&gt;&lt;br /&gt;&lt;a rel="nofollow" href="http://groups.google.com/group/blogger-help/web/use-a-proxy-server" target="_blank"&gt;http://groups.google.com/&lt;wbr&gt;group/blogger-help/web/use-a-&lt;wbr&gt;proxy-server&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Sometimes, Blogger Support will take responsibility for resolving the problem, but individual bloggers have to let them know that there is a problem.  If you are having a problem, and you don't report it, then it's partially your fault if the problem isn't fixed.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;This problem can likely be fixed by the blog readers, or the owners of the networks used by the blog readers, although occasionally Blogger Support will become involved to advise the network owners.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Custom Domain Problem&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Setting up a blog, published to a Google Custom Domain, demands precise attention to detail and procedure.  Sometimes, corruption in the Google server database will result in a well known error (which comes in several interesting flavours).&lt;br /&gt;&lt;br /&gt;   404 Not Found&lt;br /&gt;&lt;br /&gt;This problem you won't get around by using a proxy server, or by making any local or ISP changes.  You (the blog owner), or Blogger Support, will have to fix the problem.  Frequently, this will involve multiple procedures.&lt;br /&gt;&lt;br /&gt;* Post a question here.&lt;br /&gt;&lt;a rel="nofollow" href="http://www.google.com/support/forum/p/blogger/ask?hl=en" target="_blank"&gt;http://www.google.com/support/&lt;wbr&gt;forum/p/blogger/ask?hl=en&lt;/a&gt;&lt;br /&gt;* Republishing the blog back to BlogSpot, then repeating back to the custom domain.&lt;br /&gt;&lt;a rel="nofollow" href="http://blogging.nitecruzr.net/2007/11/custom-domain-publishing-and-404-error.html" target="_blank"&gt;http://blogging.nitecruzr.net/&lt;wbr&gt;2007/11/custom-domain-&lt;wbr&gt;publishing-and-404-error.html&lt;/a&gt;&lt;br /&gt;* Recycling the domain settings using Google Apps.&lt;br /&gt;&lt;a rel="nofollow" href="http://blogging.nitecruzr.net/2007/06/another-blog-is-already-hosted-at-this.html" target="_blank"&gt;http://blogging.nitecruzr.net/&lt;wbr&gt;2007/06/another-blog-is-&lt;wbr&gt;already-hosted-at-this.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Corrupted Content&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Part of the blog is gone. Maybe the header is there, but no post. Or the posts are there, but the sidebar is blank. Oh no! What do I do now? Well, in this scenario, you may be looking at another case of the old dropped post / sidebar. If it's not a simple case of the posts or the sidebar having dropped down the page, you may have a corrupt template, and reloading the template may resolve the problem.&lt;br /&gt;&lt;br /&gt;Here, too, you may see the well known error&lt;br /&gt;&lt;br /&gt;   404 Not Found&lt;br /&gt;&lt;br /&gt;This problem must be fixed by the blog owner.  Nobody else - neither Blogger Support, nor the blog readers - can fix corrupted content.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Deleted Blog&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;You made a mistake, and deleted your own blog, or maybe you or another administrator removed you from the permissions list. DOHH. Mistakes happen. Or the blog may have been removed by Blogger - for just cause - whether falsely or genuinely. Or, did you delete the blog intentionally, without considering the possible consequences?&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Hijacked Blog&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;The bad guys may have hijacked another blog.  What you're looking at may or may not contain your content.  You may or may not be able to access the dashboard, or the post editor, to correct the problem.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Login Problem&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;You're logged in with the wrong account, or not properly logged in. Or maybe you tried to change the account name, and simply setup a new account without realising it. Check and make sure that you don't have another account, that the blog is registered to. Find out what Blogger accounts are associated with your email address.&lt;br /&gt;&lt;br /&gt;* Blogger Help: &lt;i&gt;My blog disappeared from my account! What do I do?&lt;/i&gt;.&lt;br /&gt;&lt;a rel="nofollow" href="http://help.blogger.com/bin/answer.py?answer=41973" target="_blank"&gt;http://help.blogger.com/bin/&lt;wbr&gt;answer.py?answer=41973&lt;/a&gt;&lt;br /&gt;* Blogger Help: &lt;i&gt;I can't log in. What should I do?&lt;/i&gt;.&lt;br /&gt;&lt;a rel="nofollow" href="http://help.blogger.com/bin/answer.py?answer=41971" target="_blank"&gt;http://help.blogger.com/bin/&lt;wbr&gt;answer.py?answer=41971&lt;/a&gt;&lt;br /&gt;* Blogger Help Group: &lt;i&gt;Welcome to Login Issues!&lt;/i&gt;.&lt;br /&gt;&lt;a rel="nofollow" href="http://groups.google.com/group/blogger-help-loginissues/tree/browse_frm/thread/b188e22f091f0c62/18df9b57c7ccab41?rnum=1&amp;amp;_done=%2Fgroup%2Fblogger-help-loginissues%2Fbrowse_frm%2Fthread%2Fb188e22f091f0c62%2F%3F#doc_18df9b57c7ccab41" target="_blank"&gt;http://groups.google.com/&lt;wbr&gt;group/blogger-help-&lt;wbr&gt;loginissues/tree/browse_frm/&lt;wbr&gt;thread/b188e22f091f0c62/&lt;wbr&gt;18df9b57c7ccab41?rnum=1&amp;amp;_done=&lt;wbr&gt;%2Fgroup%2Fblogger-help-&lt;wbr&gt;loginissues%2Fbrowse_frm%&lt;wbr&gt;2Fthread%2Fb188e22f091f0c62%&lt;wbr&gt;2F%3F#doc_18df9b57c7ccab41&lt;/a&gt;&lt;br /&gt;* Google Accounts: &lt;i&gt;Google Accounts Help&lt;/i&gt;&lt;br /&gt;&lt;a rel="nofollow" href="https://www.google.com/support/accounts/" target="_blank"&gt;https://www.google.com/&lt;wbr&gt;support/accounts/&lt;/a&gt;&lt;br /&gt;* The Real Blogger Status: Schizophrenia When Logging In To Blogger&lt;br /&gt;&lt;a rel="nofollow" href="http://blogging.nitecruzr.net/2007/02/schizophrenia-when-logging-in-to.html" target="_blank"&gt;http://blogging.nitecruzr.net/&lt;wbr&gt;2007/02/schizophrenia-when-&lt;wbr&gt;logging-in-to.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;If you're certain that you made the right choice, but you got the wrong results, clear cache and cookies, and try again.&lt;br /&gt;&lt;br /&gt;&lt;a rel="nofollow" href="http://blogging.nitecruzr.net/2006/08/bypass-or-clear-your-local-cache.html" target="_blank"&gt;http://blogging.nitecruzr.net/&lt;wbr&gt;2006/08/bypass-or-clear-your-&lt;wbr&gt;local-cache.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Remember that part of the Blogger security strategy involves keeping the identity of the owner, of any blog, confidential. You don't want Blogger telling anybody who you are, so don't expect to email Blogger&lt;br /&gt;&lt;br /&gt;   I forgot the account (I changed my email address). What's my account?&lt;br /&gt;&lt;br /&gt;and get a useful reply. You will have to do some work, and authenticate yourself, somehow.&lt;br /&gt;&lt;br /&gt;&lt;a rel="nofollow" href="http://blogging.nitecruzr.net/2006/12/your-blog-is-forever.html" target="_blank"&gt;http://blogging.nitecruzr.net/&lt;wbr&gt;2006/12/your-blog-is-forever.&lt;wbr&gt;html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Lost Position In Search Engine Result Pages&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;There are many reasons why you won't be able to find your blog listed, in Google Search.  Some start with your needing to publicise the blog properly.&lt;br /&gt;&lt;br /&gt;&lt;a rel="nofollow" href="http://groups.google.com/group/blogger-help/web/how-to-get-traffic-and-repeated-readers-for-your-blog" target="_blank"&gt;http://groups.google.com/&lt;wbr&gt;group/blogger-help/web/how-to-&lt;wbr&gt;get-traffic-and-repeated-&lt;wbr&gt;readers-for-your-blog&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;But even when you do spend days publicising your blog, maybe somebody else spent more days, and his blog replaced yours in your desired search list position.  Now, you're just going to have to work harder.&lt;br /&gt;&lt;br /&gt;&lt;a rel="nofollow" href="http://groups.google.com/group/blogger-help/web/blogging-is-all-about-patience" target="_blank"&gt;http://groups.google.com/&lt;wbr&gt;group/blogger-help/web/&lt;wbr&gt;blogging-is-all-about-patience&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Temporary / Transient Problems&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Right now, bloggers are reporting problems with their blogs, with the well known&lt;br /&gt;&lt;br /&gt; Operation Aborted&lt;br /&gt;&lt;br /&gt;Blogger Support has to fix the problems causing this symptom.  While we await action by Blogger Support, we may have to help ourselves, using various workarounds.&lt;br /&gt;&lt;br /&gt;&lt;a rel="nofollow" href="http://blogging.nitecruzr.net/2009/05/internet-explorer-and-operation-aborted.html" target="_blank"&gt;http://blogging.nitecruzr.net/&lt;wbr&gt;2009/05/internet-explorer-and-&lt;wbr&gt;operation-aborted.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Other problems, too many (and too transient) to explicitly enumerate here, will come up from time to time.&lt;br /&gt;&lt;br /&gt;&lt;a rel="nofollow" href="http://blogging.nitecruzr.net/search/label/Current%20Problems?max-results=100" target="_blank"&gt;http://blogging.nitecruzr.net/&lt;wbr&gt;search/label/Current%&lt;wbr&gt;20Problems?max-results=100&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Last Resorts&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;If none of the above problem descriptions helps you decide how to attack your problem, and the blog really isn't accessible, act immediately.&lt;br /&gt;&lt;br /&gt;* Put a stub blog in place, if you can do so.&lt;br /&gt;&lt;a rel="nofollow" href="http://blogging.nitecruzr.net/2006/06/stub-post.html" target="_blank"&gt;http://blogging.nitecruzr.net/&lt;wbr&gt;2006/06/stub-post.html&lt;/a&gt;&lt;br /&gt;* Report the problem.&lt;br /&gt;&lt;a rel="nofollow" href="http://www.google.com/support/forum/p/blogger/ask?hl=en" target="_blank"&gt;http://www.google.com/support/&lt;wbr&gt;forum/p/blogger/ask?hl=en&lt;/a&gt;&lt;br /&gt;* And join the crowd, at Google Blogger Help.&lt;br /&gt;&lt;a rel="nofollow" href="http://www.google.com/support/forum/p/blogger?hl=en" target="_blank"&gt;http://www.google.com/support/&lt;wbr&gt;forum/p/blogger?hl=en&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-4074383095759675557?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/4074383095759675557/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/11/i-cant-see-my-blog-what-should-i-do.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/4074383095759675557?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/4074383095759675557?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/NP79qw_an8A/i-cant-see-my-blog-what-should-i-do.html" title="I Can't See My Blog - What Should I Do?" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/11/i-cant-see-my-blog-what-should-i-do.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0UDR3o5cSp7ImA9WxNUFk0.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-3701221153251441042</id><published>2009-11-07T07:05:00.000-08:00</published><updated>2009-11-07T07:54:36.429-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-07T07:54:36.429-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Following" /><category scheme="http://www.blogger.com/atom/ns#" term="Blog Feed" /><category scheme="http://www.blogger.com/atom/ns#" term="Newsfeeds" /><title>Who Are Your Anonymous Followers?</title><content type="html">Occasionally, we see queries from bloggers who are unsure what anonymous Followers are.&lt;blockquote&gt;How do I know when someone Follows my blog anonymously?&lt;/blockquote&gt;and&lt;blockquote&gt;How do I block anonymous Followers?&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;When someone Follows a blog publicly, he / she gets two things:&lt;ul&gt;&lt;li&gt;A subscription to the blog newsfeed, in the Following Reading List, and / or in Google Reader.&lt;/li&gt;&lt;li&gt;An entry in the Following community for the blog.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;When someone Follows a blog anonymously, she / he gets one thing:&lt;ul&gt;&lt;li&gt;A subscription to the blog newsfeed, in the Following Reading List, and / or in Google Reader.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;If you Block someone from Following your blog, you remove their entry from your Following community.  Newsfeed subscriptions, though, are universally open - if a feed is available to anybody, it's available to everybody.  Your anonymous Followers, as well as your Blocked Followers, can read your newsfeed - just as any reader who wishes to subscribe, without using Following.&lt;br /&gt;&lt;br /&gt;If the blog feed is &lt;a href="http://blogging.nitecruzr.net/2009/02/creating-custom-feed.html"&gt;routed through FeedBurner&lt;/a&gt;, anybody subscribing to the feed can be counted.  If you have &lt;a href="http://blogging.nitecruzr.net/2006/07/know-your-visitors.html"&gt;a visitor meter installed on the blog&lt;/a&gt;, anybody viewing the blog using a link from the blog feed (called "reach" in FeedBurner statistics) will be logged through the visitor meter.  Short of FeedBurner or a visitor meter, you won't know anything about anonymous Followers, or about Blocked Followers.&lt;br /&gt;&lt;br /&gt;A Blocked Follower appears in your Following community (in the "Blocked" list in your dashboard).  An anonymous Follower is simply anonymous, and appears nowhere.&lt;br /&gt;&lt;br /&gt;And, just as you can't track an anonymous Follower, &lt;a href="http://blogging.nitecruzr.net/2009/05/with-following-anonymous-followers-cant.html"&gt;you can't Block an anonymous Follower&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-3701221153251441042?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/3701221153251441042/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/11/who-are-your-anonymous-followers.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/3701221153251441042?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/3701221153251441042?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/wr4TzFoX5Jc/who-are-your-anonymous-followers.html" title="Who Are Your Anonymous Followers?" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/11/who-are-your-anonymous-followers.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0QGRHg-eyp7ImA9WxNUFU4.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-4530618067180280569</id><published>2009-11-06T09:49:00.000-08:00</published><updated>2009-11-06T10:15:25.653-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-06T10:15:25.653-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Limits" /><category scheme="http://www.blogger.com/atom/ns#" term="Blogger" /><category scheme="http://www.blogger.com/atom/ns#" term="Picasa" /><title>Is Blogger Free?</title><content type="html">Occasionally, in &lt;a href="http://www.google.com/support/forum/p/blogger/label?lid=3a39191b4249689a&amp;hl=en" target="_blank"&gt;Blogger Help Forum&lt;/a&gt;, we get the querulous inquiry&lt;blockquote&gt;Is Blogger free, or must I pay for the service?&lt;/blockquote&gt;or&lt;blockquote&gt;What upcharges will I have to deal with, after publishing my blog?&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;To answer the question, I'll say&lt;blockquote&gt;Yes, and no.&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Within limits, and excepting for minor details, you can publish a Blogger blog, and maintain it for a very long time, without needing a major credit card.&lt;br /&gt;&lt;br /&gt;There are two possible charge items, that I can think of.&lt;ul&gt;&lt;li&gt;If you want to publish your blog to BlogSpot, the service is free.  Publishing the blog to &lt;a href="http://blogging.nitecruzr.net/2007/08/publishing-your-blog-externally.html"&gt;a non BlogSpot URL&lt;/a&gt; will require paying for either &lt;a href="http://blogging.nitecruzr.net/2007/02/custom-domain-names-hosted-by-blogger.html"&gt;Custom Domain publishing&lt;/a&gt;, or service from &lt;a href="http://blogging.nitecruzr.net/2007/06/setting-up-ftp-published-blog.html"&gt;a remote server published using FTP&lt;/a&gt;.  Both will likely cost you some money, though you will not pay the money to Google.&lt;/li&gt;&lt;li&gt;If you publish a blog with photos, and you host the photos using the native post editor upload, you'll be using the Picasa service.  Picasa is &lt;a href="http://blogging.nitecruzr.net/2008/03/blogger-limits-picture-storage.html"&gt;free, to a limit&lt;/a&gt;, then there is an upcharge for additional Picasa storage capacity.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;For a free service, there are &lt;a href="http://blogging.nitecruzr.net/2006/10/size-limits-on-your-blogger-account.html"&gt;very few absolute limits&lt;/a&gt; to what resources you may use.  The limits that do exist may be substantial to some, and you have to decide whether they warrant you finding another blogging platform.&lt;br /&gt;&lt;br /&gt;And, as I pointed out long ago, Blogger does not charge us directly for the service, but they are not a non profit organisation.  They are compensated, to a nice profit level.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-4530618067180280569?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/4530618067180280569/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/11/is-blogger-free.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/4530618067180280569?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/4530618067180280569?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/P_eRKa5M28g/is-blogger-free.html" title="Is Blogger Free?" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/11/is-blogger-free.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUQFRH4ycCp7ImA9WxNUF0Q.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-4654095985311733191</id><published>2009-11-05T18:37:00.000-08:00</published><updated>2009-11-09T12:08:35.098-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-09T12:08:35.098-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Following" /><category scheme="http://www.blogger.com/atom/ns#" term="Navbar" /><title>Add The Followers Gadget To The Blog</title><content type="html">It's been a bit over 2 months since Following was added as a Blogger feature, and daily we see anxious bloggers asking&lt;blockquote&gt;How do I get Followers to my blog?&lt;/blockquote&gt;as if that is a holy grail of blogging.  My first answer is always &lt;blockquote&gt;Write interesting and relevant content for the blog, so people will read the blog, and will want to Follow the blog.&lt;/blockquote&gt; But there is yet another detail, that not all bloggers seem to get.&lt;br /&gt;&lt;br /&gt;Add a Followers gadget to the blog.  Having a Followers gadget, with pictures of other Followers, will attract more Followers than just &lt;a href="http://blogging.nitecruzr.net/2009/11/new-navbar-and-follow-blog-link.html"&gt;the "Follow" link in the navbar&lt;/a&gt;.  The "Follow" link, besides not having pretty pictures, works differently than the Followers gadget.&lt;br /&gt;&lt;br /&gt;You're going to get a different class of blog readers using the Followers gadget, than the Follow link.  The Followers gadget lets people Follow the blog&lt;ul&gt;&lt;li&gt; without signing in to Blogger&lt;/li&gt;&lt;li&gt;using a different Blogger account&lt;/li&gt;&lt;li&gt;using a non Google account&lt;/li&gt;&lt;/ul&gt;The navbar Follow link requires the reader to be logged in, with the primary Blogger account, to the navbar.  People who Follow the blog using the navbar link won't be as casual as those who Follow using the gadget.&lt;br /&gt;&lt;br /&gt;Also, the Followers gadget encourages readers and visitors, by making your blog into an active part of &lt;a href="http://blogging.nitecruzr.net/2008/10/following-focused-replacement-for-next.html"&gt;the Following community that contains your blog&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;The navbar link, frankly, is a poor substitute for the gadget.  If you have a blog that uses a classic template, with which &lt;a href="http://blogging.nitecruzr.net/2007/08/layouts-templates-use-dynamic-html-and.html"&gt;people who insist on publishing by FTP are stuck&lt;/a&gt;, the navbar link will be your only choice.  But if the blog has a layouts template, and you want Followers, the gadget is your best accessory to add.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-4654095985311733191?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/4654095985311733191/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/11/add-followers-gadget-to-blog.html#comment-form" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/4654095985311733191?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/4654095985311733191?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/5UyJjmTPK-A/add-followers-gadget-to-blog.html" title="Add The Followers Gadget To The Blog" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/11/add-followers-gadget-to-blog.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0cBSH0-eyp7ImA9WxNUF0Q.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-8061991522173190817</id><published>2009-11-05T10:50:00.001-08:00</published><updated>2009-11-09T11:30:59.353-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-09T11:30:59.353-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Security" /><category scheme="http://www.blogger.com/atom/ns#" term="Privacy" /><category scheme="http://www.blogger.com/atom/ns#" term="Anonymity" /><title>Blogging Anonymously</title><content type="html">We know that Blogger allows us to blog anonymously, by promising to &lt;a href="http://blogging.nitecruzr.net/2006/12/your-blog-is-forever.html"&gt;never reveal our identity as a blog owner&lt;/a&gt;.  This leads to mysterious scenarios, like when someone &lt;a href="http://blogging.nitecruzr.net/2008/11/your-email-address-and-blogger-account.html"&gt;forgets the account that they used to create a blog&lt;/a&gt;, that they do own.  And, it leads sometimes to tragic scenarios, like bloggers who don't have access to the back door email account, and &lt;a href="http://blogging.nitecruzr.net/2009/06/you-are-responsible-for-maintaining.html"&gt;can't prove blog ownership&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Even though Blogger allows us to pursue our anonymity, though, that doesn't guarantee absolute anonymity without effort.  There are things that we still need to do, to ensure that our name / identity isn't connected with a given blog.&lt;br /&gt;&lt;br /&gt;First, remove the "About Me" gadget from the blog.  Either publish the blog without a native Blogger "About Me" gadget, or &lt;a href="http://blogging.nitecruzr.net/2007/09/dont-like-profile-page-element-make.html"&gt;make up a custom one&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Second, &lt;a href="http://blogging.nitecruzr.net/2009/10/private-blog-may-not-be-completely.html"&gt;remove the blog from the "My Blogs" list&lt;/a&gt; in your Blogger profile.&lt;br /&gt;&lt;br /&gt;If you're truly paranoid, you could &lt;a href="http://blogging.nitecruzr.net/2007/06/how-to-transfer-blog-from-one-account.html"&gt;transfer control of the blog&lt;/a&gt;, to a secondary account that you own.  If you do this, it would be wise to use a non GMail account, so you can avoid a Google cookie clash caused by &lt;a href="http://blogging.nitecruzr.net/2008/10/your-email-address-and-blogger-account.html"&gt;trying to use two Google accounts simultaneously&lt;/a&gt;.  And please, if you want to retain control of the blog, &lt;a href="http://blogging.nitecruzr.net/2009/06/your-email-address-and-blogger-account.html"&gt;use a valid non GMail email address&lt;/a&gt;, and keep control of the email address.&lt;br /&gt;&lt;br /&gt;Finally, check behind yourself, carefully. Comb the contents of the blog in question, and make sure that you don't inadvertently reveal any personal details.  This may be an ongoing concern, as you publish any blog, anonymously or not.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-8061991522173190817?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/8061991522173190817/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/11/blogging-anonymously.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/8061991522173190817?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/8061991522173190817?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/6mAgMF7SDdA/blogging-anonymously.html" title="Blogging Anonymously" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/11/blogging-anonymously.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0MNQHo5fyp7ImA9WxNUFE4.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-248326548757096551</id><published>2009-11-05T08:22:00.000-08:00</published><updated>2009-11-05T08:44:51.427-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-05T08:44:51.427-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Splog Removal" /><category scheme="http://www.blogger.com/atom/ns#" term="Spam" /><category scheme="http://www.blogger.com/atom/ns#" term="Splogs" /><category scheme="http://www.blogger.com/atom/ns#" term="Blogger Support" /><title>Maybe It's Time To Start Over</title><content type="html">I've been advising folks about spam problems, and splog detection (both &lt;a href="http://blogging.nitecruzr.net/2009/01/blame-it-on-fuzz.html"&gt;righteous and spurious&lt;/a&gt;), for several years.  Sometimes, the advice is about cleaning up the blog, and &lt;a href="http://blogging.nitecruzr.net/2008/02/blogs-are-being-removed-for-just-cause.html"&gt;submitting it for review&lt;/a&gt;.  Other times, it's about &lt;a href="http://blogging.nitecruzr.net/2009/11/attack-of-clones.html"&gt;blogs unjustly accused of being spam&lt;/a&gt;.  Occasionally, it's about &lt;a href="http://blogging.nitecruzr.net/2009/10/waiting-for-tap-on-shoulder.html"&gt;spam blogs, that can't be reviewed again&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Lately, we've seen some folks asking for help, when it appears that they have been given several chances, already, to clean up their act.&lt;blockquote&gt;this is what i got from email:&lt;blockquote&gt;We'd like to inform you that we've received another complaint regarding your blog. Upon review of your account, we've noted that your blog has repeatedly violated Blogger's Terms of Service (&lt;a href="http://www.blogger.com/terms.g" target="_blank"&gt;http://www.blogger.com/terms.g&lt;/a&gt;). Given that we've provided you with several warnings of these violations and advised you of our policy towards repeat infringers, we've been forced to remove your blog.&lt;/blockquote&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;We all believe in forgiveness, but having been forgiven, should you continue with the blog restored and simply cleaned up?  Or maybe, isn't it better for everybody if you simply start over, with a new blog and new content?&lt;br /&gt;&lt;br /&gt;Focus your energy on making a new blog.  Don't waste your time (the helpers time, Blogger Support's time) trying to clean up what can't be cleaned up.&lt;br /&gt;&lt;br /&gt;Start over.  And next time, when you get the first notice about unacceptable content, heed the warning.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-248326548757096551?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/248326548757096551/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/11/maybe-its-time-to-start-over.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/248326548757096551?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/248326548757096551?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/6U2bDylK1Ms/maybe-its-time-to-start-over.html" title="Maybe It's Time To Start Over" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/11/maybe-its-time-to-start-over.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUQESHY9cSp7ImA9WxNUE0s.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-2597013993502827126</id><published>2009-11-04T12:20:00.000-08:00</published><updated>2009-11-04T12:41:49.869-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-04T12:41:49.869-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Google Webmaster Tools" /><category scheme="http://www.blogger.com/atom/ns#" term="Search Engines" /><category scheme="http://www.blogger.com/atom/ns#" term="Settings - Basic" /><title>Less Traffic To Our Blogs</title><content type="html">One of the more active (and frequently controversial) subjects discussed in this blog is getting more traffic to our blogs, also known as &lt;a href="http://blogging.nitecruzr.net/2008/01/more-traffic-to-our-blogs.html"&gt;getting the blog indexed by the search engines&lt;/a&gt;.  Not everybody wants their blogs indexed, though.&lt;blockquote&gt;How do I make sure my blog is NOT found by search engines?&lt;/blockquote&gt;That question is asked, regularly.  And, in truth, there is only one truly effective answer.&lt;blockquote&gt;Don't publish your blog on the Internet.&lt;/blockquote&gt;This is similar to the question (and answer)&lt;blockquote&gt;How do I &lt;a href="http://blogging.nitecruzr.net/2009/10/private-blog-may-not-be-completely.html"&gt;keep my blog private&lt;/a&gt;?&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Short of absolute effectiveness, the most obvious solution is the &lt;a href="http://blogging.nitecruzr.net/2008/04/controlling-search-engine-spiders.html"&gt;two Settings - Basic options&lt;/a&gt;.  And there are other tweaks which you may find, in &lt;a href="http://blogging.nitecruzr.net/2008/05/google-webmaster-tools.html"&gt;Google Webmaster Tools&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;And, in the spirit of locking the barn after the horses have been stolen, there is the subject of &lt;span style="font-style:italic;"&gt;&lt;a href="http://blogging.nitecruzr.net/2009/01/removing-your-blog-from-search-engines.html"&gt;Removing Your Blog From The Search Engines Caches&lt;/a&gt;&lt;/span&gt;.  Search engine caches, like browser caches, &lt;a href="http://blogging.nitecruzr.net/2009/03/google-search-engine-is-not-only-star.html"&gt;won't clear overnight, if ever&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-2597013993502827126?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/2597013993502827126/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/11/less-traffic-to-our-blogs.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/2597013993502827126?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/2597013993502827126?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/nW2xtBFNvdQ/less-traffic-to-our-blogs.html" title="Less Traffic To Our Blogs" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/11/less-traffic-to-our-blogs.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE4FRHcycCp7ImA9WxNUE0s.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-502599603821828323</id><published>2009-11-03T13:31:00.000-08:00</published><updated>2009-11-04T11:28:35.998-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-04T11:28:35.998-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Splog Farms" /><category scheme="http://www.blogger.com/atom/ns#" term="Search Engines" /><category scheme="http://www.blogger.com/atom/ns#" term="Splog Removal" /><category scheme="http://www.blogger.com/atom/ns#" term="Next Blog" /><category scheme="http://www.blogger.com/atom/ns#" term="Splog Restriction" /><category scheme="http://www.blogger.com/atom/ns#" term="Splogs" /><title>The Attack Of The Clones</title><content type="html">The latest spam problem, which became visible a couple weeks ago, thanks to yet another Blogger error, left a lot of bloggers (&lt;a href="http://blogging.nitecruzr.net/2009/10/waiting-for-tap-on-shoulder.html"&gt;some legitimate and others actually spammers&lt;/a&gt;) reporting both confusion and indignation&lt;blockquote&gt;My blog seems to be locked, but when I fill out the CAPTCHA, I get&lt;blockquote&gt;Your blog is not locked, and does not need review.&lt;/blockquote&gt;What do I do, now?&lt;/blockquote&gt;and&lt;blockquote&gt;My blog is not spam!  Honestly, how could Blogger legitimately call my blog spam?&lt;/blockquote&gt;Both of these reports, echoed by dozens of bloggers and spammers, show two sides of the same story.&lt;br /&gt;&lt;br /&gt;&lt;hr /&gt;&lt;span style="font-style:italic;"&gt;Note: This isn't fiction - I'm not stealing content from the Tom Clancy "&lt;a href="http://en.wikipedia.org/wiki/Tom_clancy#NetForce_Universe" target="_blank"&gt;Net Force&lt;/a&gt;" novels.  This is real.&lt;/span&gt;&lt;hr /&gt;&lt;br /&gt;&lt;br /&gt;Spammers, in order to publish one or two active splogs (blogs containing actual &lt;a href="http://networking.nitecruzr.net/2005/07/hacking-redefined.html" target="_blank"&gt;hacking, porn, and / or spam content&lt;/a&gt;), use the power of the Internet.  Each splog publisher, who may have at his control thousands of &lt;a href="http://nitecruzr.blogspot.com/2006/09/bots-and-you.html" target="_blank"&gt;hijacked computers&lt;/a&gt;, publishes &lt;a href="http://blogging.nitecruzr.net/2008/01/sploggers-and-shell-game.html"&gt;thousands of blogs&lt;/a&gt; each day.&lt;br /&gt;&lt;br /&gt;A splogger starts by simply publishing empty blogs, in a constant, all day activity.  You may see the empty blogs some time, if you &lt;a href="http://blogging.nitecruzr.net/2007/12/new-game-lets-go-pornnext-blog-surfing.html"&gt;go "Next Blog" surfing&lt;/a&gt;.  They have a title, an archives gadget in the sidebar, and maybe one or two posts with random garbage.  And a Profile gadget, with a link to the "owner", each "owner" with 10 blogs.&lt;br /&gt;&lt;br /&gt;The splogger next takes one legitimate blog - in this case, &lt;span style="font-weight:bold;"&gt;your blog&lt;/span&gt;.  He scrapes the content from &lt;span style="font-weight:bold;"&gt;your blog&lt;/span&gt;, takes a dozen or so of his empty blogs, adds your content to each, and republishes each blog.  Now, there are a dozen clones of &lt;span style="font-weight:bold;"&gt;your blog&lt;/span&gt;, plus your original, in BlogSpot.&lt;br /&gt;&lt;br /&gt;Next, the splogger takes a couple of his recently created clones, adds the payload -  &lt;a href="http://networking.nitecruzr.net/2005/07/hacking-redefined.html" target="_blank"&gt;hacking, porn, and / or spam content&lt;/a&gt;, and republishes his now active splogs.  Each time, he just uses a couple blogs (cloned from &lt;span style="font-weight:bold;"&gt;your blog&lt;/span&gt;), and keeps the others as reserve.  He has dozens of other splogs with active content out there too, using scraped content from other legitimate blogs.  The clones of your blog, joining the clones of other blogs, are now active members of his splog farm.&lt;br /&gt;&lt;br /&gt;As the splogs with active content are detected and removed by Blogger, the splogger simply activates other reserves, placing payload into each, in turn.  By the time all of the reserves, that are clones of your blog, are used up, the spam farm will have clones of still more legitimate blogs, ready to be activated.&lt;br /&gt;&lt;br /&gt;Considering this process, we see the life cycle of each splog in the splog farm.&lt;ul&gt;&lt;li&gt;Empty (just published).&lt;/li&gt;&lt;li&gt;Reserve (previously empty, republished with scraped content added).&lt;/li&gt;&lt;li&gt;Active (previously reserve, republished with payload added).&lt;/li&gt;&lt;li&gt;Detected (previously active, locked by the Blogger Spam Classification bot).&lt;/li&gt;&lt;li&gt;Deleted.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;The plan here is that each splog will pass through each stage in the life cycle, in proper sequence.  Since the splogger publishes thousands of splogs daily, if Blogger were to simply lock then delete the active splogs, the splogger simply activates the reserve splogs, as needed.  This is good project management, by the sploggers.&lt;br /&gt;&lt;br /&gt;Blogger aims to shorten this life cycle.  When the anti-spam bot detects an active splog, they search their database of suspected splogs, find similar blogs with no active content (the reserves), and lock the reserves too.&lt;br /&gt;&lt;br /&gt;Unfortunately, when Blogger locks the reserve splogs, they are also going to lock your blog.  Fuzzy spam detection techniques can't tell the difference between your blog, and the clones, because &lt;a href="http://blogging.nitecruzr.net/2009/01/blame-it-on-fuzz.html"&gt;there is no difference&lt;/a&gt;.  And that leaves you, and hundreds of other bloggers, reporting&lt;blockquote&gt;My blog is not spam!  Honestly, how could Blogger legitimately call my blog spam?&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;When you look at this differently, though, you see that Blogger is actually helping you.  Were your blog, and the clones, to remain in BlogSpot undisturbed, the search engines would see the clones, and levy a huge duplicated content penalty on all aliases of the content - &lt;span style="font-weight:bold;"&gt;including your original blog&lt;/span&gt;.  If you are able to declare your blog as legitimate to Blogger, Blogger can later delete the sploggy clones, and the search engines will, hopefully, continue to index your blog, as legitimate and unique content.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-502599603821828323?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/502599603821828323/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/11/attack-of-clones.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/502599603821828323?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/502599603821828323?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/be05yEkGQfU/attack-of-clones.html" title="The Attack Of The Clones" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/11/attack-of-clones.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkIEQHozeip7ImA9WxNUEU4.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-3383978472869808671</id><published>2009-11-01T20:00:00.000-08:00</published><updated>2009-11-01T20:01:41.482-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-01T20:01:41.482-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Following" /><category scheme="http://www.blogger.com/atom/ns#" term="Navbar" /><title>The New Navbar And The "Follow Blog" Link</title><content type="html">The new navbar, with its Follow and Share links, has been out for just over a week.  People are starting to use the Follow button, instead of the Followers gadget - which is not necessarily present on every blog.  But there are differences between the "Follow" button on the navbar, and the "Followers" gadget that's (sometimes) added to the blogs.  These differences are causing some confusion.&lt;br /&gt;&lt;br /&gt;The Followers gadget lets you login to Following, under any account, Blogger or not - and &lt;a href="http://blogging.nitecruzr.net/2009/05/following-friend-connect-requires.html"&gt;separate from the account used to login to the navbar&lt;/a&gt;.  If you so desire, you can Follow any blog without logging in - You'll &lt;a href="http://blogging.nitecruzr.net/2009/04/what-are-fantom-followers-in-your.html"&gt;add a temporary "shadow" icon to the blog&lt;/a&gt; (if you choose to Follow publicly), and you'll add the blog feed to your Reading List and / or Google Reader subscription list.&lt;br /&gt;&lt;br /&gt;With the Follow link on the navbar, if you're not logged in (using the "Sign In" link), you'll not see a "Follow" link.  Once you do login (which you can only do using a Blogger account), you can click on the Follow button.  There, you'll get a choice of Following publicly, using your Blogger / Google account - or Following anonymously.  If you Follow publicly, you'll use your Blogger profile, as connected with the account used to Sign In to the navbar.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-3383978472869808671?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/3383978472869808671/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/11/new-navbar-and-follow-blog-link.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/3383978472869808671?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/3383978472869808671?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/xcBLnGWwoow/new-navbar-and-follow-blog-link.html" title="The New Navbar And The &quot;Follow Blog&quot; Link" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/11/new-navbar-and-follow-blog-link.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUAEQXg_cCp7ImA9WxNUFU8.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-8319222585791717536</id><published>2009-11-01T07:39:00.000-08:00</published><updated>2009-11-06T09:15:00.648-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-06T09:15:00.648-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Post Editor" /><category scheme="http://www.blogger.com/atom/ns#" term="New Blogger June 2008 Production" /><title>The New Post Editor And Read More</title><content type="html">One problem which we seem to see, pretty consistently, in &lt;a href="http://www.google.com/support/forum/p/blogger/label?lid=0271191b4249689a&amp;hl=en" target="_blank"&gt;Blogger Help Forum&lt;/a&gt;, is where the posts and a sidebar end up in one long column, with one above the other.  Reports like&lt;blockquote&gt;My posts have vanished!&lt;/blockquote&gt;and&lt;blockquote&gt;My sidebar (my archives, my Followers, my profile gadget, ...) have dropped to the bottom of the page!&lt;/blockquote&gt;are seen a lot in the forum.  Generally, it's caused by &lt;a href="http://blogging.nitecruzr.net/2006/03/either-post-or-sidebar-ends-up-at.html"&gt;trying to put too much in one place&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Recently, though, a few bloggers report the dropped sidebar symptom, after they try the new post editor, and the Blogger "Read More" option (called by Blogger, "Jump Break").&lt;br /&gt;&lt;br /&gt;The "Read More" feature in Blogger blogs has been a long needed option.  Before the new post editor, Blogger, and at least 2 other bloggers, had their own competing, and mutually incompatible, procedures for making your blog show, and execute, a "Read More" link.  All 3, to my knowledge, had drawbacks.  One of the most obvious was that each different version was added by editing the post HTML, and the HTML was complex, and messy.&lt;br /&gt;&lt;br /&gt;The "Jump Break" in the new post editor is easy to add.&lt;ol&gt;&lt;li&gt;Position the cursor after the words that you want to be shown, initially.&lt;/li&gt;&lt;li&gt;Hit the "Jump Break" button.&lt;/li&gt;&lt;li&gt;The jump break is inserted into the post editor window.&lt;/li&gt;&lt;li&gt;When you publish the post, you'll see the words that you want to be shown, followed by the link "Read More".&lt;/li&gt;&lt;li&gt;What could be simpler?&lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;&lt;br /&gt;In rare cases, the "Jump Break" button in the toolbar may not work.  If you have that problem, go into the "Edit HTML" mode, and insert&lt;blockquote&gt;&lt;span style="font-weight:bold;"&gt;&amp;lt;!-- more --&amp;gt;&lt;/span&gt;&lt;/blockquote&gt;right where you need your jump break.&lt;br /&gt;&lt;br /&gt;For all the simplicity in adding this (either in Compose or "Edit HTML" mode), it's not producing simple results.&lt;br /&gt;&lt;br /&gt;There appear to be at least two scenarios where a blog, with one or more posts published with jump breaks, would have a dropped posts or sidebar section.&lt;ol&gt;&lt;li&gt;When the blog displays more than 10 posts in main page view, each post with a jump break, the 11th post will cause this problem.&lt;/li&gt;&lt;li&gt;If the jump break is inserted into the middle of a section of text with formatting implemented using a "&amp;lt;div&amp;gt; ... &amp;lt;/div&amp;gt;", a "&amp;lt;div&amp;gt;" section broken by a jump break will cause this problem.&lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;&lt;br /&gt;The workarounds to prevent these scenarios are obvious.&lt;ol&gt;&lt;li&gt;Reduce your main page size.&lt;/li&gt;&lt;li&gt;Don't add jump breaks in the middle of "&amp;lt;div&amp;gt; ... &amp;lt;/div&amp;gt;" sections.&lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;&lt;br /&gt;But those workarounds may not be popular, or easy to implement.&lt;ol&gt;&lt;li&gt;Some bloggers like to publish blogs with 15, 20, or more posts in the main page.&lt;/li&gt;&lt;li&gt;Blogger who like this new, shiny feature may not be aware of when their posts include "&amp;lt;div&amp;gt; ... &amp;lt;/div&amp;gt;" sections.  How can they avoid breaking a section that they can't see?&lt;/li&gt;&lt;/ol&gt;&lt;br /&gt;&lt;br /&gt;So, it looks like Blogger has yet to polish the "Jump Break" feature.  If you aren't technically proficient, and don't like solving problems cause by Blogger code, you may be better off not using "Jump Break" until it's a bit more polished.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-8319222585791717536?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/8319222585791717536/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/11/new-post-editor-and-read-more.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/8319222585791717536?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/8319222585791717536?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/7FuO8sBfyS0/new-post-editor-and-read-more.html" title="The New Post Editor And Read More" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/11/new-post-editor-and-read-more.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEYDRXg5eip7ImA9WxNVGEo.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-1981212411429464650</id><published>2009-10-29T19:48:00.000-07:00</published><updated>2009-10-29T20:09:34.622-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-29T20:09:34.622-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="FTP Publishing" /><category scheme="http://www.blogger.com/atom/ns#" term="FTP Publishing Problems" /><category scheme="http://www.blogger.com/atom/ns#" term="Settings - Publishing" /><title>FTP Publishing  - October 2009</title><content type="html">This month, we have several reports from bloggers who, for one reason or another, have changed the FTP username and / or password on the domain host server, and then updated the username / password in their &lt;a href="http://blogging.nitecruzr.net/2007/06/setting-up-ftp-published-blog.html"&gt;Blogger FTP settings&lt;/a&gt;.  Much to their dismay, when attempting to publish their blog, they find &lt;a href="http://www.google.com/support/forum/p/blogger/thread?tid=3bce948501842a50&amp;hl=en" target="_blank"&gt;the old username / password being sent to the remote server&lt;/a&gt;.&lt;blockquote&gt;I have verified it's saving my new username in the publishing settings and yes, I'm seeing the error based on the posting status. I get the following ...&lt;blockquote&gt;&lt;span style="font-weight:bold;"&gt;FTP login failed (server: ftp.domain.com, username: myoldusername, reason: 530 User myoldusername cannot log in. )&lt;/span&gt;&lt;/blockquote&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Are you seeing this behaviour, when trying to publish your blog?&lt;ul&gt;&lt;li&gt;What is the blog URL?&lt;/li&gt;&lt;li&gt;What is the FTP server setting?&lt;/li&gt;&lt;li&gt;When did you make the setting change?&lt;/li&gt;&lt;li&gt;Did you verify the problem, by examining the host server activity logs?&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-1981212411429464650?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/1981212411429464650/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/ftp-publishing-october-2009.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/1981212411429464650?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/1981212411429464650?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/_tFd_mjoILQ/ftp-publishing-october-2009.html" title="FTP Publishing  - October 2009" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/ftp-publishing-october-2009.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A08CQHczeSp7ImA9WxNUEkQ.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-2481822857803508799</id><published>2009-10-29T11:42:00.000-07:00</published><updated>2009-11-03T17:57:41.981-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-03T17:57:41.981-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Reality" /><category scheme="http://www.blogger.com/atom/ns#" term="Blogger Profile" /><category scheme="http://www.blogger.com/atom/ns#" term="Proxy Server" /><category scheme="http://www.blogger.com/atom/ns#" term="Private Blogs" /><category scheme="http://www.blogger.com/atom/ns#" term="Latency" /><category scheme="http://www.blogger.com/atom/ns#" term="Interstitial Warning" /><title>A Private Blog May Not Be Completely Private</title><content type="html">We've known for a while that private blogs have limitations, such as latency.  If you originally publish your blog as public, and later make it private, cached copies of the blog will be all over the Internet, &lt;a href="http://blogging.nitecruzr.net/2008/12/blog-recently-made-private-wont-be-so.html"&gt;for anybody to read, after it's supposedly private&lt;/a&gt;.  This week, we see another, &lt;a href="http://www.google.com/support/forum/p/blogger/thread?tid=733e28faed30e16a&amp;hl=en#all" target="_blank"&gt;possibly more serious limitation&lt;/a&gt;.&lt;blockquote&gt;Why was my coworker able to read my very private, personal, password protected blog yesterday?  I had it set to "Blog Author Only" and yet she found it and was able to read the whole thing.&lt;br /&gt;&lt;br /&gt;It has never, ever been public.  I started it last September and set the permissions to "blog author only" at the start for all posts.  I have never invited anyone else to read it...and have never, ever logged into it at work.&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Occasionally, while using a dialup connection, I've had occasion to load a private blog.  As the blog loads, the browser enumerates the various components of the blog, such as various pictures loading, in the browser status area (generally, the lower left border of the browser window).  The interstitial notice&lt;blockquote&gt;&lt;span style="font-weight:bold;"&gt;This blog is open to invited readers only&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;It doesn't look like you have been invited to read this blog. If you think this is a mistake, you might want to contact the blog author and request an invitation.&lt;/blockquote&gt;seems to come up well after the blog main page contents have loaded.&lt;br /&gt;&lt;br /&gt;If you are surfing from a network which goes through a server which loads the main page of the blog, and fails to subsequently load the interstitial warning, it's possible that people who surf through that server may see the main page of the blog, even though it's supposedly private.  If your Blogger profile is part of your public blogs, or people link to your profile while &lt;a href="http://blogging.nitecruzr.net/2009/08/blogger-profile-surfing-focused.html"&gt;surfing profiles&lt;/a&gt;, and your private blog is listed as one of your blogs, someone may click on the link, and may get a view of the blog.&lt;br /&gt;&lt;br /&gt;This security deficiency isn't one that you can control, as you have no way of denying anybody access to your profile, if it's published publicly.  If you want to keep your blog private, it would be a good idea to at least &lt;a href="http://www.blogger.com/edit-profile-displayed-blogs.g"&gt;remove it from the list of your blogs&lt;/a&gt;, in your profile.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-2481822857803508799?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/2481822857803508799/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/private-blog-may-not-be-completely.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/2481822857803508799?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/2481822857803508799?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/WAN-lFpPJ1M/private-blog-may-not-be-completely.html" title="A Private Blog May Not Be Completely Private" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/private-blog-may-not-be-completely.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEEGRHY6eip7ImA9WxNVGEk.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-6765412685182084211</id><published>2009-10-26T12:26:00.000-07:00</published><updated>2009-10-29T13:03:45.812-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-29T13:03:45.812-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Search Engines" /><category scheme="http://www.blogger.com/atom/ns#" term="Navbar" /><category scheme="http://www.blogger.com/atom/ns#" term="Blog Search" /><category scheme="http://www.blogger.com/atom/ns#" term="Browser" /><title>What's In The Boxes?</title><content type="html">Every day, we see one or two queries from confused bloggers, about these boxes.&lt;blockquote&gt;I type the URL in my browser, and get&lt;blockquote&gt;No blog found.&lt;/blockquote&gt;&lt;/blockquote&gt;or&lt;blockquote&gt;Why doesn't it show more than what's in my blog?&lt;/blockquote&gt;or&lt;blockquote&gt;I know the URL.  I can see it on my dashboard even.  But the search says that it's not there.&lt;/blockquote&gt;All of these observations are evidence of people who don't know what all the boxes in the browser are intended to provide.&lt;br /&gt;&lt;br /&gt;When you view your blog, there are 2 to 4 boxes of which you need to be aware.  Depending upon what accessories are provided in any given blog, there may be more.  Depending upon what browser you have, there may be less.  And depending upon what browser you have, the label, position, and size of any of these boxes isn't predictable.  But, the boxes will be there.&lt;ul&gt;&lt;li&gt;&lt;span style="font-weight:bold;"&gt;Browser Address Box&lt;/span&gt;.  This is the most important box visible.  This is where you are supposed to paste or type the URL of your blog, another blog, or any website, to browse to the blog or website.&lt;/li&gt;&lt;li&gt;&lt;span style="font-weight:bold;"&gt;Browser Search Box&lt;/span&gt;. This is a browser accessory, provided by some browsers, so you don't have to load the web page of the major search engines.  Here, as on the search boxes on the various web pages, you paste or type the search that you want to do.&lt;/li&gt;&lt;li&gt;&lt;span style="font-weight:bold;"&gt;Navbar Blog Search Box&lt;/span&gt;.  If you haven't disabled the navbar, here you can paste or type keywords which will be used to search your blog, directly - without requiring that your blog be indexed by the search engines.&lt;/li&gt;&lt;li&gt;&lt;span style="font-weight:bold;"&gt;Blog Search Gadget&lt;/span&gt;.  This will be any search gadget added to a blog by the owner.  This could be a version of the navbar blog search, or a version of the browser search box, but against different search engines.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;Except for the navbar blog search box, there is no way to predict if, what, or where any of these boxes will look like or appear.  The labeling, positioning, even whether a box is included, are all a matter of personal preference.  Some personal preference is of the blog owner, other is of the blog reader / owner of the computer used for browsing.&lt;br /&gt;&lt;br /&gt;In some browsers, the address box and search box are combined, with browser code interpreting (more or less reliably) whether a URL or search terms have been entered.  This causes confusion when the person used to such a browser uses another browser, with separate and distinct boxes.&lt;br /&gt;&lt;br /&gt;The navbar is intended as the single &lt;a href="http://blogging.nitecruzr.net/2009/10/new-navbar.html"&gt;most predictable object on the screen&lt;/a&gt;, when viewing Blogger blogs.  Unfortunately, some blogs are setup with &lt;a href="http://blogging.nitecruzr.net/2008/12/removing-navbar-from-your-blog.html"&gt;the navbar hidden&lt;/a&gt;, which prevents use of the navbar blog search.  To compensate for this, some blog owners will add &lt;a href="http://blogging.nitecruzr.net/2008/07/help-your-readers-search-your-blog.html"&gt;a blog search gadget&lt;/a&gt;.  Unfortunately, Search gadgets for Blogger blogs come in a variety of designs.  A browser search gadget may be the equivalent of the browser search window, of the navbar blog search window, or even &lt;a href="http://blogging.nitecruzr.net/2008/10/help-your-readers-search-your-blogs.html"&gt;may be customised&lt;/a&gt; so you can't tell what it does.&lt;br /&gt;&lt;br /&gt;Besides understanding the blog search box (whether navbar or blog based), we need to note a major difference between a search using a search engine, and a search directly against the blog.&lt;ul&gt;&lt;li&gt;Both a browser search box and a blog based custom search box will involve a search engine, which uses cached copies of every indexed blog and web site.  The cached copies will be subject to &lt;a href="http://groups.google.com/group/blogger-help/web/blogging-is-all-about-patience"&gt;search engine latency&lt;/a&gt;, causing discrepancies similar to &lt;a href="http://blogging.nitecruzr.net/2009/02/your-blog-search-engines-and-main-page.html"&gt;SERPs referencing main page view&lt;/a&gt;.&lt;/li&gt;&lt;li&gt;Blog direct searches, such as the navbar search box, and some custom search boxes, which will search the blog now, based upon what's in the blog, now.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;Considering all of these details, it's not surprising that there would be confusion, when people surf strange blogs and / or use strange browsers, maybe on strange computers.  Possibly, by knowing the details, we can diagnose the questions from the confused bloggers.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-6765412685182084211?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/6765412685182084211/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/whats-in-boxes.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/6765412685182084211?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/6765412685182084211?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/2gmK-9finMk/whats-in-boxes.html" title="What's In The Boxes?" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/whats-in-boxes.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0IGQns-cCp7ImA9WxNVFEU.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-458283055237138555</id><published>2009-10-25T09:25:00.000-07:00</published><updated>2009-10-25T09:52:03.558-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-25T09:52:03.558-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Post Editor" /><category scheme="http://www.blogger.com/atom/ns#" term="New Blogger June 2008 Production" /><category scheme="http://www.blogger.com/atom/ns#" term="Settings - Basic" /><category scheme="http://www.blogger.com/atom/ns#" term="Settings" /><category scheme="http://www.blogger.com/atom/ns#" term="Draft Blogger Released" /><title>Accepting Membership In Another Blog May Change Post Editor Settings</title><content type="html">Recently, we've seen an occasional question about mysteriously changed post editor selections.&lt;blockquote&gt;Where did my options toolbar go?&lt;/blockquote&gt;or&lt;blockquote&gt;Why do I now see the new post editor?&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Right now, as part of the &lt;a href="http://blogging.nitecruzr.net/2009/09/new-post-editor-is-here.html"&gt;deployment of the new post editor&lt;/a&gt;, there are 3 selections, in Settings - Basic - &lt;span style="color: rgb(204, 153, 51);"&gt;Global Settings&lt;/span&gt; - &lt;span style="font-weight: bold;"&gt;Select post editor&lt;/span&gt;.&lt;ul&gt;&lt;li&gt;Updated editor&lt;/li&gt;&lt;li&gt;Old editor&lt;/li&gt;&lt;li&gt;Hide compose mode&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;If you make this change under one blog, you'll find it true for all of your blogs.  I've also noted, under some circumstances, that when you accept membership in someone else's blog, and the other person was using a different post editor selection, the other person's selection will now be yours, globally.&lt;br /&gt;&lt;br /&gt;The next time that you accept membership in a blog, check your post editor setting.  If the owner of the blog was using a different setting, your setting may have changed.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.blogger.com/post-edit.g?blogID=24069595&amp;amp;postID=458283055237138555#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-458283055237138555?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/458283055237138555/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/accepting-membership-in-another-blog.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/458283055237138555?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/458283055237138555?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/o44ZiqazvYI/accepting-membership-in-another-blog.html" title="Accepting Membership In Another Blog May Change Post Editor Settings" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/accepting-membership-in-another-blog.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0EFQ3w8cCp7ImA9WxNVFUk.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-5296173297944956278</id><published>2009-10-24T13:03:00.000-07:00</published><updated>2009-10-26T00:20:12.278-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-26T00:20:12.278-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Google Webmaster Tools" /><category scheme="http://www.blogger.com/atom/ns#" term="Google Webmaster Tools Verification" /><category scheme="http://www.blogger.com/atom/ns#" term="Main Page View" /><title>Blogs Showing The WMX Verification File, Instead Of Main Page</title><content type="html">This week, we have various Blogger blogs reported as displaying a mysterious WMX Verification File, when main page view would be expected.&lt;blockquote&gt;&lt;span style="font-weight:bold;"&gt;This is the WMX verification file. If you are having problems with the WMX verification for your blog please visit http://help.blogger.com/bin/static.py?page=start.cs&lt;/span&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;This symptom was first observed Thursday, October 22, and Blogger Support is aware of the problem.  Supposedly, the problem was fixed, though some blog owners are still reporting it.&lt;br /&gt;&lt;br /&gt;We note that the Google Webmaster Central Blog: &lt;span style="font-style:italic;"&gt;&lt;a href="http://googlewebmastercentral.blogspot.com/2009/10/verifying-blogger-blog-in-webmaster.html" target="_blank"&gt;Verifying a Blogger blog in Webmaster Tools&lt;/a&gt;&lt;/span&gt; now instructs us to use &lt;a href="http://blogging.nitecruzr.net/2008/09/verifying-ownership-of-your-site-to.html"&gt;the meta tag verification procedure&lt;/a&gt;.&lt;blockquote&gt;The "Webmaster Tools" auto-verification link from the Blogger dashboard is no longer working and will soon be removed.&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Is your blog showing this, in place of main page view?  If you can provide some diagnostic details, you might help Blogger to help you and others.  Precision here is good - and date, time, and timezone will be appreciated.&lt;ul&gt;&lt;li&gt;What's the URL of the blog?&lt;/li&gt;&lt;li&gt;When did you first observe the problem?&lt;/li&gt;&lt;li&gt;When did you last publish a post to the blog?&lt;/li&gt;&lt;li&gt;When did you last modify the template?&lt;/li&gt;&lt;li&gt;Did you add the blog to Google Webmaster Tools, using the dashboard wizard, or using the GWT native procedure?&lt;/li&gt;&lt;li&gt;When did you add the blog to GWT?&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;(Update 10/23): Some bloggers are &lt;a href="http://www.google.com/support/forum/p/blogger/thread?tid=63206b145cb102a3&amp;hl=en&amp;fid=63206b145cb102a3000476cac83c1760" target="_blank"&gt;working around the problem&lt;/a&gt; by refreshing the blog.&lt;/span&gt;  From Settings - Publishing,&lt;ul&gt;&lt;li&gt;Change the name to any available URL, and Save.&lt;/li&gt;&lt;li&gt;Change the name back to the correct URL, and Save.&lt;/li&gt;&lt;li&gt;Note for a custom domain published blog, you'll have to publish back to BlogSpot, then back to the correct domain URL.&lt;/li&gt;&lt;/ul&gt;If you do this, you ought to examine the &lt;a href="http://blogging.nitecruzr.net/2008/05/google-webmaster-tools.html"&gt;Google Webmaster Tools&lt;/a&gt; entry for the blog, and check &lt;a href="http://blogging.nitecruzr.net/2009/06/renaming-followed-blog.html"&gt;your Following relationships&lt;/a&gt; carefully.  Both GWT and Following are sensitive to blog renames.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-5296173297944956278?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/5296173297944956278/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/blogs-showing-wmx-verification-file.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/5296173297944956278?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/5296173297944956278?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/7b6dwmxhWF4/blogs-showing-wmx-verification-file.html" title="Blogs Showing The WMX Verification File, Instead Of Main Page" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/blogs-showing-wmx-verification-file.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ak4FQH4_eyp7ImA9WxNVFE0.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-8359802050013954362</id><published>2009-10-24T09:31:00.000-07:00</published><updated>2009-10-24T11:28:31.043-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-24T11:28:31.043-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Visitors" /><category scheme="http://www.blogger.com/atom/ns#" term="Moderation" /><category scheme="http://www.blogger.com/atom/ns#" term="Blog Security" /><category scheme="http://www.blogger.com/atom/ns#" term="Comments" /><category scheme="http://www.blogger.com/atom/ns#" term="Team Blogs" /><category scheme="http://www.blogger.com/atom/ns#" term="Mail-To-Blogger" /><title>Keep Malicious Content Out Of Your Blog</title><content type="html">Every day or so, we see reported from concerned bloggers, about unknown content in their blogs.&lt;blockquote&gt;Where did those ads come from?  I didn't add them!&lt;/blockquote&gt;or&lt;blockquote&gt;How do I keep this other blogger from posting porn links in my blog?&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;As we add content to our blogs, and make them fun, interesting, and shiny, to attract readers, we risk adding undesirable content.  This is a constant problem.  The bad guys are out there, and the more fun, interesting, and shiny your blog is, the more it's likely to have readership, reputation, and value.  The more readership, reputation, and value that your blog has, the more attractive it is to the bad guys.&lt;br /&gt;&lt;br /&gt;&lt;a name="Comments"&gt;&lt;span style="font-weight:bold;"&gt;Malicious Comments&lt;/span&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;One of the easiest way to add third party content to your blog is from allowing comments.  Comments are contributed by people who, at best, you simply do not know.  Any content from someone who you do not know can always be malicious, or &lt;a href="http://blogging.nitecruzr.net/2009/03/why-we-should-all-moderate-comments.html"&gt;obnoxious in some way&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Some blog owners will try to &lt;a href="http://blogging.nitecruzr.net/2009/10/identifying-and-blocking-malicious.html"&gt;identify and block individual commentors&lt;/a&gt;.  I will continue to insist that &lt;a href="http://blogging.nitecruzr.net/2007/06/you-can-know-your-visitors-but-you-cant.html"&gt;anybody who you should fear will not be bothered greatly&lt;/a&gt; by anything that you can do here.&lt;br /&gt;&lt;br /&gt;You absolutely must &lt;a href="http://blogging.nitecruzr.net/2008/10/comment-moderation-in-blogger-blogs.html"&gt;moderate comments&lt;/a&gt;, or risk having a blog known for hosting malicious links - or worse.&lt;br /&gt;&lt;br /&gt;&lt;a name="Posts"&gt;&lt;span style="font-weight:bold;"&gt;Malicious Posts&lt;/span&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Besides comments, posts are a constant concern.  If you have a team blog, you have to be able to trust the authors in the blog.  Post moderation, using post editor to publish, isn't an option.  Anybody who you make an author can publish what they feel like publishing.  You can only moderate posts after they are published, when using post editor.&lt;br /&gt;&lt;br /&gt;An alternative to using post editor to publish is Mail-to-Blogger, where contributions are emailed to the blog.  If Mail-to-Blogger is setup to publish straight to the blog, and the bad guys figure out &lt;a href="http://blogging.nitecruzr.net/2007/08/protect-your-mail-to-blogger-address-it.html"&gt;your MTB account and password&lt;/a&gt;, you'll have malicious content a plenty.  You can &lt;a href="http://blogging.nitecruzr.net/2008/06/mail-to-blogger-can-provide-moderated.html"&gt;moderate before publishing, using Mail-to-Blogger&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;a name="Accessories"&gt;&lt;span style="font-weight:bold;"&gt;Malicious Accessories&lt;/span&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;And finally, any time that you install &lt;a href="http://blogging.nitecruzr.net/2009/09/protect-your-blog-install-third-party.html"&gt;third party accessories of any type&lt;/a&gt;, you are &lt;a href="http://blogging.nitecruzr.net/2009/01/protect-your-readers-install-third.html"&gt;placing your blog at risk&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Don't be paranoid - you have to make your blog interesting to your readers.  But do keep the risks in mind.  This is similar to &lt;a href="http://networking.nitecruzr.net/2005/05/please-protect-yourself-layer-your.html" target="_blank"&gt;layered security for your computer&lt;/a&gt;, which is a related concern here.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-8359802050013954362?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/8359802050013954362/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/keep-malicious-content-out-of-your-blog.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/8359802050013954362?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/8359802050013954362?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/_5GP_Wur66s/keep-malicious-content-out-of-your-blog.html" title="Keep Malicious Content Out Of Your Blog" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/keep-malicious-content-out-of-your-blog.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEAEQnw_fyp7ImA9WxNUEkU.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-7071894688050524802</id><published>2009-10-23T17:39:00.000-07:00</published><updated>2009-11-03T14:18:23.247-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-03T14:18:23.247-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Ambiguity" /><category scheme="http://www.blogger.com/atom/ns#" term="Splog Removal" /><category scheme="http://www.blogger.com/atom/ns#" term="Splogs" /><title>Waiting For The Tap On The Shoulder</title><content type="html">I'll be honest here.  I was &lt;a href="http://college.nitecruzr.net/" target="_blank"&gt;a nerd in college&lt;/a&gt; (and I am one &lt;a href="http://musings.nitecruzr.net/2006/11/problem.html" target="_blank"&gt;even now&lt;/a&gt;).  So this story is one that I've only seen in movies - neither I, nor my friends, got even this far.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;College Secret Societies&lt;/span&gt;&lt;br /&gt;Some of them have no name even. There are no published entrance rules - membership is by invitation only, and rules are communicated by word of mouth. And the initiation process starts like this:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;The prospective members are blindfolded, and led to a dark room.&lt;/li&gt;&lt;li&gt;The prospective members are put into a circle, in silence.&lt;/li&gt;&lt;li&gt;The prospective members wait, for what will happen, they are told nothing.&lt;/li&gt;&lt;li&gt;Periodically, one prospect will feel a slight tap on the shoulder.  In silence, he / she will be taken by the hand, and led into another room where they will join the elite.&lt;/li&gt;&lt;li&gt;And eventually, those who don't get elected will open their eyes, remove the blindfold, and find herself / himself in a pitiful group of rejects, all waiting (hopelessly) for that tap. The tap that never comes.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;Now maybe you should be advised that this article is a rehash of one that I wrote long ago, about &lt;a href="http://bloggerstatusforrealbeta.blogspot.com/2006/12/waiting-for-tap-on-shoulder.html" target="_blank"&gt;a more pleasant and positive experience&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;The subject of this narration is &lt;a href="http://blogging.nitecruzr.net/2009/10/ambiguity-in-url-availability-2.html"&gt;the spam detection problem of this week&lt;/a&gt;.  So, here are &lt;a href="http://www.google.com/support/forum/p/blogger/thread?tid=5b91210161049036&amp;hl=en" target="_blank"&gt;my words of wisdom&lt;/a&gt; about this mess.&lt;blockquote&gt;This problem is caused by criminals - spammers who are publishing thousands of spam blogs, daily.&lt;br /&gt;&lt;br /&gt;They make &lt;a href="http://blogging.nitecruzr.net/2009/11/attack-of-clones.html"&gt;dozens of clones of your blog&lt;/a&gt;, by scraping the content from your blog, pasting it into their blogs, and adding the spam content to just a few of their blogs, at any time.  Blogger can't tell the difference between the spam blogs without active content, and your blog.  So all of the blogs that look like your blog - &lt;a href="http://blogging.nitecruzr.net/2009/01/blame-it-on-fuzz.html"&gt;including your blog itself - get locked&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;If you are not a spammer, look at the next guy (also reporting the problem), because it's likely that he is one.  And when you get concerned about how long it's taking Blogger to restore your blog, if your blog is not a splog, &lt;a href="http://blogging.nitecruzr.net/2007/08/get-to-root-of-problem-blame-spammers.html"&gt;place some blame on the spammers&lt;/a&gt;, and the &lt;a href="http://blogging.nitecruzr.net/2008/01/sploggers-and-shell-game.html"&gt;thousands of splogs that have to be locked&lt;/a&gt;, then reviewed, &lt;span style="font-weight:bold;"&gt;daily&lt;/span&gt;.&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Anyway, the only thing that makes this even endurable is the thought of the spammers who have lost their blogs this week.  Many of them are gathered in Blogger Help Forum, reporting their blog loss.  Some of those gathered in BHF are not spammers - and that is what will give hope for everybody gathered there.&lt;br /&gt;&lt;br /&gt;Now Blogger, being the "secret society" in this analogy, will restore a few blogs - the ones that were not splogs.  But they will not be posting a big notice.&lt;blockquote&gt;The following blogs were determined to be spuriously locked, have been restored, and we apologise to their owners.&lt;/blockquote&gt;and conversely&lt;blockquote&gt;The following blogs were righteously detemined to be splogs, and will never be restored.&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Nope.&lt;br /&gt;&lt;br /&gt;Blogger will walk around silently, and tap the owners of the spuriously locked blogs on the shoulders.  Those owners will wake up one morning, and their blogs will be back, operational.&lt;br /&gt;&lt;br /&gt;The spammers will be the ones waiting, until they figure it out on their own, that they will never get the tap.  They will wait all night, then slink home in silence.&lt;br /&gt;&lt;br /&gt;BooHoo.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-7071894688050524802?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/7071894688050524802/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/waiting-for-tap-on-shoulder.html#comment-form" title="7 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/7071894688050524802?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/7071894688050524802?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/PAlzzEXLvdU/waiting-for-tap-on-shoulder.html" title="Waiting For The Tap On The Shoulder" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">7</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/waiting-for-tap-on-shoulder.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE8MR305fip7ImA9WxNVFko.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-4980784496287808603</id><published>2009-10-23T09:54:00.000-07:00</published><updated>2009-10-27T12:48:06.326-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-27T12:48:06.326-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Page Elements" /><category scheme="http://www.blogger.com/atom/ns#" term="Navbar" /><title>The New Navbar</title><content type="html">By now, I'm sure that you've all seen the new navbar on our blogs.  Besides having new links, and some links being renamed, there's a significant improvement - transparency.&lt;br /&gt;&lt;br /&gt;For those of you wondering where "Search Blog" went, the "Search Blog" window is still there - the "Search Blog" caption was simply removed, to make space.  And "Flag Blog" (which was, some time ago, &lt;a href="http://blogging.nitecruzr.net/2009/03/improved-porn-spam-blog-reporting-for.html"&gt;greatly enhanced&lt;/a&gt;) is now accurately captioned "Report Abuse".  And we have "Follow" (previously "Follow Blog"), matching the new "Share" link.&lt;br /&gt;&lt;br /&gt;And, for everybody who has always hated the navbar because it was ugly, and its background colour never matched the blog, you can now select a transparent option - and let the background colour / images in the blog show.  You can select "Transparent Dark", with light navbar characters and graphics - or "Transparent Light", with dark navbar characters and graphics.&lt;br /&gt;&lt;br /&gt;You select the new options in the Navbar Configuration wizard in "&lt;a href="http://blogging.nitecruzr.net/2007/09/forget-about-template-editor-use-page.html"&gt;Page Elements&lt;/a&gt;".  Click on the "Edit" link to the right of "Navbar".&lt;br /&gt;&lt;br /&gt;What you get doesn't look like complete transparency - you can see some colour variation on my home blog, "&lt;a href="http://www.nitecruzr.net/"&gt;nitecruzr dot net&lt;/a&gt;", but on this blog - look above.  Transparency on white looks pretty good.&lt;br /&gt;&lt;br /&gt;No more ugly navbar stripe - that's a small improvement, but still a significant one.  This may motivate some bloggers - though probably not all - to reverse their earlier decisions to &lt;a href="http://blogging.nitecruzr.net/2008/12/removing-navbar-from-your-blog.html"&gt;hide the navbar&lt;/a&gt; on their blogs.&lt;br /&gt;&lt;br /&gt;Now, since we're looking at the navbar, let's look at &lt;a href="http://blogging.nitecruzr.net/2009/10/whats-in-boxes.html"&gt;what the "Search Blog" box is&lt;/a&gt;.  It is for searching for posts, in this blog, which contain references to the keywords entered into the box.  It's not for searching for other blogs or web sites, neither using keywords or URLs.  Just for keywords, in the blog that's currently displayed.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-4980784496287808603?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/4980784496287808603/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/new-navbar.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/4980784496287808603?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/4980784496287808603?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/wKLWk2yr8FI/new-navbar.html" title="The New Navbar" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/new-navbar.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C08FSHY9fyp7ImA9WxNVFE0.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-5827866804171105794</id><published>2009-10-22T10:52:00.000-07:00</published><updated>2009-10-24T09:30:19.867-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-24T09:30:19.867-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Visitors" /><category scheme="http://www.blogger.com/atom/ns#" term="Moderation" /><category scheme="http://www.blogger.com/atom/ns#" term="Blog Security" /><category scheme="http://www.blogger.com/atom/ns#" term="Comments" /><category scheme="http://www.blogger.com/atom/ns#" term="Visitor Information" /><title>Identifying And Blocking Malicious Comments</title><content type="html">Almost daily, we see complaints from bloggers who are disturbed or offended by comments that they get, in their blogs.&lt;blockquote&gt;How do I stop nasty comments about my posts?&lt;/blockquote&gt;or&lt;blockquote&gt;How do I block a person who posts nasty comments?&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;My answers always start with&lt;blockquote&gt;You have to &lt;a href="http://blogging.nitecruzr.net/2008/10/comment-moderation-in-blogger-blogs.html"&gt;moderate comments, either before or after they are published&lt;/a&gt;.&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;You can identify your commentors, using a properly chosen &lt;a href="http://blogging.nitecruzr.net/2006/07/know-your-visitors.html"&gt;visitor counter / log utility&lt;/a&gt;.&lt;ul&gt;&lt;li&gt;Note the date and time of the comment, and what post it was published against.&lt;/li&gt;&lt;li&gt;Examine your visitor log, and find all clicks against the post in question, immediately preceding the comment in question.&lt;/li&gt;&lt;li&gt;Find the visitor log entry that contains a reference to the comment viewing and / or the comment posting process.&lt;/li&gt;&lt;li&gt;Now, you have the IP address of your malicious commentor, and an assortment of demographis details, possibly including &lt;a href="http://blogging.nitecruzr.net/2007/07/geolocation-where-are-my-readers.html"&gt;an &lt;span style="font-weight:bold;"&gt;approximate&lt;/span&gt; location&lt;/a&gt;.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;Now that you have the IP address in question, use &lt;a href="http://toolator.com/ban/" target="_blank"&gt;IP Address Blocker&lt;/a&gt; (free) to prevent access, from that IP address, to your blog.&lt;br /&gt;&lt;br /&gt;Simple enough?  No.  There are definite &lt;a href="http://blogging.nitecruzr.net/2007/06/you-can-know-your-visitors-but-you-cant.html"&gt;limitations to the effectiveness of this process&lt;/a&gt;.  But, you are welcome to try, anyway.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-5827866804171105794?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/5827866804171105794/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/identifying-and-blocking-malicious.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/5827866804171105794?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/5827866804171105794?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/gfQh8PPVFvg/identifying-and-blocking-malicious.html" title="Identifying And Blocking Malicious Comments" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/identifying-and-blocking-malicious.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUQEQ30_fCp7ImA9WxNVGEs.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-5717101348555247866</id><published>2009-10-21T17:54:00.000-07:00</published><updated>2009-10-29T17:41:42.344-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-29T17:41:42.344-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="URL Availability" /><category scheme="http://www.blogger.com/atom/ns#" term="Blog Address" /><category scheme="http://www.blogger.com/atom/ns#" term="Reality" /><category scheme="http://www.blogger.com/atom/ns#" term="Blog Ownership" /><title>Availability Of Any BlogSpot URL That's Not In Use</title><content type="html">I've been arguing the plain facts about URL non availability for years - if the BlogSpot URL of your choice is in use, &lt;a href="http://blogging.nitecruzr.net/2009/07/precedence-and-uniformity-justify.html"&gt;you can't have it&lt;/a&gt;.  That's not an easy answer for many bloggers, and some don't accept it without a lot of arguing.  The other side of the coin is that any available URL is there for the taking, by anybody.  Relevance of the name in question, to &lt;a href="http://blogging.nitecruzr.net/2008/12/nobody-is-guaranteed-blog-url-of-their.html"&gt;any physical existence outside the Internet world&lt;/a&gt;, has no validity.&lt;br /&gt;&lt;br /&gt;Today, we have a query of an issue not previously argued.&lt;blockquote&gt;I have website "TheNameThatIHave.com".  Today, I discovered that somebody else is publishing to "TheNameThatIHave.blogspot.com".  That's not right - I should have the right to "TheNameThatIHave.blogspot.com"!&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;And the answer here is&lt;blockquote&gt;No, if somebody else has "TheNameThatIHave.blogspot.com", it's their URL.  You have no claim to "TheNameThatIHave.blogspot.com", simply by having "TheNameThatIHave.com".&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;There is no screening, to determine the validity of anybody to publish to "TheNameThatIHave.blogspot.com", for any value of "TheNameThatIHave".  If the URL "TheNameThatIHave.blogspot.com" is available for publishing, every blogger has equal claim to take it.  If you see it, and you take it, you have it - for eternity.  The moment you take it, &lt;a href="http://blogging.nitecruzr.net/2009/07/precedence-and-uniformity-justify.html"&gt;nobody else has any claim over it&lt;/a&gt; - for eternity.  If somebody else took it, &lt;a href="http://blogging.nitecruzr.net/2009/06/no-you-cant-have-that-url.html"&gt;you have no claim over it&lt;/a&gt; - even if you own "TheNameThatIHave.com".&lt;br /&gt;&lt;br /&gt;As the well used adages go&lt;blockquote&gt;First come, first served.&lt;/blockquote&gt;and&lt;blockquote&gt;You snooze, you lose.&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-5717101348555247866?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/5717101348555247866/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/availability-of-any-blogspot-url-thats.html#comment-form" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/5717101348555247866?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/5717101348555247866?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/Bw_8v_E-N1w/availability-of-any-blogspot-url-thats.html" title="Availability Of Any BlogSpot URL That's Not In Use" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/availability-of-any-blogspot-url-thats.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkUDSHc8eip7ImA9WxNVE0k.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-2338060843065766752</id><published>2009-10-21T13:22:00.000-07:00</published><updated>2009-10-23T18:37:59.972-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-23T18:37:59.972-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="URL Availability" /><category scheme="http://www.blogger.com/atom/ns#" term="Ambiguity" /><title>Ambiguity In URL Availability #2</title><content type="html">A couple months ago, we had various bloggers report that they are initially informed that a given URL is available, but &lt;a href="http://blogging.nitecruzr.net/2009/08/ambiguity-in-url-availability.html"&gt;the "Create a blog" wizard later shows that the same URL is not available&lt;/a&gt;.  This month, we seem to have more of the same, plus &lt;a href="http://www.google.com/support/forum/p/blogger/thread?tid=017c1b37ccfe611c&amp;hl=en" target="_blank"&gt;a new, disturbing detail&lt;/a&gt;.&lt;blockquote&gt;I am unable to see my blog on the web or sign in to it on Blogger Dashboard. I initially thought my blog had been given a false positive as a spam blog and blocked. A Blogger Help forum post said that often happens and I should send a "review request."&lt;br /&gt;&lt;br /&gt;I sent a review request from my Blogger Dashboard.  It took me to a page that says:&lt;blockquote&gt;&lt;span style="font-weight:bold;"&gt;Blog is not locked. Your blog is not locked and does not need a review. If you are having problems accessing your blog or if you received an email saying that it was locked, please leave a message in the Help Group and we will investigate the issue.&lt;/span&gt;&lt;/blockquote&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Further conversation returns additional details.&lt;blockquote&gt;On my Dashboard, next to the name of my blog "This Day in Famous Quotes" (which is at the URL www.ThisDayinQuotes.com) I see this:&lt;blockquote&gt;This Day in Famous Quotes&lt;br /&gt;Restore access to this blog. Learn more&lt;/blockquote&gt; &lt;br /&gt;The word "Restore" has a link. I clicked that and got the message shown, which asks me to send my email address and fill in a captcha. I did that and then got a message saying my blog is not blocked. But I still can't see my blog on the web or access it through my Dashboard. Here's the message I get when I click "Restore":&lt;blockquote&gt;&lt;span style="font-weight:bold;"&gt;Blogger's spam-prevention robots have detected that your blog has characteristics of a spam blog. (What's a spam blog?) Since you're an actual person reading this, your blog is probably not a spam blog. Automated spam detection is inherently fuzzy, and we sincerely apologize for this false positive.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Find out more about how Blogger is fighting spam blogs.&lt;/span&gt;&lt;/blockquote&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_pzC_7PLtN-0/SuDjnZexndI/AAAAAAAACOA/-bNtz7NdAo0/s1600-h/404+Not+Found+20091022+2.JPG" target="_blank"&gt;&lt;img style="border-width:0px; float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 320px; height: 237px;" src="http://1.bp.blogspot.com/_pzC_7PLtN-0/SuDjnZexndI/AAAAAAAACOA/-bNtz7NdAo0/s320/404+Not+Found+20091022+2.JPG" border="0" alt=""id="BLOGGER_PHOTO_ID_5395562619584224722" /&gt;&lt;/a&gt;&lt;br /&gt;A normal error, when browsing to a blog published to BlogSpot.&lt;br /&gt;&lt;br clear=left /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_pzC_7PLtN-0/SuDbQEu1nnI/AAAAAAAACN4/dO6f1504C_M/s1600-h/404+Not+Found+20091022+1.JPG" target="_blank"&gt;&lt;img style="border-width:0px; float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 320px; height: 237px;" src="http://4.bp.blogspot.com/_pzC_7PLtN-0/SuDbQEu1nnI/AAAAAAAACN4/dO6f1504C_M/s320/404+Not+Found+20091022+1.JPG" border="0" alt=""id="BLOGGER_PHOTO_ID_5395553422784437874" /&gt;&lt;/a&gt;&lt;br /&gt;A cryptic, yet distinctive, error message when browsing to a blog published to a custom domain.  This is also seen for &lt;a href="http://blogging.nitecruzr.net/2008/03/custom-domains-use-301-redirect-from.html"&gt;the BlogSpot alias of the blog&lt;/a&gt;, published to a custom domain.&lt;br /&gt;&lt;br clear=left /&gt;&lt;br /&gt;&lt;br /&gt;Here, you have no blog, but there's nothing stated to be wrong.  And, we won't tell you what's wrong, we'll just ask that you report this in &lt;a href="http://www.google.com/support/forum/p/blogger/label?lid=0271191b4249689a&amp;hl=en"&gt;Blogger Help Forum: Something Is Broken&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;(Update 10/22 12:00): It appears that we have 2 relevant factors here.&lt;/span&gt;&lt;ul&gt;&lt;li&gt;A coding problem caused the ambiguity and some false positive results.&lt;/li&gt;&lt;li&gt;Not all blogs reporting the problem are legitimate.  Blogger will probably handle this on &lt;a href="http://blogging.nitecruzr.net/2009/10/waiting-for-tap-on-shoulder.html"&gt;a case by case basis&lt;/a&gt;, and unlock only legitimate blogs.  I'm betting that we won't see a lot of apologies either.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-2338060843065766752?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/2338060843065766752/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/ambiguity-in-url-availability-2.html#comment-form" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/2338060843065766752?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/2338060843065766752?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/Ik2NX2yYdks/ambiguity-in-url-availability-2.html" title="Ambiguity In URL Availability #2" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/_pzC_7PLtN-0/SuDjnZexndI/AAAAAAAACOA/-bNtz7NdAo0/s72-c/404+Not+Found+20091022+2.JPG" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/ambiguity-in-url-availability-2.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk4MR308eyp7ImA9WxNVEEk.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-4399340938550042657</id><published>2009-10-19T12:02:00.000-07:00</published><updated>2009-10-20T06:23:06.373-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-20T06:23:06.373-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Following" /><category scheme="http://www.blogger.com/atom/ns#" term="FeedBurner" /><category scheme="http://www.blogger.com/atom/ns#" term="Get Traffic - NOT" /><category scheme="http://www.blogger.com/atom/ns#" term="Blog Feed" /><title>Getting Traffic To Your Blog - How Not To Do It</title><content type="html">There are many ways of getting traffic to your blog.  If you truly respect your readers, you 'll &lt;a href="http://blogging.nitecruzr.net/2008/06/relevance-yields-readership-and-search.html"&gt;write content that's interesting and relevant to the needs of your readers&lt;/a&gt;, and you'll &lt;a href="http://groups.google.com/group/blogger-help/web/how-to-get-traffic-and-repeated-readers-for-your-blog"&gt;use the search engines to advertise your blog&lt;/a&gt;.  Other people might join a forum, where everybody promises to read each other's blogs.  A third way would be to use the magic of RSS, and &lt;a href="http://www.blogcatalog.com/groups/popular/" target="_blank"&gt;join your blog to a common feed&lt;/a&gt;.&lt;blockquote&gt;TRAFFIC via RSS&lt;br /&gt;&lt;br /&gt;by ananth77 with 2,473 members&lt;br /&gt;&lt;br /&gt;Tagged: blog, blog building, blogging, feed, Marketing, promote, rss, traffic&lt;br /&gt;&lt;br /&gt;Build your traffic via RSS. Simple Rules : - 1. Subcribe to http://feeds.feedburner.com/feed_traffic 2. Update your RSS feed address in the reply. 3. Your feed will be merged with all the other blogs and web sites.&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;What a deal.  All that you do is make your blog part of the Feed Traffic feed, and you get a piece of all of the traffic, from / to all of the other blogs in the feed.  This used to be called a "link farm", where everybody would link to each others blogs, randomly.  This is just a link farm using a FeedBurner feed as a backbone.&lt;br /&gt;&lt;br /&gt;But, there's a problem here - can you see it?&lt;br /&gt;&lt;br /&gt;When you redirect your blog feed to the Feed Traffic feed, your blog becomes part of the feed cloud.  Each post that you publish goes to that feed - and anybody subscribing to the feed, from your blog, gets a subscription to all of the blogs and web sites that are part of the Feed Traffic cloud.  Just as anybody subscribed to the feed, from any of the other blogs and web sites in the cloud, now gets your blog posts.&lt;br /&gt;&lt;br /&gt;Your readers subscribe to the feed from your blog, to read the posts from your blog.  Your readers don't want to read the feed from thousands of other blogs, they want to read the feed from your blog.  You want to encourage people to read your blog, don't you?&lt;br /&gt;&lt;br /&gt;This becomes worse when you involve Following, where your Followers subscribe to the feed from your blog.  The feed from your blog goes into the common "All blog updates" list in the Reading List for all of your Followers.  This puts thousands of unrelated blogs into the Reading Lists for all of your Followers.  This makes the Reading Lists practically useless, for Following relevant blogs.&lt;br /&gt;&lt;br /&gt;I know of &lt;a href="http://www.google.com/support/forum/p/blogger/thread?tid=72215d9f91341e4e&amp;hl=en" target="_blank"&gt;two bloggers who broke off Following with a third blogger&lt;/a&gt;, because of the volume of posts in the feed cloud overwhelmed their Reading Lists.  I don't think that these two will be the only ones who find this necessary.  If you make this technique part of your strategy for dispersing your blog, you might watch your Following community.&lt;br /&gt;&lt;br /&gt;Decide whether you want random anonymous readers, or membership in a relevant and interested community.  I don't think that you'll get both.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-4399340938550042657?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/4399340938550042657/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/getting-traffic-to-your-blog-how-not-to.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/4399340938550042657?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/4399340938550042657?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/A2WRp_-qEAM/getting-traffic-to-your-blog-how-not-to.html" title="Getting Traffic To Your Blog - How Not To Do It" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/getting-traffic-to-your-blog-how-not-to.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8HRXk8cSp7ImA9WxNVEEU.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-6754603501753269935</id><published>2009-10-18T08:02:00.000-07:00</published><updated>2009-10-20T18:00:34.779-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-20T18:00:34.779-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Reality" /><category scheme="http://www.blogger.com/atom/ns#" term="Language" /><category scheme="http://www.blogger.com/atom/ns#" term="GeoLocation" /><title>You Have To Read The Local Language</title><content type="html">As Blogger / Google continue to make their services more available to the bloggers and blog readers of the world, they are separating the language affinities of the various portions of the Blogger displays, into two categories.&lt;ul&gt;&lt;li&gt;Components most referenced by the bloggers.&lt;/li&gt;&lt;li&gt;Components most referenced by the blog readers.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;Components referenced by the bloggers can be controlled by &lt;a href="http://blogging.nitecruzr.net/2007/09/tower-of-babble-becomes-slightly-lower.html"&gt;the Blogger profile language setting&lt;/a&gt;, so you, as you publish your blog, see many Blogger wizards in your stated language.&lt;br /&gt;&lt;br /&gt;Readers of a Blogger blog, on the other hand, won't always have a Blogger profile, as they surf the Internet and land upon your blog.  To support your readers, Blogger uses Geo Location, and determines the prevalent local language where the computer is located. Blog displays that are most referenced by the blog readers will be presented in the local language.&lt;br /&gt;&lt;br /&gt;If you write your blog for your readers, this benefits you.  The more portions of your blog that are available to the blog readers of the world, in the language of each reader, the more likely they will be to continue reading your blog, rather than surfing to other web sites.  Since the vast majority of the people of the world surf the Internet at home, in their native culture, blog displays presented in the native language will be more friendly to the majority of your readers.&lt;br /&gt;&lt;br /&gt;If you accompany your blog with translation options, such as &lt;a href="http://blogging.nitecruzr.net/2008/02/make-your-blog-speak-more-languages.html"&gt;a Google Translator with a user friendly interface&lt;/a&gt;, casual visitors will be more likely to become regular readers.&lt;br /&gt;&lt;br /&gt;Of course, this won't please everybody.  Travelers to a foreign land, using a computer connected through a local network - whether their own computer, in the hotel, or a local computer in a coffee shop / Internet cafe - won't be seeing their displays in their native language.  Just like other artifacts encountered in a foreign land - advertisements, newspapers, street signs - computer displays may use unfamiliar language.&lt;br /&gt;&lt;br /&gt;This is an unavoidable result of travel to foreign lands - &lt;a href="http://blogging.nitecruzr.net/2007/06/you-have-to-speak-language.html"&gt;everybody there won't be speaking your language&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-6754603501753269935?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/6754603501753269935/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/you-have-to-read-local-language.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/6754603501753269935?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/6754603501753269935?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/hd7_HcziHQw/you-have-to-read-local-language.html" title="You Have To Read The Local Language" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/you-have-to-read-local-language.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkMESH07fip7ImA9WxNWGEk.&quot;"><id>tag:blogger.com,1999:blog-24069595.post-2137284449532160846</id><published>2009-10-17T21:53:00.000-07:00</published><updated>2009-10-17T22:40:09.306-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-17T22:40:09.306-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Nitecruzr.Net" /><category scheme="http://www.blogger.com/atom/ns#" term="Pictures" /><category scheme="http://www.blogger.com/atom/ns#" term="Inline Comments" /><category scheme="http://www.blogger.com/atom/ns#" term="Commenting Problems" /><category scheme="http://www.blogger.com/atom/ns#" term="Picture Problem" /><category scheme="http://www.blogger.com/atom/ns#" term="Comments" /><title>Missing Icons For Commenters In Inline Comments</title><content type="html">Does your blog use Inline (Embedded Below Post) Comments?  Do you have any posts with more than 5 comments?  I have a few.&lt;ul&gt;&lt;li&gt;&lt;span style="font-style:italic;"&gt;&lt;a href="http://blogging.nitecruzr.net/2009/10/new-blogger-limits-2009-labels-again.html#comments"&gt;New Blogger Limits 2009 - Labels, Again&lt;/a&gt;&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style="font-style:italic;"&gt;&lt;a href="http://blogging.nitecruzr.net/2009/09/missing-followers-september-2009-good.html#comments"&gt;Missing Followers - September 2009 - The Good News, And The Bad News&lt;/a&gt;&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style="font-style:italic;"&gt;&lt;a href="http://blogging.nitecruzr.net/2009/09/missing-followers-september-2009.html#comments"&gt;Missing Followers - September 2009&lt;/a&gt;&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style="font-style:italic;"&gt;&lt;a href="http://blogging.nitecruzr.net/2009/09/new-post-editor-and-spell-checking.html#comments"&gt;The New Post Editor And Spell Checking&lt;/a&gt;&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style="font-style:italic;"&gt;&lt;a href="http://blogging.nitecruzr.net/2009/09/new-post-editor-is-here.html#comments"&gt;The New Post Editor Is Here&lt;/a&gt;&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;Notice anything odd there?  The first 4 or 5 comments, which were made by commenters who have pictures, show the pictures.  After that, no pictures.&lt;br /&gt;&lt;br /&gt;I wonder what other surprises are in store for us this week?&lt;br /&gt;&lt;br /&gt;&lt;a href="#Top"&gt;&amp;gt;&amp;gt; Top&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/24069595-2137284449532160846?l=blogging.nitecruzr.net'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://blogging.nitecruzr.net/feeds/2137284449532160846/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blogging.nitecruzr.net/2009/10/missing-icons-for-commenters-in-inline.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/2137284449532160846?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/24069595/posts/default/2137284449532160846?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Nitecruzr-Blogging/~3/w_-ImcHwzXw/missing-icons-for-commenters-in-inline.html" title="Missing Icons For Commenters In Inline Comments" /><author><name>Chuck</name><uri>http://www.blogger.com/profile/08069634565746003311</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05403152582466850110" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blogging.nitecruzr.net/2009/10/missing-icons-for-commenters-in-inline.html</feedburner:origLink></entry></feed>
