Showing posts with label wordpress. Show all posts
Showing posts with label wordpress. Show all posts

Friday, December 22, 2023

Retiring domain associated with a DreamHost WordPress site - migrating site content to a new domain

I recently decided not to renew a domain managed and registered with DreamHost. That domain had an associated WordPress site. This is the sequence I followed to preserve the content of the site.

  1. Turned off renewal for the domain (domain_old).
  2. In WordPress for domain_old I exported the site as a XML file which I downloaded and archived.
  3. In DreamHost control panel Manage Websites I clicked "new website". This let me add a subdomain to one of my existing domains.
  4. In DreamHost control panel Manage Websites I clicked on domain_old and scrolled down to entry for Domain. That says "change your WordPress site to run under a different domain name". I chose the subdomain I created earlier. This took about 5-10 minutes to run.
  5. When I then visited the subdomain I created the WordPress site came up.
The process only took a few minutes the first time I tried.

Saturday, February 16, 2019

Migrating from Blogger to WordPress ... again ...

I’ve been contemplating migration to WordPress for almost a decade, but Google kept Blogger good enough to keep that headache at bay.

Alas, the days of good enough are ending. Google is removing their photo management API without recourse. They do support posts with images, but only by using their web interface. It’s a concrete and undeniable sign that Blogger is either dead or going to a bad place.

I though I’d migrate first to wordpress.com then to my Dreamhost open source wp install, but via Twitter Daniel Jalkut tells me he got better results using the open source importer directly.

I’ll do a dry run on one of my big blogs first. The URL won’t change but I’m sure feed subscriptions will have to be redone (ugh).

Update 2019/04/06 - results of the pipdig import process

I tested the Dreamhost free version of the pipdig importer from a Dreamhost wordpress (open source) blog. The results can be seen here for the moment, I’ll eventually delete them. I found:

  • It doesn't remap internal links. This is a big disappointment. Links continue to direct to blogger, once that account is gone they will be invalid
  • There’s no option to migrate images that I can see.
  • It missed at least 4 posts from the source blog — specifically from early on. No idea why and it suggests more are missing.
  • It does copy drafts over.
  • It requires a LOT of access to your Google account! If you use this utility I suggest creating a new google account, give it access to your blog, then after the import destroy it. 
  • The paragraph breaks are missing - line feeds vs <p>. This is an ancient Blogger problem with MarsEdit; a legacy of the original sin of English language text formatting end-of-line standards. I think Blogger is mostly to blame.
  • Images were not relocated locally, they remain at their original locations.

Pipdig is better than nothing, but I’m going to try wordpress.com’s import tool next. I wonder if a better solution wouldn’t be a static site that I could archive on my personal web server, then do a web server redirect to handle the links. For now I’m still on Blogger. The porting experience reminds me of the impossibility of leaving Apple’s defunct Aperture photo management app.

(As I write this the wordpress import is processing - result should eventually show up at gordontest.tech.blog temporarily, but we’ll see if it works. It’s taking a long time.)

Update 2019/04/06b

Well, that wordpress migration didn’t go so well:

Your site has been suspended from WordPress.com for violating the Terms of Service. If you believe this was done in error, please contact us as soon as possible to have the suspension reviewed….

I sent a contact inquiry, nothing yet.

Sunday, March 11, 2018

Error in Dreamhost WordPress one-click installs - missing code in .htaccess causes 404 errors

I’m far from a WordPress expert. I’m not even a WordPress fan — it’s too complex and powerful for what I do. That complexity means it is also very vulnerable to attack.

So take what I write here with some doubt.

As best I can tell the default Dreamhost One-Click installation of WordPress has an error. At least it did for me. My hpmtb.org site was giving 404 errors. I installed the Redirection plugin and it wasn’t doing anything.

A blog post had a fix that worked for me. I used Transmit for macOS to open the install folders .htaccess file and added this code:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

The 404 error is gone now and I suspect the Redirection plugin will work if I need it. I have a hunch that using “pretty permalinks” (not the default of “id=“) might also fix this file — based on some documentation here

WordPress uses this file to manipulate how Apache serves files from its root directory, and subdirectories thereof. Most notably, WP modifies this file to be able to handle pretty permalinks.

This page may be used to restore a corrupted .htaccess file (e.g. a misbehaving plugin).

Did I mention that WordPress is too complicated?

Tuesday, August 25, 2015

