user feedback logic was updated to report if zero posts were found in a
zip and form submissions disable the submit button until the form input
for files changes again, preventing possible duplicate submissions on
large zip uploads.

updated to v0.2.1 wfimport to prevent early error returns when an
invalid file is present in a zip.

by default all content is enabled and displayed, this allows users
without javascript enabled to still use the form and understand what is
happening.

users with javascript enabled will see actions and options
disabled until the files selected allow, and show information and
warnings about zip files in needed.

this allows zip files in the import upload form

plain files are still uploaded to the selected collection but zip
contents are considered drafts with the exception of subdirectories,
these are added to the corresponding collections. if no collection is
found then it will be created.

now checking for and returning invalid content type errors

this updates to parse the time from the imported file, using v0.1.1 of
the wfimport library

in favor of library side generation to support zip files

this changes the import handler to use CreatePost instead of
CreateOwnedPost which required generation of non expiring access tokens

handler for post request to import is now under /api/me/import
form target updated

also allow all plaintext files in form

different template action for partial or complete import success

this adds basic support for importing files as blog posts.

.txt and .md are supported at this time and the
collection is selectable, defaulting to draft.

if a collection is specified the post is federated.

Add editor config option

Support toning down WriteFreely promotion

Resolves T676

Support setting default blog visibility on instance

Resolves T675

(in returned JSON data)

Ref T675

instead of updating it later. This is more correct behavior, prevents an
additional query, and ensures that potential collection-creation when
claiming posts also respects the default (which it didn't before).

Ref T675

instead of App

Ref T675

Fix single-user instance issues

Previously, the URL of the dynamically-added pinned post on a
single-user instance would include the username, causing the link to go
to a non-existent page. This fixes that.

Fix missing hostname when publishing via API

Style collection 404 page like rest of blog

Resolves T493

Ref T493

Ref T493

Let Apper set request log format

Ref T677

Ref T677

Support <audio> element

Automatic certificates from Let's Encrypt

Resolves T542

Fix go-sitemap-generator overriding GOMAXPROCs

This adds a new ReqLog() func to the Apper interface that'll return the
log message for incoming requests.

Ref T649

changed to use stm.URL for imgs for readability
fixed error in append statement
reordered import statements

This adds a new `wf_modesty` config option that removes the copious
mentions of WriteFreely in places like the About page and site
footers.

WriteFreely remains boastful and bumptious by default; but enabling
the modesty option will tone it down and likely lead to less confusion
among average users.

Ref T676

Ref T675

This adds a new `default_visibility` config value that lets an instance
admin set the visibility of newly created collections.

Ref T675

This whitelists the HTML5 <audio> element and adds some basic style to
make it look nice.

- This removes copy mentioning the Blogs page, which isn't used on
  single-user instances
- This fixes the "Start writing" link, which on a single-user instance
  would've gone to the blog index, rather than the editor

Previously, these links showed up on user backend pages on a single-user
instance, despite them not working / only being applicable on multi-user
instances.

This is the crucial part where the hostName is needed for federation and
API clients. This change at least lets us know when we mess up like this
so the issue is easier to catch in the future.

This fixes a bug that occurred only when publishing via API and
authenticating via token (rather than cookie).

Previously, the instance's hostname wouldn't be added to the Collection
that got passed around after retrieving the owned post, meaning an
incomplete URL was returned in the API response, and federation failed due
to the missing host.

This displays the "page is missing" text within the same page as any
other blog post, keeping customizations, pinned pages, and general blog
navigation.

Ref T493

Don't consider post unpublished when title exists