Releases: cypnk/Bare
Bare 1.2.1
This is a feature release which adds Utreon video embedding and timestamp capability to both YouTube and Utreon embedded media. Embedded media now default to lazy loading, which should prevent download until the visitor scrolls to the media location on the page, saving bandwidth and improving page load speeds on modern browsers.
This release is in use on the author's personal blog also mirrored on Tor, along with the firewall and templates plugins. Use the Tor Browser Bundle to visit the Tor mirror.
Bare 1.2
This is a maintenance and bugfix release which increases compatibility with PHP 8.1+ and removes some deprecated functions. There's now a startup.log file created when Bare runs for the first time to give information regarding any missing dependencies. Cleanup behavior has also been improved for blogs running on older hardware.
This release is in use on the author's personal blog also mirrored on Tor, along with the firewall and templates plugins. Use the Tor Browser Bundle to visit the Tor mirror.
Bare 1.1.9
This is a bugfix and minor improvement release which resolves a host name priority conflict when Bare is serving multiple blogs on separate domains or IP addresses at the same time. This version also creates a logging message if the post directory is not found in the expected location and if the Timezone setting is invalid.
This release is in use on the author's personal blog also mirrored on Tor, along with the firewall and templates plugins. Use the Tor Browser Bundle to visit the Tor mirror.
Bare 1.1.8
This is a minor improvement to the previous 1.1.7 release which enables adding multiple footnote references to the same content. Previously, adding the same reference twice will overwrite the previous reference. This version no longer relies only on the position of the footnote within the global document to create the back reference and instead uses an excerpt of the footnote text and a short hash of its content. This allows more consistent linking no matter where the post is located on a page, E.G. Date archive list, RSS feed, tag page etc...
Note: Footnotes should be added after the main post body, but before the tags:
directive and any other special content markers.
This release is in use on the author's personal blog on Tor, along with the firewall and templates plugins. Use the Tor Browser Bundle to visit.
Bare 1.1.7
This is a feature release which adds simple footnotes to posts and content pages. A footnote is typically a reference to further information, definitions, or links at the bottom of each post or page.
To create a footnote, add a bracketed marker with a caret (^) symbol.
Example:
This post has a footnote[^1] and another[^2]
Footnotes are fully written at the end of the post body
[^1]: First footnote
[^2]: Second footnote with a [link](https://example.com)
This will create a list of footnotes on the bottom of each post or page with links referencing them in the content body.
The footnote prefix links to the marker location in the post body. Bare will also process text-based footnotes:
This post has a footnote[^One] and another[^Two]
Footnotes are fully written at the end of the post body
[^One]: First footnote
[^Two]: Second footnote with a [link](https://example.com)
The choice of numeric or text-based markers is up to personal aesthetics. For clarity, using one style of footnote marker is recommended even though Bare will process both styles on the same post or page. Valid symbols for the markers are letters, numbers, underscore (_), and dash (-).
Important: Using the same footnote marker twice in the same post will overwrite the previous footnote with the same marker. All footnote formatting is in the presentation render and the original post content will be left exactly as the user has written it.
This release is in use on the author's personal blog on Tor, along with the firewall and templates plugins. Use the Tor Browser Bundle to visit.
Bare 1.1.6
This release enables plugins to completely override any default stylesheets, JavaScript files, and the default Content Security Policy via hooks. Previously, Bare would only load the defined stylesheets and JS files (if any), and the CSP configured in index.php or a custom config.json file in the CACHE folder location. There is an added prefixed cookie feature, enabled by default, which further enhances privacy when Bare is served over TLS. Even if this setting is disabled, cookies sent by Bare are restricted to the domain being visited on most modern browsers.
This release is in use on the author's personal blog on Tor, along with the firewall and templates plugins. Use the Tor Browser Bundle to visit.
Bare 1.1.5
This is a bugfix and maintenance release which addresses a lock issue with SQLite when Bare is subjected to several thousand unique visitors within a short period on a server with a hard disk rated at 5200 RPM or IDE-to-CF card adapted disk. Visitors do not notice a difference when this problem occurs, however, an intermittent lock message appears in errors.log in the CACHE directory. The problem becomes more pronounced when using plugins which also use their own databases.
The cache.db in the CACHE folder must be removed or renamed after installing this update. Bare will build a new cache database on the next visit to your blog.
This release is in use on the author's personal blog on Tor, along with the firewall and templates plugins. Use the Tor Browser Bundle to visit.
Bare 1.1.4
This is a maintenance and feature release which changes the behavior of the loadFile() function. Previously, plugins were able to load files only from the CACHE directory, however now they can specify the loading root path and control loaded file caching behavior. This does have security implications where some plugins may be able to load files from less than ideal locations, however all plugins should be vetted by the plugin authors and installers before use.
This release is in use on the author's personal blog on Tor, along with the firewall and templates plugins. Use the Tor Browser Bundle to visit.
Bare 1.1.3
This is a maintenance release which changes how embedded code works and adds a pageRoutePath() helper for any future plugins. Markdown-sensitive characters can now be escaped to avoid potential conflicts. Plugins can now use the same /cache directory path to load their own database SQL file(s). Bare will always continue to support plain text files for blog posts.
This release is in use on the author's personal blog on Tor, along with the firewall and templates plugins. Use the Tor Browser Bundle to visit.
Bare 1.1.2
This is a maintenance and cleanup release which removes unused, obsolete, and some redundant code, while adding minor fixes and small features. Plugins are now able to change more configuration options and they can add/edit new blogs dynamically and change their settings at runtime. Plugins which use the mail() function can also dynamically add new recipients. The libVersion() helper has been added for Plugin authors to more easily check for available PHP extensions and their versions.
This release also removes the rarely used Parsedown and ParsedownExtra class handling functionality. These were optional third party libraries which provided more complete Markdown formatting. Bare still understands a small core set of Markdown tags and using HTML tags for any complex formatting is recommended instead.
Bare now allows hosting much older blog posts by default. Previously, the YEAR_START setting needed to be changed in index.php, or 'year_start' in config.json, to host blog posts from before 2015. Now, posts from as far back as 1990 can be served by default without having to change this value. The YEAR_END setting is no longer used.
This release is in use on the author's personal blog on Tor, along with the firewall and templates plugins. Use the Tor Browser Bundle to visit.