As if the global refugee crisis wasn’t bad enough, the Obama administration is deporting refugee children back to central america. Read up, sign petition at present.org, if like me you really don’t know what else to do about this:
I just heard Planet Money episode #666 on NPR, which was about the development of the “hoverboard” — those Segway-like things with no control stick, so they look more like a… two-wheeled skateboard or something. I’d just seen one in a production of the musical Wonder.land, ridden by the Cheshire Cat, and either he was pretty good at it, or they’re actually easier to control than I’d thought. But the PM episode is about where they come from, and who invented them. This is what they look like (image via fastcodesign.com):
At first I was interested to hear them air out the idea, which I’ve heard folks like Nadya Peek and Christina Xu mention, that folks in Shenzhen just sort of doesn’t bother with defending intellectual property, in part because it’s not worth it — I imagine for reasons of expense and enforcement — and also because it’s just not part of the culture there. I’m probably misrepresenting this idea, because I really don’t know what I’m talking about, which is why I’d really like to learn more about it from folks like Christina and Nadya. Unfortunately, listening to this Planet Money episode wasn’t going to help me in that regard…
…because then the PM folks said that they didn’t really believe that there wasn’t an inventor, and they tracked down some Kickstarter campaign from 2013 for what does in fact look like an early “hoverboard” (it’s called a “Hovertrax”) — and then basically turned the story into one about how the Shenzhen folks must’ve “stolen” or “ripped off” this design from this one true inventor.
This was really frustrating to hear. Even though they acknowledged in the episode that the patent system is “only a few hundred years old,” they insisted on fitting the whole story into a moral framework which assumes one person outright “owns” an idea in its entirety, and completely discounts collaborative development, let alone the much more nebulous process of open exchange and development of ideas which is basically how people had always “come up with” technologies before the patent system was invented.
Even more frustratingly, they also justified crowning the Hovertrax guy as the original inventor by “going into a bit of a YouTube wormhole on two-wheeled, self-balancing scooters” and asserting that “they do not exist before May 2013” — the date of the Kickstarter. Great research process. Well, I’m sorry, but a very cursory search led me to this page (among others) by a guy named Dale in 2008:
…describing, with instructions, circuit designs, and (gasp!) math, how to make things balance themselves, and I’m sure that’s not the first post on it because he cites others’ work. Now, these aren’t even just people who thought it up first (which is all you have to do to file a patent), or people who built the first ones, or even the first to post about it. It’s just a particularly thorough, (and notably open) documentation of one design. Who knows; maybe a hundred other people thought of it and decided to keep it secret so they could get rich someday. (?)
Really, after the Segway, tons of people were probably thinking of a version without a control stick — heck, I remember doodling stick-less “hoverboards” myself around that time. Partially because the Segway’s steering stick just looked dumb. But my point isn’t that the “real inventor” was one of these folks, but rather that this idea of searching for the “original inventor” is itself flawed. The lone-inventor-genius, like Iron Man, or Nikola Tesla in the Prestige (so help me if I can’t think of less ridiculous examples, but Hollywood really has caricatured this ad infinitum) is just fiction. People are never really working alone, or if they are, they can never achieve as much as those who collaborate and share their ideas. This is not to say I think the Shenzhen hoverboard makers shouldn’t credit prior examples upon which they based their work, but it’s not like Hovertrax did. And also, really, why isn’t Planet Money celebrating all the amazing work (design, manufacturing, distribution) of the folks in Shenzhen to actually get these made, at scale? Isn’t that just as much of an achievement?
Maybe this is also related to how today, if someone in tech says “I have this great idea I want to tell you about, but you have to sign this NDA first,” we kind of assume they must have a pretty crappy idea — whereas ten years ago, that mightn’t have been unusual to ask. I guess I feel that the rise of free and open source software, and its technical ubiquity, has really successfully sold the idea that you can achieve more by sharing, and that folks who are desperately clinging to their “secret, brilliant idea” are deluding themselves, or even trying to delude us. Not everyone believes this — there’s still a great big world of proprietary technology out there — but the way that this framework breaks down in favor of other models outside the US and Europe is something I’d really like to learn more about.
The open source mode of production is still fairly young here, and we could use other cultural (and legal) models to learn from, especially in the hardware space! Because it really is a better way, and it really does lead to more creativity and more interesting projects, as you can see by from the absolute blizzard of “self balancing” projects on Instructables
I recently sent this letter to the City of Somerville’s planning department, and wanted to share it. (you should send in your thoughts too, before Dec 31st 2015: firstname.lastname@example.org)
Hello, I’m writing with comments on the city’s Union Square Neighborhood Plan, and to share my concern with the city’s priorities stated within it. I am a co-founder of locally based environmental non-profit Public Lab, a co-founder of the Pirateship co-working space, a board member of Parts and Crafts kids’ makerspace, and a member of Union United, but today I am writing personally, as a resident of Union Square.
Somerville is in the midst of a major housing crisis. As the Metropolitan Area Planning Council’s “Dimensions of Displacement” report makes very clear, 3,600 lower-income households in Somerville’s GLX corridor already struggle to make rent, and an additional 7-800 will likely become rent-burdened as a result of the extension. In addition, 272 of Somerville’s affordable housing units will expire before 2020, mostly in the GLX corridor.
This means that over the next four years, approximately 4,500 households will be at risk of displacement — and that’s not even all of Somerville! Many of these are families, and because of local demographics, rent pressures disproportionately affect residents of color.
In the context of this crisis, SomerVision and the USNP’s goal to “make Somerville an even more exceptional place to live, work, play, and raise a family” seems not to acknowledge the challenges faced by (especially non-white) residents in the area. The plan paints a lovely picture of what Union Square could be — but we must decide if that future is one that will be shared by those residents who have worked so hard to make Union Square a special place.
We’ve been told by the city more than once that we must choose between community “benefits” from a limited amount of funds. But this is not a crisis of bike lanes or park benches; it’s a crisis of displacement. I live in an apartment which was formerly — for twenty years — the home of a local family. I’m sure many people feel the same guilt as I do in participating in displacement, but as renters we have little power to change the economics of the situation. As voters, and as participants in the planning of Union Square’s future, we do have that power. We have an opportunity to slow and even reverse this process.
We have this opportunity in part because, luckily, Union Square’s redevelopment will generate a lot of money. US2’s part in the development has been widely referred to as a billion dollar project. We must ensure that this wealth is not created at the expense of Somerville’s most vulnerable community members.
In short, the plan’s proposed ~500 new affordable housing units are simply not enough. Will we simply tell the other 4,000 households (see above) that there’s nothing we can do? I don’t believe we have to choose between a vibrant, beautiful, and tax-revenue-generating new Union Square, and one which can address the challenge of displacement. And I don’t believe we as a community wish to see so many residents and families pushed out in order to renew Union Square the wrong way. There’s enough space; there’s enough money: let’s act.
Many of the topics addressed in the Neighborhood Plan are important to me, and I am pleased to see the City paying attention to things like support for small local businesses, creative spaces, and other “nice-to-haves.” But these pale in comparison to the urgency of affordability for so many people in Union Square today.
Thank you for your consideration, Jeffrey Warren
Union Square, Somerville resident
I just came across this article arguing that affordable housing can profitable, and that it’s really a moral choice. A good read, and it links to an “Inclusionary Housing Calculator”:
- doors can now lead to new rooms
- new format for storing room “maps” as collections of strings
- updated README instructions for world generation and map editing
- Known bug: cake no longer nutritious :-(
- fewer dependencies
- rooms can be “slept” and “woken”
This is still not quite playable, but things are coming together enough that, once I get combat and inventory running, I think it’ll be possible to build a simple quest. I have been thinking about the separation between Pxlqst, the game, and Pxlngn, the game engine, upon which I expect pixel art enthusiasts will create many a 16×16 adventure game.
See the map format here:
And although this is also a shameless plug to donate to the Public Lab non-profit by becoming a sustaining member, it’s also just a sweet tote that I’m proud of:
Nice Etsy-style photo by fellow PL staffer Becki, too!
OK, I really wanted to say “totes” something but totes didn’t have the heart.
Antfarm class today again; I introduced walls — red pixels can’t be crossed. But the ants struggled to navigate around walls. We used a basic bump-along-the-wall strategy but some of them get stuck. Still, a great class — lots of complex behaviors and ideas, and some successful prototypes. See below. (code here posted on the wiki)
In other news, I left the colony foraging antfarm code running for a week, and it was still running when we started class today. There’s a population limit of 100, though, so this wasn’t “ecological balance” but it’s still interesting to see.
In my role as an OSHWA board member (up for re-election! ::shameless::), I spent some time over the past year (but not as much as OSHWA board president Michael Weinberg!) reading over and commenting on the evolving drafts of the Open Source Hardware Certification.
I pushed hard for certain lines and clarifications, and I just want to quickly address a few possible misconceptions or even straw men I’ve seen on recent posts about it (mostly in the comments). There are valid reasons both to support or dislike the proposal, but I believe the following three are mostly based on misunderstandings:
Folks seem to be misconstruing the “penalties” mentioned. Just to be clear, the ONLY way you’d have to pay fees is if your work is not actually open source hardware as defined in the OSH Definition. And even then, you could simply remove the logo from your products instead of paying the fees. See Michael’s response in the comments of the Certification announcement.
The idea is that no truly open source hardware project could ever incur fees. Only the bad actors!
Certified projects vs Open Source Hardware projects
Q: If you don’t get your project certified, can it still be open source hardware?
A: YES. If it conforms to the Open Source Hardware Definition. See the end of paragraph 4:
While certification is not a condition for openness, obtaining certification is a way to make it clear to others that a given project is open source hardware.
Certification vs. Licensing
Are they redundant? Are they the same thing? Does OSHWA want me to certify instead of license? No.
Also, I saw a comment on the Cert announcement that commented:
I’m seeing a stark difference between this proposal and a free (libre) software license like the GPL.
Yes! Most definitely! The cert is NOT a license, and works on a different principle. But importantly, the certification relies on compliance with the Open Source Hardware Definition, which requires that designs be licensed!
The Definition uses the word license 34 times. Certification and licensing aren’t the same thing, but certification supports licensing, adds extra clarity, and adds the ability by OSHWA to call out bad actors.
Thanks! And especially thanks to Michael for his hard work on this initiative!
P.S. I’m also in agreement with Windell that to do this well, we’ll need to be really thorough and careful — and to have a really awesome cert logo!
I’ve had some great foraging experiences in the past couple weeks — just quickly, below are some pawpaws from the east coast. In some places they are endangered or threatened, although in others they are considered “common” — these were from Maryland, where they are apparently not uncommon.
The PawPaw, aka Asimina triloba:
Best enjoyed on a freshly made waffle (HOW?!?! By the magic of my wonderful hosts, whom I’ll gladly cite if they wish.)
Great trivia about these — they were a fav. dessert of George Washington, the leaves contain a natural pesticide, and they were likely originally propagated by North American megafauna before those were all eaten by humans. Now we eat pawpaws and are likely their primary propagators.
Then, outside Portland Oregon, I (in collaboration with other Public Lab staff) found several large Leccinum Manzanitae (or variants of), which are great when roasted in slices:
…and Boletus Mirabilis, which I did not have an opportunity to actually eat:
All among an array of other interesting discoveries. At bottom are some Bitter Hedgehog mushrooms, which are beautiful if inedible.
We prototyped a lot of ant death scenarios today in AntFarm class. Also — queens creating new queens, and queen death.
More soon — but here’s the partially buggy code for the latter: https://gist.github.com/anonymous/a95bad3aaf6b7f344460
Next class: ant decomposition, trail fading, ant energy and “sight”. https://github.com/jywarren/antfarm/issues/15
First, partial day of Antfarm class at Parts & Crafts today. Much excitement and some bugs found (lol). A queen was quickly suggested and implemented, who spawns new ants, too quickly, then too slowly. New ants won’t change color, unfortunately — https://github.com/jywarren/antfarm/issues/6
Then, overpopulation quickly became a problem, so we opened issue 5, “ant death” https://github.com/jywarren/antfarm/issues/5
Good progress for a first day — the entomologists have agreed to come back next week with more ideas and I’ll get a permanent ant farm installed on the windowsill in the meantime.
Draft queen script saved as queen.ant