ppll

Nadia Asparouhova

Writer and researcher on how people organise online; wrote Working in Public, on the maintenance of open-source software, and Antimemetics.

Nadia Asparouhova did not write this page. ppll compiled it from their own words, each linked to the source. Is this you? · Report a mistake

Follow

Latest x.com

What they believe

The bold line is korrents’ wording; the quote is theirs. These one: what they wrote before what they said aloud, one per source, newest first.

All 12 beliefs and 1 change of mind, on korrents

Beliefs

  • Korrents What they believe 12 beliefs, 1 changed mind — each backed by an exact quote.

    Each is a — compiled by korrents.com, not by them: the one-line wordings are korrents', the quotes are theirs.

    Recent

    Show 9 more
    • New licences are the wrong lever for paying maintainers: copyleft’s history shows terms companies ignore, and relicensing attempts get beaten back by their own communities.
      As for my personal feelings on the matter, however, I’m skeptical that new licenses are the right approach on a systemic level, both in terms of feasibility, as well as where I think the world is going.

      Making money with licenses Said 14 Mar 2019

      Full record — everyone who holds this →

    • Free riding is not open source’s problem: the users who only download the code impose no cost on anyone.
      Most users don’t actually impose costs back to maintainers: they download the code and never interact with the project.

      Making money with licenses Said 14 Mar 2019

      Full record — everyone who holds this →

      open source

    • Information once freely shared cannot be taken back, so charging for access to code is a pre-digital answer to a digital problem.
      Information, once freely shared, is a Pandora’s box that cannot be closed again. It is very hard for me to imagine a world where we transition back to paying for access to information; these are pre-digital solutions to modern problems.

      Making money with licenses Said 14 Mar 2019

      Full record — everyone who holds this →

    • A software foundation is little more than a tax status, and gets less public accountability than a company because everyone assumes its motives are good.
      There is nothing about a foundation that is inherently good, neutral, or charitable, simply because they have a 501(c) status.

      Governance without foundations Said 31 Oct 2018

      Full record — everyone who holds this →

    • A single foundation is structurally at odds with a project whose contributors are distributed, and is easier to capture than the project is.
      Rather, I think that “the foundation”, as a single point of failure, is structurally at odds with the idea of “the project”, which is inherently distributed.

      Governance without foundations Said 31 Oct 2018

      Full record — everyone who holds this →

    • A project that skips forming a foundation still has to formalise its governance, or it drifts into a tyranny of structurelessness.
      On the other hand, by avoiding foundations, projects also avoid the question of how to formalize their governance, thus risking a “tyranny of structurelessness” that might range from projects living inside a company forever, to disorganized chaos that negatively impacts project velocity.

      Governance without foundations Said 31 Oct 2018

      Full record — everyone who holds this →

    • The right to fork works as a standing threat rather than as an event; in mature open source, political forks are rare.
      The right to fork is still critical as an implied threat to keep the system in check. But major political forks aren’t as common, and certainly not as top-of-mind, anymore.

      Do financial incentives increase the threat of forks? Said 2 Jul 2018

      Full record — everyone who holds this →

      open source

    • Successful open source developers get hired away by companies, which quietens the very people best placed to argue for making a living from open source.
      Successful open source developers get “acquihired” by a company who values their reputation and skills, which has the perverse effect of making them less noisy about how to make a living off of open source.

      Who pays the toolmakers? Said 13 Jun 2018

      Full record — everyone who holds this →

      open source

    • Open source on GitHub creates enormous value that the platform hosting it captures none of, while its policies limit how maintainers may earn.
      Open source projects on GitHub represent billions of dollars in value creation, but none of that is captured on GitHub.

      Who pays the toolmakers? Said 13 Jun 2018

      Full record — everyone who holds this →

      open source

    Beliefs others hold too

    • The thing open source can actually sell is not the code but access to its maintainers’ attention and expertise. 2 hold this
      While everyone is focused on putting up tollbooths, opportunities to “price” maintainer attention, and access to maintainers, remain undervalued.

      Making money with licenses Said 14 Mar 2019

      Full record — everyone who holds this →

      open source

    • A contribution is a cost to the maintainer, not a gift: it is taking part, not merely using the code, that consumes a project’s scarcest resource. 2 hold this
      It’s only when users cross over to the production side (ex. report bugs, ask questions, submit patches) that they start to impose costs.

      Making money with licenses Said 14 Mar 2019

      Full record — everyone who holds this →

    All 12 beliefs and 1 change of mind →

What is a korrent?

A korrent is a belief a person has stated in their own words: one sentence stating the claim, backed by a quote and a source, kept at korrents.com.

Under a name here, the quoted block is what they actually said. The korrent beneath it is the claim those words support, in korrents' wording — tap it to see the record, its source, and who else holds it.

Nobody here wrote their own korrents. They are compiled from public statements, and a person can change their mind, which is recorded too.

Recommends rcmnd

  • rcmnd What they recommend 2 things — each backed by an exact quote.

    Compiled by rcmnd.app, not by them: the quotes are theirs, and each links to the post it was copied from.

    Recent

    • Recommends Rob Burbea's talks
      If you get to any point in your practice where you’re feeling WTF about it, I’d highly recommend Rob Burbea’s talks , which are thoughtful, philosophical lectures on each jhana.

      nadia.xyz 24 Sept 2024

      What others say about Rob Burbea's talks →

    • Loved Jhourney
      I primarily learned the jhanas on two Jhourney retreats in 2024. Jhourney is a company that takes a pragmatic, fun, and accessible approach to teaching the jhanas to beginners. They are markedly different from a typical meditation retreat, and I’m grateful they exist, because I don’t think I would’ve learned the jhanas otherwise.

      nadia.xyz 24 Sept 2024

      What others say about Jhourney →

    All 2 recommendations →

Where they publish

About the English under a post

Some people here publish in a language other than English. Where they do, this site shows a machine translation beneath the post, in this typeface — the site's own, not theirs.

The post itself is never changed, moved or hidden: what is set in the serif above is exactly what the person published, and it is what to quote them on. A translation can be wrong in ways that matter, especially about tone.

Only the post's own words are translated. A quoted post, a linked article and a belief on korrents.com are left in their original language.