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



Deal With It


Blank Meemoo App

More Existing Apps Here

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



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.


TRY IT OUT! It’s pretty fun. I always wanted to be in a museum

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!


First Look at Mozilla Webmaker app on FirefoxOS

Mozilla announced at Mobile World Congress plans to help a wider audience create the mobile internet.

As previously mentioned, Webmaker helps smartphone users become creators of a Web that will improve their lives and communities, by making simple apps for things like promoting a small business, sharing community news, or building a lesson plan for students.

The concept is amazing and simple to use and runs smooth. It really help people create a simple mobile app or blog in just a few clicks, as you can see on the gallery. 

Users can share their app creations using a simple URL via SMS, Facebook, WhatsApp and other platforms. The apps will load in any mobile web browser, powered by HTML5.

Webmaker app is free, open source and available in over 20 languages. 

I have tested on a FirefoxOS device running the latest beta build of 2.2.


The BETA App is available at Firefox OS 2.1+ and Android 4.4+.

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!


Creating a catalog of curriculum & educational programming for a project as diverse as Mozilla isn’t exactly easy. We use a variety of pedagogies, we have different target audiences, we are starting from different places. There are semantics, politics, and relationships we have to consider when organizing learning materials and programming. And, a little secret, everyone organizes information a little differently, which can make it hard to see the relationships, understand the politics or even just agree on semantics. But we have to organize information in a variety of ways because we have a variety of learners. The best way to serve our learners is to utilize each other’s work, and the best way to do that is by making mash-ups and remixes from one another’s work. I’m quite pleased to see the vision of modular curriculum taking hold, and quite proud that we are creating an ecosystem of building blocks that will allow us to remix. I’m remixing my heart out, so here’s what I’ve been working on and notes on stuff I’m planning to steal:

Teach Like Mozilla

We’ve built loads of curriculum to help other people #TeachTheWeb as has our community. Using the Web Literacy Map as the raw material that focuses this work, our team has coordinated and produced hundreds of pieces and parts. We’re working on a new site that will include best of materials, which we’re remixing and collecting here. On top of curating and iterating on curriculum we built last year, we’ve now created, tested and iterated the first module for Clubs, which will launch with the new site. I’ve been working on remixing our Training program, as well as stuff from the other projects listed below, to create curriculum for Teach Like Mozilla – a series of pathways to cultivate leadership within the project. I have plenty to pull from including online learning modules for a bunch of the cognitive stuff behind our work (like group dynamics, facilitation and open participation), as well as practical things like “how to build an online presence”. Hive Learning Networks also have a wide range of professional development content to pull from. Check out this issue and included links.

Stuff I want to use:

Policy and Advocacy

Melissa Romaine is thinking about teaching and learning modules that people especially interested in specific policy or advocacy topics can utilize to spread the word about important web issues and how to address them. She’s looking to build teaching kits and engagement activities to help people teach and train others in topics like Security, Privacy, Surveillance, Covalense and Suvaillence. Andre Garzia is beginning to think about Advocacy as well, and is looking to continue testing curriculum in LAN Houses – a huge value add to what we’re doing with Club Curriculum because we can see what works and iterate on the fly.

Mozilla Science

The open science team was awarded a grant to level up their own professional development programming, and begin creating curriculum for the open science community. Bill Mills, Abby Cabunoc and Arliss Collins are also building out a fellowships program, complete with professional development and curriculum for train the trainers. They are focusing on technical skills for science, but also open source attitude and participation. I’m already pulling some of Mozilla Science’s stuff into Teach Like Mozilla, but plan on stealing more (often :)

Community Education

Emma Irwin wrote a great post about building curriculum & training opportunities as a way to better empower contributor success on project goals. The potential for volunteers is the opportunity for professional development and a new realization of contribution as a singular learning opportunity. The opportunity for functional areas (and all of Mozilla) is to reach goals with higher quality contributions, and greater impact. Things like conflict resolution and facilitation modules to help events and communities be more empathetic, supportive and participatory by nature are core to this team’s learning objectives. We’re talking regularly, and using and remixing things Emma has been working on is going to make the Teach Like Mozilla content top notch. We’re also trying to set ourselves up so that in the future we can easily pull all this great content together under a Mozilla Learning banner.


Lukas Blakk has an entire program, complete with 6 weeks of curriculum, that aims to help marginalized communities learn to contribute to open source. This curriculum pulls personal development into professional development and has weeks and weeks of agendas – I want to make sure Teach Like Mozilla does personal development and reflection too.


Chris Mills also has an entire program, complete with curriculum, that teaches the basic technologies of the web, and that is the fodder for MDN’s new “Content Kits”. Also at the MDN, Jeremie Patonnier, Justin Crawford and Diane Tate are a: friendly and 2: figuring out how the MDN can better support their communities with the Learning Zone, experiments and a fellowship program for developers in which fellows will develop teaching kits while contributing to Mozilla projects. I’m keeping my eye on the MDN work :)

Next Steps

For me, the next step is to develop a solid organizing structure for Teach Like Mozilla content. I’ve had conversations about the overarching structure and it’s time to get into the dirty details – which, as you might have guessed, I have several ideas for. The meta bit is 3-fold:
  • Meta-cognitive: Theories and Pedagogies (for learning) conceptually and in practice
  • Logistical: Practicalities of working openly. Building systems and processes to support collaborative work.
  • Social: Networking local activity with global communities (and vice versa)
