Mozilla Nederland LogoDe Nederlandse

Christian Heilmann: Google IO – A tale of two Googles

Mozilla planet - mo, 23/05/2016 - 01:59

Google IO main stage with audience

Disclaimer: The following are my personal views and experiences at this year’s Google IO. They are not representative of my employer. Should you want to quote me, please do so as Chris Heilmann, developer.

TL;DR: Is Google IO worth the $900? Yes, if you’re up for networking, getting information from experts and enjoy social gatherings. No, if you expect to be able to see talks. You’re better off watching them from home. The live streaming and recordings are excellent.

Google IO this year left me confused and disappointed. I found a massive gap between the official messaging and the tech on display. I’m underwhelmed with the keynote and the media outreach. The much more interesting work in the breakout sessions, talks and demos excited me. It seems to me that what Google wants to promote and the media to pick up is different to what its engineers showed. That’s OK, but it feels like sales stepping on a developer conference turf.

I enjoyed the messaging of the developer outreach and product owner team in the talks and demos. At times I was wondering if I was at a Google or a Mozilla event. The web and its technologies were front and centre. And there was a total lack of “our product $X leads the way” vibes.

Kudos to everyone involved. The messaging about progressive Web Apps, AMP and even the new Android Instant Apps was honest. It points to a drive in Google to return to the web for good.

Illuminated dinosaur at the after party

The vibe of the event changed a lot since moving out of Moscone Center in San Francisco. Running it on Google’s homestead in Mountain View made the whole show feel more like a music festival than a tech event. It must have been fun for the presenters to stand on the same stage they went to see bands at.

Having smaller tents for the different product and technology groups was great. It invited much more communication than booths. I saw a lot of neat demos. Having experts at hand to talk with about technologies I wanted to learn about was great.


Feet in the sun watching a talk at the Amphitheatre

Here are the good and bad things about the organisation:

  • Good: traffic control wasn’t as much of a nightmare I expected. I got there two hours in advance as I anticipated traffic jams, but it wasn’t bad at all. Shuttles and bike sheds helped getting people there.
  • Good: there was no queue at badge pickup. Why I had to have my picture taken and a – somehow sticky – plastic badge printed was a bit beyond me, though. It seems wasteful.
  • Good: the food and beverages were plentiful and applicable. With a group this big it is hard to deliver safe to eat and enjoyable food. The sandwiches, apples and crisps did the trick. The food at the social events was comfort food/fast food, but let’s face it – you’re not at a food fair. I loved that all the packaging was paper and cardboard and there was not too much excess waste in the form of plastics. We also got a reusable water bottle you could re-fill at water dispensers like you have in offices. Given the weather, this was much needed. Coffee and tea was also available throughout the day. We were well fed and watered. I’m no Vegan, and I heard a few complaints about a lack of options, but that may have been personal experiences.
  • Good: the toilets were amazing. Clean, with running water and plenty of paper, mirrors, free sunscreen and no queues. Not what I expected from a music festival surrounding.
  • Great: as it was scorching hot on the first day the welcome pack you got with your badge had a bandana to cover your head, two sachets of sun screen, a reusable water bottle and sunglasses. As a ginger: THANK YOU, THANK YOU, THANK YOU. The helpers even gave me a full tube of sunscreen on re-entry the second day, taking pity on my red skin.
  • Bad: the one thing that was exactly the same as in Moscone was the abysmal crowd control. Except for the huge stage tent number two (called HYDRA - I am on to you, people) all others were far too small. It was not uncommon to stand for an hour in a queue for the talk you wanted to see just to be refused entry as it was full up. Queuing up in the scorching sun isn’t fun for anyone and impossible for me. Hence I missed all but two talks I wanted to see.
  • Good: if you were lucky enough to see a talk, the AV quality was great. The screens were big and readable, all the talks were live transcribed and the presenters audible.

The bad parts

Apart from the terrible crowd control, two things let me down the most. The keynote and a total lack of hardware giveaway – something that might actually be related.

Don’t get me wrong, I found the showering of attendees with hardware excessive at the first few IOs. But announcing something like a massive move into VR with Daydream and Tango without giving developers something to test it on is assuming a lot. Nine hundred dollars plus flying to the US and spending a lot of money on accommodation is a lot for many attendees. Getting something amazing to bring back would be a nice “Hey, thanks”.

