DISQUS

eikonos: yeah, set "Details" as the "ViewAs" value in the config file, but there's no details to view right now... You can do "List" or "SmallIcon" though.

Dallows: I think you haven't discovered the right-click menu on the bar. As far as the config ... I made a tactical error and assumed that .config files would be associated with something. The simplest solution _at this point_ is to create a text file on your desktop and change it's extension to .config, then double click it (Windows will ask you what app to open it in: pick notepad or some other text editor). Once you've done that, you can try F1 again (or the right-click menu option). I'll fix that in the next release.

Well, I can only think of two reasons for OSX to run on generic Intel hardware:

# Price
# Performance

It would be so easy to do ... the real question is, WHY NOT? (Can you hear the cash box jingling?) Of course, I keep forgetting Apple's not about speed, and it's not about cost. It's about some sort of weird status symbol, it's about pretty whiteness, it's about branding ... and sometimes, it's about usability.

And there's not going to BE any middlemand to BIOSes because there's just no point in doing such a thing ... Microsoft _may_ release an EFI capable version of Windows XP 32 bit, if Intel's going to start making 32 bit platforms using EFI ... but honestly, I think everyone wanting to run Windows on a Mac is just going to have to wait for either Vista, or a 64 bit Mac.

Yes. In fact, you really *have* to have them both if you want to be able to target .NET 1.1, because the VS2005 IDE won't let you compile with the old framework, and the VS2005 visual forms editor uses partial classes, which are a C# 2.0 feature.

There's a "TextControl plugin":http://dev.wp-plugins.org/wiki/TextControl that allows switching post-processors per-post ... I'm not really planning on supporting that here ... Honestly, if you're using the rich-text editor, I don't see any reason to use Textile on those posts, and I'm frankly rather frustrated with Matt and the WordPress team for putting the rich text editor in as default even though people are using Textile and Markdown and others -- and can't disable them, because the original WordPress design for these plugins was that they should leave the unprocessed text in the database.

Actually, Picassa's albums (which they confusingly call labels in the UI) are the equivalent of Flickr's "sets," but they're _not_ stored in a proprietary format. They're stored in plain old XML. They're in the your user profile's "Local Settings" folder, something like: C:\Documents and Settings\[User Name]\Local Settings\Application Data\Google\Picasa2Albums\[Huge Random Seed]\

If you look there, you should see a bunch of .pal files, which are just plain XML files, containing a root @picasa2album@ tag and a few @property@ tags including the *name* of the album, and then a @files@ collection enumerating all the images that belong to that album.

Anyway. Monitoring *one* of them for Flickr uploading is fairly simple, and checking them all to see what other sets each photo is in is fairly simple too ... and the "captions" which Flickr calls "descriptions" are embedded in the actual image file in an IPTC annotation, and Flickr's "star" is stored in the Picasa.ini file in the folder with the image.

The *real problem* is that Picasa doesn't seem to actually store the _edited_ images at all (since Picasa 2?), preferring to store the edits they do as instructions in the Picasa.ini file. So unless you want to upload the un-edited image, you're actually forced to export them, unless you can find a way to turn this into actual instructions:
filters= crop=1,264,256,1372,995; enhance=1; autolight=1; finetune=1,0.000000,0.000000,0.000000,fff3f4ef,0.000000;

The trick is the priority you assign to the plugins... for instance, if you look at my "geshi plugin":http://www.huddledmasses.org/wp-content/plugins/source.php?file=geshi_plugin.php, you'll see I have it set to priority 5 (the priority is the last number in the @add_filter('the_content', 'GeshiSyntaxColorer', 5);@ command at the bottom of the file. And if you check my "textile 2.6":http://www.huddledmasses.org/wp-content/plugins/source.php?file=textile2.6b.php plugin, you'll see that I've set it to priority 6. This way seems to work for me ;)

