Spammers, And Content / Risk Management

Spammers protect their content against "unfair" deletion, and provide uninterrupted service to their "customers", by publishing multiple blogs, in spam blog farms.

Owners of better designed spam blog farms minimise the risk to their blogs, by separating the hacking / porn / spam content (Payload), from the immediately visible Blogger blogs (Collector). Spammers use a tiered structure of blogs, in their blog farms.

• Collector blogs.
• Distributor blogs.
• Payload blogs.

Only the Payload blogs contain easily identified hacking / porn / spam material - and only the Collector blogs are immediately visible to the abuse detection processes.

A tiered blog structure makes a more easily managed spam blog farm.

Collector blogs (lots of these) link to the Distributor blogs (many of these), which link to the Payload blogs (a few of these). This is good risk management, by the spammers, because it separates the visible content from the identifiable content.

In some cases, the Payload "blogs" might be non Google websites. Content hosts which have no objection to hacking / porn / spam content can host the Payload, with no risk.

Risk levels differ, according to content in each blog.

• Payloads (much risk, because of the detectable hacking / porn / spam content).
• Collectors (some risk, because of the detectable ads - plus invisible, automated links, to the Distributors).
• Distributors (little risk, only because of the invisible, automated links, to the Payloads).

As an example, one spam blog farm might be structured in geometrical progression.

Collectors (25) --> Distributors (5) --> Payload (1).

See the triangular structure, and the redundancy?

If automated links were permitted, only the Gateway blogs would be need to be advertised, to Blogger blog readers. If any of the Collector and / or Distributor blogs are detected and removed, the spammer can simply activate more blogs - and the Payload blogs can remain undisturbed.

If any Payload blogs are detected and removed, the spammer simply adds more Payload blogs - then updates the links in the Distributor blogs, with the URLs of the new Payloads. This is good project and risk management.

To interfere with this activity, Blogger prohibits automated linkage of blogs to other blogs and to non Google websites. This forces the spammers to provide visible links between the blogs and websites - and requires them to imaginatively publish both "legitimate" Collectors and Distributors with interesting and unique content and links.

DMCA Complaints Require Precise Examples

Occasionally we see confusion and impatience, in Blogger Help Forum: Something Is Broken, about previously submitted DMCA complaints.

I have repeatedly submitted a complaint about "offendingblog.blogspot.com" - and nothing is done! How long must I wait, for results??

We should start by noting that Google staff attention cannot ever be promised immediately - but if a valid complaint is submitted, repeatedly, with no results, maybe the problem is in the presentation of the complaint.

Blogger Policy Enforcement staff advises us that a DMCA complaint, when submitted, needs to include precise and specific examples of the perceived problem. Each example should be described in two parts.

1. A precise example of some content, in your blog, that was copied.
2. A precise example of some content, in the offending blog / website, which matches #1.

Instead of guessing or combing through your blog, then through the offending blog / website, and searching for matching content, the Blogger analysts time is better spent taking your complaint and submitting the complaint to Lumen (pka "ChillingEffects").

You know how you have been offended - so tell Blogger exactly how you have been offended, in the DMCA Complaint which you submit.

As always, do not submit frivolous DMCA complaints - your bank account may require discretion.

And be careful to use the right complaint procedure. DMCA Complaints are for very specific and genuine copyright violations. Other offenses must be reported, using different procedures.

Tweak The Post Template, Only When Necessary

Occasionally, we see the query, in Blogger Help Forum: How Do I?

How do I change these captions? / Add this feature? / Remove specific components of this feature?

Conversely, we see in Blogger Help Forum: Something Is Broken

Why does this new Blogger feature not work in my blog?

These questions, in many cases, may be related. We can see the connection, when we look closer at how the changes are applied.

Many changes to our blogs, that are part of the comments / posts / post header / footer, are made in the post template.

The post template is an unobtrusive section in the blog template, that lets us change the blog template as we wish - while allowing Blogger to update the comments and posts code, as they add new features, or update existing features.

Blogger lets us change the post template, using "Configure Blog Posts".

Blogger provides the "Configure Blog Posts" wizard - and lets us change specific features in the post template.

