Mozilla Nederland LogoDe Nederlandse
Mozilla gemeenschap

Mozilla Improves Malware Blocking in Firefox 31 - Threatpost

Nieuws verzameld via Google - do, 24/07/2014 - 20:26

Mozilla Improves Malware Blocking in Firefox 31
Browser vendors have been adding defenses to mitigate this threat for some time, and the newest version of Mozilla Firefox includes an improved defense against malware downloaded through the browser, which could prevent many kinds of infections.

Google Nieuws
Categorieën: Mozilla-nl planet

Firefox for Android Beta Makes it Even Easier to Customize Your Web Experience

Mozilla Futurereleases - do, 24/07/2014 - 20:19

Firefox for Android Beta introduces a powerful set of customization features for users and APIs for developers. These new features are unique to Firefox for Android Beta and offer users more personalization options and even greater control over their Web experience.

More Customization Options

Users can customize their home screen pages to see the Web content they want from a variety of websites, feeds and services. Just some of the websites, feeds and services that Mozilla has been experimenting with include Instagram, Pocket, Vimeo and Wikipedia. Users can now experience these in Firefox for Android Beta.

Instagram Home Screen

Instagram home screen page in Firefox for Android Beta

Users can pick and choose which home screen page appears as the default, re-order pages, hide unwanted pages or hide all pages for a completely clean new tab experience.

Users can now install new home screen pages for testing the same way all add-ons are installed from the settings menu under tools/add-ons. The pages can also be installed from the home screen panels collection on the Mozilla add-ons website.

A New Class of Add-Ons

This new set of APIs transforms and extends the potential of home screen pages, giving add-on developers the tools they need to build a whole new class of add-ons into the Firefox for Android Beta user experience. Add-on developers can use these APIs to create their own home screen pages, giving them a dedicated space where they can entice users to interact with their add-ons.

Easily Switch Between Languages

We added a feature to Firefox for Android Beta that enables users to easily switch between languages without restarting the browser. The feature allows us to offer 54 language options in Firefox for Android Beta, which a user can switch between regardless of the locales supported by their Android device. We created this feature in direct response to user demand, working alongside our passionate community of volunteer localization contributors to deliver it.

Help us test this new home screen experience and our new language switching feature from today. Please remember to share your feedback and file any bugs as we continue to improve performance and features for our users.

More information:

Categorieën: Mozilla-nl planet

Marco Bonardo: Unified Complete coming to Firefox 34

Mozilla planet - do, 24/07/2014 - 18:23

The awesomebar in Firefox Desktop has been so far driven by two autocomplete searches implemented by the Places component:

  1. history: managing switch-to-tab, adaptive and browsing history, bookmarks, keywords and tags
  2. urlinline: managing autoFill results

Moving on, we plan to improve the awesomebar contents making them even more awesome and personal, but the current architecture complicates things.

Some of the possible improvements suggested include:

  • Better identify searches among the results
  • Allow the user to easily find favorite search engine
  • Always show the action performed by Enter/Go
  • Separate searches from history
  • Improve the styling to make each part more distinguishable

When working on these changes we don't want to spend time fighting with outdated architecture choices:

  • Having concurrent searches makes hard to insert new entries and ensure the order is appropriate
  • Having the first popup entry disagree with the autoFill entry makes hard to guess the expected action
  • There's quite some duplicate code and logic
  • All of this code predates nice stuff like Sqlite.jsm, Task.jsm, Preferences.js
  • The existing code is scary to work with and sometimes obscure

Due to these reasons, we decided to merge the existing components into a single new component called UnifiedComplete (toolkit/components/places/UnifiedComplete.js), that will take care of both autoFill and popup results. While the component has been rewritten from scratch, we were able to re-use most of the old logic that was well tested and appreciated. We were also able to retain all of the unit tests, that have been also rewritten, making them use a single harness (you can find them in toolkit/components/places/tests/unifiedcomplete/).

So, the actual question is: which differences should I expect from this change?

  • The autoFill result will now always cope with the first popup entry. Though note the behavior didn't change, we will still autoFill up to the first '/'. This means a new popup entry is inserted as the top match.
  • All initialization is now asynchronous, so the UI should not lag anymore at the first awesomebar search
  • The searches are serialized differently, responsiveness timing may differ, usually improve
  • Installed search engines will be suggested along with other matches to improve their discoverability

