About DXNA

What DXNA is

DXNA lists what developers write on their own blogs. It reads each blog’s feed and shows every post as its title, one line of it, its author and the author’s domain.

Every post leads to the author’s own site. DXNA never shows a post inside DXNA, and DXNA carries no ads over the posts.

DXNA is not a social network, a blogging platform, a newsletter or a job board. It has no votes and no comments.

Where DXNA comes from

In the 2000s the Macromedia XML News Aggregator, MXNA, listed what the developers who worked with Macromedia’s tools wrote on their own blogs, in one place.

Reading the whole community was how MXNA readers found out what was happening, and being in that list was how a writer was found.

DXNA brings that way of reading back, for developers of every stack. Sign in with GitHub and DXNA starts you on the stacks you work in; the whole community is one click away.

Why I built DXNA

In the 2000s I was a Flash developer, and I kept a blog. It was mostly notes to myself, but people read it, because MXNA listed it next to every other Flash developer’s blog. MXNA was how I found out what the community was working on, and how the community found me.

When MXNA closed, that way of reading closed with it. Developers still write on their own blogs, but no one place lists them all, so a good post now waits for an algorithm to find it. DXNA is that one place again, for developers of every stack.

Who builds DXNA

I’m Akeem Philbert, and I have built software for over 20 years. I started with Flash and PHP for agencies and media brands in New York. Then I spent eleven years running Wepala, a consultancy that built products for startups and established businesses, including a payments platform that grew from a thousand transactions a month to six million. Today I write mostly Go, and I care most about domain-driven design, event sourcing and behaviour-driven development.

I write at ak33m.com, and you can find me on GitHub and LinkedIn.

What DXNA holds to

What DXNA lists

DXNA lists only what a person wrote themselves. DXNA does not list a blog whose posts a machine writes.

A blog is listed when it meets every one of these rules:

Using an LLM does not keep a blog off DXNA. The use of an LLM is judged by what the author meant by it: a tool that helps a person say what they mean is fine, and a tool that writes the posts for them is content automation. An author who leaned on an LLM heavily says so in the post.

DXNA’s crawler

DXNA’s crawler names itself in every request it sends: DXNA/1.0 (+https://dxna.dev/about#crawler). In a robots.txt it answers to User-agent: DXNA; where no group names DXNA, it follows the group for every crawler, User-agent: *. It waits at least a second between two requests to one site, and longer when your robots.txt sets a crawl delay.

What it reads, why, and how often:

These reads follow your robots.txt. Two reads do not: when an author claims her blog, DXNA reads the one page she names, as a browser would, to check that it links back; and when DXNA looks for an address to write to a blog’s author, it reads the feed and, if the feed gives none, the home page, once.

To keep DXNA out of your contact card and still have your feed listed, add a group for DXNA to your robots.txt:

User-agent: DXNA
Disallow: /.well-known/contact.vcf

A group that names DXNA takes the place of your User-agent: * group for DXNA, so copy into it any of those rules you want DXNA to follow. To keep the country out of your home page too, take the country out of its h-card, or add Disallow: /$ to the group. A rule that disallows your feed stops DXNA reading it, and your new posts stop appearing in DXNA.