[-] Ooops@feddit.org 1 points 8 hours ago

As long as they don't get the result you want you do more studies, so you can pretend it's still actively studied and the results aren't clear yet.

[-] Ooops@feddit.org 10 points 8 hours ago* (last edited 8 hours ago)

Don't host the calendar, just host some WebDAV/CalDAV. That format is supported by basically all apps on every platform (usually including the default app on most phones), so everyone can pick what they want (or just stick with what they already use).

My personal pick for that purpose is Radicale.

[-] Ooops@feddit.org 8 points 8 hours ago

Since when government doesn’t have access to your purchases?

How does the government know where I spend the amount of cash I withdrew from my account?

[-] Ooops@feddit.org 58 points 9 hours ago

A mandatory [AI] tag? Sure.

A [NOT AI] tag? No, that's the default. Why normalise AI bullshit even further?

[-] Ooops@feddit.org 4 points 9 hours ago

"Das Designen, Anpassen, Besitzen oder Verbreiten von KI-Systemen, die speziell für die Generierung von Missbrauchsmaterial oder Deepfakes entwickelt wurden, wird künftig mit bis zu zwei Jahren Haft bestraft."

Tja, dann braucht xAI wohl ein neues Geschäftsmodell...

[-] Ooops@feddit.org 26 points 9 hours ago

If there only was a source of cheap electricity on hot, sunny days...

[-] Ooops@feddit.org 3 points 14 hours ago* (last edited 13 hours ago)

Nö, hat sie nicht. Zum einen, weil alle ihre sonstigen Maßnahmen darauf zielen, Erneuerbare auszubremsen, zum anderen, weil die gesetzliche Planung eine Wahnvorstellung ist:

Ab dem Jahr X sind so und so viel Prozent klimaneutrales Gas/Öl verpflichtend, wenn man weiß, dass diese Mengen nicht existieren werden, ist halt kein Gesetz, sondern Bürgerveraschung.

Das ist die exakt selbe Story wie das eFuel-Märchen. "Ihr müsst jetzt nichts ändern, sondern in der Zukunft wird die Technologie das für euch erledigen!" gefolgt von einem zukünftigen "Tja, wer hätte nur absehen könnnen, dass die verlangte Änderung jetzt gar nicht machbar ist. Dann müssen wir die ursprünglichen Ziele wohl einfach streichen. War halt nicht möglich. Schade aber auch..."

Das ist das Äquivalent von "Du must an der roten Ampel des Fußgängerübergangs nicht bremsen. Bis zu den Fußgänger eirreichst gibt es sicher längst Technik, die ihn zuverlässig vor dem Aufprall schützt.", "Oh, jetzt ist er tot? Wäre das doch bloß absehbar gewesen..."

[-] Ooops@feddit.org 5 points 14 hours ago* (last edited 14 hours ago)

(heavy?)

And right there lies your misconception. Newer software is not heavier by definition. Quite the contrary it often gets more efficient because of constant optimisation and improvements.

The concept of newer software using up ressouces like crazy is the scam used by corporate OS' so you buy new hardware constantly.

[-] Ooops@feddit.org 4 points 1 day ago

Rückfuttern ist ein Synomym für Würfelhusten, oder?

[-] Ooops@feddit.org 11 points 1 day ago

But our corrupt politicians are right-wing so they stand obviously above the law (and any form of consequences)...

[-] Ooops@feddit.org 17 points 2 days ago

Oh, we just need a bit more surveilance, more culture war and more right-wing brain-rot pushed on us and then the EEP can finally argue that the only way for a stable majority is cooperation with the far-right spectrum from insane nationalists to outright nazis.

That kind of enshittification of politics works so well in the member states so it will work for the EU, too.

[-] Ooops@feddit.org 20 points 3 days ago* (last edited 3 days ago)

Tanks won't be dead until there is another system that can fullfil it's role. It's easy as that.

Everything else is just adaption to changing threat environments while doing it's job on the battle field. Which specifically means more active defenses over passive armor, so soft- and hard-kill APS and probably an highly-automated small calibre remote weapon station.

Also, no matter how hard people try to delude themselves: The war in Ukraine is NOT a modern war shaping future combat. It's primarily characterised by obsolete static and trench warfare with both sides severely lacking capable air defense and experience in proper combined arms warfare. Then Russia aggrevates that situation even further as "We can't compete on the high-tech end of things so we drag everyone down to our level via a massive electronic warfare campaign" is part of their main strategy since the cold war.

That's the reason drones are so successful there, because they perfectly exploit an existing gap of lacking air defenses and a very taxing environment that benefits cheap mass spam over electronically impaired high-precsion tech. That's also the reason the Ukrainian side learning and adapting more quickly will win this.

The actual aspect of this war shaping future combat is detailed information on how to not make the same mistakes and close the existing gap cheap drones so perfectly fit into. So no, the tank isn't even close to obsolete. The next generation will show APS alongside limited in-build anti-air capabilities (small calibre gun against small drones probably alongside a few missiles that can double against out of range/LOS ground targets) and be accompanied by more dedicated anti-air assets once again (see: how those old German Gepards that were designed for that support role back then performed in Ukraine against drones half a century more modern)... and by IFVs nearly as well protected and basically being their flanking protection against infantry/ATGMs (see: active and passive protection levels of modern IFVs and their precisely timed burst-capable auto-guns - basically oversized battle field shotguns to clear the flanks off mobile but fragile threats).

33
submitted 2 weeks ago by Ooops@feddit.org to c/unixporn@lemmy.world

26
submitted 2 months ago* (last edited 2 months ago) by Ooops@feddit.org to c/selfhosted@lemmy.world

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 ›

Ooops

0 post score
0 comment score
joined 2 years ago