The options in "Configure Blog Posts" do not satisfy everybody - and here is where many problems start. Some blog owners want features or selections that are not provided by "Configure Blog Posts" - but are part of the post template.

Some features have to be installed as post template tweaks.

To install these features, the blog owner uses the Template Editor, and tweaks the "Blog1" template widget.

Once the post template is tweaked, by the blog owner, the blog has a non standard post template. When Blogger applies their next post template update, to install or update a Blogger supplied feature, against a blog with a non standard post template, they have 3 options.

1. Overlay the entire post template, with their updated post template. The blog owner sees all tweaks previously made, suddenly vanish. Some of the owner applied features simply disappear, others stop working - with no explanation or warning.
2. Overlay specific portions of the post template, with their updated post template changes. The blog owner sees some tweaks previously made, suddenly vanish. Some of the owner applied features simply disappear, others stop working - with no explanation or warning.
3. Not install the updated post template. The new Blogger feature doesn't work - and the blog owner is left complaining about broken Blogger updates, while other blog owners are enjoying the new feature.

When Blogger upgrades the post template, what happens to your tweaks?

If Blogger updates the post template, and some owner applied features disappear or stop working, the blog owner can simply install the necessary tweaks, again. Having kept the notes, or code snippets, from the original install, many blog owners simply install everything again.

Unfortunately, if the Blogger post template changes were applied in the same post template section as the owner applied tweaks, the owner retained notes or code snippets may be out of date - and installing them again may break one or more Blogger supplied features.

Some post template tweaks can have effects outside the post template.

Some owner applied changes, if installed improperly, can affect other sections of the template, in general - and cause mysteries such as problems updating accessory gadgets, and problems using the Template Designer.

The end result is that owner installed post template tweaks must be made, selectively - and any Blogger changes, publicised or non publicised, may necessitate re install of any owner applied tweaks. Owner applied tweaks must be re installed, character by character - and frequently with the readers complaining about an unexpected change or broken blog.

The post template is actually another example of "well enough", for many blog owners.

---

Tweak The Post Template, When Necessary - And Only, When Necessary

Internet Explorer Updates, And Use Of "Compatibility View" Settings - April 2014

For several weeks, we've seen a steady stream of problem reports, in Blogger Help Forum: Something Is Broken, about the latest monolithic error in Blogger history.

bx-hg9hg2

From several conversations with Blogger Support, it now appears that this latest error code (and a few similar ones) is related to Internet Explorer, and the use of Compatibility View. Apparently, Blogger Engineering has finally updated Blogger so it is compatible with Internet Explorer V11 - and having done so, has made it incompatible with V11 using Compatibility View.

The simplest way to resolve the bx-hg9hg2 is to reset Internet Explorer.

Many Blogger blog owners may be using Internet Explorer for more than just Blogger blog maintenance - and may not appreciate the possible effect on access to other websites, caused by a browser reset. In this case, it may be better to Edit the Internet Explorer settings, and remove Blogger from Compatibility View.

To edit Compatibility View, you use the browser Tools menu, and select "Compatibility View Settings". Select any or all entries referencing "blogger.com", and hit "Remove", then "Close".

Having either reset Internet Explorer, or edited the Compatibility View list, you may next need to restart Internet Explorer.

A third possibility would be to use a different browser, until Blogger Engineering resolves all issues with IE V11 and Compatibility View. This may not happen immediately, however - and some blog owners may prefer to use IE in general. Advice to "Use a different browser" is not always appreciated, by every blog owner.

>> Top

Dynamic Templates, And Problems Editing The Layout Pages Gadget

Ever since the new Pages wizards have been in use, we've been seeing reports from blog owners, who have problems with adding, deleting, and re sequencing links on the dynamic template menu bars.

Most blog owners have gotten used to the idea of maintaining dynamic pages ("link pages", formerly known as "web address"), using the Layout Pages gadget - separately from maintaining static pages (formerly known as "blank pages"), using the dashboard Pages wizard.

Even understanding the changes, some blog owners, who publish blogs that use dynamic templates, cannot add or delete dynamic pages - or cannot resequence the various page links.

