webmaker

youtube

This is a crash course, tutorial/introduction video for using Meemoo to create GIFs for Tumblr or anywhere else for that matter. You can click on any of the GIFs below to open up the existing Meemoo web app that was used to create them. You can see the first two GIFs below being made in the tutorial video above.

You don’t need to download or install anything for Meemoo and it is open source, bringing visual programming to your browser. You can use existing web apps, hack existing web apps, create your own and share the content/apps you make with anybody for free.

Cam to GIF

Grid Hack

PizzaSkin

Slitscan

Deal With It

Stereoscopic

Blank Meemoo App

More Existing Apps Here

If you have any questions, feel free to ask me, or contact the creator of Meemoo.

2

CHECK IT OUT I GOT INTO THE SFMOMA!

Not really. I used Mozilla Webmaker.org’s X-Ray Goggles to remix the SFMOMA website. It even let me use GIFs and put my own video over the one they had posted.

http://maxcapacity.makes.org/goggles/maxcapacitys-remix-of-the-san-francisco-museum-of-modern-art-sfmoma—4

TRY IT OUT! It’s pretty fun. I always wanted to be in a museum
https://goggles.webmaker.org

You could also remix the NSA website to make them look bad (worse) or something like that.

IF you do remix something, let me know so I can check it out!

Learning, Freedom and My Job

While I was off making a human and getting him through the first 12 weeks of his life, the Mozilla Foundation has been up to some pretty cool stuff. 

Back in November 2010, some of us met in Barcelona to explore the idea of hacking and learning. What would happen if we took the hacker way of thinking and applied it to learning and education? What assumptions would get turned on their heads? What would we CHANGE? What would we TEACH? I didn’t work for Mozilla at the time so I am not sure how much of this was foreseen and how much was a surprise, but the energy, inspiration and output was incredible. Mozilla had really tapped into something special. 

A lot of projects spun out of that time together, including the Open Badges project, which obviously I have been closely aligned with since (see every blog post before this :)). But in addition to these projects, there was this lingering sense that Mozilla had more to say. More to do.

Well, now we are saying it. And we are doing it. 

This year we are building a Mozilla learning offering around web making and web literacies. We will be defining and developing a core set of web literacy skills. We will build curriculum and learning pathways around these skills. And that learning and skill development will be recognized by Mozilla badges. It’s Mozilla as a digital/web literacy evangelist. Mozilla as a learning provider. Mozilla as a badge issuer. Mozilla as a game changer.

With this refocus and my return from maternity leave, I now have the opportunity to work with an amazing group of folks to build this together. We make up the MoFo Learning Group and we can haz awesomeness. 

VERY excited about this work. 2012 is a BIG year. Welcome back to me!

29 January 2015
  • 29 January 2015
  • Web Literacy Map v1.5 community calls
  • Webmaker
Play

On this week’s community call we recapped last week’s call, discussed using GitHub as an issue tracker, highlighted blog posts from community members, and then dived into the two-part proposal from Doug.

The proposal was: 

  1. Combine the current ‘Infrastructure’ and ‘Web Mechanics’ competencies. This would create a re-scoped Web Mechanics competency under the Exploring strand.
  2. Separate out ‘Design & Accessibility’ into two re-scoped competencies within the Building strand: Designing for the Web and Accessibility.

After much back-and-forth, this proposal was accepted and will be implemented in Web Literacy Map v1.5. Some of the comments:

  • I think accessibility is so very important and would appreciate the increased focus they need to be separated and bulked up. (Ian, +1’d by Greg and Gus)
  • I don’t know enough to vote either way. (Mikko)
  • My only qualm is this bumps against the limits of the “exploring” term.
    Web mechanics definitely feels like infrastructure, but it feels more
    like building to me. But then, this is the limit of reading/writing
    dichotomy. (Gus)
  • What about swapping remixing with web mechanics, so that remixing is part of exploring and the *new* web mechanics falls where it feels like it belongs on under building? (Marc)

A lot of the other comments rested on slightly tangential (but still important) issues such as the naming of these competencies, whether reading/writing/participating is a useful taxonomy, and the links between web infrastructure and governance.

Next week, on the suggestion of Marc we’re going to be having more of a ‘doing’ call where we dive into the skills underpinning all of the competencies. This means there’ll be more more hack, less yack! This call will be at 4pm UTC on Thursday 5th February 2015.

Join the Webmaker list and/or subscribe to the calendar for updates!

Finally, Doug encouraged people to blog their thoughts and to file issues on the Web Literacy Map’s GitHub repository. There’s also the specific #TeachTheWeb discussion forum thread for this week’s call. Finally, there’s a couple of ways that people can dive into the Web Literacy Clubs work right now:

There are three NYC events with Meemoo’s maker this month!

July 12th - Open(Art) group exhibition opening: http://www.eyebeam.org/events/openart-–-creative-platforms-for-the-open-web

July 13th - Educator media hacking workshop: http://www.eyebeam.org/events/openart-workshop-day

July 15-19th - Animation workshop for teenagers: http://www.eyebeam.org/events/mozilla-maker-party-moving-storytelling

