Posted Sunday, August 2 at 2:37 AM (4 years ago)
Some pretty big new features added. First, in Authl:
- Major documentation improvements
- Bug fixes with Fediverse instance caching
- All providers now normalize to the same profile format
- Some basic spam prevention for the email provider
- 100% unit test coverage on the Fediverse provider (which is now using mastodon.py instead of a hand-rolled OAuth client)
And in Publ:
- Fenced code now uses
<figure>
and <figcaption>
instead of ad-hoc <div>
s for its layout, and the overall HTML semantic has been greatly improved
- Individual code blocks are now configurable with respect to highlighting and line numbering
- The user object now provides a user profile and separates the identity URL from the familiar name
Posted Sunday, May 31 at 3:32 AM (4 years ago)
I’ve just released new versions of Publ and Authl.
Publ v0.6.6 changes:
- Fixed a regression that made it impossible to log out
- Fixed a problem where
WWW-Authenticate
headers weren’t being cached properly
- Improve the changed-file cache-busting methodology
- Add object pooling to Entry, Category, and View (for a potentially big memory and performance improvement)
Authl v0.4.0 changes:
- Finally started to add unit tests
- Removed some legacy WebFinger code that was no longer relevant or ever touched
- Added a mechanism to allow providers to go directly to login, as appropriate
- Added friendly visual icons for providers which support them (a so-called “NASCAR interface”)
Posted Thursday, May 28 at 3:45 PM (4 years ago)
Publ v0.6.5 is now out. Has the following changes:
- Upgrading Publ will now invalidate the cache
- Fixes the missing database session around the authentication log viewer
- Fixes the way that the indexer works when an entry changes ID
- Fixes a bug where draft entries' temporary IDs were overriding the permanent/assigned IDs of visible entries
- Added some useful commandline tools
The next things I want to work on:
- Micropub endpoint (done as a separate component that you can optionally add)
- Adding more unit tests
- Maybe an actual (very basic) CMS UI? I dunno