I like it. Looks great in reader mode, too. Not that you really need it. I think posts should have a link to the previous/next post in the blog. And I wonder if there is custom CSS.
Nice! $9 for annual services on top of a well constructed platform you can also self host is a really aim-for-the-moon commitment. I hope mataroa finds phenomenal success with their business.
True. Much like Dropbox, the tooling exists beforehand. It's nice when a company brings it altogether, maintains the expert knowledgebase, and creates the process to be simple (including setup).
Edit: leaving up as an embarrassing reminder to myself fully rtfm before opening my mouth. I thought this did NOT have comments and sub by email but it does. Glad y’all provided me with some feedback to realize I was wrong.
—-
Original comment:
I don’t get it. If you want to write and don’t care how much you’re read, write privately (Google Docs, a journal, text file, etc.)
If you’re writing publicly presumably it’s for public consumption. The way you know if your writing is read is through feedback - comments, shares, email subs, etc.
Feedback on your writing both helps you understand where you need to think more deeply about what you wrote AND provides valuable positive reinforcement: somebody is reading what you put into the world.
Not providing hooks for these seems to defeat the purpose of writing in public.
Too much feedback (especially when it comes to sharing your own thoughts) poisons the purity.
It’s a cliche that every musicians best work is their early stuff. Once you become popular, famous, entangled in expectations and opinions, you lose the thing that made you great.
- Writing publicly is minimum viable pressure to make me better formulate my ideas. It doesn’t require feedback; 80% of the value is in my words being public. When my ideas are better formulated, it leads to me new ideas I wouldn’t have had otherwise
- Over time (I’ve been blogging since 2000) I’ve found that the most valuable feedback is in email. You don’t get good signal to noise in comments or Web Mentions. RSS + a public email address is all I need
- I can afford for my network to grow slowly. I don’t need to build big community with flurries of debate in a comments section. Writing publicly is an excellent way to keep in touch with the broad network I already have
I see where you’re coming from, but I personally love blogging with zero concern for who reads it, how many likes it gets, or whether or not people want to give feedback.
It prevents me from falling into a trap of crafting posts that have a bias toward what I think people might want to read, it keeps it pure.
Just writing knowing that someone might read it inspires better writing. It's like when you think about a problem really hard, come up with nothing, then spend an hour formulating a perfect StackExchange question. More often than not, the process of writing for other people leads me to the answer, even without sending the question.
Same with blogging, except I can publish any old crap on my blog without moderation.
Private feedback via email is always possible and you can chose to publish specific feedback you deem important.
It's the same for printed literature. There is no comment section in books.
As for sharing: you can always share the URL
I have a public notes repo [0] in which I only write for myself, with no real expectation that anyone will ever read it. I have however gotten feedback in the form of cold emails that people have found the notes useful or interesting. Writing in public without hooks can also be valuable.
> I thought this did NOT have comments and sub by email but it does.
Can you please elaborate? Because I was (and still am) under the exact same impression. The only appearance of the word "comments" on the home page is this:
Yeah the “example post” names Bear Blog as a direct source of inspiration.
> Created out of authentic admiration of Herman's genius idea of Bear Blog, Mataroa.blog is like Bear Blog but also a bit different. Namely, it has built-in first-class support to export your blog, and it also supports image hosting.
Re: your addition--As an oldie on the internet, this has been through a few pendulum swings. I personally think it's fine to have non-coercive weird content exist (freedom of speech sans CP and similar exploitation) without it being shoved into people's faces (newsfeed). This let's people vote with their feet.
Mobile Safari's reader mode works for me on posts. It doesn't work on home pages but I don't expect it to; home pages aren't wrapped in <article> elements, it's not semantically appropriate, but posts are.
I was using and loved mataroa. It was the fairest, most painless option I had found for blogging (as of 2020.) I eventually switched away from it because the default font was small and I couldn’t change it. I wonder if this has been updated since. (At the moment, I’m hosting my blog as a static site with NFS. I go back and forth about wanting comments/email sign-up.)
The developers were nice though, and I used their source code to learn Django. Really grateful.
I was wondering about the typography too. Specifically for multi-language support, the chances are high that you’d want something better than the one default font they provide. Not to mention that you may want to edit the language meta code if you are writing in a different language.
I built mataroa. Not sure if your comment is referring to mataroa, but in case it is:
I care a lot about typography and making a platform in which non-latin scripts can be read well. Mataroa does not provide any font. Rather, it uses the end user's system fonts. System fonts are most probably better than webfonts. They can define a large set of characters, including as many languages as they can, without caring about how big they get. This is in contrast to webfonts, of which all character glyphs need to be sent to the client—so size matters.
Thanks for your comments. However, for certain languages it is important to specify the language in the HTML with the `lang` attribute. Otherwise incorrect glyphs may be displayed. More info:
That attribute could also let you easily group your users into different languages. If you wanted to add more discovery features or something and let people search by language. Not sure what your goal is around that. Maybe opt out of discovery by default or something.
On my phone it's pretty small font and linegeight, and found uncomfortable to read. As a web & app dev I have no idea how to quickly change this, let alone someone less tech savvy. For old people often small text is a big thing. Maybe add few font enlarge buttons?
Well, you do make one bad decision with your typography (and that’s the one alecst was remarking on with “the default font was small”): you set the font size to 14px, rather than leaving it at the default value (which will normally be 16px) or possibly increasing it a little (I reckon the decent range relative to the default is about 1–1.25em).
It's a choose your own adventure blog platform where you can go headless and customize everything or choose battery included and get a yourblog.polyblog.io out of the box
Looks really polished and I love the minimalist design.
One thing I've been wondering that a lot of web platforms offer: how do you allow users to bring their custom domain with TLS? What's the tech behind that and how does the process work?
That was one of the hard things to figure out how to do in a simple way on mataroa. Just using Let's Encrypt directly was the first iteration. Now mataroa is using a combination of:
- Let's Encrypt with a wildcard certificate for mataroa.blog and all *.mataroa.blog domains
- Caddy's automated certificates for all user custom domains
You can see a few more details about this setup in the server playbook doc [1] and the Caddyfile [2]
You can do this a variety of ways, most of which boil down to automating a reverse proxy server and generating acme certs. My favorite is Caddy server if you want to build and manage it yourself.
Things get trickier if you want to handle this well for globally distributed servers, since you'll need to have a cluster of reverse proxies near or colocated to your app servers. That needs an anycast IP address to handle A records for apex domains, and usually you want them coordinating to share certs, cache, etc. efficiently. In that situation I'd recommend reaching for a paid service, since there can be a lot to build and maintain.
Source: I built approximated.app, which is a service that does all of that for you.
Whatever terminates the connection (e.g. nginx, haproxy, apache) needs to be configured for each supported domain. As a platform this would mean having code to modify and reload the config and put certs in place on behalf of users.
If this is a common complaint that you have, why not just increase the font size and pick fonts you like in the browser settings? The settings are there for a reason.
One nice thing I recognized is that the generated RSS feed contains full html text. I wish more blogging platforms are like this; save a lot of effort for feed readers.
I'd also recommend to add open graph meta for the blog posts. Presumably people will want to share the posts somewhere; a nice set of open graph metas goes a long way.
I haven't checked it out yet, but... Wouldn't one not want html text in the feed, if one chose to use a blogging platform whose focus was text and simplicity? I prefer to read feeds with plain text myself.
You're right. I shouldn't have said many. I forgot some like to put memes in their articles. I still think the ability to use images can be important, depending on topic. Quite simply a blog about anything graphics-related would benefit.
I've been told Medium requires a huge photo at the top of each post, regardless if it makes sense or not for the article. Most of the time those articles are simply junk.
Agreed, but on a technical level it makes it harder for the client software to have to decide what to do with those resources. A plain-text post can sit on my drive for months until I get around to reading it with barely any impact on disk space usage.
With images I either have to eat the storage utilization for them or suffer a privacy leak by loading them when the post is opened. For the latter, there's always a small risk that a post could be deleted or an entire website vanish in between the time my feed updates and the time I open a post, in which case it would be left with text but broken images. I guess they could be inlined (like `<img src="data:image/png;base64,etc"/>`) to avoid that risk. It's even more obnoxiously complex if we're using the modern `picture`/`srcset`/etc to serve multiple resolutions and image formats for various screen sizes, connection speeds, and platforms.
Most sane feed readers sanitize the html down to a dumb level; just headings, paragraphs, links and some inline images. If you only have the text to begin with, hyper-links won't work.
> One nice thing I recognized is that the generated RSS feed contains full html text. I wish more blogging platforms are like this; save a lot of effort for feed readers.
The reason some blogs don't include the whole thing in the RSS is because they want you to visit the site for the ad revenue. It's not an oversight.
Blogging is (was?) a job for some people. It wasn't completely supported by ads, but ads are part of it. It's like YouTubers before YouTube.
Maybe today, but I personally stopped providing full text in the feeds of my now defunct and free from advertising blog, because my content was directly vacuumed and inserted into a spammy full of advertising website.
This was around 2005 for what I can remember. Time is flying...
> This happens with the HTML contents just as easily.
On an individual scale, yes. But if you're a spammer and want to vaccuum up text from 1000 sites, you'll skip writing a scraper for individual sites (which may change their formatting later anyway) and just use reliably-formatted RSS feeds.
That was probably true back in 2004, but today there are numerous reader view, full text converter, and advanced web spider projects that anybody can plug in and get the full text from at least 90% of web sites, with no extra effort.
Unethical people is going to do whatever they can. Life is much more enjoyable if you just ignore them and whatever shit they are going to do with the content you willingly shared with the world for free.
> my content was directly vacuumed and inserted into a spammy full of advertising website
For all its faults, this is something I have no shame invoking DMCA for. You still own the copyright on your writing even if you publish it for free online.
There are some downsides: interactive pages won’t work and automated content stealers. It very easy to copy articles from such RSS feeds because you don’t need to search for the text in HTML.
That's great, but unfortunately the HTML view only shows the TITLE, ala HackerNews, and not even a single summary sentence or paragraph there. So we've got a good RSS feed, but a bad HTML view.
It lets you decide how a link you share is presented on a variety of supporting platforms, with a few bits of metadata. You can control whether/how it presents your page's title, a preview image, summary/description, and who it's attributed to. All of which are desirable for content authors, not just those platforms.
It's not dark mode by default. The text color is initially undefined and the background-color transparent. If the user's device is set to prefer dark mode, color and background color are set to be white text on a dark background.
It would be good if it was possible for a reader to choose to use the opposite of their device setting but that would would less minimal (needs a UI, JavaScript, and client-side storage of the setting).
Probably because you're commenting without being familiar with how your browser sending information to pages to use a dark scheme for you. A website that supports "@media (prefers-color-scheme: dark)" is not really a maximalist design these days.
Does mataroa, or a similar platform, offer syntax highlighting?
I'm on month 80 avoiding setting up a blog to capture my occasional thoughts and frequent side project adventures – mostly because I'd rather fiddle with the side projects than set aside time spinning up some blog platform (which often begins with promising I'll use asciidoc, and ends in frustration trying to render asciidoc _juuuuust_ right). I would love to have a dead-simple interface (for writing and reading) to collect words. But since most of those words will be about code, a lack of syntax highlighting will take residence in my mind.
(Tangentially related: I _love_ reader mode, because I like to read an article or two while rocking my baby to sleep, and reader mode offers dark mode, even on websites in stunning retina-burn white. The only downside of reader mode is how it kills syntax highlighting.)
There is an easy excuse: time. Most people have better things to do than fiddle around with setting up a blog. The setting up process provides minimal value to most people.
If you’re spending the time to write articles, it takes no more than an hour to setup a simple blog. As a developer, it is the right thing to do. It provides tremendous value to people - a sense of pride, enterprise of building something, owning it and then showing it to others.
You might as well give up on writing then.
Drew Devault gives out $20 to start your own blog. We need to perpetuate this culture, not oppose.
163 comments
[ 3.6 ms ] story [ 203 ms ] thread—-
Original comment:
I don’t get it. If you want to write and don’t care how much you’re read, write privately (Google Docs, a journal, text file, etc.)
If you’re writing publicly presumably it’s for public consumption. The way you know if your writing is read is through feedback - comments, shares, email subs, etc.
Feedback on your writing both helps you understand where you need to think more deeply about what you wrote AND provides valuable positive reinforcement: somebody is reading what you put into the world.
Not providing hooks for these seems to defeat the purpose of writing in public.
Phrasing my comment a slightly different way: what’s the point of writing *in public* if you don’t get feedback?
It’s a cliche that every musicians best work is their early stuff. Once you become popular, famous, entangled in expectations and opinions, you lose the thing that made you great.
And the usefulness of writing isn't connected to if people can reach the author or not.
- Writing publicly is minimum viable pressure to make me better formulate my ideas. It doesn’t require feedback; 80% of the value is in my words being public. When my ideas are better formulated, it leads to me new ideas I wouldn’t have had otherwise
- Over time (I’ve been blogging since 2000) I’ve found that the most valuable feedback is in email. You don’t get good signal to noise in comments or Web Mentions. RSS + a public email address is all I need
- I can afford for my network to grow slowly. I don’t need to build big community with flurries of debate in a comments section. Writing publicly is an excellent way to keep in touch with the broad network I already have
They have comments and they have (local) analytics. What more do you expect from a blog?
It prevents me from falling into a trap of crafting posts that have a bias toward what I think people might want to read, it keeps it pure.
Same with blogging, except I can publish any old crap on my blog without moderation.
[0]: https://notes.param.codes
Can you please elaborate? Because I was (and still am) under the exact same impression. The only appearance of the word "comments" on the home page is this:
• Comments (alpha)
and there is no link.
> Created out of authentic admiration of Herman's genius idea of Bear Blog, Mataroa.blog is like Bear Blog but also a bit different. Namely, it has built-in first-class support to export your blog, and it also supports image hosting.
The pricing seems to be very fair and something that i would pay to support the project.
addition: i wonder how non mainstream opinions are moderated there, e.g. conspiracy theories, pro Russian content, pro Chinese content, etc.
Been a happy user of it :D
Thanks a lot for building it !
The developers were nice though, and I used their source code to learn Django. Really grateful.
I care a lot about typography and making a platform in which non-latin scripts can be read well. Mataroa does not provide any font. Rather, it uses the end user's system fonts. System fonts are most probably better than webfonts. They can define a large set of characters, including as many languages as they can, without caring about how big they get. This is in contrast to webfonts, of which all character glyphs need to be sent to the client—so size matters.
I've also written this text on the topic: https://nutcroft.com/blog/in-defense-of-user-defined-web-fon...
https://heistak.github.io/your-code-displays-japanese-wrong/
Thank you very much for this.
Pig-ignorant and unbreakable.
It's a choose your own adventure blog platform where you can go headless and customize everything or choose battery included and get a yourblog.polyblog.io out of the box
[disclaimer, I'm the founder of Polyblog.io]
so?
Happy to see it exists in the world!
One thing I've been wondering that a lot of web platforms offer: how do you allow users to bring their custom domain with TLS? What's the tech behind that and how does the process work?
- Let's Encrypt with a wildcard certificate for mataroa.blog and all *.mataroa.blog domains
- Caddy's automated certificates for all user custom domains
You can see a few more details about this setup in the server playbook doc [1] and the Caddyfile [2]
[1]: https://github.com/sirodoht/mataroa/blob/master/docs/server-...
[2]: https://github.com/sirodoht/mataroa/blob/master/Caddyfile
Things get trickier if you want to handle this well for globally distributed servers, since you'll need to have a cluster of reverse proxies near or colocated to your app servers. That needs an anycast IP address to handle A records for apex domains, and usually you want them coordinating to share certs, cache, etc. efficiently. In that situation I'd recommend reaching for a paid service, since there can be a lot to build and maintain.
Source: I built approximated.app, which is a service that does all of that for you.
It is designed to complement SSG style blogs, but should work with blogging platforms as well.
I want to see if source code snippets, SVG, LaTeX, etc. works
Same issue with bearblog.dev. They show you example rendered posts but not the example source
For the post source, it's just simple text markdown. SVG and LaTeX do not work. Most custom HTML and CSS does not work.
The allowed HTML elements/attributes and CSS rules that work are these: https://github.com/sirodoht/mataroa/blob/2d1524e1f3ba968efcb...
"signing up" is completely painless
they've alredy given you exactly what you're asking forThe font-family is sans-serif, so it does honor that browser setting, but if you'd prefer to read it in a serif font, too bad.
I'd also recommend to add open graph meta for the blog posts. Presumably people will want to share the posts somewhere; a nice set of open graph metas goes a long way.
With images I either have to eat the storage utilization for them or suffer a privacy leak by loading them when the post is opened. For the latter, there's always a small risk that a post could be deleted or an entire website vanish in between the time my feed updates and the time I open a post, in which case it would be left with text but broken images. I guess they could be inlined (like `<img src="data:image/png;base64,etc"/>`) to avoid that risk. It's even more obnoxiously complex if we're using the modern `picture`/`srcset`/etc to serve multiple resolutions and image formats for various screen sizes, connection speeds, and platforms.
The reason some blogs don't include the whole thing in the RSS is because they want you to visit the site for the ad revenue. It's not an oversight.
Blogging is (was?) a job for some people. It wasn't completely supported by ads, but ads are part of it. It's like YouTubers before YouTube.
This was around 2005 for what I can remember. Time is flying...
This happens with the HTML contents just as easily. Perhaps just include a unique identifier in the text per client, and a link back to the source.
On an individual scale, yes. But if you're a spammer and want to vaccuum up text from 1000 sites, you'll skip writing a scraper for individual sites (which may change their formatting later anyway) and just use reliably-formatted RSS feeds.
That sentence has widely different endings for different people.
For all its faults, this is something I have no shame invoking DMCA for. You still own the copyright on your writing even if you publish it for free online.
Genuine question - what does this enable? I assume the big guys love the additional tagging for engaging similar content, but what else is there?
First of all, having a dark mode by default is not minimalistic.
Edit: wow, downvotes without any explanation. You guys must be having a lot.
It would be good if it was possible for a reader to choose to use the opposite of their device setting but that would would less minimal (needs a UI, JavaScript, and client-side storage of the setting).
I'm on month 80 avoiding setting up a blog to capture my occasional thoughts and frequent side project adventures – mostly because I'd rather fiddle with the side projects than set aside time spinning up some blog platform (which often begins with promising I'll use asciidoc, and ends in frustration trying to render asciidoc _juuuuust_ right). I would love to have a dead-simple interface (for writing and reading) to collect words. But since most of those words will be about code, a lack of syntax highlighting will take residence in my mind.
(Tangentially related: I _love_ reader mode, because I like to read an article or two while rocking my baby to sleep, and reader mode offers dark mode, even on websites in stunning retina-burn white. The only downside of reader mode is how it kills syntax highlighting.)
Pretty much anyone can make this using Hugo, no?
If I wasn't already self-hosting ghost I would probably use this service.
You might as well give up on writing then.
Drew Devault gives out $20 to start your own blog. We need to perpetuate this culture, not oppose.