Mac web authoring for non-experts: My choices 2015.

In the beginning we wrote web pages in BBEdit and we FTPd them to a NeXT box.

Things progressed quickly. Almost two decades ago, when Microsoft FrontPage 97 was released and Macromedia created Dreamweaver, there were many powerful Windows applications for creating largely static web pages - with dynamic reflow based on HTML tables [1]. Operating systems, like Windows 95, shipped with a native web server. Netscape added Composer, fulfilling TBL’s original vision of the web as authoring environment. Non-technical users worked with server based systems, ultimately producing millions of web pages on sites like GeoCities [3].

Technology has moved in odd ways. There’s nothing quite like mass market FrontPage today, though Sharepoint Designer/Wiki came close and SeaMonkey survives. Dreamweaver is the strongest survivor of the original era, but it has evolved into a high end tool leased for $20 a month. I don’t think there’s a practical way to move Dreamweaver content to another platform, so adopting Dreamweaver is a deep commitment to the Adobe platform.

At one point I thought the Wiki would fill the vanishing mid-market niche [2], but Wiki solutions seem to have stalled out - much like WebDAV technologies. iWeb/MobileMe came and went quickly - an early sign of Apple’s decade (so far) of dysfunctional application development and fondness for destroying customer data.

Today developers hand code web sites in Coda, a programmer’s tool not so different from the BBEdit we started with. Other experts use Adobe's deep lock-in solutions, from Dreamweaver to Muse ($15/month) or open-source server-based WordPress (Less technical users some might use Blogger in a similar way).

For non-experts Weebly’s small business oriented server side authoring platform is an option, but it’s another deep data lock commitment to one vendor. Google Sites, amazingly, is still around, but focused on intranet solutions.

There are two longlived Mac desktop products both sold for $80 on the Mac App Store: RapidWeaver (presumably inspired by DreamWeaver) and Sandvox. I’ve tried both in the past, Sandvox more frequently than RapidWeaver. Neither product supports wysiwyg table authoring. RapidWeaver was last updated in January of 2014 and has three stars in the Mac App Store; it may be in maintenance mode. SandVox was last updated in April 2015 and has recently added a hosting service (revenue stream!), it has 4-5 star ratings. It’s App Store page still references iPhoto and Aperture however. Of these two I think Sandbox is more likely to make it to 2017.

It’s rarely mentioned anywhere, but TextEdit will export to well formatted HTML, and it even has table support (since 2006 at least). You can embed images and export — but only in single file “webarchive” format. As a simple page editor it’s not too bad, and it’s as standard as anything is these days, but the image limitations are a killer. (I suppose one could similarly author in Pages then view in Pages/web and export the code.)

Similarly one could author in Blogger or WordPress (example: free wordpress.com blog) wysiwyg mode, switch to HTML mode, and paste the HTML into a text editor (Coda?) for FTP upload. Or I could author in MarsEdit (as in this post) and similar export the HTML view as a file. Nisus Express and Pro both include HTML import and export; I don’t know how well their table export works and if embedded images are exported. When I last tried them years ago they weren’t a practical HTML authoring solution.

Google Docs work quite well for sharing and editing online, but they’re not useful for a root (www) web document. Very proprietary of course, but in some ways Google Docs are the closest thing we have today to the original view/edit vision of the www. I haven’t tried sharing iCloud Pages web sharing, but it seems like it would work similarly; it also can’t serve as root page of a web site.

Of the options today, what makes the most sense for me? There aren’t a lot of options on the table, so things should filter quickly with a few constraints:

  • I’d like to avoid dying products.
  • I want to be able to produce a reasonably pretty looking site without a lot of effort (iWeb pretty at least).
  • I’d like a solution that works with Dreamhost and it’s (typical) constraints on www/domain mapping [4]. 
  • I don’t want to sell my soul to Adobe. 
  • I’m not a developer and web authoring isn’t my profession. 
  • I really miss wysiwyg HTML tables and table based layout, but they are clearly gone. Still, I’d love basic table support.
  • I’d prefer to avoid hard data lock.
  • I’d like something that managed a site and updated links when I rearranged web page relationships or renamed pages.
  • I’d like to avoid major malware and security issues. Static sites are very nice that way.
  • Mac (or course) or Safari if server based.

Based on my review of the options, and applying my constraints, it’s easy to see that my best choice is ….  is …. Ok. Nothing survived the constraints. It’s easy to see why I’ve been struggling with this for about 15 years.