There was no announcement at the keynote about anything physical except for some vague “this will be soon available” products. This might be the reason.

My personal translation of the keynote is the following:

We are Google, we lead in machine learning, cloud technology and data insights. Here are a few products that may soon come out that play catch-up with our competition. We advocate diversity and try to make people understand that the world is bigger than the Silicon Valley. That’s why we solve issues that aren’t a problem but annoyances for the rich. All the things we’re showing here are solving issues of people who live in huge houses, have awesome cars and suffer from the terrible ordeal of having to answer text messages using their own writing skills. Wouldn’t it be better if a computer did that for you? Why go and wake up your children with a kiss using the time you won by becoming more effective with our products when you can tell Google to do that for you? Without the kiss that is – for now.

As I put it during the event:

I actually feel poor looking at the #io16 keynote. We have lots of global problems technology can help with. This is pure consumerism.

I stand by this. Hardly anything in the keynote excited me as a developer. Or even as a well-off professional who lives in a city where public transport is a given. The announcement of Instant Apps, the Firebase bits and the new features of Android Studio are exciting. But it all got lost in an avalanche of “Look what’s coming soon!” product announcements without the developer angle. We want to look under the hood. We want to add to the experience and we want to understand how things work. This is how developer events work. Google Home has some awesome features. Where are the APIs for that?

As far as I understand it, there was a glitch in the presentation. But the part where a developer in Turkey used his skills to help the Syrian refugee crisis was borderline insulting. There was no information what the app did, who benefited from it and what it ran on. No information how the data got in and how the data was going to the people who help the refugees. The same goes for using machine learning to help with the issue of blindness. Both were teasers without any meat and felt like “Well, we’re also doing good, so here you go”.

Let me make this clear: I am not criticising the work of any Google engineer, product owner or other worker here. All these things are well done and I am excited about the prospects. I find it disappointing that the keynote was a sales pitch. It did not pay respect to this work and failed to show the workings rather than the final product. IO is advertised as a developer conference, not a end user oriented sales show. It felt disconnected.

Things that made me happy

Chris Heilmann covered in sunscreen, wearing a bandana in front of Google Loon

  • The social events were great – the concert in the amphitheatre was for those who wanted to go. Outside was a lot of space to have a chat if you’re not the dancing type. The breakout events on the second day were plentiful, all different and arty. The cynic in my sniggered at Burning Man performers (the anthithesis to commercialism by design) doing their thing at a commercial IT event, but it gave the whole event a good vibe.
  • Video recording and live streaming – I watched quite a few of the talks I missed the last two days in the gym and I am grateful that Google offers these on YouTube immediately, well described and easy to find in playlists. Using the app after the event makes it easy to see the talks you missed.
  • Boots on the ground – everyone I wanted to meet from Google was there and had time to chat. My questions got honest and sensible answers and there was no hand-waving or over-promising.
  • A good focus on health and safety – first aid tents, sunscreen and wet towels for people to cool down, creature comforts for an outside environment. The organisers did a good job making sure people are safe. Huge printouts of the Code of Conduct also made no qualm about it that antisocial or aggressive behaviour was not tolerated.


Jatinder and me at the keynote

I will go again to Google IO, to talk, to meet, to see product demos and to have people at hand that can give me insight further than the official documentation. I am likely to not get up early next time to see the keynote though and I would love to see a better handle on the crowd control. It is frustrating to queue and not being able to see talks at the conference of a company who prides itself at organising huge datasets and having self-driving cars.
Here are a few things that could make this better:

  • Having screening tents with the video and the transcription screens outside the main tents. These don’t even need sound (which is the main outside issue)
  • Use the web site instead of two apps. Advocating progressive web apps and then telling me in the official conference mail to download the Android app was not a good move. Especially as the PWA outperformed the native app at every turn – including usability (the thing native should be much better). It was also not helpful that the app showed the name of the stage but not the number of the tent.
  • Having more places to charge phones would have been good, or giving out power packs. As we were outside all the time and moving I didn’t use my computer at all and did everything on the phone.

I look forward to interacting and working with the tech Google. I am confused about the Google that tries to be in the hands of end users without me being able to crack the product open and learn from how it is done.

Categorieën: Mozilla-nl planet

Mozilla Gigabit Community Fund Expands to Austin - Silicon Hills News

