August 2010 Archives

The way I learned that the Twitter API has stopped accepting basic authentication is that my Twinbox stopped working.  After using my browser to confirm that Twitter is actually running and my account is seeing tweets, I requested that Twinbox perform an immediate refresh in Outlook, That’s when I observed the Twitter-originated message that said basic authentication is no longer supported.

I was able to remedy the situation by downloading the latest version of Twinbox.  Twinbox simply started working again the next time I opened Outlook.  I assume that whatever connection for OAuth access was needed was handled automatically based on my already having authorized Twinbox as a Twitter connection.

Since that seemed almost too easy, I noticed, in my re-animated Twitter stream, that Windows Live Writer has a plug-in that will generate Twitter notifications when I make a blog post.  The Twitter Notify plug-in is reported to be updated to connect to Twitter via OAuth and we will see how that works out.

I am still frustrated in having the Windows Live Writer Zemanta plug-in recognize my personal Zemanta profile, so I wonder if there is going to be a similar issue with the Twitter Notify plug-in.  We’ll soon see.

 

The Zemanta Panel on my Movable Type post-authoring browser interface

[update 2010-08-29T19:00Z It’s become clear that Zemanta is worthy of a category.  There will be much to do with Zemanta and I also needed to experiment with how little I need to do to add a category.  This update with Zemanta as a category is in aid of both objectives.]

When I installed Movable Type 4 on nfoCentrale, my first blog posts were accomplished with the browser interface to  the Movable Type configuration. 

As part of Movable Type 4, I took the option to integrate Zemanta.  I didn’t quite understand what it was, but I did take advantage of it in making early posts.

Once I succeeded in configuring Windows Live Writer for operation with my first blogs created/restored using Movable Type, the authoring interface seemed barren without the Zemanta panel and suggestions.

Today, I learned that there is a Zemanta plug-in for Windows Live Writer.  The announcement was about an upgrade for the Wave 4 (Windows Vista and above only) version of Windows Live Writer, but I thought I’d chance it back here on WLW 14.0 on Windows XP3. 

I have completed the plug-in in stall.  On opening WLW, the Zemanta panel showed up at once.  It didn’t customize to my Zemanta account, of course, so I needed to figure out how to have it recognize my already-established Zemanta account and not greet me as MARKO!Zemanta calls me someone else on first start-up in Windows Live Writer

The Zemanta preferences open up in my browser, so I am not that confident that this creates any recognition in the plug-in.  Going to the preferences page does give me more opportunities to customize Zemanta for my use though, and I browse around in other material that I had not dug into before.

On the preferences page, I logged-in properly and these preferences should work for me.Updating my preferences on Zemanta does not seem to have a direct effect on the WLW Plug-In.

I didn’t notice anything different back on Windows Live Writer.  Zemanta is updating and showing me recommendations on today’s hot topics.  Zemanta is also offering links for phrases that I have entered in the text above.  I am still unsure that it is recognizing my account preferences. I don’t see my Flickr recommendations in the Media Gallery, for example.

I also have some concerns for how images are handled.  I won’t know about that until I post using some Zemanta-sourced image.  This post will test that and confirm how well Zemanta in Windows Live Writer works with in the resulting Movable Type post.  Here is a Zemanta-sourced image obtained by clicking it in from the plug-in Media Gallery:Image representing Zemanta as depicted in Crun...

Additiional Category Hierarchy as of 2010-08-22

After extending the category structure for Centrale and sites, I decided to seed the web-development category in the same fashion.

Here the category for retired web-development categories is the {obsolete} sub-category.

I figured that as long as I was busy seeding categories, I might as well start this set as well.

One small problem.  Although I had gone into the Movable Type administration panel for the nfoCentrale Status blog, I could not do anything that had the expansion below the web development category show up in Windows Live Writer.

I tried all of the usual things, including having Windows Live Writer update from the blog theme, having Windows Live Writer re-publish he entire blog, and finally rebooting my computer.

Of course, if I had noticed the refresh button on the Windows Live Writer pop-up for the available categories, something I had done just the day before, I would have the problem solved, as the image demonstrates.

I also finally realized that I don’t have to wait to have something meaningful to say simply to seed each new category.  I can do it with this announcement.

There will be more about what these are when I have more to say about their role in the development of the web sites since the initial creation of InfoNuovo (and just slightly before).

The infonuovo.com domain was registered on February 2, 1999, as part of my creating a web hosting account with VServers.  VServers was a small but helpful organization that would eventually be merged into HostPro and then Interland.  Ultimately, InfoNuovo was served by web.com.  What I noticed over the course of time was the reduction in the accountability of the service provider as well as my becoming an increasingly smaller fish in a prodigiously growing pond as web hosting companies consolidated and expanded.  Typically, every time I needed to use an administrative interface for something more involved than just using FTP to my hosted-site directory, I would find that it had changed.

The original appeal was the support for FrontPage Server extensions.  This was accomplished initially on a Windows NT-based hosting service. 

I never used server-side FrontPage Server extensions directly.  I rapidly adjusted to using a development web server that I ran locally on my own machines, with FTP used to populate the public, hosted web site.  This was also more appropriate for dial-up access to the server for updating, something I would learn to do from Italy later on.