If I relax a few constraints I think my least bad options are WordPress (free) and Karelia Sandvox ($80). So I’m going to try both of those — and maybe, if only to close the long loop, Coda too.

Am I missing anything?

See also

- fn -

[1] I think we took the wrong road when we entirely substituted CSS for dynamic tables; no modern tool approaches the table management power of FrontPage 98. Perhaps this happened because it was insanely difficult to manage table authoring by hand, it was really a job computers did better than humans.

[2] Speaking of vanishing mid-market, remember when personal finance software was big? Intuit is trying to find a buyer for Quicken and its future looks quite bleak.

[3] The immolation of GeoCities, echoed on a smaller scale with the 2012 death of MobileMe’s iWeb based web pages, should not be forgotten.

[4] The odd handling of the www domain is, I think, a legacy of early net development. It is a pain in the butt.

Update 4/29/2016

Sandbox can be used free for up to 5 pages. I gave it a good try with a book site I’m working on. The lack of both drag-and-drop placement and tables made me give up on Sandbox. 

Of course RapidWeaver doesn’t do tables either, but I’m going to try it anyway.

It’s obvious that tables are insanely hard to implement; I wonder if CSS support made the challenge even greater. I wouldn’t mind an editor that handled CSS tables, but no tables at all reminds me of all the software functionality and value we have lost over the past 15 years (yeah, Apple Aperture, I miss you.)

Oh, and vendors, please stop trying to tell us we don’t really want tables or that HTML tables are fine. You are just insulting our intelligence. Just say something like “tables are extremely hard to do …”

Wednesday, October 08, 2014

Wordpress spam comment hole and fix

I had comments turned off in Gordon’s Shares [1], but on a rare visit to my admin Dashboard I found 15,000 spomments in the Pending queue [2]. They looked to be all spam, there were several from today, and they were largely related to old posts.

That was a surprise. The blog has comments disabled, there’s no way in the UI to create a comment; I presume the attackers were leveraging an API bug. So in addition to confirming the Commenting was disabled, I also restricted the (disabled) commenting to registered users (which would be me). That seems to have fixed the problem.

[1] Mirrors/archives [1] my pinboard shares. Current setup is a bit different than 2012:
[2] I used the Delete All Comments plugin to clear out the 15K — it transiently tied down my database but it worked.

Update 10/9/2014

If you have unchecked Allow people to post comments on the article on the Options > Discussion panel, then you have only disabled comments on future posts.
This is the kind of thing that gives open source a bad name -- and it doesn't say much for the tech journalists who praise the WordPress organization either. Looks like a great way to do a DOS attack on a WordPress site -- fill up database storage with spomments.

Happily my workaround works perfectly.

Saturday, April 13, 2013

WordPress attack - lessons from my personal security review

This week there's a  brute force password attack on WordPress sites. That inspired my security review, here are a few things I learned doing it:

  • I again appreciated the FileMaker database I've used since 1997 to track my net credentials. I dump data from it to a now dated version of 1Password, but it's hard to beat the ease of searching and editing my own repository. It lives on an encrypted disk image on my local machine.
  • It's easy to end up with orphan WordPress instances. I have one on Wordpress.com and two on my Dreamhost account, but I only use http://www.kateva.org/sh/. It archives my Pinboard/App.net shares; one day, if I figure out how to do it, I may append my old Google Reader shares (json).
  • I had a strong password on the wordpress.com account, but only pretty-good on my other two and they had the same pw. I upped both to very strong but still typable. I will have to review how IFTTT connects to kateva.org/sh -- obviously there are big security risk with many uses of IFTTT. 
  • I'd been keeping my WordPress blog software current (Dreamhost makes that easy!) but not the plug-ins and themes.
  • I'd changed a theme on one blog recently, and today I learned it didn't include a log-in link! I was briefly shut out, but a bit of web research turned up kateva.org/sh/wp-admin.

The most important thing I learned is that it's not trivial to safely delete a self-hosted WordPress blog. Yikes! No wonder there are lots of vulnerable old blogs lying around for the taking. WordPress.com blogs have a delete tool, but not self-hosted sites. Things can get nasty here -- two WordPress blogs can share the same database, so deletion must be done carefully. Reading some Google hits this is a very unsolved problem with lots of confusion.

We need a fix WordPress.org and we need it very soon. Dreamhost, you could help too.

Wednesday, October 10, 2012

