Summary
- After Christmas 2009, Mirjam Kühne found that apparent forum activity on RIPE Labs was spam; she blocked bogus users and removed their topics.
- From its 2009 launch through Kühne’s 2020 editorial hand-off to Alun Davies, RIPE Labs shows how openness depends on accountable editorial labour.
The first practical test of RIPE Labs was not a celebrated article or a major community milestone. It was a cleanup job. After Christmas 2009, Mirjam Kühne looked at activity on the new site and found that what appeared to be participation was spam. She blocked bogus users and removed their topics.
That episode matters because it makes editorial work visible. An open technical publication can invite contributions, but invitations do not select useful material, remove abuse or decide which format best supports readers. Someone still has to make those decisions. In RIPE Labs’ case, Kühne’s account places that work inside a longer transition: from an informal channel for tools and prototypes, to a broad publication with contributions from staff and the wider community, and eventually to a named editorial succession.
The evidence does not establish that the spam episode directly caused the later move from forums to a blog. It does support a more careful editorial inference: when a publication is open, its usefulness depends on assigning responsibility for the friction that openness creates.
An informal beginning
Daniel Karrenberg and Robert Kisteleki set up RIPE Labs in 2009 as an informal channel for tools and prototypes. The site launched on 6 October 2009. Its scope was deliberately broad, leaving room for technical experiments, observations and contributions that did not fit neatly into a formal policy document or a single institutional category.
Kühne was later asked by the RIPE NCC to return and establish RIPE Labs as a platform for community building. That assignment is important for understanding her role. The evidence does not support calling her the sole founder or inventor of RIPE Labs. Karrenberg and Kisteleki set it up. Kühne’s contribution was to help establish the editorial and operational conditions under which the platform could become durable.
Those conditions are easy to overlook when “community” is treated as an outcome rather than a system. A platform may be open to contributions, but contributors need a route into publication, readers need a way to distinguish signal from noise, and the organisation needs someone who can make decisions when the rules do not answer every case.
When participation is not participation
The post-Christmas incident was a small but concrete example. Kühne recorded that apparent forum activity was spam. She blocked bogus users and deleted their topics. Nothing in the evidence establishes the scale of the abuse, its long-term consequences or a direct causal link to a later product decision. The significance lies elsewhere: the publication required active intervention before the visible activity could be treated as meaningful participation.
That is an editorial problem, not merely a technical one. A filter can identify patterns, but a person or accountable team still has to decide what belongs, what should be removed and what the publication is trying to protect. The choice also carries reputational consequences. If unwanted activity remains visible, readers may lose confidence in the channel. If moderation is opaque or overbroad, contributors may lose confidence in the invitation to participate.
Kühne’s account therefore gives the episode a useful operational place in the story. It shows the cost of openness early, before the publication’s later shape is easy to describe in hindsight.
From forums to a journal-like publication
Kühne later described the original forums as clunky and said RIPE Labs moved to a pure blog format in which readers could comment on articles. The sequence supports an account of format becoming part of editorial governance. A forum and a blog organise attention differently. A forum foregrounds ongoing threads; a blog foregrounds selected articles and gives readers a defined object to read and discuss.
The evidence does not say that spam caused the move. A stronger claim would be unsupported. But the two facts can be placed in the same editorial analysis. First, the open channel generated a moderation burden. Later, the publication adopted a format that placed articles, rather than undifferentiated forum activity, at the centre of participation. Sofia Ren’s reading is that this was not a story of removing friction. It was a story of assigning friction: selection, moderation, presentation and continuity became visible responsibilities.
That distinction helps explain why the word “journal” is useful here as an editorial description, not as a claim about formal status. RIPE Labs was not thereby a statement of RIPE policy, consensus or endorsement. Its value came from providing a curated publication space where technical material and community contributions could be made legible to readers.
Broad scope, bounded evidence
The breadth of the publication created another responsibility: maintaining a coherent standard without narrowing the invitation too far. At the 1,000th article, Kühne reported that RIPE NCC staff and contributions from the wider community were almost equal. That observation belongs specifically to her retrospective at that milestone. It should not be extended into a general claim about every period of RIPE Labs or about the entire technical community.
Even so, the milestone illustrates the mechanism of an open publication. Staff participation can provide continuity and institutional memory; community participation can bring experience, experiments and questions from outside the organisation. Neither side removes the need for editorial judgement. Someone must decide how a contribution fits the publication, how it is presented and how readers can respond.
The balance also makes the hand-off question unavoidable. If a publication depends on one person’s memory or informal authority, its continuity is fragile. If its standards and responsibilities are sufficiently visible, a successor can inherit more than a URL: they can inherit a working editorial role.
The 2020 hand-off
In 2020, Alun Davies took over as RIPE Labs Editor as Kühne moved into the RIPE Chair role. This article treats that transition only as the endpoint of the editorial period and as a named hand-off boundary. It does not use the later role to reopen a separate argument about chair governance, consensus or neutral process.
The importance of the transition is practical. A durable publication needs continuity, but continuity is not the same as permanence of personnel. The named successor shows that editorial responsibility could be handed over. It also clarifies what should be handed over: not ownership of every future outcome, but responsibility for selection, moderation, format and the relationship with contributors and readers.
This is the central lesson of Kühne’s period at RIPE Labs. Openness is often described as the absence of gates. In practice, an open publication needs accountable gates: a way to decide what enters, a way to remove abuse, a format that helps readers navigate material, and a person who can explain or own those decisions. The gates do not invalidate participation. They make participation usable.
The post-Christmas cleanup, the move away from clunky forums, the broad editorial scope and the 2020 hand-off are not a simple causal chain. The sources do not justify saying that one incident produced one redesign or that one editor created the entire publication. Together, however, they support a disciplined inference. RIPE Labs became more than an informal tools-and-prototypes channel because editorial friction was assigned rather than denied.
That is why Kühne’s contribution is best understood as editorial labour. She did not found RIPE Labs alone. She helped make a community-facing publication operational: by dealing with the unwanted activity that openness invited, by working within a broad scope, by supporting a format centred on articles and comments, and by reaching a point at which the editorial role could be handed to Alun Davies. The journal-like character was not the absence of friction. It was the presence of accountable decisions.
Sources
- https://labs.ripe.net/author/mirjam_kuhne/
- https://labs.ripe.net/author/mirjam/this-is-the-1000th-ripe-labs-article/
- https://labs.ripe.net/author/mirjam/fighting-spam-on-ripe-labs/
- https://labs.ripe.net/author/ulka_athale_1/meet-the-new-ripe-chair-an-interview-with-mirjam-kuhne/
- https://labs.ripe.net/author/alun_davies/a-brand-new-look-at-the-best-of-ripe-labs/
Member Briefing
Deeper Profile Context
Sign in with the right membership level to unlock the full briefing and source notes.
Only for Strategic Circle
Strategic Circle
Open to all readers. Unlock profile briefings after joining and signing in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership Alliance
