Main Track
Adversarial Interoperability - Writing a Microsoft Bob application
<p>I stumbled upon a forum post of Jean, tasked in 2010 with recovering text documents for a friend from their broken Windows 95 computer. Their friend used Microsoft Bob, and the Microsoft Bob letter writer exclusively.</p>
<p>I was fascinated by this story, and then spent months reverse-engineering the Microsoft Bob APIs. Ultimately producing the first third-party Microsoft Bob application. During this I learned that Microsoft Bob isn't only a laughable flop, (The word "only" is doing a lot of work here), it also had strong ideas on what computing should be.</p>
<p>We will take a tour of Bob and its history and what I discovered about its technical underpinnings while reverse engineering. </p>
<p>Hopefully I can convince you that these stories are still relevant today, and can inform us on how we think about the software we use. But most importantly; the software we recommend our (non-techy) friends and family to use.</p>
<p>Introducing Hard-working, Easy going Software Everyone Will Use</p>
Additional information
| Live Stream | https://live.fosdem.org/watch/janson |
|---|---|
| Type | maintrack |
| Language | English |
More sessions
| 1/31/26 |
<p>FOSDEM welcome and opening talk.</p>
|
| 1/31/26 |
<p>We need to talk about war. And we need to talk about companies building bots that propose to rewrite our source code. And about the people behind both, and how we preserve what is great about FOSS while avoiding disruption. How do geopolitical conflicts on the one hand and the risk of bot-generated (adversarial) code on the other influence the global community working together on Free and Open Source software?</p> <hr /> <p>The immense corpus of free and open source software created by a ...
|
| 1/31/26 |
<p>In 2025, the Git project has turned 20 years old, and in these 20 years it has taken over the world of version control systems by storm: nowadays, almost every developer uses Git. But that doesn't mean that Git is perfect and "done", or even close to it. It still has many warts: user experience, arbitrary limitations, performance issues and no good support for large binary files are just some of the issues that users commonly complain about.</p> <p>In this talk you'll learn what is happening ...
|
| 1/31/26 |
<p><a href="https://www.mercurial-scm.org/">Mercurial</a> is a Distributed Version Control System created in 2005.</p> <p>The project has been constantly active since then, fostering <a href="https://heptapod.net/">modern tooling</a>, introducing <a href="https://octobus.net/blog/2020-11-26-modern-mercurial">new</a> <a href="https://archive.fosdem.org/2025/schedule/event/fosdem-2025-5989-a-glimpse-into-a-smoother-version-control-experience/">ideas</a>, spawning multiple <a ...
|
| 1/31/26 |
<p>Git is a tool most programmers rely on, whether for work or personal projects. It’s far more than just a method for syncing local and remote changes. Git embodies a way of thinking that serves as the foundation for development workflows and steers project evolution.</p> <p>At its core, Git has essential concepts such as commits, change history, branching, rebasing, and merging. While Git offers many features, these are its heart. Misusing them can lead to significant opportunity costs, ...
|
| 1/31/26 |
<p>Does your project get pull requests that you dread reviewing? Have you ever submitted a pull request that got ignored by project maintainers?</p> <p>Putting together a pull request that presents proposed changes in a clear, well-organized way is nearly impossible for newer contributors to do on their own. Maintainers must take the lead in providing specific guidelines for pull requests for their project.</p> <p>This talk will give maintainers a toolkit for teaching contributors how to produce ...
|
| 1/31/26 |
<p>The state of the internet, c 1990:</p> <ul> <li>Limited, opt-in connectivity: people had to both have access to a computer and that computer had to have access to the internet.</li> <li>Tooling required some in-industry knowledge to be able to run and use, not only for development but also for communication. </li> <li>Open source was a young movement. The "common source" was proprietary.</li> </ul> <p>The state of the internet, c 2025:</p> <ul> <li>Always online, might-not-even-be-to-opt-out ...
|