Microblog flow - an update

I've revised my microblog flow, built on IFTTT / My Recipes, pinboard, wordpress, and app.net. FWIW, here's how it works for today:
  • all pub pinboard shares go to a dedicated wordpress blog that's google indexed
  • pinboard 's' tag shares go to app.net (intact) and twitter (often truncated)
  • app.net 't' tags go to wordpress and twitter with link back to app.net
In general I'm deprecating twitter and favoring app.net.

Sunday, July 08, 2012

Pinboard and IFTTT - blog, task, share

Despite concerns about too many moving parts, I'm still using Reeder, Pinboard and IFTTT as my core information process workflow. I just added two more IFTT actions based on single character Pinboard tags. The current set is:

I enter the one letter space separated tags when I share to Pinboard from Reeder.app for iOS and OS X, or from Google Reader. Many posts have two or three tags.

Tuesday, June 19, 2012

Pinboard and IFTTT - credential outage

I was quite pleased with my jury rigged replacement for my long lost Google Reader Shares. (Few remember them now, the net years have passed like leaves in the wind ...)

I had IFTTT tracking Pinboard posts and creating Tweets and posts to an archival WordPress blog. The Pinboard posts were largely created from the essential iOS Reeder.app and, less often, from Google Reader and Reeder.app for OS X.

It worked. I was happy. I started composing the celebratory blog post and explanation when...

Yes, you can guess. It fell apart.

I don't know why. Pinboard had blocked Superfeedr around that timefor aggressive crawling, but this turned out to be a red herring. IFTTT doesn't use Superfeedr.

IFTTT hasn't gotten back to me, but they're a free service so support is not predictable.

Well, I did know this was going to be a fragile and shortlived solution! I particularly didn't like that IFTTT is "free". I'm now looking for an alternate solution I can build around Reeder.app and Google Reader with Twitter and WordPress as outputs.


Update 6/19/2012: I didn't hear back from IFTTT support, but Pinboard convinced me to dig deeper there. I tried creating a new task but that also failed. The clue was in a screen I'd not visited, the Channels screen.

There I found this icon:
I edited it, reentered my credentials, and it's no longer offline. Now I'll see if it starts working again.

What happened? Well, there are two possibilities, and without help from IFTTT I don't know which is true. One is that Pinboard was unresponsive and IFTTT took the channel offline, but then never restarted it.

The other, which is at least as likely, is that I changed my password to Pinboard (I do that sort of thing) and that any email notification of subsequent credential failure was either misread, mislabeled, or filtered out. IFTTT doesn't use OAuth or similar service with Pinboard, so it needs my credentials to work. If that was the problem then IFTTT might be able to come up with a better way to notify users. For example; there was nothing on the IFTTT task screen to tell me a channel was offline, and when I manually triggered my tasks there was no error message.

Update 6/19/2012b: Fixing the Channels problem did the trick.

Thinking this over, why does IFTTT need my Pinboard credentials anyway? They are reading from a public feed, not writing to my account.

Update 6/22/2012: The latest IFTTT rev has much improved diagnostics. 

Sunday, January 01, 2012

WordPress doesn't have a built-in table editor

The WordPress visual editor doesn't include tables. Neither does Blogger of course, nor, for that matter, MarsEdit.

FrontPage had terrific table support in 1995. WindowsLive Writer has decent support now. Otherwise, web tables doesn't get a lot of love. RapidWeaverdoesn't do tables. Sandvoxisn't any better and neither is Apple's abandoned iWeb.

SeaMonkey inherits the table technology built into Netscape Composer in the 1990s. TextEdit does tables (!) and (unlike Pages) will export HTML. It's hardly a web page editor though.

DreamWeaver does tables - and costs $400 (though I qualify for the $150 teacher edition).

It's too bad. HTML tables are really brilliant. I'm guessing implementation is very expensive especially when tables are combined with CSS; the market doesn't support this level of complexity.

Wednesday, December 28, 2011

Sharing and annotation: Instapaper's supporting apps

I haven't found a replacement for the rough annotation-share-feed ecosystem that had grown up around Google Reader Social (RIP). I've given up, for example, on using Twitter as a Reader Social replacement.

Yes, I miss Google 1.0. I even miss Microsoft these days.

So I'm continuing to explore the pieces of the post-Google world; trying to see where this micro-market may go. This is poorly tracked territory, but today I came across an unexpected guide in the Instapaper: Supporting iPhone and iPad Apps page.

