[–] 6 points 2 hours ago

Every new generation of WiFi brings higher transfer speeds... at lower ranges where I can just use a cable, while WiFi reliability and range often suffer in most scenarios where a cable doesn't work well.

  • source
  • [–] 5 points 2 hours ago

    after failing to produce world-leading chatbots like DeepSeek or Claude

    Oh, no! Why didn't we succeed in building our own insanity bubble that has no working business model, barely produces anything of worth, and just makes people poor by creating energy and water scarcity (not even speaking about the fact that it's also used as a pretense to burn more fossil fuels just because...), all so that a handful of ultra rich can look at big numbers that have lost any actual meaning for them... 😂

  • source
  • [–] 3 points 5 hours ago

    Das scheinen sie selber auch zu merken, aber nicht wahr haben zu wollen.

    Doch, die wissen sehr wohl, dass das wahr ist. Daher auch die klare Entscheidung lieber Faschisten zu unterstützen und linke Demokraten zu bekämpfen. Die einzig andere Option wäre sinnvolle Politik, aber dem stehen die reichen Kumpels und Großspender entgegen. Also eben Rechtspopulismus, Kulturkampf und rechtes Gekreische zur Ablenkung der Massen bis man die Demokratie abgewickelt hat. Alles für den Machterhalt...

  • source
  • parent
  • context
  • [–] 3 points 5 hours ago

    Weil "Journalismus" eben nicht geschützt ist und das jeder machen kann. Also finden sich auch immer Gestalten, die bereit sind für ausreichend Geld jeden Mist zu schreiben. Und so wurden Journalisten längst nach und nach durch rechte Propagandisten ersetzt.

  • source
  • parent
  • context
  • [–] 1 point 6 hours ago*

    I'm not missing the middle ground. I am criticising that there is no middle ground in this fake discussion manufactured to keep engagement going.

    Every single time someone makes a nuanced argument that is not matching one of the two dogmatic extremes (so exactly that Linus Torvalds is doing here, just –Linus being Linus– not very diplomatically phrased) the same kind of people start screaming about the end of the world (see again: this very thread where idiots express their condolences for Linus finally going insane by not denouncing AI alongside those praising the fact that he finally has seen the light an embraces AI as our saviour).

  • source
  • parent
  • context
  • [–] 1 point 1 day ago*

    My "script" to update the blocklist from time to time was literally

    curl <blocklist1 link> > templist
    curl <blocklist2 link> >> templist
    grep '^0\.0\.0\.0' templist | awk '{print "local-zone: \""$2"\" always_refuse"} > blocklist.conf
    systemctl restart unbound.service

    and an include blocklist.conf at the bottom of unbound.conf (awk to convert it from the "0.0.0.0 " format to "local-zone: always_refuse").

  • source
  • parent
  • context
  • [–] -1 points 1 day ago* (last edited 6 hours ago)

    No, calling pigs rolling around in the mud pigs is neither an insult nor taking part in the strange mud bath ritual.

    But as you seem to be bad with analogies:

    Spouting ideology for the sake of it is bullshit no matter which side does it. Pitting your ideological dogmas against each other is not a discussion. If that's your thing start a new religion (that's not even far off from some of the influencer and tech-bro bullshit nowadays anyway...).

    Most people are sick of the always same "AI is the evil and will destroy us all!", "No, you need to embrace our saviour AI that will save us all or get left behind!" idiocy repeated a million times in slightly different spelling. You need to be absolutely lost in a delusion to miss the costantly alternating pattern of pro-AI / anti-AI posts in social and other media pushed to keep engagement going. Ffs... when it's about the Linux kernel it's even worse and even more obvious when we are bombarded with alternating pro- and anti-AI statements from the same single person. People can't be that dense. So why pretend that at this point it's something else but induced insanity.

  • source
  • parent
  • context
  • [–] 1 point 1 day ago* (last edited 1 day ago) (1 child)

    It literally is a cron job or systemd timer to load an updated blocklist from time to time and I haven't looked at it for years (well... other an changing a path when I switched from unbound to dnsproxy, because that one is even simpler, doesn't even need a config other than a few parameters at startup and can provide DoH, DoT and/or DoQ access for when I'm not at home)

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

    Merz-Forderung nach Abbruch kommt zu spät

    Merz hat keine Forderungen zu den Koalitionsentscheidungen anderer Parteien, schon gar nicht auf Landesebenen, zu stellen, und daher ist deren Timing völlig egal.

  • 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 ›