Kermit Alexander II

I'd rather simply develop an OAuth2 bridge and let people use that instead - works for a much wider variety of applications and not just a single wiki, and anyone...

Doing this properly (making sure only URLs with proper domains get highlighted instead of just regexing `.+\..+`, making sure HTTPS is handled where linked, etc.) could take a little bit...

True, that would simplify things a fair amount. It's not a high priority of mine, but again, I'd accept a PR for this.

Searching would be a good feature to have; the infrastructure is more what needs to get worked out, I think. [Whoosh](https://whoosh.readthedocs.io/en/latest/index.html) would be my personal choice for the backend -...

You're right in that simply doing a SQL query over post subject/body would be a lot simpler, though it would be a bit more fragile as well in that SQL's...

fasttext might be worth a look since it seems at a glance not to take too much effort to add to the existing codebase, and at least as of late...

Good to know, I wasn't aware of that. [jellyfish](https://github.com/jamesturk/jellyfish) seems like a library that would be good for phonetic matching, so it could be worth a look.

Quick idea of what it might look like (obviously with different art, mind you, but you get the idea):  I think it's a lot easier to glance at a...

Also, a further mockup of a possible portrait-mode mobile layout:  The avatars might fit better to the right of "Posted by:" field, but that would be downright impossible to...

I'd prefer to have descriptive/unique thumbnails for all supported attachment types, if possible. Do you have any suggestions for what would be descriptive/unique for a file archive? I'm not opposed...