Some owners claim to have links on the menu bar that they can't delete. Others have added, deleted, or resequenced links - but have found their changes to be lost, when viewing the blog, after saving the changes.

It appears that some blogs have had multiple Pages gadgets.

Blogs using a dynamic template, with multiple Pages gadgets in their history, become a problem.

If we look at the "Edit" link of the Pages gadget, in most blogs, we find the gadget referenced as "PageList1".

https://www.blogger.com/rearrange?blogID=1573647684922284136&widgetType=PageList&widgetId=PageList1&action=editWidget§ionId=sidebar-right-1

That is the "Edit" link for the gadget, for my dynamic template test blog.

Some blogs show signs of having had multiple Pages gadgets. "PageList2" - or even "PageList3" - are seen in some blogs.

https://www.blogger.com/rearrange?blogID=3821418744348630367&widgetType=PageList&widgetId=PageList2&action=editWidget§ionId=sidebar-right-1

That is the "Edit" link for the gadget, for one blog with this problem.

Apparently the dynamic templates only use "PageList1" in the menu bar - even if "PageList2" or "PageList3" is the active "Pages" gadget. This is not a problem for non dynamic templates.

The workaround, in this case, is simple enough. The blog owner must edit "PageList1".

https://www.blogger.com/rearrange?blogID=3821418744348630367&widgetType=PageList&widgetId=PageList1&action=editWidget§ionId=sidebar-right-1

Just extract the URL from the "Edit" link, paste it into the browser address window, change the "2" to "1", and hit Enter. Then add, delete, and rearrange links as necessary - and Save the changes.

The workaround is simple enough - but until Blogger Engineering fixes the problem, the blog owners affected have to use the workaround, each time they need to update Pages. And, if they ever switch back to a non dynamic template, they will need to update the active alias of "PageList", with any changes made to "PageList1".

Let's hope that Blogger Engineering can identify and fix the problem.

Loss Of Ability To Let The Reader Choose A Dynamic View Or Non Dynamic View, When Viewing The Blog

When the Blogger dynamic templates were first introduced, back in 2011, they provided choices.

Besides letting the reader choose, on the fly, which dynamic view to use, it was possible to let the reader choose whether to view the blog using a dynamic view - or a non dynamic view.

When dynamic templates were first introduced, they offered a dynamic view of the blog posts - and little else. Popular features like static pages were added later, and in pieces.

As the various pieces of the dynamic views became better defined, the need to switch between dynamic and non dynamic views became less essential - and eventually, some choices were eliminated.

If you look at the menu bar for this blog, you'll see a selection "DYNAMIC".

If you click on the "DYNAMIC" menu selection, you'll get a link to the "sidebar" dynamic view of this blog. At one time, this would have actually shown you this blog, using a dynamic template. Now, it leads you to a blank screen.

We asked Blogger Support recently, about the recently discovered inability to allow the reader to switch from a non dynamic view to a dynamic view, and were told that option had been discontinued, for "privacy reasons".

Apparently, some portions of the posts, when removed using the "Configure Blog Posts" wizard, were still displayed when a dynamic view was used. This caused problems for some blog owners, who had intentionally used a non dynamic view with personal details like author name removed from the posts. When they viewed the blog in a dynamic view, they found their name displayed, for all to see.

If anonymity is your concern, there are other techniques, which you may consider.

Another possible problem involved the blogs being simultaneously published using a dynamic template, and a non dynamic template. Last year, many blog owners reported various problems encountered, when their blogs were viewed using a dynamic template. It's possible that solution of the various problems involved simplification of code - including the ability to use either a dynamic or non dynamic view, at will.

Whatever the details, it appears that dynamic templates, and non dynamic templates, are completely separate options now. And as Blogger improves the dynamic templates in general, this should be good for all blogs.

>> Top

The New Google Login, And Using Public / Shared Computers

I've written a few times about protecting your Blogger / Google account, when you use public / shared computers.

Generally, any concern about use of public / shared computers discusses cookies, which are simply invisible traces that you might leave behind when using any computer. If you only use your own computer - and never share your computer - this issue is probably of no concern to you.