Nieuws verzameld via Google - snein, 22/05/2016 - 22:24

Mozilla Gigabit Community Fund Expands to Austin
Silicon Hills News
The fund is a joint initiative among Mozilla, the maker of the Firefox web browser, the National Science Foundation and U.S. Ignite. Mozilla is providing $150,000 in grant funding to Austin projects and tools that use the city's Google Fiber network ...

Categorieën: Mozilla-nl planet

Mozilla's Firefox surpasses IE/Edge in market share for first time ever - AfterDawn

Nieuws verzameld via Google - snein, 22/05/2016 - 18:34


Mozilla's Firefox surpasses IE/Edge in market share for first time ever
Mozilla's Firefox surpasses IE/Edge in market share for first time ever According to the most recent StatCounter figures, Firefox has surpassed Internet Explorer/Edge in market share for the first time ever, although all three browsers still have ...

en meer »
Categorieën: Mozilla-nl planet

Daniel Glazman: CSS Variables in BlueGriffon

Mozilla planet - snein, 22/05/2016 - 16:44

I guess the title says it all :-) Click on the thumbnail to enlarge it.

CSS Variables in BlueGriffon

Categorieën: Mozilla-nl planet

Mozilla Firefox – tipy pro ochranu soukromí - 2.díl - PC

Nieuws verzameld via Google - snein, 22/05/2016 - 10:18


Mozilla Firefox – tipy pro ochranu soukromí - 2.díl
Mozilla Firefox – tipy pro ochranu soukromí - 2.díl. Internet | 22.05.16. Pokud jste příznivci internetového prohlížeče Mozilla Firefox, pak určitě oceníte následující tipy, které vám umožní zefektivnit ochranu vašeho soukromí právě v souvislosti s ...

en meer »Google Nieuws
Categorieën: Mozilla-nl planet

Mozilla Firefox 46.0.1 Lands in the Ubuntu Repos, But No Sign of Thunderbird 45 - Softpedia News

Nieuws verzameld via Google - snein, 22/05/2016 - 03:37

Softpedia News

Mozilla Firefox 46.0.1 Lands in the Ubuntu Repos, But No Sign of Thunderbird 45
Softpedia News
Canonical recently pushed the first point release of the Mozilla Firefox 46.0 web browser to the stable channels for all supported Ubuntu Linux operating systems, along with Mozilla Thunderbird 38.8.0. Mozilla Firefox 46.0.1 is a small bug fix update ...

Categorieën: Mozilla-nl planet

Mozilla Invests $59000 In Three Kansas City Startups - KCUR

Nieuws verzameld via Google - sn, 21/05/2016 - 22:20


Mozilla Invests $59000 In Three Kansas City Startups
Three Kansas City startups will receive a combined $59,000 from the Mozilla Gigabit Community Fund to expand and develop programs that promote innovation in the classroom. KC Social Innovation Center, PlanIT Impact and Pennez were awarded money ...

Categorieën: Mozilla-nl planet

Kennst du schon…? Interessante, aber weniger bekannte Mozilla-Projekte #3 -

Nieuws verzameld via Google - sn, 21/05/2016 - 16:16

Kennst du schon…? Interessante, aber weniger bekannte Mozilla-Projekte #3
Die meisten kennen Mozilla durch Firefox, einige vielleicht auch noch durch Thunderbird und Firefox OS. Dann aber hört es oft schon auf. Dabei macht Mozilla so viel mehr, was vielen gar nicht bewusst ist. In dieser Artikel-Serie sollen andere Mozilla ...

en meer »
Categorieën: Mozilla-nl planet

Linksys says 'no' to the FCC, Mozilla expands open source funding, and more ... -

Nieuws verzameld via Google - sn, 21/05/2016 - 09:07

Linksys says 'no' to the FCC, Mozilla expands open source funding, and more ...
In this week's edition of our open source news roundup, we take a look at Linksys saying no to the FCC's router rules, Mozilla expands its funding for open source projects, a new open source project from LinkedIn, and more.

Categorieën: Mozilla-nl planet

Gian-Carlo Pascutto: Technical Debt, Episode 1

Mozilla planet - sn, 21/05/2016 - 00:30
One of the projects I'm working on for Mozilla is our Content Sandboxing. We've been using sandboxing for a while to protect some plugins like Flash, as well as media plugins, but now that Firefox can render webpages in a separate process, we can apply restrictions to what those "Web Content" processes can do, too. Those processes are the part of Firefox that is essentially exposed to the internet, and hence to potentially dangerous webpages.

