Science blogs have been around for at least 20 years and have become an important part of science communication. So are there any fundamental issues that need fixing?
Barriers to Entry
Blogging platforms are mature at this point, and the technology is not imposing barriers to entry for most people. The user experience has greatly improved over the last few years and there are a number of affordable ways for hosting a blog that also work for science blogs, including free options such as GitHub Pages.
Science blogs have traditionally been free to read, but there is a general trend towards subscriptions for blogs (and related newsletters), as the advertising business model isn't really working for niche content such as most science. How to sustain science blogging in the long run is an unresolved question, and charging authors (beyond a nominal hosting fee) doesn't look like a path forward. Luckily the costs of publishing science blogs are very reasonable compared to journal publishing or hosting research data and code.
The basic functionality of formatted text with embedded figures and links is supported by many blogging platforms. The requirements of data-intensive science, e.g. interactive visualizations, can be a challenge, but that is also true for publishing journal articles. Interactive environments such as Jupyter Notebooks might be a better fit for these use cases.
Reference management is probably the biggest gap in science blogging, as handling more than a few references in standard ways is not easily done by hand.
Impact or Credit
Unfortunately a lot of the activities of scholars are driven by perceived Impact or Credit, and science blogs typically don't score high in this regard – with the exception of some disciplines such as mathematics. There is probably no short-term solution, and I am not even sure it is a problem that needs fixing.
The long-term solution should focus on increasing the visibility and thus discoverability of science blogs to reach a larger audience. As I discussed in a previous post, my preferred approach is a central repository for science blog content originally published in many different locations (the PubMed/PubMed Central) model.
This leaves persistence as the other main problem with science blogs besides discoverability that needs fixing. Link rot (the resource identified by a URI vanishes from the web) and content drift (the resource identified by a URI changes over time) are well-known problems with digital content, from newspapers to scholarly content. There are mainly two approaches to address this problem:
- Archiving using generic services such as the Internet Archive and specialized services such as Software Heritage for software source code or Portico for scholarly content.
- Persistent Identifiers by maintaining links independent of URL host and path, both of which may change over time. This blog post of mine is almost 14 years old, and the URL has changed at least four times as I changed blogging platforms. Since 2021 the post has had a persistent identifier in form of a DOI, and that DOI will not change going forward, eventually pointing to an archive when I retire.
Some science blog content is ephemeral and may not be worth archiving, but a lot of content is still worth reading years later (the first post of this blog is more than 15 years old), even if only to provide historical context.
In summary, we don't need to fix everything with science blogs but rather focus on two aspects: discoverability and persistence. In doing that we also need to sort out better sustainability for science blogs, and as an added bonus improve their reference management.
Discoverability and persistence are an issue for all science blogs, and we are trying to fix them by launching the Rogue Scholar in the second quarter of 2023. If you are managing a science blog and care about discoverability and persistence, sign up for the Rogue Scholar waitlist. Particularly if your blog is no longer actively maintained, for example blogs hosted by grant-funded projects that have ended or are ending soon.
Today I launched the Rogue Scholar Documentation site, where I will document how to use the Rogue Scholar, e.g. what you can do to prepare your science blog for Rogue Scholar archiving. The site is written in markdown and hosted on GitHub, so feel free to ask questions or suggest additions via the links provided by the documentation site.