Showing posts with label Site Feed. Show all posts
Showing posts with label Site Feed. Show all posts

Sunday, January 12, 2020

Dynamic Templates As Well As Visitor Information

As the dynamic templates proceed to hold upward installed on diverse Blogger blogs, to a greater extent than together with to a greater extent than weblog owners are noticing problems alongside their visitor logs.
I installed a dynamic template on my blog, together with my Stats display shows
No stats yet, banking concern gibe dorsum later.
and
StatCounter shows no traffic, at nowadays that my weblog uses the dynamic views.
These reports come upward from people who don't realise how the novel templates operate - together with why they don't appear to work, inwards these cases.

Blogs that purpose the dynamic views are able to display content faster.

The display speed improvement is possible, because dynamic templates purpose the weblog feed - which is downloaded from the Blogger newsfeed servers, together with rendered every bit a spider web display on our computers. Non Dynamic templates display static or semi static HTML (with CSS, XML, together with other extensions) - rendered into spider web displays on the Blogger servers, together with downloaded every bit spider web content.

The differences inwards spider web page display are non consistent alongside how visitor activity is observed.

  • Dynamic templates render less customisation ability, for most weblog owners.
  • Newsfeed content is simpler than spider web pages.
  • Newsfeed content is read i display page at a time.
  • Displayed dynamic pages comprise less formatting tweaks.
  • Individual posts, when displayed, are already cached on the local computer.

Dynamic templates render less customisation ability, for most weblog owners.

The downloaded dynamic templates are really simple, together with comprise no custom code for dissimilar blogs. Once downloaded for your blog, they volition operate the same for my blogs, together with for my neighbours weblog - alongside all blogs using dynamic views. This makes these blogs really stable.

Newsfeed content is simpler than spider web pages.

Non rendered newsfeed content is much simpler than rendered display pages. Once the template code is downloaded once, downloading the information is fifty-fifty quicker than downloading the templates.

Newsfeed content is read i display page at a time.

The newsfeed content is read from the Blogger newsfeed servers i display page at a time, together with cached on each readers computer. As each weblog is read, the most recent articles are at the top. Many readers, every bit alongside viewers, volition never become beyond the start display page.

Displayed dynamic pages comprise less formatting tweaks.

The displayed pages comprise really lilliputian accessories together with formatting, which is then pop alongside many weblog owners, together with which generates charge on networks together with processors.

Individual posts, when displayed, are already cached on the local computer.

When an private ship service is displayed, the cached content is already correct there, on the computer.

There are disadvantages to having all content cached, however.

The advantages, together with the disadvantages, of the dynamic views originate from the same basic details - purpose of the weblog newsfeed, together with of a really unproblematic together with criterion template. People who distribute their weblog every bit newsfeed subscriptions bring been shout out for the same question, for years.

How practise I rails my subscribers, also every bit I rails my viewers?

There is no slow answer to this need. With all content cached on the local computer, tracking reader activity is non then simple.

Tracking reader activity is a challenge - for both Blogger together with non Blogger features.

Both tertiary political party visitor logs together with meters, together with the Blogger Stats feature, bring problems providing details virtually our readers - alongside our blogs using the dynamic templates.

  1. Older installations of tertiary political party products purpose HTML / JavaScript, installed straight into the weblog templates (generally Classic, merely unopen to Layout together with Designer templates). The dynamic templates volition non include this tertiary political party code. Newsfeeds comprise exclusively really unproblematic text, together with pictures, alongside no scripts.
  2. Newer installations of tertiary political party products purpose HTML / JavaScript / XML gadgets, installed every bit accessories into the header, footer, or sidebar sections of the display. The dynamic templates, correct now, comprise neither sidebars nor accessories.
  3. Stats reads the Blogger server activity logs, generated every bit rendered display pages are downloaded to the customer computers. Newsfeed content may non require the same server activity, together with generate comparable activity logs.