Although we go to great lengths to make this impossible, there is always a chance that a bug in Firefox would allow an attacker to exploit and take over a Web Content process. But by using features provided by the operating system, we can prevent them from taking over the rest of the computing device by disallowing many ways to interact with it, for example by stopping them from starting new programs or reading or writing specific files.

This feature has been enabled on Firefox Nightly builds for a while, at least on Windows and Mac OS X. Due to the diversity of the ecosystem, it's taken a bit longer for Linux, but we are now ready to flip that switch too.

The initial version on Linux will block very, very little. It's our goal to get Firefox working and shipping with this first and foremost, while we iterate rapidly and hammer down the hatches as we go, shipping a gradual stream of improvements to our users.

One of the first things to hammer down is filesystem access. If an attacker is free to write to any file on the filesystem, he can quickly take over the system. Similarly, if he can read any file, it's easy to leak out confidential information to an attacking webpage. We're currently figuring out the list of files and locations the Web Content process needs to access (e.g. system font directories) and which ones it definitely shouldn't (your passwords database).

And that's where this story about technical debt really starts.

While tracing filesystem access, we noticed at some point that the Web Content process accesses /etc/passwd. Although on most modern Unix systems this file doesn't actually contain any (hashed) passwords, it still typically contains the complete real name of the users on the system, so it's definitely not something that we'd want to leave accessible to an attacker.

My first thought was that something was trying to enumerate valid users on the system, because that would've been a good reason to try to read /etc/passwd.

Tracing the system call to its origin revealed another caller, though. libfreebl, a part of NSS (Network Security Services) was reading it during its initialization. Specifically, we traced it to this array in the source. Reading on what it is used for is, eh, quite eyebrow-raising in the modern security age.

The NSS random number generator seeds itself by attempting to read /dev/urandom (good), ignoring whether that fails or not (not so good), and then continuing by reading and hashing the password file into the random number generator as additional entropy. The same code then goes on to read in several temporary directories (and I do mean directories, not the files inside them) and perform the same procedure.

Should all of this have failed, it will make a last ditch effort to fork/exec "netstat -ni" and hash the output of that. Note that the usage of fork here is especially "amusing" from the sandboxing perspective, as it's the one thing you'll absolutely never want to allow.

Now, almost none of this has ever been a *good* idea, but in its defense NSS is old and caters to many exotic and ancient configurations. The discussion about /dev/urandom reliability was raised in 2002, and I'd wager the relevant Linux code has seen a few changes since. I'm sure that 15 years ago, this might've been a defensible decision to make. Apparently one could even argue that some unnamed Oracle product running on Windows 2000 was a defensible use case to keep this code in 2009.

Nevertheless, it's technical debt. Debt that hurt on the release of Firefox 3.5, when it caused Firefox startup to take over 2 minutes on some people's systems.

It's not that people didn't notice this idea was problematic:
I'm fully tired of this particular trail of tears. There's no good reason to waste users' time at startup pretending to scrape entropy off the filesystem. -- Brendan Eich, July 2009RNG_SystemInfoForRNG - which tries to make entropy appear out of the air. -- Ryan Sleevi, April 2014 Though sandboxing was clearly not considered much of a use case in 2006:
Only a subset of particularly messed-up applications suffer from the use of fork. -- Well meaning contributor, September 2006Nevertheless, I'm - still - looking at this code in the year of our Lord 2016 and wondering if it shouldn't all just be replaced by a single getrandom() call.

If your system doesn't have getrandom(), well maybe there's a solution for that too.

Don't agree? Can we then at least agree that if your /dev/urandom isn't secure, it's your problem, not ours?

Categorieën: Mozilla-nl planet

Air Mozilla: Webdev Beer and Tell: May 2016

Mozilla planet - fr, 20/05/2016 - 20:00

 May 2016 Once a month web developers across the Mozilla community get together (in person and virtually) to share what cool stuff we've been working on in...

Categorieën: Mozilla-nl planet

Support.Mozilla.Org: Event Report: Mozilla Ivory Coast SUMO Sprint

Mozilla planet - fr, 20/05/2016 - 18:18

