Nathan Wrigley opens the latest Jukebox episode by introducing guest Wes Tatters, a technologist with nearly four decades of experience. Wes’s journey began on early home computers like the Commodore 64 and TRS-80 and moved through authorship, AV and media work, and now leadership at Rapyd Cloud, a globally distributed hosting company. Along the way he helped build communities on platforms such as CompuServe, AOL, and MSN and has been closely involved with open source projects, especially WordPress.
Wes traces the internet’s roots to DARPA’s objective of creating a resilient communications network. That early focus on redundancy and interoperability shaped the architecture that later allowed disparate systems to talk to one another. He contrasts those engineering origins with the early days of broadcast media, where even live TV interviews were slowed by satellite roundtrips and engineered “dump” controls—an image that underscores how far instant web conversation has come.
His own start in tech was practical and curious: programming rather than gaming, then working at an Australian IT firm with access to systems like Wang. He remembers the transformative sense of progress as modem speeds climbed from 300 baud to 56k—each step widened his reach from local to global. Bulletin-board-style forums and services like CompuServe enabled sustained conversations and connections that later became professional opportunities, including an invitation to write books on internet connectivity and early web browsers.
Wes recounts the excitement around Netscape and the birth of JavaScript. He was invited to document emerging features and helped produce one of the first developer guides for a language whose long-term significance was still unclear. Early web conferences were small and exploratory; he met pioneers such as Tim Berners-Lee and James Gosling and shares a whimsical memory of conference projects that show how informal and playful the community was at the time.
When asked about what pushed the internet into the mainstream, Wes points to Windows 95 and Microsoft’s MSN. Those products made online access straightforward for ordinary users and introduced community-focused features—forums moderated around television shows and other shared interests. In Australia, Wes curated some of those efforts and saw firsthand how community design was baked into consumer services long before social media took over the public imagination.
The conversation shifts to content-management platforms. Parallel efforts from Microsoft (ASP, DotNetNuke) and others ran alongside WordPress, which started as a blogging tool but grew into something far broader. Wes emphasizes WordPress’s pivotal role in democratizing publishing: non-developers could create sites, control content, and extend functionality via plugins and themes. That openness invited hosting companies, designers, and independent creators to build commercial ecosystems on top of an open foundation—aligning technical extensibility with values of ownership and free expression.
Wes gives concrete examples of community-driven WordPress solutions: during the COVID pandemic, private social platforms built on WordPress and services like BuddyBoss allowed professionals—doctors, frontline workers—to share information and coordinate away from public social networks. The ability to own raw data and control community spaces proved invaluable.
They also discuss the web’s social downsides. Wes points to data on loneliness and the idea of “false community”—many online interactions are shallow and can leave people more isolated. Mobile-first, always-on experiences encourage quick dopamine-driven consumption and short attention spans; newer platforms that prioritize ephemeral or highly consumable content can weaken deeper communal bonds.
The interview touches on Tim Berners-Lee’s semantic web vision—which relied on structured metadata—and why it didn’t fully materialize. Search engines favored indexable discoverability instead, and that indexing became the substrate for later layers of innovation. Artificial intelligence, for example, has rapidly added new capabilities: generative text and video tools can now summarize, plan, and create in seconds, altering workflows for businesses and creators.
Wes acknowledges missteps in how the internet evolved—particularly how commercialization and certain consumption patterns have shaped younger generations’ habits—but argues the web’s original design gives it room to self-correct. Communities tend to moderate themselves once they scale, and open-source ecosystems often renew through contributions, forks, and fresh conversations. He frames internal disputes within the WordPress community not only as challenges but as opportunities to rethink governance, contribution, and community health.
Events like PressConf and WordCamps matter because they bring people together to listen, learn, and collaborate. Wes stresses the importance of hearing diverse voices and then taking action to improve how projects are run and supported. Rapyd Cloud’s own remote-first, globally distributed team reflects the practical side of these values: aligning work hours to customer time zones, supporting a worldwide user base, and relying on connected, remote collaboration.
Wes closes with a cautiously optimistic view. Despite loneliness, misinformation, commercialization, and rapid technological change, he believes the core of community persists. WordPress’s openness and the internet’s resilient architecture give people tools to reclaim ownership of conversations and build spaces aligned with their values. His call to action is straightforward: listen more, get involved, and contribute—those are the ways to steer the web toward healthier communities.
Nathan thanks Wes for tracing the arc from early modems and community forums to modern AI and open-source platforms. Wes reiterates a simple message: conversation and community still matter most.