Instapaper has an ecosystem, and although it doesn't have a feed, it will post to Tumblr, Twitter and Pinboard. Tumblr has a feed (barely), Twitter can be turned into a feed (awkwardly) and Pinboard has a feed (and, mercifully, it's not free).

So what can I do with these pieces? Can I archive the output of Pinboard as WordPress posts?

I'll find out.

See also:
Update
  • I tried Instapaper's bookmarklet, but it hangs in Chrome with a "saving" status in the tab.

Wednesday, November 30, 2011

Martin's WordPress plugins

I think my microblogging experiments will likely end with WordPress. It's a complex world to learn however. For one thing, there are hundreds of "plugins" available for WordPress, and no obvious way to tell the useful from the disastrous.

So I'm grateful to Martin Steiger for sharing the ones he uses on different sites ...

Essential:

- Chunk Urls for WordPress
- Germanix URL (probably not necessary for you)
- WordPress Database Backup
- WP Super Cache

Essential for sites with comments on:

- Akismet (default WordPress plugin)
- Antispam Bee (in addition to Akismet)
- Subscribe To 'Double-Opt-In' Comments (if you provide comment subscriptions)

Useful / additional features:

- Better Delete Revision
- Better WordPress Recent Comments
- Comment Form Quicktags
- Comment Whitelist
- Contact Form 7
- Country Filter
- Exclude Pages from Navigation
- Get Recent Comments (depreciated)
- Google XML Sitemaps
- Intypo
- Limit Login Attempts
- No Self Pings (maybe no longer necessary)
- Optimize DB
- Posts By Tag
- WP Minify
- WordPress Popular Posts
- Yet Another Related Post Plugin

On the way out:

- AbsoluteRSS (no longer necessary)
- AntiVirus (too many false positives)
- Flattr
- Google Analyticator
- Google News Sitemap
- PubSubHubbub
- Really simple Facebook Twitter share buttons (sharing buttons slow down any site)
- Save Post. Check Links.
- RSS Cloud
- WP SUP