None of these features volition hold upward easily included inwards the dynamic views, without unopen to rethinking of the unproblematic together with criterion dynamic template structure.

  1. Blogger has suggested that they volition render back upward for JavaScript code, inwards the dynamic templates. We tin install tertiary political party JavaScript code straight into the dynamic templates, making them to a greater extent than complex, together with unique for dissimilar blogs.
  2. Blogger has suggested that they volition render sidebars, together with back upward for accessory gadgets. We tin install tertiary political party JavaScript code every bit sidebar gadgets.
  3. Similar to accessory gadgets used for tertiary political party JavaScript, or to JavaScript embedded into the templates, Blogger tin render additional code to drive Stats displays, together with render pageview counts, into the template code.

Unfortunately, all of these alternatives volition come upward alongside a price. We volition come across increased code complexity, increased downloaded code volume, together with increased network together with processor activity on our computers.

In short, practise non aspect to come across detailed visitor information, comparable to what nosotros come across correct at nowadays inwards Stats or tertiary political party products, straightaway - together with scout for increased latency i time these features are added.



Owners of #Blogger blogs occasionally unwrap discrepancies inwards visitor activity, when they alter their blogs to purpose dynamic templates, together with examine their visitor logs.

Some - merely non all - changes come upward from reader reaction to the dynamic template displays together with features. Other changes involve how the dynamic templates are processed, past times the local computers beingness used past times the weblog readers.

Tuesday, November 19, 2019

Custom Domain Publishing Does Non Purpose Post Feed Redirect

One of the benefits of custom domain publishing, for a properly setup domain, is that the BlogSpot URL is automatically redirected to the domain.

Not all weblog owners realise that the BlogSpot to domain URL redirect includes the weblog feed - 1 time the Transition period ends, in addition to the weblog is republished to the domain.

Some weblog owners intend that the Post Feed Redirect setting needs to live on used when re publishing their weblog to a custom domain. This is non true, however. Use of the custom domain redirect, addition the post feed redirect, tin solely number inwards 1 of 2 problems.
  • A feed redirect loop.
  • A feed URL that points to invalid content.
In neither illustration volition whatever newsfeed client, such every bit a Dynamic Template, Google Reader, Reading List, or whatever 3rd political party feed service, honor a feed that tin live on used.

The Post Feed Redirect setting is used to redirect feed references, to a separately existing feed file.

The Post Feed Redirect is non used where it is non needed - in addition to amongst a weblog published to a properly setup custom domain, it's non needed.

Let's await at an HTTP trace, showing the weblog feed for a custom domain published blog, that uses a post feed redirect - inwards this case, nosotros stimulate got the feed for "mybloggerblog.blogspot.com" redirected to "mybloggerblog.com".

Start amongst the BlogSpot based feed URL, for "mybloggerblog.blogspot.com".

Sending request:

GET /feeds/posts/default HTTP/1.1
Host: mybloggerblog.blogspot.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Referer: http://www.rexswain.com/httpview.html
Connection: close

• Finding host IP address...
• Host IP address = 74.125.224.106
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·301·Moved·Permanently(CR)(LF)
Content-Type:·text/html;·charset=UTF-8(CR)(LF)
Location:·http://www.mybloggerblog.com/feeds/posts/default(CR)(LF)

With a properly setup custom domain, in addition to no PFR setting used, the adjacent display would live on the XML file, for the feed. Here, the PFR was develop to "http://mybloggerblog.com/".

Sending request:

GET /feeds/posts/default HTTP/1.1
Host: www.mybloggerblog.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Referer: http://www.rexswain.com/httpview.html
Connection: close

• Finding host IP address...
• Host IP address = 74.125.127.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·302·Moved·Temporarily(CR)(LF)
Location:·http://mybloggerblog.com/(CR)(LF)

Now, nosotros are looking at a typical custom domain rootage to "www" alias redirect.

Sending request:

GET / HTTP/1.1
Host: mybloggerblog.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Referer: http://www.rexswain.com/httpview.html
Connection: close

• Finding host IP address...
• Host IP address = 216.239.32.21
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·301·Moved·Permanently(CR)(LF)
Location:·http://www.mybloggerblog.com/(CR)(LF)