We’re back, SUMO Nation! This time with a great event report from Abbackar Diomande, our awesome community spirit in Ivory Coast! Grab a cup of something nice to drink and enjoy his report from the Mozilla Ivory Coast SUMO Sprint.

The Mozilla Ivory Coast community is not yet ready to forget Saturday, May 15. It was then that the first SUMO Sprint in Ivory Coast took place, lasting six hours!
For this occasion, we were welcomed and hosted by the Abobo Adjame University, the second largest university in the country.
Many students, some members of the Mozilla local community, and other members of the free software community gathered on this day.

The event began with a Mozilla manifesto presentation by Kouadio – a young member of our local SUMO team and the Lead of the Firefox Club at the university.

After that, I introduced everyone to SUMO, the areas of SUMO contribution, the our Nouchi translation project, and Locamotion (the tool we use to localize).
During my presentation I learned that all the guests were really surprised and happy to learn of the existence of and a translation project for Nouchi
They were very happy and excited to participate in this sprint, and you can see that in the photos, emanating from their smiles and the joy that you can read from their the faces.

After all presentations and introductions, the really serious things could begin. Everyone spent two hours answering questions of French users on Twitter – the session passed very quickly in the friendly atmosphere.

We couldn’t reach the goal of answering all the Army of Awesome posts in French, but everyone appreciated what we achieved, providing answers to over half the posts – we were (and still are) very proud of our job!

After the Army of Awesome session, our SUMO warriors have turned to Locamotion for Nouchi localization. It was at once serious and fun. Originally planned for three hours, we localized for four – because it was so interesting :-)

Mozilla and myself received congratulations from all participants for this initiative, which promotes the Ivorian language and Ivory Coast as a digital country present on the internet.

Even though we were not able to reach all our objectives, we are still very proud of what we have done. We contributed very intensely, both to help people who needed it and to improve the scale and quality of Nouchi translations in open source, with the help of new and dynamic contributors.

The sprint ended with a group tasting of garba (a traditional local dish) and a beautiful family picture.

Thank you, Abbackar! It’s always great to see happy people contributing their skills and time to open source initiatives like this. SUMO is proud to be included in Ivory Coast’s open source movement! We hope to see more awesomeness coming from the local community in the future – in the meantime, I think it’s time to cook some garba! ;-)

Categorieën: Mozilla-nl planet

Patrick Cloke: Google Summer of Code 2016 projects

Mozilla planet - fr, 20/05/2016 - 15:15

I’d like to introduce the 13 students that are being mentored by Mozilla this year as part of Google Summer of Code 2016! Currently the “community bonding” period is ongoing, but we are on the cusp of the “coding period” starting.

As part of Google Summer of Code (GSoC), we ask students to provide weekly updates of their progress in a public area (usually a blog). If you’re interested in a particular project, please follow along! Lastly, remember that GSoC is a community effort: if a student is working in an area where you consider yourself knowledgable, please introduce yourself and offer to provide help and/or advice!

Below is a listing of each student’s project (linked to their weekly updates), the name of each student and the name of their mentor(s).

Project Student Mentor(s) Download app assets at runtime (Firefox for Android) Krish skaspari File API Support (Servo) izgzhen Manishearth Implement RFC7512 PKCS#11 URI support and system integration (NSS) varunnaganathan Bob Relyea, David Woodhoue Implementing Service Worker Infrastructure in Servo Browser Engine creativcoder jdm Improving and expanding the JavaScript XMPP Implementation Abdelrhman Ahmed aleth, nhnt11 Mozilla Calendar – Event in a Tab paulmorris Philipp Kewisch Mozilla Investigator (MIG): Auditd integration Arun kang Prevent Failures due to Update Races (Balrog) varunjoshi Ben Hearsum Proposal of Redesign SETA MikeLing Joel Maher Schedule TaskCluster Jobs in Treeherder martianwars armenzg Thunderbird - Implement mbox -> maildir converter Shiva mkmelin Two Projects to Make A-Frame More Useful, Accessible, and Exciting bryik Diego Marcos Web-based GDB Frontend baygeldin jonasfj
Categorieën: Mozilla-nl planet

Air Mozilla: Foundation Demos May 20 2016

Mozilla planet - fr, 20/05/2016 - 15:00

Foundation Demos May 20 2016 Foundation Demos May 20 2016

Categorieën: Mozilla-nl planet