Yeah! Actually, it's not just the version, it's the register_globals being off. For some reason, I had mine on... hopefully i haven't broken anything by turning it off.

Anyway, @$file@ is the parameter that you need to pass to the script, like to view the source.php script, you need a link to "source.php?file=source.php":http://www.huddledmasses.org/wp-content/plugins/source.php?file=source.php or else you should just get the "sorry, that file doesn't exist" error.

Anyway, I think I fixed my copy of "View Source":":http://www.huddledmasses.org/wp-content/plugins/source.php?file=source.php, so you can use that link I just posted to view it, and even download it.

They do their own advertising ... which is a tiny bit more in your face than Google's ... but I'm not actually sure how they're managing the whole interface to Google, I was assuming they're using the Google API, or are actually a covert Google setup to try new ways to market search engines.

Yep, Sorry. I fixed the post now ... Apparently I was having issues with Geshi and Textile again ... they don't get along very well.

Actually, I'm kind-of looking into it. There's no way to actually write a plugin for Picasa -- they haven't published an API -- however, they do create a Picasa.ini file in each folder, and although I can't tell right away where they store the "label"s, they have a "star" feature, and THAT is stored in the ini file (so I could use that as a way to detect which files should be uploaded). And the captions are actually put into the image as IPTC data.

Of course, the bummer is that all the "edits" you do to the image aren't actually real unless you export (they don't actually make a copy of the original as I said about, they simply don't change it, all the edits are in memory only, as far as I can tell. That is, they don't touch the original file, they simply make a note of what edits you've done, in the .ini file.

IMHO BSD variations fall in the same bucket. Way to much effort being spent in all the wrong places. Just to pick on one minor BSD variant:

bq. It is our belief that the correct choice of features and algorithms can yield the potential for excellent scalability, robustness, and debuggability in a number of broad system categories. Not just for SMP or NUMA, but for everything from a single-node UP system to a massively clustered system [... blah, blah, blah, ...] existing BSD cores... are still primarily based on [old] models ... true innovation has given way to basically just laying on hacks to add features, such as encrypted disks and security layering ... ??What is Dragonfly BSD - dragonflybsd.org??

If you want to argue that when open source developers wise up, standardize on a few distributions -- and develop a common API platform so someone can finally write some usable software -- one of them should be BSD, honestly, that just makes you like every other platform geek with a cause :) Yeah, OpenBSD is great, so is NetBSD and OpenDarwin, and Ubuntu, and Fedora, and ....

Preaching about your favorite distribution as a comment on this post is kind-of like trying to convince a wanderer in the Sahara that the sand is nicer "on this side of the dune." What he needs is water. What we need is a standard Open Source platform so we can move on from "look at all the cool things my computer can do" to actually doing cool things. ??Ben Schneiderman -- "Leonardo's Laptop(Sapmple Chapters)":http://mitpress.mit.edu/main/feature/leonardoslaptop/index.html ??

Hmm... it should leave html alone, I'll have to check that one out.

If you're using textile ... you should be using "bq. " at the begginning of the line for blockquotes, not the @blockquote@ tag ...

You *can* use xhtml while using textile, but you need to take into account that you *are* using textile. Which is to say: if you leave a blank line, textile is going to start a new paragraph for you, unless you're in a @notextile@ block -- which does weird things converting everything to code blocks-- so to accommodate the fact that your are using textile, you need to put a leading space on the line if you're starting a block-level xhtml tag after blank lines ... or use textile markup.

bq. For example, this blockquote was put in using the bq. textile markup.
It breaks on lines like a @pre@ section, but you can use XHTML inside it, or the usual textile markup.

Now, here's some normal text, and we'll break for a new paragraph.

Lastly, I've got a simple @blockquote@ tag with a space in front of it ...

This is that simple @blockquote@ tag with a space in front of it that they mentioned in the "textpattern wiki":http://textpattern.net/wiki/index.php?title=Troubleshooting_Common_XHTML_Validation_Issues_in_a_Textpattern_Site#Block_Elements_Wrapped_by_Paragraph_Elements.
Again, you can use textile markup or XHTML...

