WEBVTT 00:00.000 --> 00:10.000 I'm particularly interested the first time meeting the folks from BOMFI here myself. 00:10.000 --> 00:15.000 I've been following the project from a distance but I'm really happy to meet them both 00:15.000 --> 00:20.000 and looking forward to hearing how things are going so I will pass across the mic 00:20.000 --> 00:23.000 and let's hear about MOMFI. 00:23.000 --> 00:24.000 Did I put? 00:24.000 --> 00:25.000 Yeah, it works. 00:31.000 --> 00:32.000 Thank you. 00:32.000 --> 00:40.000 So we are quite happy that Mastodam take the lead this morning not having a technical talk. 00:40.000 --> 00:45.000 Our talk will not be a technical leader and we think it's actually a good sign. 00:45.000 --> 00:52.000 And actually also the title is not the real one because this talk is called a contaminated infrastructure. 00:53.000 --> 00:58.000 And this is talk about embracing contamination. 00:58.000 --> 01:04.000 It suggests with example how we can allow ideas, code and communities to reshape each other 01:04.000 --> 01:09.000 for a mutual benefit about how we approach and navigate complexity in BOMFI. 01:09.000 --> 01:14.000 About an alternative path to the big tech dominant vision and about how the Fedivers and the social web 01:14.000 --> 01:19.000 can enable building things that are greater than the sum of their part. 01:19.000 --> 01:23.000 And also about why it is important right now. 01:23.000 --> 01:28.000 To talk about contamination may be easier to start from the opposite and the opposite of contamination 01:28.000 --> 01:29.000 is purity. 01:29.000 --> 01:34.000 And the Silicon Valley builds for purity. 01:34.000 --> 01:37.000 They scale by eliminating variants. 01:37.000 --> 01:40.000 They change acquisition over partnership. 01:40.000 --> 01:43.000 They create wallet guard and over ecosystem. 01:43.000 --> 01:48.000 And they use everything they create are monetized. 01:48.000 --> 01:52.000 And therefore big tech produces monocultures. 01:52.000 --> 01:54.000 And monocultures are fragile. 01:54.000 --> 01:59.000 And when a platform identifies users have nowhere to go with their relationship intact. 01:59.000 --> 02:05.000 When a company strategy shift and their communities discovered their infrastructure was only rented. 02:05.000 --> 02:10.000 And their landlord can change the rules and kick them out anytime. 02:10.000 --> 02:12.000 We see this in agriculture. 02:12.000 --> 02:14.000 Monocultures produce enormous yields. 02:14.000 --> 02:18.000 We can use it in the field of pesticides that the single crops can resist. 02:18.000 --> 02:22.000 Then everything collapses at once. 02:22.000 --> 02:24.000 We are watching the same things happening in tech. 02:24.000 --> 02:26.000 Platform after platform. 02:26.000 --> 02:28.000 The same pattern. 02:28.000 --> 02:30.000 But communities need a viable alternative. 02:30.000 --> 02:33.000 The democracy needs social infrastructure. 02:33.000 --> 02:35.000 The tarpabli common good. 02:35.000 --> 02:36.000 Yeah. 02:36.000 --> 02:39.000 And so we are trying to take a different path. 02:39.000 --> 02:44.000 It's an infrastructure that can involve through the people that we meet and get involved. 02:44.000 --> 02:50.000 We try and build components that interact and combine in ways that even we can't predict. 02:50.000 --> 02:53.000 Organizations that we shape each other's road maps. 02:53.000 --> 02:56.000 Resilience through entanglement rather than control. 02:56.000 --> 03:03.000 We think that plurality is actually a strength rather than a problem to be hidden and complexity as well. 03:03.000 --> 03:06.000 And yes, this means that people are constantly asking. 03:06.000 --> 03:08.000 But what is bonfire? 03:08.000 --> 03:09.000 I don't get it. 03:09.000 --> 03:12.000 And sorry if you still don't get it after this talk. 03:12.000 --> 03:19.000 At first glance, bonfire might look like another microblog in platform. 03:19.000 --> 03:21.000 But we try to go beyond that. 03:21.000 --> 03:25.000 You can share long-form articles, events, book reviews and much more. 03:25.000 --> 03:27.000 And unlike traditional social networks, 03:27.000 --> 03:30.000 where connections are just like friends or followers, 03:30.000 --> 03:33.000 bonfire goes beyond that binary. 03:33.000 --> 03:36.000 You can create circles for like your family, a book club, 03:36.000 --> 03:39.000 a fostering peers, or any group you want. 03:39.000 --> 03:44.000 And when you post, you can choose what circles can see interact or even comment or edit. 03:44.000 --> 03:47.000 Each circle also comes with its own feed. 03:47.000 --> 03:51.000 And you can then share a circle itself publicly. 03:51.000 --> 03:54.000 And that becomes like a starter pack in bush guy. 03:54.000 --> 03:56.000 Or just with selective circles. 03:56.000 --> 03:59.000 Bonfire puts communities in control of their experience. 04:00.000 --> 04:02.000 And how do we do that? 04:02.000 --> 04:06.000 It's by being modular and extensible. 04:06.000 --> 04:09.000 Every feature in bonfire, every bonfire app, 04:09.000 --> 04:12.000 is assembled from extensions. 04:12.000 --> 04:16.000 Extensions aren't just add-ons, plugins that you can add a little feature. 04:16.000 --> 04:17.000 They're the substance. 04:17.000 --> 04:20.000 Everything in bonfire is built as an extension. 04:20.000 --> 04:23.000 And that means that you can swap them out and replace them. 04:23.000 --> 04:27.000 Every feature, including posts, accounts, following, likes, boosts, events. 04:27.000 --> 04:33.000 All of that is just an extension that can be replaced or forked. 04:33.000 --> 04:36.000 This means communities can assemble their own apps, 04:36.000 --> 04:40.000 enable what they need, disable what they don't, set their own defaults. 04:40.000 --> 04:42.000 And people can create their own extensions, 04:42.000 --> 04:46.000 and easily fork them and customize just a specific feature 04:46.000 --> 04:52.000 without having to maintain an entire fork, which takes a lot of work. 04:52.000 --> 04:55.000 The software then becomes different things in different hands and bonfire 04:55.000 --> 04:57.000 adapts to each context. 04:57.000 --> 04:59.000 No communities need the exact same thing. 04:59.000 --> 05:03.000 And thanks to modularity, we don't have to pretend that they do. 05:08.000 --> 05:11.000 An activity pop is what enables all of that. 05:11.000 --> 05:15.000 It enables features and content to flow between platforms and apps. 05:15.000 --> 05:17.000 And since they're evolving as they go, 05:17.000 --> 05:20.000 the specifications are very rich and extensible. 05:20.000 --> 05:23.000 We can go beyond notes with events, articles, audio, 05:23.000 --> 05:27.000 etc., etc., a whole vocabulary of social forms. 05:27.000 --> 05:31.000 And we're building for communities that don't have a single purpose 05:31.000 --> 05:34.000 and can do whatever they need to do. 05:34.000 --> 05:37.000 We want to support a diversity of needs, 05:37.000 --> 05:40.000 and that's why software needs to be able to be changed 05:40.000 --> 05:43.000 by their users, by people involved. 05:43.000 --> 05:46.000 Communities can become a meeting point, 05:46.000 --> 05:50.000 where everything flows through your space without losing shape. 05:50.000 --> 05:54.000 And people don't have to sign up to a bunch of different places. 05:54.000 --> 05:58.000 This doesn't mean centralizing everything in one place. 05:58.000 --> 06:02.000 It just means that everything is discoverable where you are. 06:02.000 --> 06:05.000 But people can still use the best tool for the job. 06:05.000 --> 06:08.000 If you want to upload a video to appear to you, that's great. 06:08.000 --> 06:11.000 But it can still flow back to your space and not feel disconnected. 06:11.000 --> 06:19.000 But Federation and Contamination depends also beyond code. 06:19.000 --> 06:23.000 Between organizations, between different people, 06:23.000 --> 06:26.000 between different communities, between different ways of working. 06:26.000 --> 06:29.000 Bonfire exists within this web of alliances. 06:29.000 --> 06:32.000 Each of them bringing different expertise. 06:32.000 --> 06:34.000 Each shaping what we are building together. 06:34.000 --> 06:36.000 And here are some example. 06:37.000 --> 06:41.000 Newsman's Foundation, there are UK non-profit. 06:41.000 --> 06:45.000 They build native iOS and Android apps for some community needs. 06:45.000 --> 06:49.000 When a client, like a local community, a publication or a cooperative, 06:49.000 --> 06:51.000 needs a community space. 06:51.000 --> 06:55.000 Newsman's provide them custom mobile application in the app or store. 06:55.000 --> 06:58.000 This means that they have their community name, their identity, 06:58.000 --> 07:01.000 their different content and their members. 07:01.000 --> 07:07.000 Now, in the short future, a custom version of Newsman's. 07:07.000 --> 07:10.000 Nativap will be powered by a bonfire instance. 07:10.000 --> 07:12.000 Federated with the open-source web. 07:12.000 --> 07:15.000 And this means that when clients need new features, 07:15.000 --> 07:17.000 we can coordinate. 07:17.000 --> 07:20.000 We build together and create interoperability through API. 07:20.000 --> 07:23.000 So both bonfire and Newsman's grow together. 07:23.000 --> 07:27.000 Module development means we all benefit and improve. 07:28.000 --> 07:31.000 Lowty, classmate and metoder. 07:31.000 --> 07:33.000 It's a German tech collective. 07:33.000 --> 07:38.000 They build a lowty that is a great calendar and event publication tool 07:38.000 --> 07:40.000 for grassroots organizing. 07:40.000 --> 07:43.000 They're also here in this room. 07:43.000 --> 07:47.000 Events functionality are core needs for most communities. 07:47.000 --> 07:50.000 But we didn't want to remain the wheel in bonfire. 07:50.000 --> 07:54.000 And increase the maintenance burden when there are great open source up available. 07:54.000 --> 07:57.000 So instead, we are collaborating to integrate the tool. 07:57.000 --> 08:01.000 Events will be soon able to federate from lowty to bonfire, 08:01.000 --> 08:06.000 using the activity pipeline to serve very PI more on this later. 08:06.000 --> 08:10.000 And people on the other side can join lowty with their bonfire account 08:10.000 --> 08:16.000 and publish events directly without extra login or silos. 08:16.000 --> 08:18.000 And cop cloud. 08:18.000 --> 08:22.000 Cop cloud is cooperatively governing the comments for self hosting. 08:23.000 --> 08:27.000 They include a simple and reproducible deployment tool called Abra. 08:27.000 --> 08:31.000 And a catalogue of resipes for deploying open source application, 08:31.000 --> 08:36.000 which are maintained collectively, reducing the risk and the maintenance burden for everyone. 08:36.000 --> 08:39.000 Cop cloud is also the recommended way to install bonfire. 08:39.000 --> 08:43.000 And this is because it's also meaning that you can join 08:43.000 --> 08:45.000 a community of cooperative infrastructure. 08:45.000 --> 08:50.000 You are not on your own just installing another app on a server. 08:51.000 --> 08:55.000 And this is all great, but actually, what does it means for real community? 08:55.000 --> 09:01.000 Here are two community that are already building with such infrastructure. 09:01.000 --> 09:05.000 The first is Jacob in the German edition. 09:05.000 --> 09:09.000 It's a political magazine probably most of you know them. 09:09.000 --> 09:14.000 The German edition has 100,000 or more readers. 09:14.000 --> 09:18.000 And they needed a community space that isn't ancient and should be able. 09:18.000 --> 09:21.000 Some where the readers can discuss. 09:21.000 --> 09:24.000 They can organize and connect on ground they control. 09:24.000 --> 09:26.000 We are co-designing this together. 09:26.000 --> 09:28.000 They're a tutorial team. 09:28.000 --> 09:31.000 They're a designer working with the bonfire infrastructure. 09:31.000 --> 09:32.000 But not only us. 09:32.000 --> 09:36.000 They will have a community app that will be built on news must. 09:36.000 --> 09:39.000 They will use the loudty calendar for organizing events. 09:39.000 --> 09:44.000 And their infrastructure will be hosted on cop cloud. 09:45.000 --> 09:47.000 And this is the other. 09:47.000 --> 09:49.000 Another example is topless posts. 09:49.000 --> 09:53.000 Topless is a small town in southwest UK. 09:53.000 --> 09:59.000 And they have a WordPress blog and a place where they post events and create events. 09:59.000 --> 10:02.000 Everything that's happening in town. 10:02.000 --> 10:04.000 And what they're missing is a community. 10:04.000 --> 10:08.000 The community of the town instead is split in like three Facebook groups. 10:08.000 --> 10:12.000 There's like, you know, the forked group that is not fascist. 10:12.000 --> 10:13.000 And there's the other one. 10:13.000 --> 10:16.000 And there's the one that allows ads. 10:16.000 --> 10:18.000 And yeah, everybody hates it. 10:18.000 --> 10:20.000 Everybody would like a lot of people would like to leave. 10:20.000 --> 10:24.000 But there's stuck there because that's where you are involved in the town. 10:24.000 --> 10:25.000 Goings on. 10:25.000 --> 10:26.000 And that's the true. 10:26.000 --> 10:30.000 The case in many towns and neighborhoods around the world. 10:30.000 --> 10:38.000 So they're setting up similarly at app and events to power by loudty. 10:38.000 --> 10:43.000 And with the back end power by bonfire, where they're going to have events and local news. 10:43.000 --> 10:46.000 But also community discussions. 10:46.000 --> 10:53.000 Optionally connected to the rest of the Fediverse, but first focus on just the residents. 10:53.000 --> 10:56.000 So here's how it works. 10:56.000 --> 11:00.000 From the point of view of an event organizer in this case. 11:00.000 --> 11:05.000 Topless cinema, which is a little nonprofit really cool cinema. 11:06.000 --> 11:10.000 That puts on several events every week. 11:10.000 --> 11:13.000 And so here they would be posting an event. 11:13.000 --> 11:17.000 This is the loudty interface for event organizers. 11:17.000 --> 11:19.000 And so they can upload a picture. 11:19.000 --> 11:21.000 They put all the event details in. 11:21.000 --> 11:22.000 Post that. 11:22.000 --> 11:24.000 And then magic happens when you press that button. 11:24.000 --> 11:28.000 Not only is there an event in loudty, but. 11:28.000 --> 11:31.000 And there it is. 11:31.000 --> 11:36.000 But it also federates to bonfire. 11:36.000 --> 11:39.000 And shows up there. 11:39.000 --> 11:40.000 And you can comment on it. 11:40.000 --> 11:44.000 You can boost it, which you cannot usually do with an event. 11:44.000 --> 11:47.000 But here, you know, it's a social thing. 11:47.000 --> 11:52.000 And this is all thanks to client to server API. 11:52.000 --> 11:54.000 A few people talked about it today. 11:54.000 --> 11:56.000 What we realized client to server API. 11:56.000 --> 11:58.000 Even if no client apps are using it. 11:59.000 --> 12:02.000 It's perfect for server to server. 12:02.000 --> 12:08.000 Federation when the app like loudty is not yet federated. 12:08.000 --> 12:12.000 They very quickly were able to implement client to server API. 12:12.000 --> 12:14.000 Just send the event metadata to bonfire. 12:14.000 --> 12:17.000 And then we can federate that on. 12:17.000 --> 12:23.000 And then, of course, it shows up also in a mobile app. 12:23.000 --> 12:25.000 So to sum up what we're offering here. 12:25.000 --> 12:26.000 It's not a product. 12:26.000 --> 12:27.000 It's not a service. 12:27.000 --> 12:30.000 It's an ecosystem of people who meet together. 12:30.000 --> 12:31.000 To meet needs. 12:31.000 --> 12:35.000 People who share costs share risk share expertise in knowledge. 12:35.000 --> 12:37.000 Share governance over the tools they rely on. 12:37.000 --> 12:42.000 And reinforce each other's capacity to adapt surviving thrive. 12:42.000 --> 12:45.000 This is how we think open source can become sustainable. 12:45.000 --> 12:47.000 Not by mimicking startup economics. 12:47.000 --> 12:50.000 But by building ecologies where survival is mutual. 12:50.000 --> 12:54.000 By making sustainability a shared ongoing cooperative project. 12:54.000 --> 13:00.000 Rather than a lonely competition. 13:00.000 --> 13:02.000 Europe today is as a crossroads. 13:02.000 --> 13:04.000 And Sandra talked about earlier really well. 13:04.000 --> 13:06.000 So I'm not going to go into it. 13:06.000 --> 13:11.000 But basically, we think that public funds need to fund. 13:11.000 --> 13:15.000 Not just public code, but public truly public infrastructure. 13:15.000 --> 13:18.000 And that means not just the software. 13:18.000 --> 13:22.000 But also the moderation labor, the maintenance, 13:22.000 --> 13:27.000 localization, accessibility, research, including social science. 13:27.000 --> 13:32.000 To figure out what is the impact of what we're doing and how to improve on that. 13:32.000 --> 13:35.000 So what's coming next for bonfire. 13:35.000 --> 13:39.000 We are working with the social web foundation and with the mystery event. 13:39.000 --> 13:42.000 On implementing end-to-end encryption. 13:42.000 --> 13:46.000 So it means privacy at the protocol level. 13:46.000 --> 13:50.000 And then we really would like to work on federated groups. 13:50.000 --> 13:54.000 And actually we extended the profiting campaign. 13:54.000 --> 13:56.000 And it's active right now. 13:56.000 --> 14:02.000 Mostly used for hopefully funding the federated group development. 14:02.000 --> 14:05.000 And they will work across instances. 14:05.000 --> 14:10.000 They will have it's own governance and their own boundaries and privacy level. 14:10.000 --> 14:17.000 Also bridging, we love the work that the bridge fed and you social are doing. 14:17.000 --> 14:19.000 And we support the federates. 14:19.000 --> 14:22.000 It's not only the only decentralized social network emerging. 14:22.000 --> 14:26.000 Users should be able to talk to all of them if they choose so. 14:26.000 --> 14:28.000 And of course more extension and widget. 14:28.000 --> 14:32.000 We are proposing this idea of having a dashboard that's the logo on page for bonfire. 14:32.000 --> 14:36.000 So the user will not go straight to a timeline to a feed. 14:36.000 --> 14:41.000 But they will have a dashboard that is basically set of components of plugin. 14:41.000 --> 14:45.000 Where all their meaningful data for them will be shown. 14:46.000 --> 14:49.000 And then it will be their own choice to go through a timeline if they want. 14:49.000 --> 14:54.000 Trying to not have a dark pattern enabled by default. 14:54.000 --> 14:57.000 So please get involved. 14:57.000 --> 14:58.000 Try bonfire. 14:58.000 --> 15:00.000 If this resonate. 15:00.000 --> 15:01.000 Run any stance. 15:01.000 --> 15:03.000 See what breaks because bugs. 15:03.000 --> 15:06.000 There are a lot of bugs but we will fix them. 15:06.000 --> 15:09.000 And more of anything tell us. 15:09.000 --> 15:10.000 Build on it. 15:10.000 --> 15:11.000 The extension system is open. 15:11.000 --> 15:13.000 Build what your community really needs. 15:14.000 --> 15:16.000 Form a new alliances. 15:16.000 --> 15:19.000 The ecology that we just described is just one example. 15:19.000 --> 15:20.000 It's one possibility. 15:20.000 --> 15:21.000 Other entanglement. 15:21.000 --> 15:24.000 Other combination can emerge. 15:24.000 --> 15:27.000 We want to hear from you. 15:27.000 --> 15:33.000 And just to wrap up as the beginning we end up with a quote from announcing that really 15:33.000 --> 15:36.000 inspired the bonfire project in a lot of ways. 15:36.000 --> 15:38.000 As contamination change. 15:38.000 --> 15:39.000 Workmaking project. 15:40.000 --> 15:42.000 A new direction may emerge. 15:42.000 --> 15:45.000 Everyone carries a mystery of contamination. 15:45.000 --> 15:47.000 Poority is not an option. 15:47.000 --> 15:51.000 One value of keeping precariety means that it makes us remember the changing with 15:51.000 --> 15:54.000 Shirkostancies is the stuff of survival. 15:54.000 --> 15:57.000 Anatzing studying ecology and capitalism. 15:57.000 --> 15:59.000 About forest. 15:59.000 --> 16:02.000 And about supply chain and survival in the ruins of industrial capitalism. 16:02.000 --> 16:04.000 And of course, she was talking about us. 16:04.000 --> 16:05.000 Thank you. 16:06.000 --> 16:07.000 Thank you. 16:13.000 --> 16:14.000 Thank you. 16:14.000 --> 16:17.000 I'm imagining there's going to be some questions. 16:17.000 --> 16:18.000 Here's one in the front. 16:18.000 --> 16:19.000 Already. 16:22.000 --> 16:27.000 I like to ask if the disadvantage system is already useful. 16:27.000 --> 16:29.000 I can use it this now. 16:29.000 --> 16:32.000 And how it does compare with, for example, 16:32.000 --> 16:34.000 the gantula and molython. 16:34.000 --> 16:36.000 There are similar applications. 16:36.000 --> 16:38.000 And again. 16:38.000 --> 16:40.000 Okay. 16:44.000 --> 16:45.000 Yeah. 16:45.000 --> 16:50.000 It's definitely interalping with Gantula mobiles on the others. 16:50.000 --> 16:53.000 There's a workshop tomorrow if you're interested about that. 16:53.000 --> 16:57.000 Birds of a feather think we're going to participate in. 16:57.000 --> 16:58.000 Yeah. 16:58.000 --> 17:07.000 So in terms of the event park, you can talk to louty in the hall afterwards. 17:07.000 --> 17:08.000 Yeah. 17:08.000 --> 17:10.000 There's birds with a feather tomorrow. 17:10.000 --> 17:11.000 There's two. 17:11.000 --> 17:12.000 Fedabers related ones. 17:12.000 --> 17:13.000 There's a hacky dome one. 17:13.000 --> 17:14.000 A 10 a.m. 17:14.000 --> 17:15.000 And then there's an events. 17:15.000 --> 17:17.000 And calendaring one at 11 a.m. 17:17.000 --> 17:18.000 So if you check the fuzz game schedule. 17:18.000 --> 17:20.000 You should see those as also. 17:20.000 --> 17:24.000 A panel that the executive director from Mastodon is on. 17:24.000 --> 17:27.000 In the EU and pop open source policy debris in tomorrow. 17:27.000 --> 17:30.000 We should probably put a little slide in our. 17:30.000 --> 17:32.000 Holding sections. 17:32.000 --> 17:35.000 Well, in between sessions today just to make sure everybody knew about the other. 17:35.000 --> 17:37.000 Feddy related content. 17:37.000 --> 17:40.000 Any other questions as one from jazz. 17:40.000 --> 17:47.000 Oops. 17:47.000 --> 17:49.000 Hey, guys. 17:49.000 --> 17:55.000 I feel like you slipped in their little tip of an iceberg. 17:55.000 --> 17:59.000 And everyone we have missed something below the surface. 17:59.000 --> 18:12.000 It's a little flavor. 18:12.000 --> 18:26.000 Can you add a little flavor to what you spoke about with the client to server working for you in that particular non-federating application? 18:26.000 --> 18:28.000 Yeah. 18:28.000 --> 18:29.000 Yeah. 18:29.000 --> 18:45.000 So we realize client to server is perfect for apps that haven't yet or maybe won't implement full Federation because that's a huge job, especially to get it right and interrupt with all the other projects. 18:45.000 --> 18:48.000 You know, unless you're using maybe a shared library. 18:48.000 --> 18:51.000 They're starting to be some of those. 18:51.000 --> 18:56.000 The Federation code in bonfire is also available as a library for other projects to use. 18:56.000 --> 18:58.000 But it's still a lot of effort. 18:58.000 --> 19:05.000 So instead, what Laughty does is simply create a JSON and I'm getting technical. 19:05.000 --> 19:18.000 JSON object and activity streams with all the metadata of the event and sending one post request to bonfire with that saying post that to my account. 19:18.000 --> 19:21.000 The account has already been authenticated with OAuth. 19:21.000 --> 19:24.000 So you know, you just click a button and it authenticates. 19:24.000 --> 19:26.000 So it's as simple as that. 19:26.000 --> 19:35.000 You set that up once and then when you post the event on Laughty, it gets pushed to bonfire and then that enables commenting following and all that. 19:35.000 --> 19:40.000 Okay, we'll take one more question and then we'll switch sessions.