 provides here. So I'm joined for those who don't know me, I've been found for a while I'm running the Twitter, by the way, I live for Graphics Media, so if you have any complaints about that, it shouldn't be. But I want to talk about a project I started like a few months ago following something that you might know of which is this project called Fort Awesome. For those who don't know, it's an icon font, right? It's been quite popular, not Fort Awesome, font awesome, that's the one I'm already jumping. So you guys have to help me. Sorry, who does the sheet? Fort Awesome. No, I wanted to start with Fort Awesome actually. So it's part of the confusion. So Fort Awesome creates this project called Font Awesome, which has been used by millions of websites. You probably know the version 4.7, which is all, you can only find it from here, by the way, and the appetizer for the new version. But basically, it's this icon font that's been used on millions of websites. You've seen them everywhere. Who doesn't know about this project? I'm curious. One, two, three. Okay, so if you design websites and you don't want a web app or whatever you call it right now, it's like if you want a quick set of icons, you just import this icon set and then you're pretty much covered for a lot of cases. But what happens is that they advertise themselves as an open source project on GitHub. Let's find their GitHub page. And I've been actually annoying them because I made, basically, file issues and make pull requests. And especially since last year, because I'm a big fan of a project called Master Long, I asked last year in April 2017 to add the Master Long logo to the icon set because I think people will find that useful to ask to add the icon next to their handle name and use that on their website. But as you can see, the issue is still open a year later. Even if the main developer of Master Long joined in, he came with a new logo, showed the files, and in the end I made myself, I did the pull request for it, which was denied. And what's denied for good reason is that since 2016, they've stopped accepting any pull request to add new icons and they started a Kickstarter campaign, of which they received a million dollars for it. They were asking for $30,000. And they switched to a different model where now they're releasing the file in three versions or two versions, a free one still with Creative Commons licensing, but they're promoting for a pro version which you pay for. And since my pull request wasn't accepted, and I was, there have been so many pull requests, unaccepted for people who wanted to add new icons, I decided to fork it and I forked it. I first asked, actually the console of two people that are here, Nathan and Brandon, to see if it was a good idea to fork and if it was legitimate, you know, forking is still a big deal in the free software movement. So, yeah, I decided to fork it to a project that I called Fork Awesome. And that's what we've been doing for the last couple months. What we started doing is adding a lot of new icons, which you can see if you go here. So, we've added a lot of icons, such as for massive amount of forms, but new social hubs like that, and even Scuttlebot for those who know the social network. We added icons for open source projects such as Charlie or any other like non-open source project in the mix. And so this has been, my point of doing this is that I was frustrated that what they were calling themselves an open source project, an open source design project if you wish, were not accepting pull requests for design improvements or adding to the sets. And also they were like keep focusing on basically the main author of the project, which is Dave Gandhi, which did most of the work of the following self. But I thought that it wasn't really beneficial to the community, and especially with the latest move they made, which, I mean, I'm very glad for them that they managed to take that much money and turn it into a profitable project. But somehow it was kind of for me betraying what I think open source design could be. So what we've been doing with this project right now is I've onboarded in the project a few contributors. I've also, in the website itself, mentioned and did the work of going through all the contributions that have been done in the past to actually reference them and acknowledge the contribution of every people that have participated in the fund awesome, but also since then, since this moment, all the people that have participated in the full awesome project. I'm giving also access to the repo to some people and we've been tackling issues and discussing design and improving on the project. As you can see, there's already like 35 issue closed. The price itself has received, I can't, or you can see that, but yeah, 300 stars and people are starting to use this in their own projects as a replacement because it's basically for people who want to replace for awesome with for awesome. It's really like using either CDN files that we're using right now and you can see it's getting quite some hits or downloading the files and just replacing. We basically haven't changed anything. We're keeping the code as it existed. We're just adding new features and new icons. And so if you find this interesting, I welcome you to talk to me or to join us on GitHub and participate. The goal is to really turn this into a community project and move out of the single person who decides everything and owns everything in the end. That's it. That's my presentation. Actually, in my slides, I wanted to show you something. We've been accepting full requests for icons, especially where they said there's one for XMPP. Basically, the issue was open since 2012 on the front awesome. So we finally closed that issue in 2018 with Fork Awesome. So that's the kind of things that I'm proud of for this project. I invite you to join. Thank you. This is a very much improvised talk. So the slides are actually in German and I hope I can take from the context what this is about. And there also is a chance that I already did a talk on this project at the library graphics meeting. This is something that I'm being kind of obsessed now again, although the project itself is something that is with me since at least 2006. The goal is to have a MIDI to SVG project, basically trying to use MIDI files and convert them to something you can plot out on a laser cutter to play music from. So the talk I gave at the make up on a few weeks ago, I gave together was Gjörgen Land. He is a musician and also writer for mostly Orion. And let's just skip to the story. Basically, we met at a summer music festival, which is like a world music festival somewhere in the middle of Germany. And yeah, basically it's quite a colorful event and there were a lot of discussions going on. And they were discussing, I've witnessed people discussing a present for the organizer of this event. And they were talking about having a custom music box playing a song from the organizer. And yeah, I told them actually I did something like this. So, I'm sorry. So this is actually the start of my part of the story there. This kind of music boxes we are talking about here is something I know for a very long time already because my father had one of these things. I remember playing with this thing as a child. In 2006 I bought my own and the idea is basically I can just show how these things look like. There's some. So very nice little things and the music is encoded as holds in the paper strip. And so the first thing you do is actually you get paper strip with black dots printed on it. And you're supposed to use a small hole puncher to clip out all the black dots. And yeah, this is something that gets annoying fast. So my first goal was to actually build a robot to punch holes. And I actually started and bought products which were supposed at some point to end up as this kind of robot. And I did a design and a meaning play and I found what kind of works to do before to find the right things to punch holes in the paper. And that's what my mechanism meant whatever. Checked out, I'm not a mechanical engineer. So this is something basically it's in the same state today this project as it was. But then I'm used to projects which take quite a long time. And then in 2011 I attended the case communication camp. And it turns out there was a favelet truck from the Netherlands. The favelet truck and it looks actually like this. Which this is actually not a photo from this event that the truck is the same. And it's just a favelet on wheels. There is a laser cutter in it. There are 3D printers in it. And so at that point it made like click and I thought okay I can do that because I know how to deal with graphics. I know how to deal with media. I already had written software to pass media files. And extract the relevant information. So all I had to do was to create graphics that I could then print out on the laser cutter. Yeah and basically this is in 2012 then the meeting with Jürgen happened. And this actually was a totally different view on my project because he also has bigger plans. Let's just skip to this a little bit to the technique things. I know of 4 different variants of these kinds of music boxes. They basically look like this. This is a 50 note C major scale scale. So this is a bigger variant. It has 30 notes. It actually has some chromatic notes in the middle. And it plus some bass notes. And this is actually mechanically or from production quality the nicest one. But it is limited to 20 notes and a major scale as well. So how do these things work? This is a sample version. You can see there are the metal strips that produce the sound by getting plucked. They get plucked by these kind of wheels. And the paper strip basically goes through like this. And the holes enable the pins on the wheel to enter the hole. And then get pulled forward, plucking the metal strip down here. There are 4 of these pins around the wheels. You can see that here. This is from the bottom. So basically, yeah, this is about it. You have 2, 2... No idea. Paper is transported between 2 rows, thank you. And the holes allow the wheels to grip into the paper strip. And, well, the next pin then flux the metal strip. What I find kind of interesting is that there is a whole range of things you can actually do. You have these kind of objects you are more or less obsessed with. You can start by just printing out something which you then clip by hand. You can try to find a way to do actually laser. Use a laser cutter to do this. You can do it with a whole punching robot. And you can try to automate the playing as much as possible. And you could also be happy with just sampling the music box and just using your regular media software to play this stuff. Or you can even go a step further. This is not a project for me. This has talked up in the last few weeks. It's actually actuating the pin wheels with individual servo motors. So you have like 13 servo motors here. And it actually is possible to do live music playing with this thing. It's quite an impressive project. And, yeah, so you have this big kind of spectrum. And you have to find a way a project is. And my project actually stops for now at the laser cutting of the whole strips. And, yeah, that's it. I'm not sure into how much of a detail I should go. I could tell a lot about browsing these files. I could tell you a lot about creating the graphics using, in this case, Tyro. But I guess I'll stop for now. And if you're interested, feel free to contact me. Thank you. How about using Vox with you? Unfortunately, I didn't think of it. Sorry. No, it won't show again. I can show you generated PDFs on my laptop. It's basically just an outline with lots of circles. And, yeah, there is a little bit of strategy involved. Because the laser cutter in our FabLab has some mechanical issues. Regarding the positions, all I had to do was slide back around. But this is very much nitpicking. Thank you. So, I think something you may be familiar with this project that I've been working on. I presented it a few years ago at another LGM in Leipzig. And it's still going. It's fits and squirts, but the project is still kind of active. And there's still ongoing experiments. So I wanted to, I guess I should give some people some, if you're not familiar with it, some background. So the idea of this greenless office is to come up with, I call it an artistic operating system. Not because I think it's somehow pretentious, somehow superior to non-artistic operating systems. But because by calling it an artistic operating system, I can get away with not being efficient or working in a way that would be expected of a proper operating system. So I decided, I mean, I guess one of my problems is that I feel like the screen is, I mean it's obviously very powerful interface, but it's kind of obvious in some ways. It gets us into certain habits of ways we work and maybe some of these aren't good or maybe they can be kind of boring. So if we're going to do something that's experimental, why don't you do the most difficult and get rid of the most obvious aspect of the whole thing so we get rid of the screen. So things become really difficult, but then maybe there's some interesting ideas that come up. So what I sort of started with the first functional thing was I thought, okay, how do I get through my day? I'm still using the internet, but how can I not use a screen? What do I need? So the first thing was, all right, so I can avoid sitting at the breakfast table with my laptop or some other device looking at that. And so I started making, basically, it's an RSS reader that this is what I print out every morning. So I have... So you reinvented newspapers? I've reinvented newspapers, but it's up to the minute. It's really up to date, you know, it's not like hours old, like one of these old newspapers. This is fresh. Yeah, sure. Yeah, and so basically then the way it works is it... Yeah, I have RSS feeds. It grabs the RSS feeds, then in order... I mean, I like images, even though it's screenless, I still want some images. So I go and I get the open graph headers from the HTML and pull out some images maybe. And then if there's a particularly interesting article, then... So these are just the summaries, then I take out my barcode scanner and I scan the barcode, which then prints out the web page. So then the web pages look like, like here's a few examples like this. You know, it's a pretty kind of boring layout, but... If anyone has design critiques, I'm open for it. We can talk about whatever. And here, if anyone's interested, I'm actually using the browser. So I'm using Firefox and rendering it to PDF. And the trick I do is when I pre-process it, I strip out, I use some... I think, yeah, basically it's a Python implementation which strips out most of the junk. And that's also one of the things that I like, that it's sort of like taking the control back with the interface, that if you're browsing the web, but you're no longer... There's no pop-ups, there's no annoying thing that's hovering over it and saying, please turn off your hand blocker or this kind of stuff, that it's all stripped out and I've just got the parts of it that I want. I mean, there's a lot of sites that don't quite render properly, so then occasionally I do have to open up my laptop, but I'm okay with it. And then, yeah, the main sort of operative thing that goes on is I scan through all the links and then I make a number, a footnote, number where the link would be. So then if you're reading the text and you see a little footnote, then you can go to the end of the document and then instead of clicking the link, you scan the barcode and then that prints out the next one. So that's gotten through a certain amount of my day with that. I also have... the layout is awful, but I can... And I also have my inbox, so I have some simple iMap stuff that grabs my inbox, tells me everything there. And in some ways it's kind of nice because I have one that's like spam and delete, so I can really quickly just... they're really nice stuff. But I can also print out pages and then what I have in terms of... I don't think I should show you this as well. So then Twitter, of course. So this is... So it will print something. Yeah, so I have a receipt printer. I don't have my A4 printer, but I also have a receipt printer. I recently implemented, so I can even do the debugging. So now if there's a stack trace, it actually prints out. Which is kind of nice. Usually in screens you do that kind of stuff, so that's a little bit of... without that. So, yeah, so I've been working on that for a few years. Different people have helped me. And the other thing I have is, in terms of input, I built a document camera. So the software right now, it's running on this sort of... It's actually like one of these Raspberry Pi-esque things from this Bulgarian company called Olimax. It's not very fast, it can do some optimization, I mean, the whole point of this is to do a little slow computing anyway. So it works out. But, yeah, so I use this document camera. So if I want to post something to Twitter, I have this... I should have brought an image. I don't have one here. But I have a sort of A3-sized black blotter and I just put something down on it. You know, it could be one of these things, or I could write something on a piece of paper and there's a switch so that I can set the size of the actual image that I want to post, somewhere between A6 and A3. And then I can set the orientation if it's landscape or portrait. And then when I scan here, the... Yeah, exactly. So here's the menu of my software. So when I scan here, tweet, or even I did implement Facebook, although I think it just seems quite the sound. But I occasionally post to Twitter and what I can do is I just scan this barcode and I have an LED light that turns on and it takes a photo of whatever's on this surface and then uploads it as a tweet. Do you bring the photo before tweeting? You see if it's good. No, I just have to hope that it's good. I mean, I can reload my own feed and print it out and then I can get some idea of if I really screwed up if it's out of focus or something. Actually, no, I have a fixed focus. But yeah, for some reason the composition... I guess I could see that. But yeah. So that's sort of going on. How much paper do you buy per month? Not that much, actually, because that's the thing that I realized is that by... I mean, paper, you see it. Once you start, you realize how much I'm printing out. I printed like 10 pages one morning while I'm drinking my coffee and I think, like, this is maybe enough for now. And then I'll sit there and read it. I mean, I use recycled paper. I use both sides. I try to be aware of it. But there's this sort of feeling that I mean, come on. I think about it when you're sitting in front of a screen. You may have something, if you have a decent-sized screen, that thing probably uses like, maybe, I don't know, 100 watts. 60 or 80 watts or something like that. And you're sitting there for hours going on some deep dive into obscure parts of Wikipedia or something. And you don't have... There's no point where you see this stack of paper that, oh my God, I just wasted two hours researching obscure snakes or something. And it's never... Whereas here, at some point, you're like, this is ridiculous. I just printed 40 pages. I have to stop. You know, this... For me, it's a way of being more reflective about this usage, because I don't agree with the screen. It sucks, you know. That's part of what makes it amazing, but it's also scary. Yeah, so the input stuff is still kind of the main problem. So, a friend of mine is a Dutch hacker and he ran into one of these things. Moleskine puts out this very fancy digital pen, which works with their very fancy notebooks. And these notebooks have this micro-printing on them. And the way the pen works is it has a camera inside of it. And the camera will recognize the X and Y coordinates and which page it's on, which page in the notebook. And so, it saves this as a sort of little stream of data on the pen. And then if you are connected by Bluetooth to your PC, then they have some apps that are up to a smartphone or whatever. It then will send this stream of basically vector data of, you know, pathing it to various apps. Now, if you haven't figured out that they had published some kind of specs to this thing and we went through this back and we realized it wasn't that complicated that we managed to get a sort of rough prototype working. And I thought, alright, this could be cool. This could be a nice way. What if we work it out like basically like a screenless content management system? So instead of having, you know, some gigantic droop hole set up with, you know, all this stuff, then you just say, alright, fine. You want to update the website, okay, here. There's the pen, the paper. You do it. And then you sit down and write whatever and if you screw up, I guess you have to cross it out. The racing wasn't quite good, but that's the same way with pens. Consistent. So I can give you guys a quick demo. So it's kind of primitive right now. The way it works, the synchronization is essentially, so this is an SVG embedded in a minimal bit of HTML. And then what we do is then append the end of the SVG with more path data. We're just using ourselves to push that so that it's not so we don't have to sync the whole thing every time. But this probably should be done with some kind of cool WebSockets whatever thing. If anybody knows about this stuff I'm interested to hear about it. But let me give you a quick demo. A little latency, but it seems alright. Yeah. So what I brought the thing is right now I'm not sure what to do with this thing. I think it's kind of cool and it's fun, but I think this is room full of interesting people. So I have one and this is a cool thing about these pens is they actually publish some PDFs so you can roll your own and print your own whatever formats you want to cook up. So I thought if people are interested and want to try it out maybe we could do something where we try to make a kind of improvised publication I don't know if you can start to comment. I don't know what people want to do. But I thought it would be an interesting format to play with. So I have this book and maybe we can have a beer tonight and people can give me some suggestions and then tomorrow we can maybe do some kind of scheme for passing this around and say if we can produce some interesting little experiment. Yeah, so yeah, that's all I have to say. Is it printed long? Days? No, usually I throw it out. It's really like, you know, just recyclable it and be done with it. A few things I do keep or I like, the other thing I brought into kind of like scrapbooking. So I'll have if I have an interesting image or one of these something here or a tweet that we're like the image or the text then I'll just cut it out and paste it into my notebook. And then there's a lot of other stuff where I mean I think it's good to be able to there's one thing that's also a tendency with digital is that storage is cheap it's getting cheaper every day and everyone becomes like a sort of crazy librarian and we never throw anything away and then you get a lot of crufts and it's kind of maybe good to I mean I like this, I can totally understand this it's great, you know, archive.org but at the same time I think it's good in terms of like I don't want my apartment to be full of crap and being nice with my digital life could also have a certain level of tidiness to and just maybe my weird way of trying to figure that out any other questions? If it's a practice operating system, who's the audience? Who's the audience? Are you? I think I, I mean it's totally egotistical, I'm the only user here. But it's also it is, if there's code and it's actually not too bad, there's only one dependency where I just figured out how to I mean it's complicated to get it going and depending on what hardware you want to use, we may have to I may have to help you out, but it's not so exotic so if anyone is interested I'm totally surprised surprised and I'm very happy to help you like get your own screen this office running. But I think for me it's about, it's also about confronting this idea of universality. Like that's one big problem I have with a lot of interface stuff is it's based on this sort of old modernist idea which is in some ways kind of nice, you know like the Bauhaus and this idea that we should design for people, but it implies this sort of, there's a kind of arrogance, you know, that like this idea that there's a universal standard that is good for these kinds of things and I'm by doing this in a way I'm provoking to say like, well maybe that's not really true, maybe there's like a weird messed up personal way that all of us would like to interact with these things and maybe that's okay to do that, to come up with your own more personally acceptable way of dealing with all this needy because it's not easy to get into magic yeah yeah