[–] 1 point 52 minutes ago* (last edited 37 minutes ago)

Small cars are dangerous because larger cars can crush them.

That's true in a world of cars, not in one for people though where the driver of the small car sees you and might hurt you if they screw up while the driver of that big ass pseudo-tank(*) just kills you without having ever realized you were there.

(*)scrap that: actual tanks have better visibility than those idiotic US trucks never hauling anything...

  • source
  • parent
  • context
  • [–] 2 points 54 minutes ago*

    There are stupid, rich asshole everywhere.

    But stupid rich assholes are too small a group to sustain an industry. They will spend stupid amounts of money on ridiculous hand-crafted luxury cars but they will never actually have any real impact on the car industry as a whole market.

  • source
  • parent
  • context
  • [–] 3 points 57 minutes ago (4 children)

    They "caved in" just like they did years ago when they agreed to buy US beef... if it was produced to the neccessary standards nobody in the US ever met.

    There is barely anything preventing US cars from being sold here technically. That they rarely meet minimum technical standards required in the EU by any vehicle and there is also no reason for EU citizens to buy such an abomination is the real point here. Only smooth-brains like Trump see not being treated preferential and being allowed to break the rules as a barrier for US trade.

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

    Did you really not get (given the topic was margins and AI) that "tech giants making money" obviously meant "with AI"?

    Not while also spending money on AI. Not despite using AI. Not while hoping AI will be their next big thing. But making money with AI. As in: income from AI making up for the costs, e.g. actual AI profits.

    The only ones making actual money are the chip producers (and a lot of it is caused by the scarcity thus price hike caused by the hype).

  • source
  • parent
  • context
  • [–] 4 points 1 hour ago

    Are PPPoE credentials integrated into your modem and not extractable in plain readable form still a wide-spread thing? I think it has been decades since providers where I live were required by law to provide those credentials so you are not artificially bound to some provided hardware.

  • source
  • [–] 3 points 1 hour ago

    Or you could have just scrolled down about half a page and taken a look at the explanation and sources...

    Especially as "scam detector" serve an entirely different purpose. Yes, a single page created by single person to post some information as a hobby and without making any money is not rating high in terms of "does this page seem to be from a legitimate business" because it really isn't.

    But somehow I am not surprised that the same kind of person subscribing to the fairy tale of the whole world being a nail for that shiny hammer that is AI would use an automated checkup entirely unsuited for the actual taks, too...

  • source
  • parent
  • context
  • [–] 3 points 1 hour ago* (2 children)

    Yeah, all those purely AI companies make money with AI. Oh, wait. They don't. At best the amounts invested into AI hasn't squashed the profits from their actually profitable business (yet) because the constant circular investments hide the losses until the insane bubble bursts.

  • source
  • parent
  • context
  • [–] 27 points 2 hours ago* (3 children)

    And Republicans continue to say the Left is the ones responsible for fomenting political violence.

    That's no contradiction. They say is with the expliciet intent to distort the discussion to support their violence.

  • source
  • [–] 6 points 2 hours ago

    No, the point is that the tool has no use case massive enough to ever justify the insane amount of investments.

    So they now need to convince the whole world that everything in existence is a nail for their shiny new hammer or that this magical hammer will get the ability to transform into every actually useful tool soon™ and you will totally be left behind when that singularity event happens and you are not already on board.

  • source
  • parent
  • context
  •  

    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 ›