<commit_before><?php
require_once("lib/init.php");
require_once("lib/lang.php");
include("header.php");
?>

<h2>Collecting Feedback on Browser-Updates</h2>
<small>October 19th, 2016</small>
<div class="entry">
    <p>
        We implemented a small <a href="/en/update-browser.html">feedback form on the browser update page</a> 
        where people can report why they can't or don't want to update.
        We are collecting now some data and already got some valuable feedback. 
        With this we can improve our notification and the selection of browsers we offer.
    </p>
    <img src="/img/blog/feedback.png"/>
    <p>
        For now this only on the english language version of the browser update page.
    </p>
</div>
<div class="com"><a href="blog-entry.html?n=feedback" onclick="SC('feedback'); return false;">Comments</a></div>


<h2>Improved notification and more options</h2>
<small>September 6th, 2016</small>
<div class="entry">
    <p>
    We now check for more browsers if they are up-to-date: Yandex Browser, Pale Moon Browser, and Vivaldi Browser. 
    </p>
    <p>
    The detection script was slimmed down more and we improved detection of Microsoft Edge.
    </p>
    <p>
        When creating your update-notification code for your site you have now a few new options:<commit_msg>blog post on shrinked script size<commit_after><?php
require_once("lib/init.php");
require_once("lib/lang.php");
include("header.php");
?>

<h2>Shrinked script size: now only 2 kB</h2>
<small>January 4th, 2017</small>
<div class="entry">
    <p>
        We've split the oudated browser detection script into two parts: 1) the detection if the browser is outdated and 2) the showing of the message to users with outdated browser.
    </p>
    <p>
        The detection part is what you embed into your site (<code>update.js</code>). This is what all users will have to download. And this is is now only 2.2 kB in size gzipped, five times smaller than before
        (>10kB).
        Then, if the browser is outdated and needs to be notified, the message file (<code>update.show.js</code>) will be loaded, but this will only happen for about 1% of the users.
    </p>
</div>
<div class="com"><a href="blog-entry.html?n=shrinked" onclick="SC('shrinked'); return false;">Comments</a></div>

<h2>Collecting Feedback on Browser-Updates</h2>
<small>October 19th, 2016</small>
<div class="entry">
    <p>
        We implemented a small <a href="/en/update-browser.html">feedback form on the browser update page</a> 
        where people can report why they can't or don't want to update.
        We are collecting now some data and already got some valuable feedback. 
        With this we can improve our notification and the selection of browsers we offer.
    </p>
    <img src="/img/blog/feedback.png"/>
    <p>
        For now this only on the english language version of the browser update page.
    </p>
</div>
<div class="com"><a href="blog-entry.html?n=feedback" onclick="SC('feedback'); return false;">Comments</a></div>


<h2>Improved notification and more options</h2>
<small>September 6th, 2016</small>
<div class="entry">
    <p>
    We now check for more browsers if they are up-to-date: Yandex Browser, Pale Moon Browser, and Vivaldi Browser. 
    </p>
    <p>
    The detection script was slimmed down more and we improved detection of Microsoft Edge.
    </p>
    <p>
        When creating your update-notification code for your site you have now a few new options:
{'fraction_non_alphanumeric': 0.11369509043927649, 'fraction_numerical': 0.012919896640826873, 'mean_word_length': 3.4781491002570695, 'pattern_counts': {'":': 0, '<': 77, '<?xml version=': 0, '>': 78, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '429000', 'n_tokens_mistral': 1102, 'n_tokens_neox': 1007, 'n_words': 427}