FBI využívá ke sledování díru, která je zřejmě i ve Firefoxu. Mozilla chce chybu ... - Živě.cz

Nieuws verzameld via Google - fr, 20/05/2016 - 13:39

FBI využívá ke sledování díru, která je zřejmě i ve Firefoxu. Mozilla chce chybu ...
Američtí federální vyšetřovatelé z FBI objevili díru v zabezpečení internetového prohlížeče Tor Browser, díky které mohli sledovat a dopadnout uživatele serveru s dětskou pornografií. Tor Browser je však prohlížeč postavený na Firefoxu a je docela ...
Mozilla podala žalobu na FBI, chce informace o zranitelnosti Tor BrowseruDeep in IT

alle 3 nieuwsartikelen »
Categorieën: Mozilla-nl planet

FBI využívá ke sledování díru, která je zřejmě i ve Firefoxu. Mozilla chce chybu ... - Živě.cz

Nieuws verzameld via Google - fr, 20/05/2016 - 13:39

FBI využívá ke sledování díru, která je zřejmě i ve Firefoxu. Mozilla chce chybu ...
Američtí federální vyšetřovatelé z FBI objevili díru v zabezpečení internetového prohlížeče Tor Browser, díky které mohli sledovat a dopadnout uživatele serveru s dětskou pornografií. Tor Browser je však prohlížeč postavený na Firefoxu a je docela ...
Mozilla podala žalobu na FBI, chce informace o zranitelnosti Tor BrowseruDeep in IT
FBI nemusí Mozille vydat informace o chybě, rozhodl

alle 3 nieuwsartikelen »Google Nieuws
Categorieën: Mozilla-nl planet

Doug Belshaw: What does it mean to be a digitally literate school leader?

Mozilla planet - fr, 20/05/2016 - 12:32

As part of the work I’m doing with London CLC, their Director, Sarah Horrocks, asked me to write something on what it means to be a digitally literate school leader. I’d like to thank her for agreeing to me writing this for public consumption.

Image CC BY K.W. Barrett

Image CC BY K.W. Barrett

Before I start, I think it’s important to say why I might be in a good position to be able to answer this question. First off, I’m a former teacher and senior leader. I used to be Director of E-Learning of a large (3,000 student), all-age, multi-site Academy. I worked for Jisc on their digital literacies programme, writing my thesis on the same topic. I’ve written a book entitled The Essential Elements of Digital Literacies. I also worked for the Mozilla Foundation on their Web Literacy Map, taking it from preliminary work through to version 1.5. I now consult with clients around identifying, developing, and credentialing digital skills.

That being said, it’s now been a little over six years since I last worked in a school, and literacy practices change quickly. So I’d appreciate comments and pushback on what follows.

Let me begin by saying that, as Allan Martin (2006) pointed out, “Digital literacy is a condition, not a threshold.” That’s why, as I pointed out in my 2012 TEDx talk, we shouldn’t talk about ‘digital literacy’ as a binary. People are not either digitally literate or digitally illiterate - instead literacy practices in a given domain exist on a spectrum.

In the context of a school and other educational institutions, we should be aware that that there are several cultures at play. As a result, there are multiple, overlapping literacy practices. For this reason we should talk of digital literacies in their plurality. As I found in the years spent researching my thesis, there is no one, single, definition of digital literacy that is adequate in capturing the complexity of human experience when using digital devices.

In addition, I think that it’s important to note that digital literacies are highly context dependent. This is perhaps most evident when addressing the dangerous myth of the 'digital native’. We see young people confidently using smartphones, tablets, and other devices and therefore we assume that their skillsets in one domain are matched by the requisite mindsets from another.

So to recap so far, I think it’s important to note that digital literacies are plural and context-dependent. Although it’s tempting to attempt to do so, it’s impossible to impose a one-size-fits-all digital literacy programme on students, teachers, or leaders and meet with success. Instead, and this is the third 'pillar’ one which my approach rests, I’d suggest that definitions of digital literacies need to be co-created.

By 'co-created’ I mean that there are so many ways in which one can understand both the 'digital’ and 'literacies’ aspects of the term 'digital literacies’ that it can be unproductively ambiguous. Instead, a dialogic approach to teasing out what this means in your particular context is much more useful. In my thesis and book I came up with eight elements of digital literacies from the research literature which prove useful to scaffold these conversations:

  1. Cultural
  2. Cognitive
  3. Constructive
  4. Communicative
  5. Confident
  6. Creative
  7. Critical
  8. Civic