The component is currently disabled, but I will shortly push a patch to flip the pref that enables it. The preference to control whether to use new or old components is browser.urlbar.unifiedcomplete, you can already set it to true into your current Nightly build to enable it.

This also means old components will shortly be deprecated and won't be maintained anymore. That won't happen until we are completely satisfied with the new component, but you should start looking at the new one if you use autocomplete in your project. Regardless we'll add console warnings at least 2 versions before complete removal.

If you notice anything wrong with the new awesomebar behavior please file a bug in Toolkit/Places and make it block Bug UnifiedComplete so we are notified of it and can improve the handling before we reach the first Release.

Categorieën: Mozilla-nl planet

Christian Heilmann: [Video]: The web is dead? – My talk at TEDx Thessaloniki

Mozilla planet - do, 24/07/2014 - 18:18

Today the good folks at TEDx Thessaloniki released the recording of my talk “The web is dead“.

Christian Heilmann at TEDx

I’ve given you the slides and notes earlier here on this blog but here’s another recap of what I talked about:

  • The excitement for the web is waning – instead apps are the cool thing
  • At first glance, the reason for this is that apps deliver much better on a mobile form factor and have a better, high fidelity interaction patterns
  • If you scratch the surface of this message though you find a few disturbing points:
    • Everything in apps is a number game – the marketplaces with the most apps win, the apps with the most users are the ones that will get more users as those are the most promoted ones
    • The form factor of an app was not really a technical necessity. Instead it makes software and services a consumable. The full control of the interface and the content of the app lies with the app provider, not the users. On the web you can change the display of content to your needs, you can even translate and have content spoken out for you. In apps, you get what the provider allows you to get
    • The web allowed anyone to be a creator. The curb to mount from reader to writer was incredibly low. In the apps world, it becomes much harder to become a creator of functionality.
    • Content creation is easy in apps. If you create the content the app makers wants you to. The question is who the owner of that content is, who is allowed to use it and if you have the right to stop app providers from analysing and re-using your content in ways you don’t want them to. Likes and upvotes/downvotes aren’t really content creation. They are easy to do, don’t mean much but make sure the app creator has traffic and interaction on their app – something that VCs like to see.
    • Apps are just another form factor to control software for the benefit of the publisher. Much like movies on DVDs are great, because when you scratch them you need to buy a new one, publishers can now make software services become outdated, broken and change, forcing you to buy a new one instead of enjoying new features cropping up automatically.
    • Apps lack the data interoperability of the web. If you want your app to succeed, you need to keep the users locked into yours and not go off and look at others. That way most apps are created to be highly addictive with constant stimulation and calls to action to do more with them. In essence, the business models of apps these days force developers to create needy, bullying tamagotchi and call them innovation

Categorieën: Mozilla-nl planet

Mozilla leaders announce funding for gig-related projects -

Nieuws verzameld via Google - do, 24/07/2014 - 16:27

Mozilla leaders announce funding for gig-related projects
Mozilla announced yesterday six Chattanooga projects that will get money from the Gigabit Community Fund to build and pilot gigabit-enabled applications and curricula. "The Gigabit Fund is turning Chattanooga into a living laboratory in which to ...
Mozilla Gigabit Fund picks six more Chattanooga projects for pilot fundingChattanooga Times Free Press

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

Mozilla changes Private Browsing Clipboard handling in Firefox 33 - Ghacks Technology News

Nieuws verzameld via Google - do, 24/07/2014 - 14:03

Ghacks Technology News

Mozilla changes Private Browsing Clipboard handling in Firefox 33
Ghacks Technology News
If you copy data from a private browsing window to the clipboard and close the private browsing window afterwards, you will notice that the data is not there anymore. Firefox empties the clipboard whenever you exit private browsing mode. You can test ...

Google Nieuws
Categorieën: Mozilla-nl planet

Mozilla chystá konkurenta Chromecastu postaveného na Firefox OS -

Nieuws verzameld via Google - do, 24/07/2014 - 11:15

Mozilla chystá konkurenta Chromecastu postaveného na Firefox OS
Šeptanda běží několik měsíců, ale zatím šlo jen o nepotvrzené dohady. Mozilla však potvrdila, že připravuje konkurenta zařízení Chromecast, který by ale měl běžet na otevřené platformě Firefox OS: Mozilla se společností Panasonic připravuje novou ...
Nový Firefox se snaží zatočit s
Firefox 31: novinky hlavně pro vývojářeLinuxEXPRES

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