If you use a computer that someone else, who you know, also uses, cookies are a small concern. If you use a computer that other people, who you don't know, also use - as in a public computer in a coffee shop or library - this should be a larger concern.

If you look at the Google login screen, you'll see a common option, on many login screens.

Stay signed in.

If you hover the mouse over the option, you'll see a small popup.

For your convenience, keep this checked. On shared devices, additional precautions are recommended. Learn more.

Clicking on "learn more", you get to read Securely signing in to Google.

The Google Help article mentions cookies as a significant risk to you, when using a public computer ("Devices used by lots of people").

Public computers, if well-maintained, automatically clear a user’s web history and cookies. If you’re unsure, we recommend that you use the private browsing feature of the browser. If private browsing isn’t available, clear the browser’s history, cache, and cookies before and after you use the device.

With a shared computer ("Devices shared with a few people"), the risk is less alarming.

If you only plan to use the device briefly, such as when visiting a friend or relative, we suggest using private browsing.

If you plan to use the device often (say, for example, it’s your family computer), then we suggest creating a user profile either in the operating system or in the browser so you can keep your information private from other users. We recommend you leave the "Stay signed in" checkbox selected to take advantage of Account Chooser and longer sessions. Learn how to add user profiles on an Android device or in Chrome.

And the final note.

If none of these security options are available to you, we strongly suggest you do not sign in to your Google Account. If you do sign in, we recommend deselecting the "Stay signed in" checkbox in case you forget to sign out.

I've discussed clearing cache, cookies, and sessions, in a few articles - and in more than a few forum discussions. In many cases, before the new Google Login (2014) was developed, cookies were moderately significant. Cookies, along with cache and sessions, are normal bits of data, which a knowleagable hacker might find hidden away, on a computer.

With the new Google login display, cookies are a more significant concern. Look at a typical Account Chooser login screen might look like, on a computer shared by a number of people who use Google products.

Would you want any later user of your computer, checking out Account Chooser, and finding your email address in plain view?


If you, personally, only use one Google account, and never use a public or shared computer, you may never see the Account Chooser login screen. If you do see Account Chooser, in its native state (un erased), you will see the account name ("Display Name" in Blogger) and email address of each Google account owner who has used the computer, since cookies were last cleared. Note that the screen print, shown here, has display name and email address, for each of the 5 previous users, erased.

With the Google login display (2014), and Account Chooser, we have gone from account vulnerability to any knowleagable hacker, to account vulnerability to anybody who cares to click on "Use a different account".

Obviously, when using a public computer - and probably a shared computer - you would not want to ever select "Stay signed in". Also, if you ever have to use a public computer, I would always use 2-Step Verification.

>> Top

Help Me! I Can't Access My Blogger Account!

Every week, we see the anguished cry of blog owners, who don't have access to maintain, or publish to, their blogs.

Help me! My email address changed last month, I dropped my phone into the sink, and now I can't sign in to my blog!

If you look at the fine print, you see the full story.

Ask enough questions, and the details will come forth.

Help Me! I never bothered to remember my password - I used the Forgot Password wizard to reset my password every time I wanted to sign in to my Blogger account. My email address changed last month, my phone number changed last week, I can't get the email from the Forgot Password wizard, or the new Blogger Account / Blog Recovery wizard - and now I can't sign in to my blog!

As I have repeatedly advised folks, and previously pointed out in 2010, Blogger lets us maintain our blogs anonymously, and promises anonymous access and ownership for eternity. There is no magic token attached to our blogs, that let us conveniently email Blogger and ask for a second (or a third) back door access to our accounts.

If you can't access your Blogger account, you can't maintain your blog. Use the Forgot Password wizard, when you have access to the email account - or the new Blogger Account / Blog Recovery wizard.

And learn how to use the Google "One account" login wizard, properly.

Blogger wants to protect us, and our blogs, from attacks from people who claim to be us, but are not. Help them to protect our accounts, and our blogs - don't require that they gratuitously allow you access to your blog when you forget the password, and have no second - or third - back door access to reset the password.