Science, culture, complexity

Tag: blogging

  • Against the idea of building loyal subscribers

    Daily writing prompt
    How do you build loyal subscribers?

    I’ve always found that a somewhat strange thing to aim for. I understand there are several thousand people worldwide working to build a loyal subscriber base (“building loyal subscribers” makes one sound like Dr. Frankenstein). And whatever their reasons are, I’m sure at least one of them is “to build community” or “to make money”. Those are perfectly legitimate things to do. But insofar as the question of a loyal subscriber base is raised with regards to writing, I don’t have an answer. Before I became a journalist in 2012, I’d been a blogger for four years, writing about physics and an intellectual life centered on that topic. After I became a journalist, I began to write on science, health, environment, spaceflight, higher education, science policy and administration, research fraud, and many other things that caught my fancy. And I continued blogging. Over time, I realised a few things:

    (i) I write because I have something to say, rather than because someone wanted something specific to read or even because someone might find what I say useful.

    Follow-up: I’ve found that by making of myself a better person every day, in as many of the infinite ways in which a life can be lived as possible, in steps marginally small or revolutionarily big, I can still ensure the number of people who find what I have to say engaging, entertaining or even useful is non-zero. That is, I believe good people have good things to say. I’m not there yet but I hope to be. As a corollary, my writing at various times has only mirrored me at various times, opening windows into my own psyche that might otherwise have taken me years of mental probing.

    (ii) I attach a great deal of importance to writing something just because one needs to say it, or more broadly to communicate per se, rather than keep it to oneself. No self-censoring (with reasonable limits).

    Follow-up: Writing has its own merits. The more you write, the better you write and the clearer you think. Importantly, these relationships are entirely independent of whether someone is reading your words. (To be sure, audiences are not redundant. Having one will also train you in the peculiarities of public sensibilities, social norms, satire, the virtues of dialogue, and what a difference writing when you’re angry makes, among other things.)

    (iii) The internet has increased by leaps and bounds a person’s ability to seek out, find, and consistently access new information. This includes both loitering over the internet, jumping from one website (or Wikipedia page) to the next, and staying in ‘touch’ using bookmarks, RSS feeds, email subscriptions, and other forms of notifications.

    (iv) Frankly, I care little for a loyal subscriber base. I care much more for having a place to write, for more people to write, and for you to find whatever kind of writing you’re looking for. (This is why my fondness for WordPress.com persists: the cost of getting started is just a little time, and not even any money.)

    (v) If there is something you won’t say because your subscribers might disagree and/or unsubscribe — I’ll be disappointed but not surprised. Such is the world. But if you won’t say something because your subscribers won’t be interested, you should drop the subscribers and keep the writing habit. If you can’t, you should admit that you’re being dishonest.

    Follow-up: Point (v) might do a good job of tempting you into believing that I’m really repudiating my readers (such as they are) before they can repudiate me, but in my defence… I don’t care.

    Granted in the first instance: applying these same ideas over and over while maintaining a fixed presence online — e.g. at the same domain name or the same account on a platform — is what leads to loyal subscribers. However, these days, you’ll agree such a base also demands that the writer, or content-producer more broadly, focus on a fixed set of themes, ideas, peeves or what-have-you. I don’t think I could ever promise such a thing. All I can promise is that I will think about the contents of a post to the best of my ability on that particular day before publishing it. This together with point no. (iv) means that if I write about bananas one day, I expect banana-reader to be able to discover it, and if I write about chillies the next day, I expect chilli-reader to be able to discover it.

    Granted in the second: my professional identity as a journalist is bound up with this kind of thinking. I’ve always only worked for publications that had a daily readership of at least a million. Each of my articles has been read by at least a few thousand people, but often by many more, and on some rare occasions by more people than the number that reads my blog in a whole year. You’ll have to trust me when I say I don’t take this readership for granted, and in return I will admit that it also allows me to adopt that laid-back but sincere policy towards my blog. If you won’t do something even when you’re suitably privileged, you suck.

  • Writing with WordPress Write

    I’m writing this post on Write, the new text composer/editor on WordPress.com. According to the official blog post, Write is a response to last year’s Creators survey, where “‘simplify the editor’ was the single most-requested improvement from the people already publishing on WordPress.com”. The tool itself was originally created by WordPress developer Jamie Marsland, with the WordPress.com team then adopting/adapting it. According to Marsland:

    WordPress is extraordinary software. But when you sit down to write a blog post, you’re greeted by a dashboard, a sidebar, an admin bar, a block inserter, a settings panel, and dozens of options that have nothing to do with the words you’re about to put down. For writers — especially those who aren’t developers — it’s a lot of visual noise between you and a blank page. Write strips all of that away.

    So far, Write looks good to me. WordPress.com ruined the writing experience when it introduced Gutenberg. Many bloggers have already commented that WordPress.com should just have brought back the Classic editor, i.e. the TinyMCE editor. I don’t think the Classic editor produces blocks when you publish, so it can’t benefit from the advantages of the block editor, such as they are.

    However, I also don’t think WordPress.com needs to go that far back to restore a good writing experience. Calypso, the WordPress.com front-end before Gutenberg, was remarkably smooth and conducive to writing. WordPress.com has been bloated for a long time; the “you’re greeted by a dashboard, a sidebar, an admin bar, a block inserter, a settings panel, and dozens of options” was as true of Gutenberg as it was of prior versions. What changed was the additional bloat of Gutenberg, which made the writing experience unwieldy and unsupportive of the speed of thinking, as it were.

    Since the launch of Gutenberg with WordPress 5.0 (and then Full-Site Editing with v5.9), I’ve considered the editor that shipped with Ghost.org, Koenig, to be the gold standard. To be clear, I’m restricting myself to editors that ship along with publishing platforms, rather than including standalone editors (in that case, my current favourite is Sublime Text). Ghost built Koenig on the Lexical framework and ever since its launch in 2018, it has been damn smooth.

    Koenig and Gutenberg both allow the writer (composer) to invoke blocks in the writing area. In Gutenberg alone, however, the view-port would jump back and forth depending on which paragraph the cursor was on, the cursor wouldn’t move in an intuitive war, the font in the composing area would change depending on the site theme, and there would be a noticeable lag when invoking a block or moving between paragraphs on a long article (1,000+ words across 5-6+ paragraphs).

    If Write is to stay good, it needs to beat Koenig (although hosting with WordPress remains a lot cheaper than hosting with Ghost, so there’s that). That means making Write easy to find, introducing and harmonising keyboard shortcuts — even now, Ctrl+S sometimes saves the post, sometimes asks to save the webpage —, supporting Markdown, and removing all of the clunk that belaboured Gutenberg.

    Most of all, as more and more writers use Write in different ways, the people at WordPress.com should streamline the feedback and changes that arise in a way that doesn’t compromise the raison d’être of Write. Losing track of that spirit was what gave us the Gutenberg writing experience in the first place.

    Featured image: A preview of the new Write editor. Credit: WordPress.com.

  • Memoirs, Substack, and psychology

    The English poet Blake Morrison had a thought-provoking essay in The Guardian titled ‘‘Enough of this me me me’: Blake Morrison on memoir in the age of oversharing’ on April 4. He traced the evolution of memoir from a self-congratulatory genre for the accomplished to today’s more “confessionalist” texts that are open to everyone, concluding that both forms have value — with a twist. In the course of his discourse, he arrives at two particular conclusions that struck me because he overlooks their real causes and skips a chance to clarify how cultural and institutional forces also shape literary form.

    (i)

    If memoirists can make a living through online snippets (with enough subscriptions, Substack pays well), why worry about publication in print? What’s so sacrosanct about a physical book?

    For myself – no social media junkie – I think published memoirs have plenty to offer that social platforms can’t, not least the rewards of a full-length story with a narrative arc, a set of characters, and an approach that doesn’t depend on sensational self-exposure, allowing room for reversals, surprises, digressions, complications and a tussle between adversity and reprieve. At their best, memoirs develop with a subtlety unavailable in a short extract and the writer faces bigger issues than how much to share – which tense to use, what stretch of time to cover, how many points of view to accommodate, and what resolution to offer, if any, since a life story written by a living person won’t have ended. Far from exulting in the drama of the tale they’re telling, memoir writers face the worry that it’s humdrum and inconsequential. Success lies in the quality of the telling, not in the shamelessness of the tale.

    This passage caught my eye because it seems to imply that writing via a publisher and unto a physical book will give rise to everything from a “full-length story with a narrative arc” to “allowing room for adversity … and reprieve” — whereas that writing for Substack cannot. This is true, but it is true for a reason that does not come through here: writing with a publisher gets you an editor, and if they are good they will empathise with your narrative, your stories, and they will guide you to improving it only the way a professional editor who knows how, and importantly why, good writing works. The reason writing for Substack does not get you these improvements is not because the platform magically disallows them but because the people who publish on Substack, or any blogging or newsletter platform for that matter, have elected to not have a second pair of eyes on their draft.

    Substack adoption bloomed in 2020 and many journalists, opinionists, commentators, and pundits migrated from indie platforms and legacy news publishers, because of Substack’s then-relatively-simpler options to monetise their content and/or to avoid what they perceived to be censorship. Democratising information benefits from democratising the platforms from which they can be broadcast, and Substack did help. But it also helped people with statements or opinions that an editor would have massaged or altogether removed sidestep that check keep talking. Good editors often push back and without that it is easy to believe everything one has to say is correct and that more people should hear it.

    But if a Substacker has an editor, they could get the same experience Blake Morrison says they would with a good publisher.

    (ii)

    What was once a geriatric, self-satisfied genre … is now open to anyone with a story to tell – “nobody memoirs”, the American journalist Lorraine Adams has called them. Candour is the key, no matter how fraught the consequences. “Most writers I know,” Maggie Nelson writes in The Argonauts, “nurse persistent fantasies about the horrible things – or the horrible thing – that will happen to them if and when they express themselves as they desire”. But she takes that risk, addressing the book to “you”, her fluidly gendered husband Harry (who’s angry when she shows him a draft), while exploring identity, pregnancy, motherhood and sexuality.

    “The words I love you come tumbling out of my mouth in an incantation the first time you fuck me in the ass, my face smashed against the concrete floor”; this appears in the first paragraph of The Argonauts in 2015. It’s hard to imagine an author volunteering that 30 years ago, or being allowed to be so passionately upfront (and violently facedown) at the start of the story. …

    Shock is an integral part of memoir and sometimes the facts are shocking, without embroidery. … In literature the mode used to be called confessionalism. These days, pejoratively, it’s called oversharing. At best it prompts welcome recognition: Wow, great, here’s someone who’s had the same experiences, thoughts and feelings that I’ve had. But there’s often resistance as well: Ugh. TMI. I don’t need to know this. When the divulgence is sad-fishing on Facebook, curated self-glorification on Instagram or out-there revelation in a memoir, readers may feel irritated or affronted. … It’s not essential for writers to bean-spill, after all. They’re not victims on a talkshow, outmanoeuvred by Jerry Springer or Jeremy Kyle; they’re writing on their own terms and in control of what’s committed to print.

    An important detail Blake Morrison leaves unwritten here — plausibly because that gives his readers “room to interpret and explore” — is mental health. Specifically, public awareness of mental well-being, of the forms and ways by which trauma can be inflicted, and how it can be healed is more widespread today than it was only two decades ago. Granted, in some geographies, including India, there is still a long way to go, but it is not inconsiderable. Awareness is all the more pronounced, if also often inchoate, on social media platforms such as Facebook and Instagram. And I would be really surprised if this had nothing to do with the rise of “nobody memoirs” that — at least in their best forms — have breached the shame associated with weirdness, idiosyncrasies, and the simple freedom to be one’s own person.

  • GST 2.0 + WordPress.com

    Union finance minister Nirmala Sitharaman announced sweeping changes to the GST rates on September 3. However, I think the rate for software services (HSN 99831) will remain unchanged at 18%. This is a bummer because every time I renew my WordPress.com site or purchase software over the internet in rupees, the total cost increases by almost a fifth.

    The disappointment is compounded by the fact that WordPress.com and many other software service providers provide adjusted rates for users in India in order to offset the country’s lower purchasing power per capita. For example, the lowest WordPress and Ghost plans by WordPress.com and MagicPages.co, respectively, cost $4 and $12 a month. But for users in India, the WordPress.com plan costs Rs 200 a month while MagicPages.co offers a Rs 450 per month plan, both with the same feature set — a big difference. The 18% GST however wipes out some, not all, of these gains.

    Paying for software services over the internet when they’re billed in dollars rather than rupees isn’t much different. While GST doesn’t apply, the rupee-to-dollar rate has become abysmal. [Checks] Rs 88.14 to the dollar at 11 am. Ugh.

    I also hoped for a GST rate cut on software services because if content management software in particular becomes more affordable, more people would be able to publish on the internet.

  • A blog questions challenge

    I hadn’t checked my notifications on X.com in a while. When I did yesterday, I found Pradx had tagged me in a blog post called “a challenge of blog questions” in March. The point is to answer a short list of questions about my blogging history, then tag other bloggers to carry the enterprise forward. With thanks to Pradx, here goes.

    Why did you start blogging in the first place?

    I started blogging for two reasons in 2008. I started writing itself when I realised it helps me clarify my thoughts, then I started publishing my writing on the web so I could share those thoughts with my friends in different parts of the world. My blog soon gave me a kind of third space on the internet, a separate world I could escape to as I laboured through four years of engineering school, which I didn’t like at the time.

    What platform are you using to manage your blog and why did you choose it? Have you blogged on other platforms before?

    I’ve blogged on Xanga, Blogspot, Typed, Movable Type, various static site generators, Svbtle, Geocities, Grav, October, Mataroa, Ghost, and WordPress. And I’ve always found myself returning to WordPress, which — despite its flaws — allows me to have just the kind of blog I’d like to in terms of look, feel, spirit, and community. The last two are particularly important. Ghost comes a close second to WordPress but it’s too magaziney. The options to host Ghost are also (relatively) more expensive.

    Earlier this year, Matt Mullenweg of Automattic tested my support for WordPress.com with his words and actions vis-à-vis his vendetta against WP Engine but the sentiments and conversations in the wider WordPress community encouraged me to keep going.

    How do you write your posts? For example, in a local editing tool, or in a panel/dashboard that’s part of your blog?

    I used to love WordPress’s Calypso interface and its WYSIWYG editor both on desktop and mobile and used to use that to compose posts. But then WordPress ‘upgraded’ to the blocks-based Gutenberg interface, which made composing a jerky, clunky, glitchy process. At that point I tried a combination of different local editors, including Visual Studio Code, iA Writer, and Obsidian.md. Each editor provided an idiosyncratic environment: e.g. VS Code seemed like a good environment in which to compose technical posts, Obsidian (with its dark UI) for angry/moody ones, and iA writer for opinionated ones with long sentences and complex thoughts.

    Then about three years ago I discovered MarsEdit and have been using it for all kinds of posts since. I particularly appreciate its old-school-like interface, that it’s built to work with WordPress, and the fact that it maintains an offline archive of all the posts on the blog.

    When do you feel most inspired to write?

    I’ve answered this question before in conversations with friends and every time my answer has prompted them to wonder if I’m lying or mocking them.

    When I feel most inspired to write is not in my control. I’ve been writing for so long that it’s become a part of the way I think. If I have a thought and I’m not able to articulate it clearly in writing, it’s a sign for me that the thought is still inchoate. In this paradigm, whenever I have a fully formed thought that I think could help someone else think about or through something, I enter a half-trance-like state, where my entire brain is seized of the need to write and I’m only conscious enough to open MarsEdit and start typing.

    In these circumstance my ability to multi-task even minor activities, like typing with one hand while sipping from a mug of tea in the other, vanishes.

    Do you publish immediately after writing, or do you let it simmer a bit as a draft?

    That depends on what I’m writing about. When I draft posts in the ‘Op-eds’ or ‘Science’ categories, I’m usually more clear-headed and confident about my post’s contents, and publish as soon as the post is ready. For ‘Analysis’ and ‘Scicomm’ posts, however, I distract myself for about 30 minutes after finishing a draft and read it again to make sure there aren’t any holes in my arguments.

    I also have a few friends who peer-review my posts if I’m not sure I’ve articulated myself well or if I’m not able to think through the soundness of my own arguments by myself (usually because I suspect there’s something I don’t know). Four of the most frequent reviewers are Thomas Manuel, Srividya Tadepalli, Mahima Jain, and Chitralekha Manohar.

    In all these cases, however, I do read the post a couple times more after it’s finished to fix grammar and clumsy sentence constructions.

    What’s your favorite post on your blog?

    No such thing. 🙂

    Any future plans for your blog? Maybe a redesign, a move to another platform, or adding a new feature?

    I’m not keen on major redesigns. There are too many WordPress themes available off the shelf and for free these days. I change my blog’s theme depending on my mood. I don’t think it makes a difference to whether or how people read my posts. I think those that have been reading will continue to read. The text is paramount.

    I don’t see myself moving to another platform either. If anything, I might move from WordPress.com to a self-hosted setup in future but it’s not something I’m thinking of right now.

    I am currently in the process of removing duplicated posts in the archives — at last count I spotted about 20. Many posts are also missing images I’d added at the time of publishing, mostly because they were associated with a domain that I no longer use. I need to fix that.

    A few years ago I lost around 120 posts after someone managed to hack my account when the blog was hosted with a provider of cPanel hosting services. I maintain a long-term backup of all my posts on a Backblaze dump. I’m still in the process of identifying which posts I lost and retrieving them from the archive.

    So yeah, focusing on this clean-up right now.

    Who’s next?

    This is embarrassing: I only know a few other bloggers. I stopped keeping track after many bloggers I’d been following in the early years just stopped at some point. Right now, of those blogs I still follow, Jatan and Pradx have already been nominated for this ‘challenge’. So let me nominate Suvrat Kher and Dhiya Gerber next, both of whom I think will have interesting answers.

    Featured image credit: Chris Briggs/Unsplash.

  • Posting stats — 2024

    When I joined The Wire in 2015, the average length of my blog posts increased from around 700 words to around 850 words, and over time to 1,000 words. This wasn’t forced so much as a natural reflection of the average length of pieces that worked on The Wire, also around 1,000 words. The trend held through 2018 and 2019 as well: the average post length dipped in these years because I published a very large number of posts and many of them were short, vignette-like. The same ‘natural forcing’ happened when I joined The Hindu in January 2023, with the average blog post length matching what worked at my workplace. I don’t understand exactly how this happens but I’m glad that it does.

    On a related note, I recently discovered this amusing snippet in The Book of Imaginary Beings (1969) by Jorge Luis Borges and Margarita Guerrero. Now I like to imagine I keep writing to prevent the monkey from drinking whatever is left of the ink…

  • A salvage

    At the start of this month, I began my first vacation in six years. A friend and colleague had done a similar thing recently and said that it takes a week just to switch off from thinking about work. My experience has been a little different, and the time off has also afforded a clearer view of the way I feel about what I do. I’m still to switch off from work, per se, but not because I’m so committed to the job. I think it’s because what I do for a living is a marginal extension of what I do in my default state: think about science, write, and keep learning. The last two are in fact my most favourite things to do. Work requires in addition to these things a scattering of obligations that I’m happy to fulfill and in exchange for a suitable fee. More recently, with India’s social and political climate being what it is, I realise that the things I like doing have acquired yet another layer of identity: that of being salvaged material – stories and ideas protected from the violence of misinterpretation, forgetfulness and irrelevance. I admit I much like the idea that my blog is a safe haven in this sense, but because it is, I also feel compelled to collect the preservation-worthy stories and ideas of others (as words or as permalinks). Most of all, it directly imbues the act of writing, within the framework of the internet and online publishing, with purpose. Purpose is easiest to acknowledge when its temper is evident in the smallest, most nuclear elements of the thing it inhabits. The purpose of war for example finds simple and complete expression in every plan conceived and bullet fired, in the direction of and against the welfare of Others. But it is much harder to answer the question “Why do you write?”. So when an answer presents itself, however briefly, you seize upon it, treasure it. You want more than anything to remember it because the instruments with which you express and understand purpose – words – are, to every writer, whether of postcards or of magnum opi, the same instruments with which to make and wield a million other meanings, and in the churn of which purpose is at constant risk of corruption. Words are semantically ergodic: they are capable of visiting every point in the universe of all possible meanings available to be constructed. This is infinitely beautiful but also diminishes the opportunities for historicity – of a sequence of events that is meaningful because of the sequence itself, instead of no one sequence being able to be privileged over any others. I can’t possibly write to visit every point in this universe, nor do I wish to; I write to construct a history that I find meaningful, and my heuristic of choice is the identity and evolution of purpose. Right now, it seems, the purpose is to salvage, and I’m grateful that it is as strong as to be immutable even in the articles and the commas of this silly post.

  • WordPress.com rolls back its botched ‘experiment’

    So, WordPress.com has restored the family of premium plans that it had until April this year, and has done away with the controversial ‘Starter’ and ‘Pro’ plans. The announcement on the WordPress.com blog yesterday has already garnered a high 65 comments, even as the post itself was brief and didn’t contain indication that WordPress.com had screwed up with the new plans. Excerpt:

    Our philosophy has always been one of experimenting, learning, and adjusting. As we began to roll out our new pricing plans a couple of months back, we took note of the feedback you shared. What we heard is that some of you missed the more granular flexibility of our previous plans. Additionally, the features you needed and pricing of the new plans didn’t always align for you. This led us to a decision that we believe is the right call.

    You might recall that when the new plans were announced in April, my blog post reacting to them became a big deal on the Hacker News forum on that day, and (probably) first drew the attention of Automattic chief Matt Mullenweg and WordPress.com CEO Dave Martin. Since then, WordPress.com has been working to adapt the ‘Starter’ and ‘Pro’ plans for different markets as well as introduced à la carte upgrades to remove ads, add custom CSS and buy more storage space. However, the company continued to receive negative feedback on the changes from the previous plans.

    One vein that I really resonated with was a rebuttal of WordPress.com’s claim that the older plans were messy whereas the newer ones are clearer. That’s absolutely not true. But on July 21, they seemed to have finally really listened and changed their minds for the better. (And even then, there are many expressions of confusion among the 65 comments.)

    I also want to point out here that WordPress.com is being disingenuous when it claims its new plans were an “experiment”. That’s bullshit. No experiment rolls out to all users on production, is accompanied by formal announcements of change on the official blog and, in the face of criticism, forces the CEO to apologise for a hamfisted rollout process – all without mentioning the word ‘experiment’ even once. WordPress.com is saying now that its development has followed the path of “experimenting, learning, and adjusting” when all it did was force the change, inform users post facto, then solicited feedback on which it acted (before doing that in advance), and finally reverted to a previous state.

  • The Higgs boson and I

    My first byline as a professional journalist (a.k.a. my first byline ever) was oddly for a tech story – about the advent of IPv6 internet addresses. I started writing it after 7 pm, had to wrap it up by 9 pm and it was published in the paper the next day (I was at The Hindu).

    The first byline that I actually wanted to take credit for appeared around a month later, on July 4, 2012 – ten years ago – on the discovery of the Higgs boson at the Large Hadron Collider (LHC) in Europe. I published a live blog as Fabiola Gianotti, Joe Incandela and Rolf-Dieter Heuer, the spokespersons of the ATLAS and CMS detector collaborations and the director-general of CERN, respectively, announced and discussed the results. I also distinctly remember taking a pee break after telling readers “I have to leave my desk for a minute” and receiving mildly annoyed, but also amused, comments complaining of TMI.

    After the results had been announced, the science editor, R. Prasad, told me that R. Ramachandran (a.k.a. Bajji) was filing the main copy and that I should work around that. So I wrote a ‘what next’ piece describing the work that remained for physicists to do, including open problems in particle physics that stayed open and the alternative theories, like supersymmetry, required to explain them. (Some jingoism surrounding the lack of acknowledgment for S.N. Bose – wholly justifiable, in my view – also forced me to write this.)

    I also remember placing a bet with someone that the Nobel Prize for physics in 2012 wouldn’t be awarded for the discovery (because I knew, but the other person didn’t, that the nominations for that year’s prizes had closed by then).

    To write about the feats and mysteries of particle physics is why I became a science journalist, so the Higgs boson’s discovery being announced a month after I started working was special – not least because it considerably eased the amount of effort I had to put in to pitches and have them accepted (specifically, I didn’t have to spend too much time or effort spelling out why a story was important). It was also a great opportunity for me to learn about how breaking news is reported as well as accelerated my induction into the newsroom and its ways.

    But my interest in particle physics has since waned, especially from around 2017, as I began to focus in my role as science editor of The Wire (which I cofounded/joined in May 2015) on other areas of science as well. My heart is still with physics, and I have greatly enjoyed writing the occasional article about topological phases, neutrino astronomy, laser cooling and, recently, the AdS/CFT correspondence.

    A couple years ago, I realised during a spell of daydreaming that even though I have stuck with physics, my act of ‘dropping’ particle physics as a specialty had left me without an edge as a writer. Just physics was and is too broad – even if there are very few others in India writing on it in the press, giving me lots of room to display my skills (such as they are). I briefly considered and rejected quantum computing and BECCS technologies – the former because its stories were often bursting with hype, especially in my neck of the woods, and the latter because, while it seemed important, it didn’t sit well morally. I was indifferent towards them because they were centered on technologies whereas I wanted to write about pure, supposedly boring science.

    In all, penning an article commemorating the tenth anniversary of the announcement of the Higgs boson’s discovery brought back pleasant memories of my early days at The Hindu but also reminded me of this choice that I still need to make, for my sake. I don’t know if there is a clear winner yet, although quantum physics more broadly and condensed-matter physics more specifically are appealing. This said, I’m also looking forward to returning to writing more about physics in general, paralleling the evolution of The Wire Science itself (some announcements coming soon).

    I should also note that I started blogging in 2008, when I was still an undergraduate student of mechanical engineering, in order to clarify my own knowledge of and thoughts on particle physics.

    So in all, today is a special day.

  • Hosting a Ghost blog on Fly.io

    Fly.io is a platform as a service (PaaS) provider. I discovered it after the Heroku hack earlier this year precipitated many discussions on Hacker News about suitable alternatives.

    Among them, I found Render.com and Fly.io to be most suitable (no affiliate links). Railway.app didn’t make the cut because it doesn’t have persistent storage, which imposed certain limitations on how much Ghost could simplify your blogging workflow, e.g. changing themes. I’m sure there are other PaaS cos but these appeared to be the most popular alternatives.

    Between Fly.io and Render.com, the former seemed better because it has more locations and has a generous free tier. This said, you’ll find that hosting on either can be much cheaper and come with more peace of mind than with many other options.

    So without further ado, here’s a noob’s guide to hosting your Ghost blog on Fly.io.

    Install the Fly.io command line interface

    Open the Terminal app on your Mac or its counterpart on Windows/Linux. There…

    On MacOS

    brew install flyctl

    On Windows

    iwr https://fly.io/install.ps1 -useb | iex

    On Linux

    curl -L https://fly.io/install.sh | sh

    Create a folder for your blog and then move into it

    Within the Terminal itself, type:

    mkdir <name-of-your-blog>

    cd <name-of-your-blog>

    Sign up for a Fly.io account

    flyctl auth signup

    This will open a tab in your default browser and start the sign-up process. Fly.io will ask for your card details. You won’t be charged unless you exceed the limits of the free plan; it requires your card to prevent people from abusing the resources in its free plan. Once you’re done signing up, check your Terminal (or its counterpart), where it should say something like “you’re signed from <your-email-ID>”. If you see it, good.

    Launch a Ghost site

    flyctl launch --image=ghost:5-alpine --no-deploy

    You’ll be asked to choose a region at which to situate your site. Use up and down arrows on your keyboard select your region of choice and hit enter.

    This step will generate a TOML file in the folder you’re in, called fly.toml. The contents of this file will dictate what Fly.io needs to do the next time you deploy your site. Become able to edit the file with this command:

    nano fly.toml

    Some checks

    The first line will say app = "<your-app-name>". The name will be something like fiery-shadow-1234. Make sure the url environment variable is equal to "fiery-shadow-1234.fly.dev". Also make sure that internal_port value, under [[services]], is 2368.

    One addition

    In a new line after the one that reads port = 443, add the following:

     [[services.ports]]
    handlers = ["http"]
    port = 80

    Once you’re done, you can exit with ctrl + x.

    Create a volume that will store your site’s database

    Fly.io offers up to 3 GB of storage on its free plan. This proved more than sufficient for my blog, which has 10 years’ worth of posts and images. Going ahead, you could host images on Flickr or Cloudinary (both offer sufficiently ample free plans).

    flyctl volumes create data --size 2

    (‘2’ here refers to the volume’s size in GB.)

    You will be asked to choose a region in which to deploy the volume – choose the same one as for your site.

    Mount the volume

    Open the fly.toml file and check for a section called [mounts]. If there isn’t one, add it.

     [mounts]
    source = "data"
    destination = "/var/lib/ghost/content"

    Exit with ctrl + x.

    You’re ready to fly.

    Launch

    Type the following command and hit enter:

    flyctl deploy

    The Terminal will show you the progress of your deployment. You can also view it on your new Fly.io dashboard, under ‘Monitoring’ on the left sidebar. Your site will be ready if you see a line that says “1 desired, 1 placed, 1 healthy, 0 unhealthy”. If you see it, open a tab on your browser and navigate to fiery-shadow-1234.fly.dev to see your Ghost site.

    If, however, you run into trouble, check out Fly.io’s troubleshooting guide.

    Custom domain

    To use a custom domain for your site, navigate to ‘Certificates’ on the left sidebar on your Fly.io dashboard and click ‘Add certificate’. Follow the instructions that appear on screen to, first, verify that you own the domain you’re using and, second, add the A and AAAA records – both with your domain registrar.

    Say your domain is example.com. Once Fly.io verifies the records, open the fly.toml file and edit the url thus:

    url = "example.com"

    Exit and redeploy your site:

    flyctl deploy

    Importing posts

    If you, have a sizeable JSON file of your exported Ghost posts, the CMS may fail repeatedly to import them. To get around this, go to ‘Scale’ on your dashboard sidebar and set the “Size name” to shared-cpu-1x and “Memory” to 1GB. You should be able to import the JSON file now.

    Once the import is done, you can reset the “Memory” to 256MB, which the free plan offers. You might incur a small charge for this short-lived change (the billing is per-second). You can check Fly.io’s prices on this page. In any case, you should expect to pay lower than if you were to host with Ghost(Pro) or self-host on Digital Ocean. Ghost(Pro) also offers to manage the setup so you can focus on your site, but that’s also the purpose of PaaS.

    To have your (forthcoming) posts backed up, you could set up a Zapier integration that copies the contents of each new post – taken from the RSS feed – into a Doc file in a folder in your Google Drive account. Again, Zapier offers this for free (as long as you’re not the sort of furious blogger who publishes three posts a day every day).

    A final note

    Peace of mind is important, especially if you’re not familiar with the tools you’re using to set up your site. Launching your blog based on instructions from the internet is one thing; putting out a fire when something goes wrong will be something else entirely.

    With PaaS, this worry is lower, but providers like Fly.io, Render.com and Railway.app are still oriented at developers, and so is their support team and documentation. This is to say that even if they help you, they will expect some level of technical chops from you.

    If you’re confident that you can manage, go ahead because there are significant advantages. One of them, for me personally, is that with regular backups I have a relatively risk-free environment in which to learn these things, and I believe that this knowledge will serve me well in the longer term.

    Root Privileges itself will continue to be a WordPress site hosted in a more ‘conventional’ way because it’s too important for me to be experimenting with at this point. But I’ll be changing my publishing workflow to be Fly + Ghost first, meaning I’ll be publishing posts there first and, more importantly, regularly thinking about how I can improve my experience there.

    Sources

    I compiled this guide based on instructions on the following pages:

    The authors of the latter two guides have put together nearly complete instructions. But each of their guides taken separately didn’t work for me whereas a combination did. If my guide didn’t work for you, you can also check out their guides and where they’ve deviated.

    I should also mention that I discovered that a Ghost blog could be hosted on Fly.io after finding that Anil Dash’s blog is.