Mozilla Gigabit Fund picks six more Chattanooga projects for pilot funding - Chattanooga Times Free Press

Nieuws verzameld via Google - do, 24/07/2014 - 06:13

Chattanooga Times Free Press

Mozilla Gigabit Fund picks six more Chattanooga projects for pilot funding
Chattanooga Times Free Press
Mozilla, backed by the National Science Foundation, announced today that 10 projects in Kansas City and Chattanooga will receive grants from $5,000 to $30,000 each to build and pilot gigabit-enabled applications and associated curricula in the two ...

en meer »
Categorieën: Mozilla-nl planet

Mozilla patches security bugs in Firefox - Register

Nieuws verzameld via Google - do, 24/07/2014 - 06:03

International Business Times UK

Mozilla patches security bugs in Firefox
From the advisory: “Mozilla community member James Kitchener reported a crash in DirectWrite when rendering MathML content with specific fonts due to an error in how font resources and tables are handled. This leads to use-after-free of a DirectWrite ...
Mozilla Firefox 31 Now Officially Available for Download: What's New?International Business Times UK
Mozilla's Asm.js Technology Makes Its Commercial Debut With Dungeon ...TechCrunch
Mozilla ships Firefox 31, adds search to new tab pageComputerworld Australia
GMA News
alle 25 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Monica Chew: Download files more safely with Firefox 31

Mozilla planet - do, 24/07/2014 - 02:54

Did you know that the estimated cost of malware is hundreds of billions of dollars per year? Even without data loss or identity theft, the time and annoyance spent dealing with infected machines is a significant cost.

Firefox 31 offers improved malware detection. Firefox has integrated Google’s Safe Browsing API for detecting phishing and malware sites since Firefox 2. In 2012 Google expanded their malware detection to include downloaded files and made it available to other browsers. I am happy to report that improved malware detection has landed in Firefox 31, and will have expanded coverage in Firefox 32.

In preliminary testing, this feature cuts the amount of undetected malware by half. That’s a significant user benefit.
What happens when you download malware? Firefox checks URLs associated with the download against a local Safe Browsing blocklist. If the binary is signed, Firefox checks the verified signature against a local allowlist of known good publishers. If no match is found, Firefox 32 and later queries the Safe Browsing service with download metadata (NB: this happens only on Windows, because signature verification APIs to suppress remote lookups are only available on Windows). In case malware is detected, the Download Manager will block access to the downloaded file and remove it from disk, displaying an error in the Downloads Panel below.

How can I turn this feature off? This feature respects the existing Safe Browsing preference for malware detection, so if you’ve already turned that off, there’s nothing further to do. Below is a screenshot of the new, beautiful in-content preferences (Preferences > Security) with all Safe Browsing integration turned off. I strongly recommend against turning off malware detection, but if you decide to do so, keep in mind that phishing detection also relies on Safe Browsing.
Many thanks to Gian-Carlo Pascutto and Paolo Amadini for reviews, and the Google Safe Browsing team for helping keep Firefox users safe and secure!
Categorieën: Mozilla-nl planet

Erik Vold: Mozilla University

Mozilla planet - do, 24/07/2014 - 02:00

When I was young I only cared about Math, math and math, but saw no support, no interesting future, no jobs (that I cared for), nor any respect for the field. In my last year of high school I started thinking about my future, so I sought out advice and suggestions from the adults that I respected. The only piece of advice that I cared for was from my father, he simply suggested that I start with statistics because there are good jobs available for a person with those skills and if I didn’t like it I would find something else. I had taken an intro class to statistics and it was pretty easy, so I decided to give it a try.

Statistics was easy, and boring, so I tried computer science because I had been making web sites for people on the side, off and on, since I was 16, and it was interesting, especially since the best application of statistics to my mind is computer learning. I enjoyed the comp sci classes most of all, and I took 5 years to get my bachelor’s degree in statistics and computer science. It was a great experience for me.

Slightly before I graduated I started working full time as a web developer, after a couple of years I started tinkering with creating add-ons, because I was spending 8+ hours a day using Firefox and I figured I could make it suite my needs a little more, and maybe others would enjoy my hacks too, so I started making userscripts, ubiquity commands, jetpacks, and add-ons.

