News and updates about Publ
Both a minor update, and a major one; due to upstream vulnerabilities in Pillow, which are only resolved in a version which drops support Python 3.6, Publ now also drops support for Python 3.6.
There are no other changes.
Releasing v0.7.5 of Publ just to get some bugfixes out. Namely:
path_alias_regexReleased new versions of Publ and Authl today.
First, the Authl changes:
profile_url field to user profiles to make up for the Twitter URL thingAnd the Publ changes:
profile_url fieldPubl v0.7.3 is now out, with the following changes:
AUTHL_FORCE_SSL configuration settingNote that entry.summary now takes an optional parameter, markup, which defaults to True, for the sake of consistency with the rest of the Publ templating API. If you are using entry.summary to provide descriptive text for things (e.g. <a title="{{entry.summary}}"> or <meta name="description" content="{{entry.summary}}">) this will have to change to {{entry.summary(markup=False)}}.
Pushl has been updated, specifically to rewrite the way that feeds are parsed to avoid a problem due to feedparser internals changing in a way that made the caching mechanism stop working.
Authl v0.5.2 is now out.
Changes:
I’ve just released v0.5.1 of Authl. The only functional change is adding support for actually parsing IndieAuth server response profiles (rather than just requesting one and only using the h-card), now that there’s implementations in the wild, meaning that egg has hatched into a chicken.
There were also some minor documentation cleanups since v0.5.0.
Big new releases for Publ and Authl!
Publ changes:
Authl changes:
There’s a general belief that SQLite is a “slow” database and Postgres is “fast,” and many software packages (including FOSS) insist that SQLite is only suitable for testing and doesn’t scale. However, this doesn’t make much sense when you think about it; SQLite is an in-process database so there’s no communications overhead between the service and the database, and because it’s only designed to be accessed from a single process it can make use of optimistic locking to speed up transactions.
Since I was installing postgres for another purpose on my webserver, I decided to quickly see if Publ performs better on Postgres vs SQLite. To test the performance I compared the timing for my website on both doing a full site reindex, and rendering the Atom feed several times (using the debug Flask server and caching disabled).
I finally got around to adding whoosh full-text search to Publ, as an experimental feature. See it in operation.
Other changes:
entry.prev and entry.next to not default to subcategory recursion if a category context is specifiedIt took me way longer than I should have, but I finally decided to bump the minor version of Publ to 0.7.0.
My original intention was to only do that after getting the unit test coverage up to 90%, then to 80%, then to 50%… but it’s at 45% and that’s Good Enough I guess. I’d still like to get some proper automated testing in place for the bits that are tricky to test but with a system as complex as Publ it’s not particularly clear how to do a lot of that. The main issue is a fundamental mismatch between how the underlying ORM works vs. how unit testing is supposed to work, and I’ve so far been unable to square that circle. But maybe someday I’ll get the test coverage number up where I want it to be.
In any case, the only actual code change since 0.6.14 was some fixes to how page redirection works, especially around private entries.
End-of-the-year updates to Publ, mostly bug/interoperability fixes but a couple of small new features:
example.com/1234 → example.com/blog/1234-hello-world) now uses permanent redirectsview now has a has_unauthorized propertycategory.tagsview(tag=...).link, entry.archive(tag=...), etc.) will normalize the case and order of included tagsAssuming this is stable, this will become the basis of the long-overdue 0.7.0 release.
Just some minor fixes for v0.6.13:
Wow, it’s been a while since I’ve worked on this stuff, huh?
Anyway, IndieAuth validation rules have changed for the better, so Authl has been updated accordingly.
There’s a few other changes as well:
p-pronoun is treated as a fallback for p-pronounsrel="nofollow" in some appropriate placesA mostly-bugfix update:
Path-Canonical/Path-Mount now works properly in conjunction with AuthPath-Alias et al now support URL-encoded special characters for the path mapping400 Bad Request error instead of a 500 Internal Server ErrorJust some cleanups and usability fixes:
GONE/HIDDEN/etc.)Also I forgot to announce v0.6.10, released back on September 1; the changes from v0.6.9 were:
401 Unauthorized status overcome a path aliasPubl 0.6.9 is out and has the following changes:
Path-alias now works for all URL paths, and not just ones which happened to match Publ’s routing rulesImportant: In the incredibly unlikely event you were using the token_endpoint function, that has been removed, along with the token endpoint itself.
Some pretty big new features added. First, in Authl:
And in Publ:
<figure> and <figcaption> instead of ad-hoc <div>s for its layout, and the overall HTML semantic has been greatly improvedSince there’s now a lot more to PlaidWeb than just Publ, there is now a new organization website which will become the top-level home of these different things, which allows for better organization of this stuff to begin with.
While I’m still trying to work out how I’m going to organize things, my expectations are as follows:
Also, publ.beesbuzz.biz is intended to redirect over here, but it’s disappeared from my DNS host for some reason; it was actually this happening which inspired me to finally take this action. It seems to be a bug with how LiNode’s wildcard domains work, and I have an active support ticket open. Update: Turns out this was a subtle issue with how DNS wildcards work, which is explained below the cut.
Publ v0.6.7 is out now. Various changes:
Redirect-Url logic to cut down on the number of page load hopsmain1I’m already regretting some of the decisions I made with the fenced code amendments; in the future it will almost certainly switch to using <figure> and <figcaption>, and change some of the other structural bits. Feel free to share your opinions.
There’s also a known issue where the quick-login link (for e.g. Twitter) doesn’t work on pages which are login-required; this is actually an issue with the Authl login template, and has already been fixed in Authl pending the next release.
And speaking of Authl, the online docs are way better now. Hopefully it’s finally in a state where other people will be able to use it!