OBI Public Beta

We are announcing today that we launched the Public Beta of the Open Badge Infrastructure. Huge milestone and huge kudos to the team for making it happen. 

What’s the OBI?

The OBI is the ‘plumbing’ of the badge ecosystem. It is a specification for badges, set of repositories (“Backpacks”) for storing badges and APIs for pushing badges in and pulling badges out. It’s an important piece of this badge experiment because it moves us beyond more silo’d systems, allows the learner to collect badges from lots of different learning experiences and provides the structural components to enable badges to be transferred and leveraged across the ecosystem for real results like jobs or credits.

What’s Public Beta?

With this Public Beta launch, the OBI is now publicly available for use. Badges can be pushed in and pulled out and earners can store badges in the middle in their Backpacks. And more! Specifically, Public Beta includes:

  • New and improved issuer API
  • Backpack feature upgrades:
    • Store badges
    • Manage badges
    • Import badges
    • Group badges
    • Publish groups to a unique URL and add narrations/notes around each badge to share
  • New displayer API
  • New documentation
  • Legal docs! Privacy policy, terms of use and FAQs specifically for the Backpacks.

Wait, weren’t you already in beta?

Yes and no. We were calling it ‘beta1’ which was a made up word to mean that it was a step up from alpha but not quite all the way to beta. It was essentially the initial issuer API and Backpacks, but was available basically by invite only. We should have called it a ‘developer preview’ but hindsight, something something. This Public Beta (capital B!) is a proper Mozilla beta (security review, user data committee review, on Mozilla servers, etc.) and its publicly available! Woo!

What does it look like?

Technically like this…

But really like this…

(Sample Badge Backpack)

And this….

(Published group of badges)

How can I get involved?

What’s Next?

We are moving to a much shorter release cycle - releasing things at least every two weeks, but possibly more quickly as we go. But we are aiming to move from Beta to 1.0 by the end of the year. In addition that work, plus bug fixes along the way, we are also working on some lightweight tools that make creating and issuing badges easier, and eventually will most likely do the same for displaying badges. 

Who should we congratulate?

The team for being some of the smartest, hardest working game changers I’ve known, as well as our community who have been advising us every step of the way. Thanks to you all - congratulations!

-E

As part of their 2013 Maker Party, Mozilla have developed three tools designed to hack and remix the content of the world wide web (WWW), collectively termed the Webmaker suite. Liaison for Hacking Popular culture Kat Braybrooke has assembled a team of webmaker fellows and our tech editor and media artist Stephen Fortune is among them. He’ll be sharing his reflections on the Webmaker tools with the Hacked & Burned blog for the next threee weeks. (via Break the internet | Dazed Digital)

this is going to start showing up on google image search for “max capacity” i can tell

StopWatching.Us

Last week, we learned that the U.S. government is using secret surveillance programs to collect vast amounts of our personal data from Internet and phone companies.  If true, these revelations represent a stunning abuse of our basic right to privacy. Many troubling questions are being raised, including what this means for the future of the Internet. Here at Mozilla, we strongly believe that when users fear government surveillance or are unable to know when, how and why their private data is being collected and used, a free and open web becomes impossible.

That’s why Mozilla is launching StopWatching.Us — a campaign sponsored by a broad coalition of political and tech organizations. We’re calling on citizens and organizations from around the world to demand that the U.S. Congress reveal the full extent of the National Security Agency’s spying programs.

We don’t want an Internet where everything we do is secretly tracked, monitored and logged by companies or governments. And we don’t want a government whose actions are invisible and unaccountable.

Please add your name to the petition:
https://stopwatching.us

Web Literacy Teaching Plans for Libraries

Are you interested in library instruction? Want to work on something easy, quick, and concrete?
I just started a draft of a ‪#‎webmaker‬ teaching plan based on the “exploring” section of the ‪#‎webliteracystandard‬.
Let’s collaborate! I was hoping that this can be used for community computer workshops and concrete programming in public libraries. The goal is to create a customizable, two hour lesson plan based on this: https://webmaker.org/en-US/standard/exploring


https://jennierose.makes.org/thimble/web-literacy-standard-for-libraries

I’m particularly looking for help to figure out exciting online activities to explore the web.

Remix away! Let me know if you need any help learning to use the Webmaker editor.

Find out more about Webmaker here.

So on Saturday I’m meeting Tavi.  I KNOW, RIGHT?! <3 <3 

I’m hosting the Melbourne Rookie Day which is massive and terrifying and incredibly exciting all at once.  It’s kinda like jumping out of a plane, but without the cool parachute thingo. 

And I know, it’s sold out and why didn’t I put it on here before it sold out?  WELL I have a really good reason.  Even though it’s taken me forever to post about it on here (I think I was trying to work out what my really good reason was) but basically the Rookie Day event tickets were released in the morning and by the time I got home and could post about it, it was SOLD OUT.  Yup.  Tavi is box office gold. 