It’s been 5 years now since I started hacking on projects in the Mozilla community, and these last five years have been just as valuable to me as the 5 years that I spent at UBC. I consider this to be my 2nd degree.

Now when I think about how to grow the community, how to educate the masses, how to reward people for their awesome contributions, I can think of no better way than a free Mozilla University.

We have webmaker today, and I thought it was interesting at first, so I contributed to the best of ability for the first 2 years, but I see some fundamental issues with it. For instance, how do we measure the success of webmaker? how do we know that we’ve affected people? how do we know whether or not these people have decided to continue their education or not? and if they decide to continue their webmaker education then how do we help them? finally, do we respect the skills we teach if do we not provide credentials?

I, for one, would like to see Open Badges and Webmaker become Mozilla University, a free, open source, peer-to-peer, distributed, and widely respected place to learn.

I feel that one of the most important parts of my job at Mozilla is to teach, but how many of us are really doing this? Mozilla University could also be a way to measure our progress.

Categorieën: Mozilla-nl planet

FossaMail Is A 64-Bit Optimised Thunderbird Clone For Windows - Lifehacker Australia

Nieuws verzameld via Google - do, 24/07/2014 - 01:00

FossaMail Is A 64-Bit Optimised Thunderbird Clone For Windows
Lifehacker Australia
Windows: Mozilla's Thunderbird is a solid email client, but it still doesn't support 64-bit processors. FossaMail is a free clone optimised for 64-bit systems, all while supporting the same extensions. FossaMail is made by the developers behind Pale ...
FossaMail is a 64-bit Optimized, Faster Thunderbird Clone for WindowsLifehacker

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

Nick Cameron: LibHoare - pre- and postconditions in Rust

Mozilla planet - wo, 23/07/2014 - 23:13
I wrote a small macro library for writing pre- and postconditions (design by contract style) in Rust. It is called LibHoare (named after the logic and in turn Tony Hoare) and is here (along with installation instructions). It should be easy to use in your Rust programs, especially if you use Cargo. If it isn't, please let me know by filing issues on GitHub.

The syntax is straightforward, you add `[#precond="predicate"]` annotations before a function where `predicate` is any Rust expression which will evaluate to a bool. You can use any variables which would be in scope where the function is defined and any arguments to the function. Preconditions are checked dynamically before a function is executed on every call to that function.

You can also write `[#postcond="predicate"]` which is checked on leaving a function and `[#invariant="predicate"]` which is checked before and after. You can write any combination of annotations too. In postconditions you can use the special variable `result` (soon to be renamed to `return`) to access the value returned by the function.

There are also `debug_*` versions of each annotation which are not checked in --ndebug builds.

The biggest limitation at the moment is that you can only write conditions on functions, not methods (even static ones). This is due to a restriction on where any annotation can be placed in the Rust compiler. That should be resolved at some point and then LibHoare should be pretty easy to update.

If you have ideas for improvement, please let me know! Contributions are very welcome.

# Implementation

The implementation of these syntax extensions is fairly simple. Where the old function used to be, we create a new function with the same signature and an empty body. Then we declare the old function inside the new function and call it with all the arguments (generating the list of arguments is the only interesting bit here because arguments in Rust can be arbitrary patterns). We then return the result of that function call as the result of the outer function. Preconditions are just an `assert!` inserted before calling the inner function and postconditions are an `assert!` inserted after the function call and before returning.
Categorieën: Mozilla-nl planet

Mozilla Gigabit Fund picks six more Chattanooga projects for pilot funding - Chattanooga Times Free Press

Nieuws verzameld via Google - wo, 23/07/2014 - 22:51

Chattanooga Times Free Press

Mozilla Gigabit Fund picks six more Chattanooga projects for pilot funding
Chattanooga Times Free Press
Mozilla, backed by the National Science Foundation, announced today that 10 projects in Kansas City and Chattanooga will receive grants from $5,000 to $30,000 each to build and pilot gigabit-enabled applications and associated curricula in the two ...

en meer »
Categorieën: Mozilla-nl planet

Mozilla Gigabit Fund picks six more Chattanooga projects for pilot funding - Chattanooga Times Free Press

Nieuws verzameld via Google - wo, 23/07/2014 - 22:51

Chattanooga Times Free Press

