mozilla

Mozilla Nederland LogoDe Nederlandse
Mozilla gemeenschap

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
Register
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: https://etherpad.mozilla.org/bootcamp1plans.

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:
  • b2g-XX.0a1.en-US.android-arm.tar.gz (XX is the version number)
  • gaia.zip

    Set up environmentOnce you have the build, decompress both of them in the same directory. Download the flash.sh 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 flash.sh).
    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 $ ./flash.sh
    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. :) https://gist.github.com/debloper/e7d194ddb7c1011bbeda
    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:

    progressive-complexity.png http://slidesha.re/1kbYyYU

    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: http://server.com/directory/sub-directory/file.htm. 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 doug@mozillafoundation.org.

    Categorieën: Mozilla-nl planet

    Pete Moore: Weekly review 2014-07-23

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

    Highlights

    This week I rolled out the l10n changes, after a few more iterations of tweaks / improvements / nice-to-haves. I am coordinating with Hal about when we can cut over from legacy (as this will need his involvement) which depends a little bit on his availability - he has already proactively contacted me to let me know he is quite tied up at the moment, so it is unlikely we’ll be able to engage in roll out work together for the next couple of weeks until hg issues have stablised, and he has completed some work with fubar/bkero and the interns.

    I’ve had discussions with Aki about various vcs sync matters (both technical and business relationship-wise) and am confident I am in a good position to lead this going forward.

    I also rolled out changes to the email notifications, which unfortunately I had to roll back.

    Now l10n is done (apart from cutover) the last two parts are gecko.git and gecko-projects - which I anticipate as being relatively trouble-free.

    After that comes git-hg and git-git support (currently new vcs sync only supports hg-git).

    Other

    Looking forward to getting involved with release process (https://bugzilla.mozilla.org/show_bug.cgi?id=1042128)

    Categorieën: Mozilla-nl planet

    Mozilla Firefox 31 Now Officially Available for Download: What's New? - International Business Times UK

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

    International Business Times UK

    Mozilla Firefox 31 Now Officially Available for Download: What's New?
    International Business Times UK
    Another major enhancement in Mozilla's latest web browser is the 'Malware detection and Block' mechanism, which is implemented by default whenever users download files. However, users can also choose to turn-off the in-browser safety mechanism.
    Mozilla's Asm.js Technology Makes Its Commercial Debut With Dungeon ...TechCrunch
    Mozilla Firefox gets better search bar, dev toolsGMA News
    Browser-based gaming gets a push with Mozilla's plugin-free technologyLiliputing
    BetaNews -Naked Security
    alle 19 nieuwsartikelen »
    Categorieën: Mozilla-nl planet

    Dave Hunt: A new home for the gaiatest documentation

    Mozilla planet - wo, 23/07/2014 - 14:56

    The gaiatest python package provides a test framework and runner for testing Gaia (the user interface for Firefox OS). It also provides a handy command line tool and can be used as a dependency from other packages that need to interact with Firefox OS.

    Documentation for this package has now been moved to gaiatest.readthedocs.org, which is generated directly from the source code whenever there’s an update. In order to make this more useful we will continue to add documentation to the Python source code. If you’re interested in helping us out please get in touch by leaving a comment, or joining #ateam on irc.mozilla.org and letting us know.

    Categorieën: Mozilla-nl planet

    FossaMail is a 64-bit Optimized, Faster Thunderbird Clone for Windows - Lifehacker

    Nieuws verzameld via Google - wo, 23/07/2014 - 13:35

    FossaMail is a 64-bit Optimized, Faster Thunderbird Clone for Windows
    Lifehacker
    Windows: Mozilla's Thunderbird is a solid email client, but it can be a bit sluggish and it still doesn't support 64-bit processors. FossaMail is a freely downloadable clone optimized for 64-bit systems, all while supporting the same extensions ...

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

    FossaMail is a 64-bit Optimized, Faster Thunderbird Clone for Windows - Lifehacker

    Nieuws verzameld via Google - wo, 23/07/2014 - 13:35

    FossaMail is a 64-bit Optimized, Faster Thunderbird Clone for Windows
    Lifehacker
    Windows: Mozilla's Thunderbird is a solid email client, but it can be a bit sluggish and it still doesn't support 64-bit processors. FossaMail is a freely downloadable clone optimized for 64-bit systems, all while supporting the same extensions ...

    en meer »
    Categorieën: Mozilla-nl planet

    Francesca Ciceri: Adventures in Mozillaland #3

    Mozilla planet - wo, 23/07/2014 - 13:04

    Yet another update from my internship at Mozilla, as part of the OPW.

    A brief one, this time, sorry.

    Bugs, Bugs, Bugs, Bacon and Bugs

    I've continued with my triaging/verifying work and I feel now pretty confident when working on a bug.
    On the other hand, I think I've learned more or less what was to be learned here, so I must think (and ask my mentor) where to go from now on.
    Maybe focus on a specific Component?
    Or steadily work on a specific channel for both triaging/poking and verifying?
    Or try my hand at patches?
    Not sure, yet.

    Also, I'd like to point out that, while working on bug triaging, the developer's answers on the bug report are really important.
    Comments like this help me as a triager to learn something new, and be a better triager for that component.
    I do realize that developers cannot always take the time to put in comments basic information on how to better debug their component/product, but trust me: this will make you happy on the long run.
    A wiki page with basic information on how debug problems for your component is also a good idea, as long as that page is easy to find ;).

    So, big shout-out for MattN for a very useful comment!

    Community

    After much delaying, we finally managed to pick a date for the Bug Triage Workshop: it will be on July 25th. The workshop will be an online session focused on what is triaging, why is important, how to reproduce bugs and what information ask to the reporter to make a bug report the most complete and useful possible.
    We will do it in two different time slots, to accomodate various timezones, and it will be held on #testday on irc.mozilla.org.
    Take a look at the official announcement and subscribe on the event's etherpad!

    See you on Friday! :)

    Categorieën: Mozilla-nl planet

    Gervase Markham: Fraudulent Passport Price List

    Mozilla planet - wo, 23/07/2014 - 12:24

    This is a list (URL acquired from spam) of prices for fraudulent (but perhaps “genuine” in terms of the materials used, I don’t know) passports, driving licenses and ID cards. It is a fascinating insight into the relative security of the identification systems of a number of countries. Of course, the prices may also factor in the economic value of the passport, but it’s interesting that a Canadian passport is more expensive than a US one. That probably reflects difficulty of obtaining the passport rather than the greater desirability of Canada over the US. (Sorry, Canadians, I know you’d disagree! Still, you can be happy at the competence and lack of corruption in your passport service.)

    One interesting thing to note is that one of the joint lowest-price countries, Latvia (€900), is a member of the EU. A Latvian passport allows you to live and work in any EU country, even Germany, which has the most expensive passports (€5200). The right to live anywhere in the EU – yours for only €900…

    Also interesting is to sort by passport price and look if the other prices follow the same curve. A discrepancy may indicate particularly weak or strong security. So Russian ID cards are cheaper than one might expect, whereas Belgian ones are more expensive. Austrian and Belgian driver’s licenses also seem to be particularly hard to forge, but the prize there goes to the UK, which has the top-priced spot (€2000). I wonder if that’s related to the fact that the UK doesn’t have ID cards, so the driver’s license often functions as one?

    Here is the data in spreadsheet form (ODS), so you can sort and analyse, and just in case the original page disappears…

    Categorieën: Mozilla-nl planet

    Sylvestre Ledru: Auto-comment on the Release Management flags

    Mozilla planet - wo, 23/07/2014 - 12:03

    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.

    Original post blogged on b2evolution.

    Categorieën: Mozilla-nl planet

    Mozilla Firefox gets better search bar, dev tools - GMA News

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

    VentureBeat

    Mozilla Firefox gets better search bar, dev tools
    GMA News
    Mozilla has rolled out a new version of Firefox, giving it the ability to natively handle certain types of files and adding a search field on the New Tab page. Firefox Version 31 has variants for desktop and mobile platforms, including Microsoft's ...
    New Firefox 31 focuses on improving developer toolsVentureBeat

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

    Pagina's