In order not to make this post any longer than it needs to be, I’ll encourage you to look at my book and thesis for more details on this. Suffice to say, it’s important both to collaboratively define the above eight terms and define then what you mean by 'digital literacies’ in a particular context.

All of this means that the job of the school leader is not to reach a predetermined threshold laid down by a governing body or professional body. Instead, the role of the school leader is to be always learning, questioning their practice, and encouraging colleagues and students in all eight of the 'essential elements’ listed above.

As with any area of interest and focus, school leaders should model the kinds of knowledge, skills, and behaviours they want to see develop in those around them. Just as we help people learn that being punctual is important by always turning up on time ourselves, so the importance of developing digital literacies can be demonstrated by sharing learning experiences and revelations.

There is much more on this in my thesis, book, and presentations but I’ll finish with some recommendations as to what school leaders can do to ensure they are constantly improving their practices around digital literacies:

  • Seek out new people: it’s easy for us to become trapped in what are known as filter bubbles, either through the choices we make as a result of confirmation bias, or algorithmically-curated newsfeeds. Why not find people and organisations who you wouldn’t usually follow, and add them to your daily reading habits?
  • Share what you learn: why not create a regular way to update those in your school community about issues relating to the considered use of technology? This could be a discussion forum, a newsletter pointing to the work of people like the Electronic Frontier Foundation or Common Sense Media, or 'clubs’ that help staff and students get to grips with new technologies.
  • Find other ways: the danger of 'best practices’ or established workflows is that they can make you blind to new, better ways of doing things. As Clay Shirky notes in this interview it can be liberating to jettison existing working practices in favour of new ones. What other ways can you find to write documents, collaborate with others, be creative, and/or keep people informed?

Comments? Questions? I’m @dajbelshaw or you can get in touch with me at: I consult around identifying, developing, and credentialing digital skills.

Categorieën: Mozilla-nl planet

Mozilla Firefox – tipy pro ochranu soukromí - 1.díl - PC

Nieuws verzameld via Google - fr, 20/05/2016 - 10:17


Mozilla Firefox – tipy pro ochranu soukromí - 1.díl
V tomto ohledu vám bez obav můžeme nabídnout prohlížeč Mozilla Firefox, který je šířený pod licencí Open Source a který je tou nejlepší volbou právě v souvislosti s ochranou vašich soukromých dat před zvědavýma očima ostatních. I přesto, že má Mozilla ...

Categorieën: Mozilla-nl planet

La justice refuse à Mozilla les détails sur une faille de Firefox - ZDNet France

Nieuws verzameld via Google - fr, 20/05/2016 - 10:12

Next INpact

La justice refuse à Mozilla les détails sur une faille de Firefox
ZDNet France
Mozilla avait déposé un recours dans une affaire opposant le FBI à un réseau de trafic d'images pédopornographiques sur Tor. L'éditeur de Firefox soupçonne les autorités d'avoir réuni ses preuves en exploitant une faille au sein du navigateur.
Tor : un juge refuse à Mozilla les détails d'une éventuelle faille de FirefoxNext INpact
Le FBI refuse de communiquer sur une faille touchant Tor et Firefox, la justice lui ...Le Journal du Geek
Le FBI refuse de communiquer sur une faille affectant Tor Browser et FirefoxClubic

alle 4 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Tor : un juge refuse à Mozilla les détails d'une éventuelle faille de Firefox - Next INpact

Nieuws verzameld via Google - fr, 20/05/2016 - 08:30

Next INpact

Tor : un juge refuse à Mozilla les détails d'une éventuelle faille de Firefox
Next INpact
Un juge américain vient de débouter Mozilla dans sa demande d'intervention dans un procès pour pédopornographie. L'éditeur aimerait connaître les détails d'une possible faille de sécurité utilisée pour traquer des utilisateurs du réseau Tor. Il ne ...
Le FBI refuse de communiquer sur une faille touchant Tor et Firefox, la justice lui ...Le Journal du Geek
Le FBI refuse de communiquer sur une faille affectant Tor Browser et FirefoxClubic

alle 3 nieuwsartikelen »
Categorieën: Mozilla-nl planet