Mozilla Gigabit Fund picks six more Chattanooga projects for pilot funding
Chattanooga Times Free Press
Mozilla, backed by the National Science Foundation, announced today that 10 projects in Kansas City and Chattanooga will receive grants from $5,000 to $30,000 each to build and pilot gigabit-enabled applications and associated curricula in the two ...

en meer »
Categorieën: Mozilla-nl planet

Andrew Overholt: We held a Mozilla “bootcamp”. You won’t believe how it went!

Mozilla planet - wo, 23/07/2014 - 22:33

For a while now a number of Mozillians have been discussing the need for some sort of technical training on Gecko and other Mozilla codebases. A few months ago, Vlad and I and a few others came up with a plan to try out a “bootcamp”-like event. We initially thought we’d have non-core developers learn from more senior developers for 4 days and had a few goals:

  • teach people not developing Mozilla code daily about the development process
  • expose Mozillians to areas with which they’re not familiar
  • foster shared ownership of areas of code and tools
  • teach people where to look in the code when they encounter a bug and to more accurately file a bug (“teach someone how to fish”)

While working towards this we realized that there isn’t as much shared ownership as there could be within Mozilla codebases so we focused on 2 engineering teams teaching other engineers. The JavaScript and Graphics teams agreed to be mentors and we solicited participants from a few paid Mozillians to try this out. We intentionally limited the audience and hand-picked them for this first “beta” since we had no idea how it would go.

The event took place over 4 days in Toronto in early June. We ended up with 5 or 6 mentors (the Graphics team having a strong employee presence in Toronto helped with pulling in experts here and there) and 9 attendees from a variety of engineering teams (Firefox OS, Desktop, and Platform).

The week’s schedule was fairly loose to accommodate questions and make it more of a conversational atmosphere. We planned sessions in an order to give a high level overview followed by deeper dives. We also made sessions about complementary Gecko components happen in a logical order (ex. layout then graphics). You can see details about the schedule we settled upon here:

We collaboratively took notes and recorded everything on video. We’re still in the process of creating usable short videos out of the raw feeds we recorded. Text notes were captured on this etherpad which had some real-time clarifications made by people not physically present (Ms2ger and others) which was great.

The week taught us a few things, some obvious, some not so obvious:

  • people really want time for learning. This was noted more than once and positive comments I received made me realize it could have been held in the rain and people would have been happy
  • having a few days set aside for professional development was very much appreciated so paid Mozillians incorporating this into their goals should be encouraged
  • people really want the opportunity to learn from and ask questions of more seasoned Mozilla hackers
  • hosting this in a MozSpace ensured reliable facilities, flexibility in terms of space, and the availability of others to give ad hoc talks and answer questions when necessary. It also allowed others who weren’t official attendees to listen in for a session or two. Having it in the office also let us use the existing video recording setup and let us lean on the ever-amazing Jonathan Lin for audio and video help. I think you could do this outside a MozSpace but you’d need to plan a bit more for A/V and wifi, etc.
  • background noise (HVAC, server fans, etc.) is very frustrating for conversations and audio recording (but we already knew this)
  • this type of event is unsuitable for brand new {employees|contributors} since it’s way too much information. It would be more applicable after someone’s been involved for a while (6 months, 1 year?).

In terms of lessons for the future, a few things come to mind:

  • interactive exercises were very well received (thanks, kats!) and cemented people’s learning as expected
  • we should perhaps define homework to be done in advance and strongly encourage completion of it; videos of previous talks may be good material
  • scheduling around 2 months in advance seemed to be best to balance “I have no idea what I’ll be doing then” and “I’m already busy that week”
  • keeping the ratio of attendees to “instructors” to around 2 or 3 to 1 worked well for interactivity and ensuring the right people were present who could answer questions
  • although very difficult, attempting to schedule around major deadlines is useful (this week didn’t work for a few of the Firefox OS teams)
  • having people wear lapel microphones instead of a hand-held one makes for much better and more natural audio
  • building a schedule, mentors, and attendee list based on common topics of interest would be an interesting experiment instead of the somewhat mixed bag of topics we had this time
  • using whiteboards and live coding/demos instead of “slides” worked very well

Vlad and I think we should do this again. He proposed chaining organizers so each organizer sets one up and helps the next person do it. Are you interested in being the next organizer?

I’m very interested in hearing other people’s thoughts about this so if you have any, leave a comment or email me or find me on IRC or send me a postcard c/o the Toronto office (that would be awesome).