And now, nosotros are looking at the formatted weblog contents - non the newsfeed.

Sending request:

GET / HTTP/1.1
Host: www.mybloggerblog.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Referer: http://www.rexswain.com/httpview.html
Connection: close

• Finding host IP address...
• Host IP address = 74.125.127.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·200·OK(CR)(LF)

Unfortunately, the weblog itself is non a proper XML file (required for a feed), it's HTML / XML.

<!DOCTYPE·html·PUBLIC·"-//W3C//DTD·XHTML·1.0·Strict//EN"·"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">(LF)
<html·dir='ltr'·xmlns='http://www.w3.org/1999/xhtml'·xmlns:b='http://www.google.com/2005/gml/b'·xmlns:data='http://www.google.com/2005/gml/data'·xmlns:expr='http://www.google.com/2005/gml/expr'>(LF)
<head>(LF)

...

<link·href='http://www.mybloggerblog.com/'·rel='canonical'/>(LF)
<link·rel="alternate"·type="application/atom+xml"·title="Custom Domain Publishing Does Not Use Post Feed Redirect"·href="http://www.mybloggerblog.com/feeds/posts/default"·/>(LF)
<link·rel="alternate"·type="application/rss+xml"·title="Custom Domain Publishing Does Not Use Post Feed Redirect"·href="http://www.mybloggerblog.com/feeds/posts/default?alt=rss"·/>(LF)
<link·rel="service.post"·type="application/atom+xml"·title="Custom Domain Publishing Does Not Use Post Feed Redirect"·href="http://www.blogger.com/feeds/2302596229887627781/posts/default"·/>(LF)
<link·rel="EditURI"·type="application/rsd+xml"·title="Custom Domain Publishing Does Not Use Post Feed Redirect"·href="http://www.blogger.com/rsd.g?blogID=2302596229887627781"·/>(LF)
<link·rel="me"·href="http://www.blogger.com/profile/12619425977406185402"·/>(LF)
<link·rel="openid.server"·href="http://www.blogger.com/openid-server.g"·/>(LF)
<link·rel="openid.delegate"·href="http://www.mybloggerblog.com/"·/>(LF)

And if the feed customer is, for instance, a dynamic template, the would live on reader is looking at the former spinning gears. Until he gets bored, closes the browser, in addition to emails you
Your weblog is downwards - again.

If you lot stimulate got made this mistake, merely clear the Post Feed Redirect.

Monday, November 18, 2019

Blogger Magic - Activating The Spider Web Log Feed

One of the neatest - as well as easiest - techniques, to brand your weblog available to a larger audience, uses a replica of the weblog posts - the weblog newsfeed.

Most blogs, when new, convey the feed activated past times default. Oddly enough, roughly blogs - fifty-fifty published publicly - produce non seat out a newsfeed.

Some weblog owners, wondering why their blogs are non beingness indexed past times the search engines, are perplexed.
Why isn't my weblog publishing a feed?
If yous desire total visibility, activate the weblog newsfeeds.

You activate the diverse newsfeeds, for the blog, from the dashboard Settings - Other - Site Feed wizard.

Routinely, you'll convey 1 setting - "Allow Blog Feeds" - as well as this setting volition send upon all feed options equally. If yous guide "Custom", yous tin destination enable or disable whatever of the three feed options, separately.
  • Blog Posts Feed
  • Blog Comments Feed
  • Per-Post Comment Feeds

Each setting volition convey three possible selections - Full, Until Jump Break, Short, None.

(Note): If yous enable a feed, it is available to anybody alongside a feed reader, either a feed reader that they personally use, or 1 built inward to a blog. There is no alternative to trammel feed access - feeds are available, equally, to all interested parties. This is why feeds are non published past times express access (private) blogs.

If yous fearfulness that unknown parties powerfulness pocket content from your blog past times using your feed, don't seat out a Full feed, seat out a Short feed. This volition involve anybody wishing to read a consummate post service to access your blog, rather than reading it inward their newsreader.

In close cases, though, a "Full" setting, for all feeds, is best.