The devil is in the details – the organizing structure will help me figure out how to take all of this amazing work and crochet it into a usable set of modules that is cohesive in style and voice. I love your feedback and comments, and I’m always happy for help. Please do reach out!

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


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:

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


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.

Mozilla Webmaker, a free & open source mobile content creation app!

Mozilla is working to ensure that the next billion people to come online for the first time through their smartphones will discover a Web that’s open, participatory and invites creativity.

Webmaker »


Webmaker helps smartphone users become creators of a Web that will improve their lives and communities, by making simple apps for things like promoting a small business, sharing community news, or building a lesson plan for students.

Webmaker is available in over 20 languages and backed by a growing community of volunteer digital skills mentors. It will be available for Android, Firefox OS, and modern mobile browsers later this year.

Download the Webmaker Beta at https://webmaker.org/app, available for FirefoxOS 2.1+ and Android 4.4+

12 March 2015
  • 12 March 2015
  • Web Literacy Map v1.5 community calls
  • Mozilla Webmaker

On this week community call we were making the final push to finish the skills under the competencies of version 1.5 of the Web Literacy Map. We started off with Ian sharing a Cory Doctorow talk, but then dove write into the work.

Doug was on personal time off but checked in throughout the day and helped to set up the etherpad (learning to take PTO like an American I guess).

We first reviewed the activity on Git as we shifted to asynchronous work to ensure Version 1.5 can ship by the end of Q1. The team is getting more comfortable with filing and responding to issues on Git and we encourage everyone to visit the issues to track our progress,

We first reviewed the sharing competency as we noted earlier that this was our most problematic competency. Too much overlap existed with other competencies in version 1.1 of the Map.

The following skills were proposed in GitHub:

  • Contributing content and finding content for the benefit of others (Greg)
  • Creating, curating and circulating web resources to elicit peer feedback (Greg)
  • Understanding the needs of audience in order to make relevant contributions to a community (Greg)
  • Creating and using a system to distribute web resources to others (Greg)
  • Identifying when it is safe to contribute content in a variety of situations on the web (Tim)

Ian and Mikko suggested that creating a system to share should be ordered as the first skill. The final list of skills included.

  • Creating and using a system to distribute web resources to others.
  • Contributing  and finding content for the benefit of others.
  • Creating, curating, and circulating web resources  to elicit peer feedback.
  • Understanding the needs of audiences in order to make relevant contributions to a community.
  • Identifying when it is safe to contribute content in a variety of situations on the web.

Next we turned to Search

  • Developing questions related to your goal and knowing when these questions are answered. (proposed)
  • Using and revising keywords to make your web searches more efficient.(approved)
  • Evaluating search results to determine if the information is relevant to your needs. (edited needs approval)
  • Finding real-time or time-sensitive information using a range of search techniques. (approved)
  • Discovering information and resources by asking people within social networks (proposed)

These were discussed extensively. Gadit and Tim were looking for clarification on the questioning skill. We spent a good amount of time deciding if formulating questions was part of a searching skill. The group decided to keep the skill. The skills were edited to only include third person language and they were approved.

Next we turned to Composing for the Web

We began with the following proposed skills -

  • Inserting hyperlinks into a web page (defined)
  • Embedding multimedia content into a web page (defined)
  • Creating web resources in ways appropriate to the medium/genre (defined)
  • Identifying and using HTML tags (defined)
  • Creating and controlling a space to publish on the Web (Doug)

We debated the last skill. Specifically if you create a space and why you have to control the space. Laura brought up the issue of how we started on hosted spaces and moved to open spaces. Greg argued for trying to push people out of silos and on to the open web. Mikko and Gadit supported a similar position.

In the end we voted on:

  • Setting up and maintaining a space to publish on the web+1+1+1+1+1
  • establishing, acquiring+1+1, and setting up
  • maintaining controlling +1

The skills under the competency were then set.

Next we turned to remix, but once we realized that we could not come to agreement we decided to abandon the issue in kicked it to asynchronous debate. Ian argued for renaming the competency synthesis. Greg argued to move the synthesis skills booted from search to remix. He felt you are making something new wit someone else idea. Gadit felt strong that, “Remixing is under building - it should have a very specific ‘publishing’ aspect,” and therefore should not include “in your head” skills. Laura questions whether we were discussing a web literacy skill or a life skill.,

There was also debate whether attribution fit under remix or under open practice. We did agree that the skill on remixing open content should be changed to, “Identifying and using content that can be ethically remixed.” This separated the skill from the open practices competency.

We also turned to the skill, “Creating something new on the web using existing resources” and felt it was too close to a new remix we added: “Shifting context and meaning by creating derivative content.” There is a current debate on GitHub whether these are similar skills and only one is needed or if both skills are needed under the remix competency.

We tried then to turn to credibility and we nailed down a skill before time was up.

Wrapping Up

We have almost finished Version 1.5 of the Web Literacy Map. Here is our current state of progress

Finished competencies:

  • Search
  • Sharing
  • Composing for the web
  • Navigation
  • Web Mechanics
  • Designing for the web
  • Accessibility
  • Community Participation

Unresolved competencies:

  • Credibility
  • Security
  • Remixing
  • Coding/scripting
  • Collaborating
  • Privacy
  • Open Practices

Final Steps

It was decided to host a hack session on Monday 5pm UTC (10am PT / 1pm ET / 5pm CET / 10.30pm IST). The group also decided to abandon the spreadsheet for work (though Ian will update it) and just finish off our work on Github.

Please visit the meta-issue if you would like to contribute.