thebaer
Would also note it works pretty well for microblogging -- here's an example (with some custom styling)[0]. Small posts with a single paragraph also get federated out as `Note`s instead of `Article`s, which makes them show up on Mastodon pretty nicely.
There will definitely be future releases, especially once we get through a roadblock with the tool we use to cross-compile WriteFreely [0]. Otherwise, anyone who wants to see the project move faster is more than welcome to contribute, especially with tasks like code review, to help clear out those PRs [1].
[0] https://github.com/techknowlogick/xgo/issues/155
[1] https://github.com/writefreely/writefreely/discussions/550
There are a lot of other great small platforms that are made especially for blogging, rather than being general-purpose like some of the options you mentioned. E.g. Bear Blog [1] and Svbtle [2]
[0] https://write.as
And out of curiosity, what didn't you like about our thought process on micropayments?
The primary reasons for including certain features in Write.as but not in WriteFreely are when they're very early (it's easier to deploy and fix on a single hosted service), or when they involve a ton of external dependencies. My thinking on the latter is that I'd rather leave a feature out than leave admins with a poor experience, vendor lock-in, lacking documentation, etc. But maybe that's the wrong way to think about it.
Either way, "locking features off" isn't a business strategy here, but just a matter of practicality as a very small open source project. As I mentioned elsewhere, we plan to bring things into parity for v1.0. And we very much welcome contributors -- even if it's just reviewing pull requests!
For a little update on where the project is today: we just put out our last update [0] before v1.0, which we're aiming to release later this year. In 1.0, among other things, you'll find many features we've been piloting on our hosted service (Write.as), including newsletters, social media cross-posting, eBook export, etc.
We're also experimenting with new, non-core features, like photo hosting [1] and comments [2]. Our core focus has always been on just writing, which is why many features (including ones afforded by ActivityPub) have been left out. So we're trying to see what's possible when we keep a clean, simple core with optional "rooms" of functionality around it. If you want to keep up with us, you should see more developments around this before the end of the year, too.
[0] https://blog.writefreely.org/version-0-13
[1] https://snap.as
As for exporting your content, yes you can do that at any time. Everything is downloadable as JSON, CSV, or a zipped archive of plain text files.
Write.as is a simple, privacy-friendly blogging platform made for writers. It's focused on doing just one thing well: helping you get your words published on the open web. It's powered by open source software called WriteFreely, and is part of a suite of interconnected publishing tools that I'm building: Snap.as for photos, Submit.as for submission management, Draft.as for collaboration, and so on.
As a company, we're entirely bootstrapped and founder-owned, and after 6 years, very modestly profitable. But in many ways, we're still very early. Our customers are writers, bloggers, teachers, and authors, plus some companies, publications, and public libraries. There's no "exit" or fundraising potential in sight; just a small, sustainable company I hope to continue running for many decades.
I put most of my focus on building product and supporting current customers, to the detriment of us growing quicker. But there is plenty of room to grow, and I'm looking for someone who can join in a cofounder-like capacity to help move the needle in a way that matches our calm pace and principles [0]. If you're interested, I'd love to hear from you: matt {at} write.as
Beyond Feature/Bug Dualism
Show HN: Monetized Writing with Micropayments on Write.as
A Revolution in Write.as Design
That's the rub. If you were running the service, just speaking practically, how many customers would you need at $10 / €10 per year to pay for the servers? How about to pay your salary? What if you wanted to hire one additional employee?
(Also, WordPress.com shows you ads unless you pay at least $36 / year -- and they're large enough that they could reduce the price to whatever they want, unlike a bootstrapped service starting from $0.)
But there's also the valid point you mention, which is that many people have no more than a passing interest in blogging, and thus might not value a blogging platform at more than the price you suggested. We see this happen with Write.as. But then it might actually make more sense for platforms to charge more -- think about if you were just starting out a workout routine. Would you be more willing to go to the gym regularly if you were paying just $1 per month for a membership, or $40 per month? An investment in the tool helps you invest in the habit.
On another note, I'm really excited to see that A Pattern Language was an inspiration for this sim. That seems like a great start!
Think of WordPress -- free software you can either run yourself or pay a company to run for you. If you don't like a particular hosting company, you can click a button to export your data, and upload it with a new host -- or with other software that understands the WordPress export format. All of this data handling is manageable by most non-technical people. The process is hardly any different than downloading an email attachment and sending it to someone else, or uploading it somewhere.
It seems to me the biggest problem is either data not being exportable from these services, or the exported data not being machine-readable. If the format is machine-readable, developers can create alternative software that works with it; managed services can then develop around that software; everyday consumers can eventually end up with more choice, freedom, and power.
Ask HN: Why a Static Site Generator?
If you use a static site generator, especially to create a blog, why do you use it? Some reasons I've heard before are:* Pages load faster * Hosting costs are low or free * Can write while offline * Can publish with a workflow you like (e.g. text editor > commit > push) * Can keep a history of changes (version control) * Posts start offline and are saved locally by defaultAnything else?
Yes, the trains are often late. Yes, it's slower than flying and maybe even driving. But it's a journey. You can show up 15 minutes before the train leaves and still make it on board. You can bring snacks and some beer, meet people you never would've talked to otherwise, see parts of the country you'd never see otherwise.
You get to travel for the sake of traveling -- a rare pleasure indeed.
By not supporting following in the other direction, these specialized platforms can stay focused on the content shared there, instead of also supporting microblogging, video, photos, events, and whatever other types come up in the future. But of course you're not limited to just following in one direction -- comments go both ways. So someone can comment on your Pixelfed photo with a Mastodon account, and you can respond to that comment with your Pixelfed account, and they'll see your comment back on Mastodon.
What are some of the bigger problems you see?
We can still create a world of free products that enable what your forum has -- it just needs a simple business model like, Hey, do you enjoy writing here? Send me $5! Then subsidize your free users with paid ones. If you have a day job, you can consider it a success when the servers are paid for every month.
There is nothing inherent about the internet that says it must be run on ads. That's just what ad-powered platforms want you to think, to justify their own terrible existence. Get creative, put on the tiniest of marketing hats, and just ask people. There is no quick and easy lunch, but I think you'll be surprised by what you find.