Version 0.14
Our next release is here, with a ton of improvements and fixes from the last year!
Download v0.14.0 now, or read on to see what’s new in this version.
Our next release is here, with a ton of improvements and fixes from the last year!
Download v0.14.0 now, or read on to see what’s new in this version.
After a long break, our next release is finally here! This includes some important bugfixes, plus minor improvements and updates.
Download v0.13.2 now, or read on to see what’s new in this version.
This release fixes issues that were mostly introduced in our last release, v0.13. Most critically, it fixes a database lock bug that caused SQLite-backed instances with the Reader enabled to become unresponsive — so we recommend that admins of these instances absolutely upgrade to this version.
Download v0.13.1 now, or read on to see what’s new in this version.
Hello again! 👋 After a long absence, we’re pleased to release WriteFreely v0.13 today! This one includes a new rich editor, generic OAuth support, Web Monetization support, and a ton of small improvements. Besides that, this is one of our last releases before version 1.0!
This summer we largely took a break from major work on WriteFreely to turn our focus to something new: native apps for the Apple ecosystem. Now, after developing in the open, building a Swift library, writing about our adventures with SwiftUI, and opening the app to beta testers, we're excited to finally release WriteFreely for iOS v1.0!
You can buy it now for $14.99 on the App Store (requires iOS 14 or later), and find the GPL-licensed source code on GitHub.
We're excited to release WriteFreely v0.12, our biggest update yet! This version comes with a ton of great features for communities and organizations, and officially moves WriteFreely into the beta stage — just a few steps away from version 1.0.
Besides our new features and performance improvements, this update also includes plenty of contributions from new members of the community! Thank you to everyone who helped out, whether you contributed code or tested our release candidate!
ActivityPub Mentions (T627)
Enable more interaction with your posts by mentioning users on Mastodon, Pleroma, and other ActivityPub platforms! Users on instances with federation enabled can now insert @handle@their.instance to mention someone. You might use this to write a long response to someone in the fediverse, or even mention your own microblogging account, so that replies to your blog post also notify you there, where you can continue the conversation.
New Admin Dashboard (T694)
We've redesigned the admin dashboard to be a little easier to navigate, and generally more user friendly. It now includes an overview of stats for your instance, dedicated pages for app settings and monitoring, and more details on what each configuration option does. We've also made it easier for admins to get to the “Invite people” page.
OAuth 2.0 Support (#225)
Now you can authenticate with your WriteFreely instance via OAuth! This is perfect for WriteFreely communities that are set up to accompany other platforms. We support three providers so far: GitLab, Slack, and Write.as.
Reader Filter Updates (#269)
Now the Reader will show the most recent 250 public posts, instead of only the last three months of public posts. This should be much more fitting for most WriteFreely instances.
Plain Text Import
Now you can import plain text files to publish them as posts on WriteFreely.
js, jsx, html (#270)@context fields to fix Friendica federation (#299)update_checks = true in config/api/markdown endpoint for generating HTML from MarkdownDownload the latest release for your operating system. Stop running your writefreely service, replace all files in your installation with the ones in the archive, and then start your writefreely service again.
Now make sure your database is backed up, and update it with:
writefreely db migrate
No additional steps are needed to upgrade from v0.11.x. Follow the instructions in each previous #release if you're upgrading from an earlier version.
If you are running a custom build, note that there were style changes in this release. Run the following command to generate the latest stylesheets:
make ui
Thanks to everyone who contributed to this release!
@thebaer @robjloranger @qwazix @yalh76 @ngerakines @techknowlogick @shleeable @nkoehring @paddatrapper @cjeller1592
@barbrastreisand @wakest @judges119 @laBecasse @misaka00251 @OliverViking @mrvdb @darddan @wiwie @annando
This version fixes some regressions introduced in our last major release, particularly around #federation. We highly recommend that all admins upgrade to this version, especially if you're on v0.11.x.
On that note: want to help us test WriteFreely before future major releases? We'd love your help! Let us know over on the forum.
Announceing posts via ActivityPub (#212)id property in collection posts' ActivityStreams data (#214)Download the latest release for your operating system. Stop running your writefreely service, replace all files in your installation with the ones in the archive, and then start your writefreely service again.
No additional steps are needed to upgrade from v0.11.x. Follow the instructions in each previous #release if you're upgrading from v0.10.0 or earlier.
Thanks for contributing to this release!
Today we're excited to release WriteFreely v0.11! This is a huge update that includes many fixes and improvements, built-in automatic, free SSL certificates, support for our command-line client, and more moderation controls for multi-user instances.
Besides all of these improvements, this update come just over a year after our very first release, v0.1. Keep an eye out for a future post about the last year in review — a lot has happened!
Get the lastest release now (you'll notice it's v0.11.1), or jump into the updates below.
Automatic SSL certificates from Let's Encrypt (T542)
It's now even easier to start up a WriteFreely instance with free, automatic certificates from Let's Encrypt. With the application facing the public internet (i.e. not behind a reverse proxy), you can set a few configuration values to have WriteFreely generate the certificate for you.
For new instances, choose Production, standalone > Secure (port 443), auto certificate during the interactive setup process.
For existing instances, set autocert = true and tls_cert_path = certs (see config documentation for more information).
WriteFreely Command-Line Interface
We've released our first official WriteFreely client along with this version: wf-cli! This is a simple command-line-based tool for publishing to one or many WriteFreely instances. It's perfect for tech-savvy users who don't want to leave their terminal window or anyone looking to build WriteFreely publishing into their desktop writing workflow — and it's available for Windows, Mac, Linux, and anywhere else you can build a Go application.
<audio> HTML element (#147)title attribute getting stripped on <abbr> elements (#184)make build-arm7Accept: application/json headers (not only Content-Type) (#178)User Silencing (T661)
Now instance admins can silence problematic users to make their writing inaccessible to the world and prevent further publishing. This strikes a balance between preventing further abuse and making reversible moderation decisions, as users will still be able to log in to their account and access their data.
This is still experimental, as it needs more extensive testing. Please report any bugs you find and give us any feedback you have on this feature!
Reader-centric instances (T681, #157)
As part of our new Write.as for Teams service, we're experimenting with an alternative configuration for admins that want their site to be more focused on the collective work of its writers, rather than on individuals. It's meant for businesses, organizations, and institutions that want to create more of a shared blog than provide individual blog hosting. It sets the Reader view as the home page, uses blog templates with global navigation, and has hashtags search across all public blogs.
This functionality is not at all finalized, and subject to change drastically without notice. We don't recommend enabling this in your configuration unless you're merely curious or want to provide feedback (which we highly encourage!).
Download the latest release for your operating system. Stop running your writefreely service, replace all files in your installation with the ones in the archive, and then start your writefreely service again.
Now make sure your database is backed up, and update it with writefreely --migrate.
No additional steps are needed to upgrade from v0.10.0. Follow the instructions in each previous #release if you're upgrading from an earlier version.
If you are running a custom build, note that there were style changes in this release. Run make ui to generate the latest stylesheets.
Thanks for contributing to this release!
Today we're happy to release WriteFreely v0.10, one of our largest updates yet.
This is a pretty important release for us. It brings together improvements driven by our thoughtful community and features that'll help us take the next step into our future — namely, one where WriteFreely helps organizations and groups effortlessly communicate via simple, open source tools.
For anyone running WriteFreely, this means more control over your community, starting with more customization in this version and better moderation in the next. Really, this is just the start. Let's jump in.
Communities looking for more privacy can now start up WriteFreely instances meant only for internal use. Just enable the private config value to make all blogs and content accessible only to authenticated users in your instance.
NOTE: this is a breaking change! This changes behavior for existing instances with the private config value already set to true. If you have it set, you should verify that the new behavior is what you want.
Now admins have two new ways to customize their multi-user instance:
Editing your landing page. Now you can change the content of your landing page from the Admin dashboard, including the banner text to the left of the signup form and the optional text below.
Changing the landing URL. For anyone who doesn't want to use their normal landing page — such as with closed or invite-only instances — this lets you set the URL that unauthenticated users go to when they first come to your site. For example, you might send them to your About page (/about) or your public Reader (/read).
background-color not set (#132)private config option now makes an instance readable only by registered, authenticated users (T576)--config command now automatically initializes the database, removing the need for --init-db during setup--sections flag, e.g. writefreely --config --section="app db server"writefreely.Serve() func has been split out into multiple functionswritefreely pkg to cmd/writefreely/main.goDownload the latest release for your operating system. Stop running your writefreely service, replace all files in your installation with the ones in the archive, and then start your writefreely service again.
No additional steps are needed to upgrade from v0.9.x. Follow the instructions in each previous #release if you're upgrading from an earlier version.
If you are running a custom build, note that there were style changes in this release. Run make ui to generate the latest stylesheets.
Thanks to everyone who contributed to this release!
@dariusk @gytisrepecka @robjloranger @joyeusenoelle @sandrockcstm @qwazix @mrvdb
Today's non-critical release fixes issues with new WriteFreely installations, introduced in the previous release (v0.9.0).
Download the latest release for your operating system. Stop running your writefreely service, replace all files in your installation with the ones in the archive, and then start your writefreely service again.
No additional steps are needed to upgrade from v0.9.0. Follow the instructions in each previous #release if you're upgrading from an earlier version.
Thanks for contributing to this release!