So, I guess I'm not sure what else to say.

Well, honestly, I think all these social bookmarking sites have big impact as a factor in the google recipe (that is: people create links to sites, google's recipe is based on the number of links to sites ...). However, other than that, I don't really use these sites for searching at this point ... more for surfing and discovery. I can add the bookmark lists of people I know (who share one or more of my interests) to my daily rotation, so to speak.

Just taking delicious as an example: I can subscribe to an RSS feed for all the links that you post, or all the links that you post and tag with "programming" or whatever tags I'm interested in. It's a lot like StumbleUpon, but with more control to me ;)

I'm not sure about the error, because I don't know how you edited the file... but to make the acronyms case sensitive, all you have to do is remove the "i" from the regular expression (that is: replace |imsU with |msU).

I *re*found it, and updated all the links in the article.

Well, the simplest answer to Patrick's problem is to change the _ to a _ which textile will pretty much ignore, but which will render properly in the image.

The complicated answer is that you should go to http://textism.com/tools/textile/ and post a bug to Dean ;)

If you use the "For Beautifiers" version, and set the priority of Geshi *higher* than that of Textile, you shouldn't have any problems, although I seem to be getting an extra < br />. Of course, only I can get < code > (or anything else that looks like HTML) into these pages, so let me show by example:

h6. Perl:

$foo = $_;
print $foo;

h6. Html

<div class="somesillytestcode">

This is a paragraph with a bold word in it.

This is another paragraph with an emphasized word in it.

</div>

A flawless install isn't worth two cents if after it's installed the user has to learn how to compile source code on the command line in order to get their laptop's internal wireless card to work. Or their desktop's flash card reader. Or the DVD burner ...

Besides, the fact that there are huge disparities in the install experience, documentation, and aesthetics just goes to prove my point: people are wasting their efforts developing new installers instead of better ones.

Looks like the @==@ notextile @==@ stuff is acting like his @code@ blocks used to. *Ugh.* You think he'd take my fixes if I could figure this out?

To reply to the question about math: - and + work fine, as long as there's a space on either side of them. You could turn that feature off fairly simply: edit the file, go to the "fSpan" function and remove the line(s) defining them: @'-' => 'del',@ and @'+' => 'ins',@

About the block quote, I'm not sure why it doesn't work in that spot, but I have no intentions of adding features to Dean's Textile parser, I want to keep them the same so that people can trust his documentation. The best bet is to raise this question on "his blog":http://www.textism.com/ or "textpattern support forums":http://forum.textpattern.com/

The @< notextile >@ blocks, and double = blocks work now, too (in 2.6) so I think most of the problems have been cleaned up.

You mean one of <  !-- these -- >, but, _as far as I know_ (and this is being parsed by Textile, as you can tell), there's nothing preventing you from putting <!-- comment one --> *comments* <!-- comment two --> in your page.

Try viewing the source of this page. There should be two comments, one on either side of the bold "comments" above. You can also look at the post I made for the recent "Textile 2.6 release":http://www.huddledmasses.org/2005/10/03/textile-plugin-26-released/, there's a comment right in the main post that says "there's a Jaykul comment here" so I'm sure it's not Textile stripping it out...

Which version did you grab?

I've _finally_ gotten around to adding a "download" link to my source script. All of my plugins should be simple and easy to download now, just click through to the source and hit the download link.

Hopefully that will solve all the download problems people have had.

I've _finally_ gotten around to adding a "download" link to my source script. All of my plugins should be simple and easy to download now, just click through to the source and hit the download link.

Hopefully that will solve all the download problems people have had.

I've _finally_ gotten around to adding a "download" link to my source script. All of my plugins should be simple and easy to download now, just click through to the source and hit the download link.

Hopefully that will solve all the download problems people have had.