So sorry if you wanted tickets and didn’t get them in time, I totally failed on the quick post draw.  But well, if you’re really disappointed you can write to me here.  I can’t get you tickets, no really trust me, I can’t get you any tickets… but I can write you an apology haiku… or um, send you a sorry gif of a cat waving (pro tip: I might not have the coding skills for this). 

Speaking of coding (smooth transition Barnes) Mozilla Firefox are doing an interesting how-to-code style thing over on their webmaker website.  It is actually really interesting and do-able.  Definitely worth spending an hour or four on.  One day my coding abilities will sate my cat gif appetite.  One day…

What is webmaking?

Mozilla is building a generation of webmakers. We are defining webmaker literacies. We are building pathways for people to learn webmaking by webmaking. But what the heck is webmaking? What is our vision really all about?

The initial list of webmaker skills starts to pave the way for our definition of webmaking, but I think there needs more context and nuance here. Lots of smart people are working on a more public facing brand/definition around webmaking so there’s that to look forward to, but in the meantime I wanted to log my thoughts on what (I think) it is and what it isn’t.  

Webmaking is not just coding. 

We are seeing a number of teach-to-code initiatives popping up which are certainly compelling and we hope to work closely with many of them moving forward. But when we say webmaking, I think we are talking more broadly, more at the literacy level. Our ultimate webmaker curriculum suite will have coding in it in some capacity (or again, we’ll point people to all the great stuff emerging), but it will have a much broader set of skills as well. Even just glancing back at the current iteration of the webmaker skills, we can see some of the foundations of coding in the Building column (and some HTML-y stuff in one chunk of Authoring) - but there are 4 OTHER COLUMNS! Even with this 101 content, we are aiming at higher level competencies and literacies that people can use to shape their pathway forward, not dictate one path for them to go down. If they decide to be coders - great! - but they will hopefully be better coders because of the full range of skills they’ve developed and honed along the way.

(NOTE: MichelleL dives further this as well on her blog

Webmaking is not a static thing.

Webmaking is made up of a set of hard skills like HTML, CSS, etc., but a host of ‘softer’ skills like collaborative making, awareness of the open web, etc. The softer skills, as evidenced by the controversial category name, are fluid and personal. We know they are not static. But with webmaking, even the hard skills are not static. Things evolve fast, new technologies and standards come out everyday. So its important to teach people enough of the hard skills to know enough to build what they want to build but we also need to teach them how to refresh those skills, stay up on current developments, contribute to the evolution. 

Webmaking is (can be) about jobs.

Webmaking skills are real, job relevant skills and not just for future web developers, but people across many disciplines. Journalists, filmmakers, scientists, business professionals, doctors, teachers…most of these skills are relevant. Through the Open Badges work, we’ve talked to a lot of employers about what they are looking for and in addition to the basic digital skills, they want people that know how to collaborate, innovate and think critically. All webmaking skills! Again, its about arming people with the range of skills needed so that they can shape their own pathway and excel.

Webmaking is understanding, building and innovating. 

We want to help webmakers not only learn basic skills, but use those skills to build things that matter to them (in fact, we’d prefer it if they learned the skills BY building the things), and by actually innovating around the initial skills so that they are leaving their mark and making the web better for webmakers to follow.

Webmaking is about capitalizing on the affordances of the Web.

Personally I think webmaking should include being prepared for and able to capitalize on the affordances of the web. When you look at things like learning - the Web opens up the possibilities for learning (open ed courses, learning games, collaborative discussions, wikipedia, etc.) but simply having an internet connection is not going to necessarily help people take advantage of these options and learn more. They need to understand how to find and evaluate these opportunities, how to participate and share information, etc. This is a hugely important piece of webmaking to me. 

Webmaking is about empowerment.

It is a high-paced, information-saturated world out there and it is very easy for people to just be consumers - to simply take things in and accept everything at face value. Part of webmaking is empowering them to take control, to realize that things (the Web for one) are not immutable, to develop and assert their own voice, to question information, to remix things and channel inner creativity, etc. 

Webmaking is a way of life.

We want to prepare people for participation and contribution in today’s (and tomorrow’s) digital society and global economy. Webmaking skills can set up an approach to life in general that fosters not only looking-under-the-hood, embracing failure, tinkering and remixing, but also participation, citizenship and action. These are not just life skills but ultimately a way of approaching life. 

Again, this is my personal opinion of webmaking. While I know that many Mozilla colleagues would agree with a lot of the above, we also need to scope it to a clear and concise definition that we can all get behind. As I mentioned, that work is in progress so more to come on that.

I am also not trying to imply that we think we can teach everyone all of this, but I think our concept of webmaking should be this far reaching. We should want to change the world (or more to the point, give people the tools to change their own worlds) and with that as a guiding principle, we will build more thoughtful, powerful and holistic learning experiences. 

-E

Game On Winner: Best Hackable Game: Code Injection by Nick Liow and Jason Church from Vancouver


"Inject real code to move your character around. Hack other characters to steal your enemies abilities and share their powers. Like hacking the Matrix — using real code that works on the web."


Play the Game:
http://inject.craftyy.com

See other winning entries & find out more about the competition:
https://gameon.mozilla.org/en-US