2019-03-29 @ 09:05: Internet illiterates Politics

No matter how you explain things to clueless offline politicians, they will never ever understand the impact of their choices.

Article 13 just passed as expected, people play it down like nothing changed and Axel Voss is celebrated as the savior of the media.

Messages start popping up about VPN services to disguise your location etc. to circumvent the consequences of that bill. That’s not how it works. At least not this time. You can’t use a VPN to log in to a service which doesn’t exist any longer due to this bill. Ever thought about that, huh?

People don’t seem to understand what this bill is all about. It’s not limited to EU citizens. It has global impact, most noticeable in the EU though, but it still affects the rest of the world.

Huge companies will likely turn their back to the EU and make money elsewhere. Thousands of jobs will be cut when companies move to outside of the EU. The Internet in its whole variety will be stripped down to the bare minimum. There’ll be only a hand full of companies in the EU dictating what’s allowed on the net and what’s not.

Smaller companies and especially start-ups won’t be able to comply to the bill, as they simply do not have the required resources and will go out of business. Due to that people will lose their livelihood.

At the end nobody but lawyers will make money out of that bill. And the media? When they notice what they did, they’ll claim it’s someone else’s fault. But then it’s too late.

Download the final votes here.

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("de.wikipedia.org") {
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.

Interview with Axel Voss and Julia Reda
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. :( Also, I shouldn’t make shitty posts. Anyway, here’s your shitpost for today! MWAHAHA!!

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. A 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

  • About

    Destabilizing cishetero amatonormativity. Providing disruption as a service. Once you know the way, you see it in all things. Unless you puke, faint or die, keep going. Also we never asked for this. I̸͝t̸̑ ̵̽i̷͗s̶͐ ̵͝a̶͒l̷ ͍r̷ ̗͕e̵͑a̶͌d̸̄y̷̚ ̶̀ ͓͑t̷̚ô̶o̸ ̥ ̶́ ̡l̷͝a̶̽t̵͒ė̶.̸ ̋͑

  • Got something interesting?

    You think you got something which should be on this site? Then contact us. You want something removed from this site, because you think it should not be here? Then go fuck yourself. This is a free website. Free as in freedom. It tolerates every opinion from everyone. However, it does not tolerate things which are illegal according to the Swiss legislation.

  • Disclaimer

    We cannot be held responsible for any kind of direct, indirect or consequential damages caused by the stuff and or opinions we provide here. Use this on your own risk. Don’t blame us if something goes wrong or totally messes up your machine, your life or whatever. If this is unacceptable for you then go away and never come back again. Thank you!