Here is what the WHOIS for InfoNuovo still looked like in 2001, with (later-corrected) out-of-date contact information.  InfoNuovo, my business name, was registered at the Mountain View address in 1999 when this started.  By 2001 I was living in Washington State and using the NuovoDoc business name.  InfoNuovo was too close to the name of an already-registered Washington State business that was involved in computers systems work as well. 

Registrant:
InfoNuovo

   316 Escuela Avenue, 
   Suite 40 Mountain View, CA 94040-1819
   US

   Domain Name: INFONUOVO.COM

   Administrative Contact, Billing Contact:
      Hamilton, Dennis
 infonuovo@EMAIL.COM
      InfoNuovo
      316 Escuela Avenue, Suite 40
      Mountain View , CA 94040-1819
      +1(650)938-4584 (FAX) +1(650)567-9846
   Technical Contact:
     
Hostmaster, Interland domreg@INTERLAND.COM

   Record last updated on 14-Mar-2001.
   Record expires on 09-Feb-2003.
   Record created on 09-Feb-1999.
   Database last updated on 23-Dec-2001 22:29:00 EST.

   Domain servers in listed order:

   NS1.NAMESERVE.NET
207.159.128.3
   NS2.NAMESERVE.NET
207.159.128.11

 

I stopped operating as InfoNuovo near the end of 1999.  I held onto and continued to use infonuovo.com as an anchor site for several years.  Part of the reason was the number of links from external web sites that continued to reference infonuovo.com, especially for access to infonuovo.com/odma, the original anchor for http://ODMA.info. 

After renewing the domain at least two years longer than I needed to, I I ceased renewing my lease on the infonuovo.com domain, allowing it to expire on February 2, 2009.

[update 2010-08-23T04:14Z I realized, when posting about additional web-development categories, that I can seed the unseeded subcategories simply by using the seeding post: this one.  This repost is strictly to accomplish that.]

As part of the nfoCentrale anchor-site stabilization, I am seeding all of the new categories I have established.  This will cause each category subfolder to be created and populated as part of the nfoCentrale Status blog structure on the hosted site.  I will then bring those folders under the construction-structure management of the nfoCentrale anchor site.

I have been quietly repaving the nfoCentrale anchor, as part of bringing a systematic sites cleanup and repaving under a single coordination point.

I will also be experimenting with alterations of Movable Type templates here and on Spanner Wingnut in preparation and confirmation of the stages to be undertaken in the systematic re-animation of my now-dormant blogs.

Although this seems to be a diversion from the task of restoring blogs, and I have this pent-up urge to be posting anew on them, this repaving work is crucial for providing me a place where I capture my experience and arrive at a guide that I can follow systematically.  This is also a precaution against any future situation where I need to do more of this, whether because of upgrading to new releases of Movable Type, porting to a new hosted site, simply adding more blogs, or integrating with new, now-unanticipated content-management facilities.

In preparing for the Centrale Retirees I learned that when there are duplicate sub-category names, as with Centrale/{retired} and sites/{retired}, posting via Windows Live Writer will publish to both {retired} sub categories no matter which branch I select it from.  To repair that, I avoided duplication by having Centrale/{retired} and sites/{retirees}.

I renamed the sites sub-category but retained the status/sites/retired-1 location.  By republishing the site, the duplication disappeared, which is useful to know.  This was all done with the Movable Type administrative interface via my browser, so that I had the necessary fine control to eliminate the duplication.

Although the site/{retirees} category has the same function as that explained for Centrale/{retired}, there probably won’t be so much retirement going on.  Still, if some site becomes completely stabilized and no further posting is expected, it will be useful to freeze its status.  Whether I move it to emeritus status here in the {retiree} category or not remains to be seen.

The Centrale/{retired} category is being furnished as retirement quarters for previously-active Centrale subcategories.

That may seem a little strange but it works.

A category is implemented under Movable Type as a subdirectory of the blog.  Nested categories fit into nested subdirectories.

I want to capture historical information about the various components of Centrale that go back to even before there was a LAN and workgroup named Centrale to tie them together.

While I’m doing that, I will use the expanded categories that go back to the beginning of my adventure with personal computers.

Later, when I’ve captured and said enough to suit my purposes, I will remove the category from use.  That won’t delete the pages created under those categories though.  And even though the category structure will be streamlined and simpler to navigate, they retired categories will still have their pages available.

This {retired} category will tie those category-specific subdirectories into an index page here as their categories achieve emeritus venerability.

I am seeding all of the new categories with posts so that they will be included in my backup procedures and archived on my development web site from now on.  I can then populate them further as time permits and the spirit moves me.

The subcategories under centrale and sites have been expanded extensively.

The expansion serves two purposes:

    1. The subcategories that I will be needing for a while will have their folders created on the site for backup and maintenance.  They provide places to link to.  They provide places for status about all components of nfoCentrale, including previous components that are now retired.
        
    2. I can capture historical information about the development of what is now nfoCentrale, by category.

To prevent the categories from being too cluttered in the long run, information about retired nfoCentrale components will eventually be removed from active categories but will remain reachable from the {retired} subcategories under centrale and sites.

About this Archive

This page is an archive of entries from August 2010 listed from newest to oldest.

July 2010 is the previous archive.

September 2010 is the next archive.

Find recent content on the main index or look in the archives to find all content.

Pages

OpenID accepted here Learn more about OpenID
Powered by Movable Type 4.34-en