MartinCleaver replies on " Some ideas to improve BlogPlugin ":

Default naming of topics is a common pattern: Socialtext, Note Studio and Confluence all handle it by defaulting to the time of posting. Not only is this unique it is somewhat meaningful.

However, using the time also raises the spectre of clashes and TZ ambiguity: the user would need to coerce the times into a single TZ. And where there are multiple TZs for multiple users no one is going to be particularly happy.

Where there is a posting headline then using this is potentially more meaningful, if it can be made unique. Wordpress allows the user to define the URI structure, allowing compositions such as date + user + title

TWiki's "Add Page" javascript mechanism (not used by NatSkin) has "Coerce a Valid Page Name" was based on the TWikiRegistration form for creating a username from the user's First & Last name. That needs to be made redundant, however, with an implementation also running server-side, if users who don't have javascript are to be served.

Creating such a server-side implementation of this "Coerce a Valid Page Name" would also go a distance to serve BlogPlugin: the coercion could happen primarily on the client side with server side back up.

MartinCleaver replies on " Back-blogging wiki entries ":

So its not a case of TWiki:Codev.ImplementBeforeTheCompetition...

MichaelDaum replies on " Back-blogging wiki entries ":

How about to using PinkBack for exactly that. You could write topics from within your own blog or wiki, refer to a TWiki.org topic and get that inserted there on a dedicated corner of the page.

But that means TWiki.org topics must become pingable which is not very likely to happen any soon.

If we had a PingBackPlugin we could have networks of wikis.

MichaelDaum replies on " Some ideas to improve BlogPlugin ":

Having cooler urls for BlogEntries would be nice. But I want them to be created automatically. Other TWikiApplications add the ability to decide yourself on the name of the new topic to be created. That's not what I want to do. As your above example supposes the topic name can in principle be derived from the headline or topic description of the BlogEntry, BlogComment or BlogPage. The pattern how to derive and which information to take is quite application-specific. This needs more rethinking.

The standard Xx10 mechanism is the obvious thing to do for now. The BugsContrib does that too.

MichaelDaum replies on " Some ideas to improve BlogPlugin ":

Martin, we had that for ages. We discussed that via email. You keep asking me on IRC and you always come up with the same arguments again, presenting them without my weak excuses. Have you forgotten you what I emaild you in response? Last thing I remember that we did start to compare different desktop applications and what their terminology is. So, sigh here is my response again on NatSkinDev. Please feel free to extend the survey there with counter examples.

MichaelDaum replies on " Martin starts Blogging... with BlogPlugin ":

Hope to see your site ``personalized''.

MichaelDaum replies on " Aghh. I just lost another posting to BlogPlugin ":

Wbniv reported the same thing and I made the same painful experience just recently after typing for nearly an hour.

This is almost certainly not related to the BlogPlugin. The only thing that we can do is to remove as many of the mandatory flags as possible.

I recasted Item2314 to "Engine/Urgent".

This is a showstopper .

MichaelDaum replies on " Wikis in the Enterprise: Democratizing and Directing Collaboration and Content Management ":

I tried to really get to this document but failed so far. After registration they've sent me the credentials but I still got no access to the compartment this document is stored in. Quite annoying.

replies on " ":