It’s the height of summer in the Northern Hemisphere, and hackers and makers everywhere are letting their hair down and enjoying the hot weather on the water. By coincidence last weekend there were two very different raft races in the European hackspace community, at the SHACamp2017 gathering in the Netherlands the villages competed in a cardboard raft race, while on the other side of the English Channel the various hackspaces in and around London came together in a raft race using more conventional materials.
The SHA race came about through the happy confluence of a surplus of disposable cardboard tents, a sunny afternoon, and the inviting waters of the Nuldemauw. The aim of the contest was for hacker camp villages to make it from the bank to the end of the boat dock, a distance of about 100m, in a boat made from cardboard there and then at the camp. Meanwhile the London spaces met at City Road Basin in London with their more robust watercraft for a series of races, the aim of which seems to have been to be the first to get their crew disembarked at the other end of the course. and sitting in a chair on the bank.
In both races the inventiveness of the entrants showed itself in a wide range of boat designs. As you might expect those craft with a wider beam fared better than the far less stable narrower ones, with capsizes a feature at each location. Clear winners in the Netherlands were a pair of German teenagers in a very stable wide raft, while in London it was South London Makerspace’s catamaran that scooped the crown. There is a video of the London race which we’ve placed below the break.
The hackspace and makerspace spirit is at its strongest when bonds are forged between members of different spaces. Skills and capabilities are shared, collaboration opportunities abound. The sight of a bunch of European makers getting wet might serve more as entertainment than edification, but behind it lies an important facet of hackspace culture. If you’ve not yet been the spaces closest to yours, do so. You never know, one day you might end up on a capsizing raft because of it.
There is one constant in the world of hardware hacker’s workshops, be they a private workshop in your garage or a public hackspace, and it goes something like this:
Everybody’s a safety expert in whatever it is they are working with, right up until the accident.
In other words, it is very tempting to harbour a cavalier attitude to something that either you are familiar with or the hazards of which you do not understand, and this breeds an environment in which mishaps become a distinct possibility.
As hardware people, we are familiar with basic tool safety or electrical safety. The chances are that we’ve had it drummed into us at some time in our growing up, by a lab supervisor, a workshop teacher, or a parent. That you as readers and I as writer have survived this long is testament enough to the success of that education. But what about those areas in which we may not have received such an education, those things which we either encounter rarely or seem harmless enough that their safety needn’t be our concern? Chemicals, for example: everything from glue through solvents and soldering consumables to PCB chemicals and even paint. It all seems safe enough, what could possibly go wrong? The answer to that question is probably something most of us would prefer never to find out, so it’s worth looking in to how a well-run workshop can manage its chemicals in as safe a manner as possible.
More than one member of the Hackaday team has significant involvement in a hackspace, as member, director, or even founder. We talk about hackspaces quite rarely on these pages though, not because we don’t have anything to say on the matter but because even when we write in general terms our fellow members invariably think it’s all about them rather than the hackspace world at large.
For once I’m going to break the silence, and not only talk about hackspaces, but talk about my own hackspace in specific terms. Because, fellow Oxford Hackspace members, this isn’t about you personally though I’m using our home to illustrate a point. The topic is a thorny issue that must affect all spaces, that of donations of physical items. People want to help their hackspace, they have a pile of what they consider to be good stuff, and when they’re having a clear-out they make a donation. But, as we all know, “one man’s trash is another man’s treasure” and vice-versa. Continue reading “The Complex Issue Of Hackspace Donations”→
When you are running a hackspace, network security presents a particular problem. All your users will expect a wireless network, but given the people your space will attract, some of them are inevitably going to be curious enough to push at its edges. Simply plugging in a home WiFi router isn’t going to cut it.
At Santa Barbara Hackerspace they use Unifi access points on their wireless network, and their guest network has a system of single-use codes to grant a user 24-hour access. The system has the ability to print a full sheet of codes that can be cut individually, but it’s inconvenient and messy. So the enterprising hackspace members have used a Raspberry Pi and a receipt printer to deliver a single code on-demand at the press of a button.
The hardware is simple enough, just a pull-up and a button to a GPIO on the Pi. Meanwhile the software side of the equation has a component on both client and server. At the server end is a Python script that accesses the Unifi MongoDB database and extracts a single code, while at the client end is another Python script that reacts to a button press by calling the server script and printing the result. It’s a simple arrangement that was put together in an evening, but it’s an effective solution to their one-time WiFi access needs.
It’s a temptation as a hackspace to view all of your problems as solvable in one go with the One Piece Of Software To Rule Them All, and as a result some spaces spend a lot of time trying to hack another space’s effort to fit their needs or even to write their own. But in reality it is the small things like this one that make things work for members, and in a hackspace that’s important.
Does your space have any quick and simple projects that have automated a hackspace process? Let us know in the comments.
It’s funny, how obsessed we are with qualifications these days. Kids go to school and are immediately thrust into a relentless machine of tests, league tables, and exams. They are ruthlessly judged on grades, yet both the knowledge and qualifications those grades represent so often boil down to relatively useless pieces of paper. It doesn’t even end for the poor youngsters when they leave school, for we are now in an age in which when on moving on from school a greater number of them than ever before are expected to go to university. They emerge three years later carrying a student debt and a freshly-printed degree certificate, only to find that all this education hasn’t really taught them the stuff they really need to do whatever job they land.
A gold standard of education is revealed as an expensive piece of paper with a networking opportunity if you are lucky. You need it to get the job, but in most cases the job overestimates the requirement for it. When a prospective employer ignores twenty years of industry experience to ask you what class of degree you got twenty years ago you begin to see the farcical nature of the situation.
In our hackspaces, we see plenty of people engaged in this educational treadmill. From high schoolers desperately seeking to learn something other than simply how to regurgitate the textbook, through university students seeking an environment closer to an industrial lab or workshop, to perhaps most interestingly those young people who have eschewed university and gone straight from school into their own startups.
Part of the job of a Hackaday writer involves seeking out new stories to write for your delectation and edification. Our tips line provides a fruitful fount of interesting things to write about, but we’d miss so much if we restricted ourselves to only writing up stories from that source. Each of us writers will therefore have a list of favourite places to keep an eye on and catch new stuff as it appears. News sites, blogs, videos, forums, that kind of thing. In my case I hope I’m not giving away too much to my colleagues when I say I keep an eye on the activities of as many hackspaces as I can.
So aside from picking up the occasional gem for these pages there is something else I gain that is of great personal interest as a director of my local hackspace. I see how a lot of other spaces approach the web, and can couple it to my behind-the-scenes view of doing the same thing here in our space. Along the way due to both experiences I’ve begun to despair slightly at the way our movement approaches the dissemination of information, the web, and software in general. So here follows a highly personal treatise on the subject that probably skirts the edge of outright ranting but within which I hope you’ll see parallels in your own spaces.
Before continuing it’s worth for a moment considering why a hackspace needs a public website. What is its purpose, who are its audience, and what information does it need to have?
As a hackspace member, it’s easy to fall into the belief that your own everyday skills are universal. Soldering for example. You’ve handled an iron since you were a youngster, the solder bends to your will as a matter of course, and since you see your fellow makers doing the same thing you might imagine that it’s a universal hackspace skill. Everyone can do it, can’t they?
Of course, they can’t. If you weren’t lucky enough to have a parent who tolerated your occasional propensity for acquiring burns on your fingers then you probably won’t have that innate experience with an iron. This extends to people you might expect to have those skills, indeed as an electronic engineering student a couple of decades ago your scribe was surprised to find that the ability to solder was her hotly tradeable skill, amazingly even a lot of EE students couldn’t solder.
So, perhaps it’s time to put our money where our mouth is. How difficult would it be to run a hackspace soldering workshop for the uninitiated? Assuming your space is used to the mechanics of running events, the challenge is to find for each participant a soldering iron, some solder, and a radio or other kit without breaking the bank. An ideal budget from where this is being written in the UK would be £20 (about $29), into which a Chinese kit from AliBaba or similar and a cheap iron kit could be fitted. Some work to decipher the Chinese instructions with the help of an overseas student member and to write an English manual, and we’d be ready to go. If this comes together we’ll report back on whether the non-solderers of our hackspace successfully learned the craft.