Categorieën: Mozilla-nl planet

Swarnava Sengupta: Flashing Flame Devices with Firefox OS

Mozilla planet - wo, 23/07/2014 - 19:52
If you have a Flame reference device and wanna try out alternate versions of Firefox OS apart from the stock one, but not willing to build from source, then follow this mini-manual.
Get the buildYou can download the packages from the Nightly Build directories of Mozilla FTP. You specifically need the following two files:
  • (XX is the version number)

    Set up environmentOnce you have the build, decompress both of them in the same directory. Download the file from this gist and put it into the same directory as well.
    N.B: You will have to set executable bit to the script file ($ chmod a+x
    Flashing the device
    1. Enable remote debugging in Device's Developer Settings
    2. Connect the device to the system over USB
    3. You will need to have have ADB installed 3.1. Run $ adb devices3.2. Check for Flame in the listed devices 3.3. If device is listed, proceed to step 4 (if not, troubleshoot)
    4. Run the script to initiate flashing $ ./
    5. Follow the instructions to customize your flashing as per your need.
    6. If you face issues, try flashing with /data partition formatted when asked.
    7. Profit!
    UpdatesAfter you're done flashing, your device will be on the Nightly channel, receiving updates almost each day. Those updates will be over the air (OTA) download of ~60MB, and completely hassle free.

    Credit: Thanks to Deb. :)
    Categorieën: Mozilla-nl planet

    Mozilla Release Management Team: Auto-comment on the Release Management flags

    Mozilla planet - wo, 23/07/2014 - 17:46

    Implemented in bug 853108 by the bmo team, using the tracking flags will automatically updated the comment field with some templates. The goal is to reduce back and forth in Bugzilla on bug tracking. We also hope that is going to improve our response time.

    For example, for the tracking requests (tracking-firefoxNN, tracking-firefox-esrNN or blocking-b2g), the user will see the text added into the Bugzilla comment field:

    [Tracking Requested - why for this release]:

    With this change, we hope to simplify the decision process for the release team.

    For the relnotes-* flags:

    Release Note Request (optional, but appreciated) [Why is this notable]: [Suggested wording]: [Links (documentation, blog post, etc)]:

    This change aims to simplify the process of release notes writing. In some cases, it can be hard for release manager to translate a bug into a new feature description.

    Flags on which this option is enabled are:

    • relnote-firefox
    • relnote-b2g
    • tracking-firefoxNN
    • tracking-firefox-esrNN
    • blocking-b2g

    Finally, we reported bug 1041964 to discuss about a potential auto-focus on the comment area.

    Categorieën: Mozilla-nl planet

    Doug Belshaw: Making the web simple, but not simplistic

    Mozilla planet - wo, 23/07/2014 - 16:49

    A couple of months ago, an experimental feature Google introduced in the ‘Canary’ build of its Chrome browser prompted a flurry of posts in the tech press. The change was to go one step further than displaying an ‘origin chip’ and do away with the URL entirely:

    Hidden URL

    I have to admit that when I first heard of this I was horrified – I assumed it was being done for the worst of reasons (i.e. driving more traffic to Google search). However, on reflection, I think it’s a nice example of progressive complexity. Clicking on the root name of the site reveals the URL. Otherwise, typing in the omnibox allows you to search the web:

    Google Chrome experiment

    Progressive complexity is something we should aspire to when designing tools for a wide range of users. It’s demonstrated well by my former Mozilla colleague Rob Hawkes in his work on ViziCities:


    Using this approach means that those that are used to manipulating URLs are catered for – but the process is simplified for novice users.

    Something we forget is that URLs often depend on the file structures of web servers: There’s no particular reason why this should be the case.

    iCloud and Pages on OS X Pages on Mac OS X saving to iCloud

    google-drive.png Google Drive interface

    It’s worth noting that both Apple and Google here don’t presuppose you will create folders to organise your documents and digital artefacts. You can do so, or add tags, but it’s just as easy to dump them all in one place and search efficiently. It’s human-centred design.

    My guiding principle here from a web literacy point of view is whether simplification and progressive complexity is communicated to users. Is it clear that there’s more to this than what’s presented on the surface? With the examples I’ve given in this post, I feel that they are.

    Questions? Comments? I’m @dajbelshaw or you can email me at

    Categorieën: Mozilla-nl planet