[–] 2 points 28 minutes ago

Breaking News: Deutschland hat eine vergleichweise große Bevölkerung!

Tatsächlich relevanter Vergleich:

"Laut der Studie liegt der Anteil bei 25- bis 34-Jährigen, die einen solchen Abschluss vorweisen können, in Deutschland bei mittlerweile 41 Prozent. Das bedeute ein Plus von elf Prozentpunkten gegenüber 2016. Insgesamt liegt der OECD-Durchschnitt aber bei 47 Prozent."

  • source
  • [–] 1 point 47 minutes ago

    More the fact that it's Debian and they still support huge amounts of ancient stuff. There are year's old ones in the list... alas, Debian still supports kernels like 5.10LTS. And backporting fixes doesn't get easier over time.

  • source
  • parent
  • context
  • [–] 2 points 1 hour ago* (last edited 51 minutes ago)

    but globally we will see this I am afraid.

    Yeah, that's what the brain rot they drown you in is telling. In reality you can look up additions to electric grids globally. It's renewables with everything else basically a rounding error.

    PS: the thing about China a good example. Look up their actual capacities. It's a joke compared to everything else they are building. Tripling nearly nothing is still irrelevant but for pro-nuclear propaganda, which 9 out of 10 times is just a diversion to slow down renewables so our fossil overlords can make some more money a few more years.

    (for reference: China's production capacities are at about 4% nuclear, 40% renewable; globally ~700GW in power plants were build in 2025, 85% of those solar, wind or hydro power)

  • source
  • parent
  • context
  • [–] 8 points 1 day ago (2 children)

    nothing can stick out beyond the body of the car (expect mirrors), not even wheels.

    That might be true for civilised countries.

    But then it's also the main reason why cars brought over by US military staff fail the inspection for road worthiness here.

  • source
  • parent
  • context
  • [–] 7 points 1 day ago

    Da mir bisher nie eine der ins Haus geflüchteten Wanzen verraten hat, ob sie 'ne Stinkwanze ist, während ich sie einfach wieder raus auf den Balkon gebracht habe, erschließt sich mir das Problem nicht.

  • source
  • [–] 13 points 1 day ago (2 children)

    Das Schlagwort, dass er in guter Populistenmanier eigentlich auspacken wollte, war "polarisiert". Aber dann ist ihm augefallen, dass es dafür ja irgendwen geben müsste, der ihn positiv sieht.

  • source
  • parent
  • context
  • [–] 52 points 1 day ago (2 children)

    I personally have gone for Manjaro

    Why would anyone intentionally do that?

    The whole Manjaro concept of delaying Arch updates by two weeks is bullshit, because they don't actually use that time for additional tests or include fixes. They just ship exactly the same bugs 2 weeks later.

    On top of this where Arch explicitly warns users about the AUR as unvetted community content and only lets you install AUR helpers manually (increasing the chance that people see the warning and think twice) Manjaro comes with their own AUR helper pre-installed. No warning, no nothing. Oh, and they use the unmodified AUR which is running under the assumption that you have an updated Arch system, not one weeks out-of-date. So welcome to breakages and dependency hell.

    Said Manjaro-specific AUR helper also has ddos'ed the AUR on multiple occasions because they don't seem to believe in testing.

    Have I mentioned the –by now meme-worthy– fact that they are too stupid to not let their SSL certificates expire and unironically proposed setting your PC's clock/date back as a solution?

  • source
  •  

    As this will -thanks to me being quite clueless- be a very open question I will start with the setup:

    One nginx server on an old Raspi getting ports 80 and 443 routed from the access point and serving several pages as well as some reverse proxies for other sevices.

    So a (very simplified) nginx server-block that looks like this:

    # serve stuff internally (without a hostname) via http
    server {
    	listen 80 default_server;
    	http2 on;
    	server_name _; 
    	location / {
    		proxy_pass http://localhost:5555/;
                    \# that's where all actual stuff is located
    	}
    }
    # reroute http traffic with hostname to https
    server {
    	listen 80;
    	http2 on;
    	server_name server_a.bla;
    	location / {
    		return 301 https://$host$request_uri;
    	}
    }
    server {
    	listen 443 ssl default_server;
    	http2 on;
    	server_name server_a.bla;
       	ssl_certificate     A_fullchain.pem;
        	ssl_certificate_key A_privkey.pem;
    	location / {
    		proxy_pass http://localhost:5555/;
    	}
    }
    #actual content here...
    server {
    	listen 5555;
    	http2 on;
        	root /srv/http;
    	location / {
            	index index.html;
       	} 
        	location = /page1 {
    		return 301 page1.html;
    	}
        	location = /page2 {
    		return 301 page2.html;
    	}
            #reverse proxy for an example webdav server 
    	location /dav/ {
    		proxy_pass        http://localhost:6666/;
    	}
    }
    

    Which works well.

    And intuitively it looked like putting Anubis into the chain should be simple. Just point the proxy_pass (and the required headers) in the "port 443"-section to Anubis and set it to pass along to localhost:5555 again.

    Which really worked just as expected... but only for server_a.bla, server_a.bla/page1 or server_a.bla/page2.

    server_a.bla/dav just hangs and hangs, to then time out, seemingly trying to open server_a.bla:6666/dav.

    So long story short...

    How does proxy_pass actually work that the first setup works, yet the second breaks? How does a call for localhost:6666 (already behind earlier proxy passes in both cases) somehow end up querying the hostname instead?

    And what do I need to configure -or what information/header do I need to pass on- to keep the internal communication intact?

    view more: next ›