GoldED - GoldED

GoldED public record Front page rewritten

History. Source. Archive.

GoldED belonged to a whole message-world. Enough of it survived to deserve a proper record.

This site holds the GoldED lineage in one place: the original open-source release, the modern macOS port, the Laravel-based reinterpretation, the timeline, and the archive material around the wider FTN ecosystem. Nostalgia fog can wait outside.

Signal

Three code lines worth distinguishing.

History, archive, FAQ, and terminology now have their own rooms.

The next work is depth, sources, and curation.

What this is

GoldED belongs to the bulletin board and FidoNet world of message areas, packets, tossers, scanners, and message-base formats. If those words sound like a coded invitation to a basement meeting, that is exactly why this site needs a terminology page.

The project now has more than one line worth following: the historical GoldED3 release, the current macOS port, and GoldED 7, the Laravel-based reinterpretation. Treating those as one blurry thing would break the map before anyone starts walking.

The surrounding record matters too. Old `goldware.dk` captures, surviving docs, archive files, and format bundles are part of the story because they show the world GoldED lived in.

By-line Maintained by Odinn Adalsteinsson

With thanks to Dirk A. Müller, core-team contributor and part of the line this site is trying not to flatten into anonymous legend.

Why it matters

GoldED still matters because it was working software inside a real communication culture, not a loose artifact in a display case.

The historical record needs dates and sources.

The living ports need clear status.

The surrounding archive needs curation, not a shovel.

The three code lines

Same lineage, different jobs

Original release

GoldED3 is the anchor point.

The released source matters because it fixes the historical line in place. It is the part of the story that later ports and preservation work can actually point back to.

Living preservation

The macOS port keeps the old line honest.

A modern port changes the work from remembrance to maintenance. The old editor has to survive current machines, current habits, and the small indignities of contemporary tooling.

Greenfield reinterpretation

GoldED 7 asks what should survive on purpose.

This is the Laravel-based branch: a greenfield reinterpretation with a deliberately unreasonable name and a direct question about which GoldED instincts still earn their keep.

History and archive

The site needs both a timeline and an archive room.

The history page should become a dated timeline from early emergence through open-source release, preservation work, and current reinterpretation. Broad placeholders are fine for now. Fake precision is not.

The archive page should hold curated `goldware.dk` captures and downloadable zip bundles grouped by format. That means explanation, labels, and restraint. Old files do not become history just because they are old.

Open history Open archive

Related lineage

GoldED+ belongs in the family photo, even if it is not the main plot.

The wider lineage still matters, especially when it helps map what survived, what forked, and what people can still browse publicly without reconstructing the past from ash and half-dead links.

See GoldED+

Orientation pages

Useful before the deep dive

History

GoldED belonged to a whole message-world. Enough of it survived to deserve a proper record.

GoldED3 is the anchor point.

The macOS port keeps the old line honest.

GoldED 7 asks what should survive on purpose.

The site needs both a timeline and an archive room.

GoldED+ belongs in the family photo, even if it is not the main plot.

Build the timeline properly.

Curate the old web and the old message bases.

Answer the obvious questions once.

Explain the vocabulary without flattening it.

A short note on the person behind the project.