On my latest WordPress-based site, steigerlegal.ch, I use as few plugins as possible. Some are essential and some are needed if you wish certain features. In any case, I carefully read the reviews on WordPress.org and I try to use only plugins in active development. I have trust in some reputable developers such as Sergej Müller. I cannot review each plugin from A to Z but I never get plugins from dubious sources. Up to now, I have never had a security problem with any of my WordPress-based sites (although being careful cannot rule such problems out but it's a start).

Thursday, November 24, 2011

WordPress.com - Blogger Import

I'm continuing to examine exit strategies from Google 2.0 as I prepare to delete my TrueName G+ Profile [1].

Other than Gmail and Google Apps, my strongest Google Connection post Reader Social is Blogger. It hosts this post, for example.

I've considered Posterous and Tumblr, but both have fallen short. I think I'm going to have to learn the WordPress world, starting with hosted at WordPress.com and migrating to self-hosted.

I suspect that will take a while, but I'm starting to experiment, starting with an experimental import of tech.kateva. org to WordPress.com. It's not a complete import, draft posts are not included. For example, import dialog shows 3738 Gordon's Tech posts, but that omits 467 draft posts. For Gordon's Notes it shows 5754, so 1277 draft posts are omitted.

Wordpress also supports import of a Blogger Atom export file. I don't know if that will include Drafts, but I may experiment with it.

I can live without the draft posts, especially since I'll still have access to those drafts post-migration. I can plumb those that look interesting and abandon the others.

I don't expect any quick changes. In any case I own the domain kateva.org, so the changeover ought to be relatively invisible to my visitors (though I bet feeds will need to be revised).

If you'd like to inspect the results of the import, here's Gordon's Tech at WordPress.com - http://gordonstech.wordpress.com/. It's pubic but not-indexed with a temporary URL. The import went more smoothly than I'd expected, but it uncovered two surprises, both of which make me keen to move sooner than later ...

  • The "New" Blogger has no UI control to move to the earliest post. The "Old" Blogger UI has this.
  • Old Blogger doesn't show my 2003 Blog posts, it starts with 2004. WordPress imported them.

[1] I'll keep my John Gordon profile -- until Google deletes it as a TrueName violation.

Tuesday, November 22, 2011

Google's Omnibox and implementing Google search alternatives

Since I'm distancing myself from Google 2.0, I was receptive to Phil Bradley's alternative engine advice. I'm testing blekko (spam free) and Duck Duck Go (no tracking). I believe both are wrappers that enhance Google search.

Naturally, this experimentation works best with Chrome's Omnibox. It's very easy to add search engines; Chrome 'detects' an engine during a search site visit and adds them to it's collection. You can make any a default, and define a text shortcut. Type the shortcut in the Omnibox, hit spacebar, and your custom search is ready.

I made Blekko my default, and assigned it the letter 'b'. Google gets 'g', etc.

While I was at it, I defined a search string for one a Google custom search engine that searches my own content (web pages, blog posts): <http://www.google.com/cse?cx=009911250981951822495%3Aphjhjp-tdfa&ie=UTF-8&q=%s>. I already had one for searching my dev team's Rally project.

I can distrust Google and still appreciate Chrome ... right?

Update 11/24/2011: I ran a search on moving from blogger to wordpress on both Blekko and Google. Blekko wasn't just a bit better. It was immensely better.

    Thursday, November 10, 2011

    Tumblr - a Google Reader social replacement?

    I liked many things about Posterous. Alas, it doesn't seem to have a revenue stream. Recently, in a desperation move, they tried to become more like G+ -- they even dropped post tags!

    I also didn't care for the Posterous bookmarklet -- it pulled in too much of the source material.

    Today I'm visiting Tumblr. It and Twitter seem to be the new homes for many of the Google Reader Social Diaspora. For example, both Twitter and Tumblr are on Feedly's one click share panel, but Posterous is an extra click away. That extra click kills. (Unsurprisingly the new Google Reader really only supports G+ well.)

    Tumblr has the usual rich text edit options, but for microblogging I don't care too much about that. The bookmarket is impressive; better suited to microblogging than Posterous. The work of creating a Tumblr post from Feedly is very similar to creating a Google Reader Note/Share in the old Google Reader.

    Tumblr will create tweets for each post and they do provide a (proprietary) backup. However there's no secondary posting; one of Posterous' best features is that they'll create a replica post on Blogger and WordPress. I've seen mention of ways to repost into wordpress from an RSS stream, or import a Tumblr export file into WordPress, but nothing that looks rock solid.

    I like Tumblr, but I don't like the absence of an exit strategy.

    Still, it's ahead of Posterous - particularly because of the Feedly support (wish Reeder supported Tumblr!).

    Wednesday, November 09, 2011

    Sunday, November 06, 2011

    Posterous - a Google Reader social replacement?

    It's tough to replace Google Reader Social (damn you Google). I've been generating tweets from Google Reader, but the workflow is awkward on the native web app. Tweeting from the feedstream is a bit better with Reeder.app, but still not good enough. In any case, Twitter isn't what I want...

    Gordon's Tech: After the fall of Google Reader: Posterous, Tumblr and Zootool with Twitter on the side

    I'm looking for ...

    1. Bookmarklet that generates posts with title, url, excerpt and annotation.
    2. Must have an RSS feed.
    3. Must have a business model that involves me paying for services received.
    4. Either I have control over the data store or there's a way to create a read-only repository I can keep.
    5. Reeder.app support, so I can use Reeder.app for IOS and Reeder.app for Mac, avoid Google's miserable UI, and prepare for migration to another OPML store.
    6. Twitter integration so it tweets shares for those who are good with Twitter's limitations.

    There are GR.oldstyle replacements under development, but for now most of us are looking at Tumblr and Posterous as microblogging solutions. For unclear reasons I've been experimenting first with Posterous.

    Posterous does pretty well against my list...

    1. Big time bookmarklet with title, url, excerpt and annotation.
    2. RSS feeds, though these are being minimized in favor of (yes, you guessed) proprietary and closed pub/sub (like G+).
    3. Business model that .... ummm .... ok, so they don't have a way to make money ....
    4. Each Posterous post can generate a secondary post to my Dreamhost Wordpress blog.
    5. No built in Reader.app support, but good support for processing emailed content. Google Reader will 'send to' Posterous but I don't like how it works.
    6. Tweets on post.

    In addition Posterous will import from Blogger and Wordpress but not, alas, from an RSS feed (or I'd pull in my Google Reader Shares).

    Documentation is a bit hard to find, in fact, once you sign in to Posterous it's pretty much hidden. The Posterous 'faq' is a good start, but eventually I blundered my way to Posterous Help. It includes ...

    Overall, it's promising.

    Except ....

    Except for my #3 item. They're "free". I don't like "free". Autopost alleviates some of the risk, but free is bad. It's not good that just two months ago they went from a focus on microblogging to trying to imitate G+.

    See also:

    Update 11/9/2011: Thinking this over more. I see from comments on the Mashable 9/11 article that Posterous dropped tagging from posts. That's a real change in direction for a microblogging solution. I'm getting the sinking feeling that I would have loved Posterous in early 2010, but now their future is bleak. I'm not looking for a revenue-free small world version of G+. I'll review Tumblr next.
    Update 11/24/2011: I searched. And searched. And I can't find any way to delete a Posterous Space. I do see how to delete accounts, but not Spaces. If there really is no way to delete a Space, short of deleting an Account, then Posterous is a crazy-most-avoid kind of place.

    Sunday, October 30, 2011

    Components of a knowledge share solution

    Both at work and at home i've been studying our current toolkit for sharing knowledge. At work I'm supporting our software development, at home I'm looking at a ways to share knowledge to support lifelong education of persons with cognitive disabilities, including formal public education and home schooling. Naturally I'm looking at similar technologies in both environments.

    I've summarized a few of the components I'm thinking about in a table. I compared best of breed solutions to the best (not free!) suite I know of and to Google's offerings.

    Function

    Best of breed

    Atlassian Confluence

    Google

    commentary, notices

    Wordpress

    yes

    Blogger

    Q&A

    StackExchange

    no

    no

    collaborative hypertext document

    TWiki?

    yes

    Sites

    PDF, other

    FTP/HTTP server

    yes

    Docs, Share

    Calendar/event

    Google Calendar

    no

    Google Calendar

    Social, networking

    Facebook

    no

    G+

    Subscribe/notify

    RSS

    RSS

    ?

    Looking at this solution set it's clear that each has its advantages and weaknesses.

    Atlassian Confluence is the best integrated knowledge sharing and collaboration solution I know of. It's not at all free, but it's inexpensive for 10 or fewer users and anonymous users can have read only access. I give Atlassian extra marks for actually publishing an easily discoverable price list. Unfortunately I don't think I can get Confluence running at Dreamhost, my net hosting provider.

    Google, like Atlassian, is free for a small number of users and provides high performance anonymous access. Sadly, Sites is a great disappointment. On the other hand, I'm not impressed with any of the currently available open source wiki solutions. In many ways FrontPage 98 was better.

    Lastly the best of breed solutions have advantages in terms of data freedom and ease of switching providers or changing knowledge base ownership. An integrated approach can also leverage StackExchange -- the net's best technology for question/answer based information sharing. Likewise a Facebook Page can engage customers and provide a secondary notification solution in addition to RSS/Twitter.

    Any thoughts? Comments are most welcome.

    PS. I've been looking at collaboration technologies for about 20 years -- starting with BBS software and a long string of innovative solutions. The functional list would have had answers 20 years ago. What's different is that the audience today is vastly larger.

    Saturday, March 19, 2011

    Blogger's text editor: I make another plea for a rational approach to paragraph formatting

    It took considerable restraint for me to write this so politely.

    Please stop using div tags to define paragraphs - Blogger Help

    My blogs start around 2002, when Blogger used carriage returns to delimit paragraphs. They extend through the time that Blogger used <br> tags with or without hidden carriage returns.

    These days, with either the "new" or legacy editor, it's unclear to me what Blogger does. I only know that when I use MarsEdit, Ecto or the native editor I see pairs of div tags. This causes a mess. Depending on which editor I use paragraphs vanish or spacing doubles. If I open older posts with the editors I get no paragraph spacing.

    If I go into preferences I see:

    "If Yes is selected, single hard-returns entered in the Post Editor will be replaced with single <br /> tags in your blog, and two hard-returns will be replaced with two tags (<br /><br />))."

    Of course br tags are no longer used, so this language is simply wrong. If set it to "No" my old posts format incorrectly. To put it mildly, this is a mess.

    I would like Blogger to use tags to, you know, delimit paragraphs. I would like Blogger to convert older posts to use <p> tags. Please Blogger, stop using <div> and <br> to define paragraphs, it's not what they're made for.

    It's hopeless (yes, I've tried changing templates). Alas, I don't think there's really any way to move my blogs and keep any sort of reasonable formatting across 5,300 or so posts.

    See also: