The figures remained constant across education levels, gender, and political affiliation.

Image by Center for the Governance of Change

Even if the AI would become completely inoperative it still would be an improvement over Axel Voss. Download the complete report here. This is a local backup of the report originally published here.

Due to protests against the reformation of the European copyright law known as Article 11 and Article 13, the German version of Wikipedia ist censored for today and therefore unusable.

For now Switzerland is neither affected by that law, nor is it responsible for the bullshit happening in the EU, but still we see Wikipedia censored – at least the German version.

In order to remove censorship install the Stylus browser add-on (see below for links) and import this script afterwards:

@-moz-document domain("") {
html #p-logo a {
    filter: none !important;    

body {
    display: block !important;
 	background-color: #f6f6f6;

.noscroll {
    position: static !important;
    overflow: unset !important;

.mw-parser-output img {
    opacity: 1 !important;
    filter: brightness(1) saturate(1) !important;
    -webkit-filter: brightness(1) saturate(1) !important;
    -moz-filter:brightness(1) saturate(1) !important;
    -ms-filter:brightness(1) saturate(1) !important;
    -o-filter: brightness(1) saturate(1) !important;

#siteNotice {
    display: none !important;

.mw-parser-output .toc, .mw-warning, .toccolours {
	border: 1px solid #a2a9b1 !important;
	background: #f8f9fa !important;

.toc .toctitle,
.toc .toctitle h2,
.mw-parser-output a,
.mw-parser-output div,
.mw-parser-output li,
.mw-parser-output label,
.mw-parser-output caption,
.mw-parser-output code,
.mw-parser-output video,
.mw-parser-output ol,
.mw-parser-output ul,
.mw-parser-output strong {
    background: none !important;
    border: 0 none !important;

.mw-parser-output pre, .mw-code {
	color: #000 !important;
	background: #f8f9fa !important;
	border: 1px solid #eaecf0 !important;

.mw-parser-output a::selection,
.mw-parser-output div::selection,
.mw-parser-output h1::selection,
.mw-parser-output h2::selection,
.mw-parser-output h3::selection,
.mw-parser-output h4::selection,
.mw-parser-output h5::selection,
.mw-parser-output li::selection,
.mw-parser-output label::selection,
.mw-parser-output caption::selection,
.mw-parser-output ul::selection {
    background-color: #0078D7 !important;
    color: #fff !important;

.mw-parser-output a {
    color: #0645ad !important;

.mw-parser-output h1 .mw-parser-output span,
.mw-parser-output h2 .mw-parser-output span,
.mw-parser-output h3 .mw-parser-output span,
.mw-parser-output h4 .mw-parser-output span,
.mw-parser-output h5 .mw-parser-output span,
.mw-parser-output span::selection,
.mw-parser-output p, .mw-parser-output p::selection {
    background: #fff !important;
    border: 0 none !important;

.mw-parser-output h1, .mw-parser-output h1::selection,
.mw-parser-output h2, .mw-parser-output h2::selection,
.mw-parser-output h3, .mw-parser-output h3::selection,
.mw-parser-output h4, .mw-parser-output h4::selection,
.mw-parser-output h5, .mw-parser-output h5::selection {
    background: #fff !important;
    border: 0 none !important;
    border-bottom: 1px solid #000 !important;

.mw-parser-output th, .mw-parser-output th::selection,
.mw-parser-output td, .mw-parser-output td::selection,
.mw-parser-output tr, .mw-parser-output tr::selection {
    color: unset !important;
    background: unset !important;
    border: inherit !important;

.wikitable > tr > th, .wikitable > * > tr > th {
    background: #fff68f !important;

.wikitable > tr > td, .wikitable > * > tr > td {
    border: 1px solid #555 !important;

.wikitable > * > tr > td > table > tbody > tr > th {
    border: none !important;

#hauptseite h2 {
	background: #d8e8ff !important;
	border: 1px solid #8898bf !important;

#hauptseite .inhalt {
	background: #fff !important;
	border: 1px solid #8898bf !important;

.inhalt > div,
.inhalt p {
    border: 0 none !important;
    background: #fff !important;


After importing the script make sure the script is activated. Otherwise it won’t work. I know the script is not perfect. I just checked some articles on Wikipedia and also the main page and they look very well. If you find bugs, feel free to contact me.

Stylus is available for these browsers:

Axel Voss really doesn’t have a clue of what the Internet is and how it works. This is so unbelievably sad. Unfortunately, it doesn’t seem that experience and in-depth knowledge in the field you decide on is a mandatory requirement if you’re a member of the European Parliament.

2019-03-15 @ 10:52: Referrer hell Browsers | PHP | Security

Relying on the HTTP referrer is bad. Everyone knows this, but at least the WordPress developers seem to ignore the fact. Also I never understood, why PHP keeps writing HTTP_REFERER with a single “R” in the middle. The correct term would be HTTP_REFERRER.

Anyway, instead of storing the current URL in $_SESSION[‘HTTP_REFERRER’] as one would normally do, WordPress checks for $_SERVER[‘HTTP_REFERER’] instead.

The PHP documentation is very clear on this to not trust this referrer:

The address of the page (if any) which referred the user agent to the current page. This is set by the user agent. Not all user agents will set this, and some provide the ability to modify HTTP_REFERER as a feature. In short, it cannot really be trusted.

Imagine the following case: you run WordPress from a sub-folder of the root-directory and the referrer is – for whatever reason – set to the web-root of the server, rather than the web-root of your WordPress installation. In fact this is the case on my development machine; I talk about the reason somewhere below.

Now, when you try to delete/recycle a post/page/whatever WordPress checks the referrer in post.php in line 55:

$sendback = wp_get_referer();
if ( ! $sendback ||
	 strpos( $sendback, 'post.php' ) !== false ||
	 strpos( $sendback, 'post-new.php' ) !== false ) {
	if ( 'attachment' == $post_type ) {
		$sendback = admin_url( 'upload.php' );
	} else {
		$sendback = admin_url( 'edit.php' );
		if ( ! empty( $post_type ) ) {
			$sendback = add_query_arg( 'post_type', $post_type, $sendback );
} else {
	$sendback = remove_query_arg( array( 'trashed', 'untrashed', 'deleted', 'ids' ), $sendback );

For instance, the code above is taken from WordPress 5.1.1.

So, what happens when the referrer returned by wp_get_referer() contains the wrong URL? You’ll get redirected to anywhere, but the correct location. The only way to somehow fix this without messing with the code is to disable the referrer entirely. You still won’t get to the correct location, but at least you remain inside the WordPress web-root.

Why is the referrer wrong?

As stated above the referrer is set by the user agent (e.g. the browser). It seems like my Waterfox does not set the referrer correctly. For instance, it does not occur in Firefox and Opera. Looking at about:config in Waterfox I found the setting “network.http.referer.trimmingPolicy” being set to “2”. According to this page it will strip the referrer to its origin without any query strings etc.

Setting it back to its default solved the issue, but enables the browser to send the full referrer, which is not desirable by privacy means. On the other hand it did not break any other pages besides the WordPress backend, so I guess it’s time for the WordPress developers to fix their code.

I shouldn’t code when being tired as hell. 🙁

2019-03-04 @ 12:20: Blurry text Browsers | Bugs

In case you use a Chromium based browser you’ll likely have noticed blurry fonts on this website. First I thought it’s related to font-smoothing, but I don’t use such CSS rules, because they are not part of the standard, yet. Also I checked if forcing the browser to disable font-smoothing changes the way the text is rendered. To my surprise it had no effect at all. So, it must be something else that breaks the font-rendering. In Firefox, Edge and IE the issue does not appear. To make a long story short, in Chrome 72 the text gets blurry if it’s positioned using

position: absolute;
top: 50%;
left: 50%;
transform: translate(-50%,-50%);

That is quite annoying, because you use this rule to center content where the absolute width and height is unknown. If it’s known you could use negative margins instead.

In Opera the positioning using transform does not affect the font-rendering. However, and now things are getting really weird, the cause of the blurry text is the border-radius of the surrounding div element. Wtf!? Yes, the border-radius causes strange font-rendering. And it’s independent of the actual font. As simple

border-radius: 1px;

is just enough to make it ugly. Additionally the size of the browser window affects the rendering, too. So, if the browser window is resized by 1-2 pixels, the blurring disappears. Here are some screen shots to illustrate the issue:

Chrome 72 using transform
Chrome 72 absolute positioning
Opera 58 blurry font
Opera 58 crisp due to no border-radius

Opera 58 nearly crisp due to resizing the browser window

2018-10-18 @ 16:15: I broke Windows 10 Bugs

Sometimes the top 96 pixels of a maximized window disappear and are no longer click-able. Instead the click is received and handled by the desktop. This happens randomly on my Windows 10 Pro (10.0.16299) machine, which is a dual-monitor system as you can see. The issue is independent of the applications used; it happens in any application, but it cannot be triggered by a special action or similar. I first noticed it in Excel. Later in Firefox’s development tools and now quite often in Opera. All software is the latest. When it happens in a browser toggling full-screen on/off by pressing F11 helps sometimes. Otherwise a reboot is required to make it work again, because restarting the application does not help. Very annoying. Here’s a screenshot how it looks like:

I believe this is an error related to the display driver (Intel HD 4600, version, but prove me wrong. In case anyone has a suggestion what might be the cause, mail me.

UPDATE: Unfortunately, the following does no longer work with the latest Chromium version. 🙁

So, the autoplay policy for HTML5 videos in Chromium based browsers has been changed some time ago to disallow autoplay if the video contains audio. The intent was to not bother the user with sound being played automatically upon visitin a website, and in turn give him an option to selectively choose to have sound turned on/off for HTML5 videos. Well, I’ve found a nifty workaorund which allows you to play videos with sound automatically.

Create a video element as usual:

<video id="myvideo" src="myvideo.mp4" preload="auto" autoplay loop muted></video>


As you see the video is muted and will therefore play automatically in Chromium based browsers.

Now add this small JavaScript to unmute the video:

setTimeout(function() {
	var video = document.getElementById("myvideo");
	video.muted = false;
	console.log('Video unmuted.');
}, 1000);


This will unmute the video after one second. Bingo! Works like a charm. 🙂

Looks like the website of the beloved Gnome Connection Manager seems to be dead. I created a clone of the original code and will implement the fix mentioned here as soon as I find the code. It’s somewhere burried in a bunch of data on a pile of harddisks. What a mess!

I don’t like the WordPress plugin directory, so I publish my plugins only on Github. Grab the latest version here. Feel free to fork this. If you find a bug, please create an issue for that. I will have a look on that as soon as I have time.

  • About

    We never asked for this.