The Ghost team has pushed out a release to the project's some-6,000 Kickstarter backers. Ars Technica staffer Lee Hutchinson reviews and posts in Ghost.

The double-paned Markdown/HTML view looks a lot like Ode's EditEdit, right?

According to the Ghost blog, while the code is only going to Kickstarter supporters right now, there will be a public release in the weeks ahead.

Does the release announcement include the names of every one of those 6,000 people? I think it does.

http://thoughts.smallpict.com/2013/09/20/bloggingIsDifferentAndNewTheseDays

Warning: The AMD Catalyst 13.9 Linux video driver was on the site this morning but has disappeared since then. As of 4 p.m. Pacific time on Sept. 19, 2013, it has not yet reappeared. AMD, it's your move.

Before the driver disappeared, here is what I wrote:

Now that the 3.11 version of the Linux kernel is available on my Fedora 19 system, AMD has released a new version of its closed-source, stable driver, version 13.9, that brings support to ... the 3.10 kernel.

Not that I haven't been running the 13.6 (suspend/resume worked) and 13.8 betas (suspend/resume didn't work in 13.8 beta 1, not sure about beta 2), because I have.

You can download the new driver here, though I recommend NEVER installing from what AMD provides and always, ALWAYS using a version packaged for your distribution, which for Fedora means the packages provided by RPM Fusion.

Running Fedora and needing AMD Catalyst for working 3D graphics means willfully ignoring new kernels that aren't yet supported and accompanied by a new kmod-catalyst package. That's what I'm doing with the new 3.11.1 kernel that moved into Fedora 19 today. I won't install a 3.11 kernel until there's a corresponding kmod-catalyst package from RPM Fusion to go with it. And given that this new 13.9 release of AMD Catalyst only supports the 3.10 kernel and isn't yet in the RPM Fusion repository (which, given the fact that it was just released, I totally understand), I'll wait for the next kmod-catalyst to roll onto my machine and once again test suspend-resume. If it works (like it did during the brief 13.6 beta window), I'll be of a mind to stick with the 3.10 kernel for a good long while.

But if suspend-resume doesn't work with the combination of Linux kernel 3.10.x and Catalyst 13.9, it'll be back on the beta train until AMD decides to better-support the GPUs it makes, including my AMD Radeon HD 7420g.

Potential problem: I just checked the AMD page, and the new driver is (hopefully temporarily) gone.

There's still more to do, but I have enough hacks roughed in to flip the switch on the responsive version of my Ode site.

Thanks to Hans Fast who did most of the work on this here and here.

I'll detail what changes I made to my main Ode theme's HTML and CSS in a near-future post (which I'm already working on).

Responsive design is a big thing for me. It was easy to do in Ode -- and easier thanks to hints from Hans. I still have quite a few elements in Ode's main Logic theme to work on, and I'll knock them down as I get the time to do it.

Thanks once again to Hans Fast for his code, and to Rob Reed for shipping such good code to start with in Ode.

Recent changes:

I tried to code the CSS so the "desktop" layout is what you see in tablets as well. I continue to think that most web sites, including this one, look pretty good on the standard 10-inch tablet (like a full-size iPad), and having sidebars pushed to the bottom is unnecessary on those devices.

So I simplified part of the CSS to make the site stay "normal" until 400px in screen width instead of 800px.

I also made some changes in sidebar behavior. When the screen is small, the sidebar not only goes to the bottom of the page, its text goes from float: right to float: left, and the colored image overlay on the sidebar disappears.

I've been meaning to roll the rest of the posts in my FlatPress blog centered on Debian into this Ode site.

In the past, I've moved quite a few of them in here, but there were about 30 or so from the early days of the FlatPress blog that I had yet to move.

I plowed through about 20 today and have 17 more to go. Rather than taking HTML source from FlatPress, I'm copy/pasting regular text from the FlatPress blog into text files and using Markdown to re-create the links and bolding.

Read the rest of this post

Through the Ode forum, I just found Jim's graphic design and history site, Codex 99 Annex.

It's nice to see what you can do with Ode when it comes to design. (hint: just about anything).

This guy lost it all when he didn't backup a decade of web content: http://www.craiglockwood.co.uk/

Level of difficulty: Medium to high

Description

A utility that will crawl the Ode documents folder and create a list of links by year and month that can be used in the sidebar of the blog as an archive. Another possible archive listing (which I had in Movable Type and quite liked) is a single page with a list of every individual entry by title.

While this could be done with its own Ode addin, this functionality could be folded into the Indexette addin. In this case, the "reindex" call would also build the year/month and full-archive index HTML, which could then be inserted in the appropriate places in the theme file (for the year/month index) and a single "archive" page for the full archive.

Discussion and questions

Am I missing something, or is this an easy project? It's possible to reuse code from Blosxom, PyBlosxom, or just about any blogging system that offers this functionality.

I love Pencil Revolution. That is all.

Rob and I have been talking about licensing a bit over the past month or so, and I'm listening to a lot of discussion and debate about software freedom and licensing courtesy of the Free as in Freedom podcast.

So I decided to license the content of this blog. It's possible to use a software license like the GPL for written, "creative" content, just as it's possible to use a license like those from Creative Commons, which were written with "creative" works in mind, for software.

But since what's here is, for lack of a better word, prose, I am choosing a Creative Commons license: the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported (CC BY-NC-SA 3.0) license, the full text of which you can read here.

It means you can use what you see here for non-commercial purposes if you attribute it and share it under the same (or a like-minded) license.

If you do want to use what you see here in a commercial (read: moneymaking) setting, contact me at steven (at) stevenrosenberg (dot) net. We can probably work something out.

What licensing is (and isn't): A lack of a license on your code or content -- seemingly giving no rights -- doesn't "protect" it more than having an actual license. Nor will a license in and of itself keep others from doing things with your content that are in violation of the license.

As Bradley Kuhn often says on Free as in Freedom, sometimes enforcement is required. If you find somebody violating terms of the license under which you have made your work available, you might have to get out there and do some enforcement. The license gives you a legal framework under which to do that enforcement.