sipb.mit.edu Git - ikiwiki.git/log

added a tripple of links

Merge branch 'master' of ssh://git.ikiwiki.info/srv/git/ikiwiki.info

Fix syntax of recently added JavaScript syntax in meta.pm (<script /> apparently does not work).

the "not" keyword doesn't work for pagespecs (or no longer does). use an ! instead.

Reporting bug: YAML setup files vs. UTF-8 vs. YAML::XS.

Random blog software

Site has been domain-grabbed.

Added http://richardhartmann.de/blog

added www.meebey.net

Respond to the responses

meta: Fix bug in loading of HTML::Entities that can break inline archive=yes (mostly masked by other plugins that load the module).

edit to include link to page summarizing the sources

comment on my progress with the LaTeXML plugin

Bug: transient autocreated tagbase is not transient autoindexed: new

Google Analytics support

extend sorting pagespec

reformat, I forgot about anonyous pushing in this wiki

Revert "testcomment about the page"

This reverts commit 68208cffb32ed8560778046107dac2f1e7f5e3d6.

testcomment about the page

git repos: Add new repository jo

untrusted_git_push: extend ikiwiki call

some ideas for how to fix this

dagnabbit, another typo!

more flexible, perhaps?

Researched a bit the internal/external links styling todo item.

well, that was fun while it lasted

Reply... cannot think of a great solution.

Merge remote-tracking branch 'levitte/master'

document fix I'm about to merge

look up avatar at comment post time

There is a tension between looking up the avatar at post time
and build time. I have not yet decided which is better.

Lookup at build time has the benefit that if a user changes their
email address, or sets up their own federated libravatar
server, on rebuild their new avatar will show up.

It also allows getting a https version of the avatar easily if
the site was using http but was changed to use https.

And it can look up avatars for posts that have already been made.
Which is a nice thing, especially as we roll this out, eh?

But it has a drawback, that it depends on the sessiondb contents
for emails and so rebuilding a site w/o that will lose info.

And, it means dns lookups every time a comment is rendered. A page
with a lot of comments on it would render them all whenever another is
posted or the page is changed, and that could significantly slow things
down. (This could be amelorated by caching the lookups.)

Since I'm undecided, I have moved it into a function that could be called
either way. Currently looking up only at post time.