Avatar
goodtiding5
c22c5332c5ff9150ccf1d96040ba8216a16e1bf0cbc33b5ed628836f8c679ef3

The UK labour government has a lot of paedos!

https://labour25.com/labour25/

So heartbroken to hear this British woman: “I was raped over 1000 times”

A Pakistani rape gang from Telford repeatedly raped this women since she was 14.

https://nitter.poast.org/visegrad24/status/1878195426727190971

Santa Ynez Reservoir for providing water to fire hydrants to Pacific Palisades has been mostly empty since 2024!!!

https://nitter.poast.org/TheFP/status/1878088302936379881

Replying to Avatar Alex Gleason

Let me tell you about the theory of my weird homelab imagination.

I want to run a rack server in an undisclosed location, with a dynamic IP address. I want it to be flexible so it can be easily moved and resistant to deplatforming. It will host public websites.

It consists of two essential parts: "keystone" and "decoy"

"keystone" is the entrypoint of my rack - one big http server (running caddy, not nginx), that routes traffic to hostnames within my internal network.

"decoy" is a cloud VPS, running nginx, which streams requests to the keystone over WireGuard.

DNS is all pointed at "decoy".

From the outside, it looks like the cloud VPS is hosting the sites. In reality I pay them very little money to just transfer data, and I can easily switch to a different provider. As a result, I get a static IP and a layer of protection/obscurity from the VPS, but the rack will continue to "just work" even if the decoy is changed or even removed. Only DNS entries would need to be updated.

This is not exactly groundbreaking. I know people have used VPNs to route traffic for decades. The main thing that's new is just my weird terminology for it.

To connect the "keystone" and the "decoy" together... I call this "trepanning".

I want to make this easily reproducible so others can copy my setup. Later I will release code and a guide.

nostr:nevent1qvzqqqqqqypzqprpljlvcnpnw3pejvkkhrc3y6wvmd7vjuad0fg2ud3dky66gaxaqydhwumn8ghj7emvv4shxmmwv96x7u3wv3jhvtmjv4kxz7gqyrm5kdaazpcukade8n9mgzaa54624hcxvd0dr0xkwuxyhe6vemdx7zuktv0

You can use tinc vpn to connect your decoy and keystone servers. It's pretty easy and will autoconnect. Use fixed IP addresses in your decoy host file and setup keystone config to connect to the decoy.

I once used two decoys to provide web access to one keystone using this method and it worked very well.

On the other hand, maybe you want to consider to containerize all your services in your keystone server. I just use a simple debian 12 minimum server with docker installed. Just export the ports from running containers and the caddies in the remote can do the reverse proxy.

I have got rebased+soapbox and ditto+soapbox dockerized and they just keep running.

The death of a president -- The life and legacy of Jimmy Carter

https://wng.org/opinions/the-death-of-a-president-1735561136

Adoration ofJesus

John Mearsheimer vs Alexander Dugin: All You Need to Know about China, Russia, and the US

https://www.youtube.com/watch?v=Iv02AsNATAg

Winners and losers in Syria

Iran and Russia are the two big losers in the ouster of Syria’s President Bashar al-Assad on Sunday by the Sunni Islamist groups affiliated to al-Qaeda. Assad fled in the nick of time after giving orders that there be a peaceful handover of power. The likelihood is that he is in Russia. At any rate, a rollback of the Islamist takeover in Syria is out of the question.

Israel and Turkey are the biggest winners, having established links with the al-Qaeda groups. Both are all well-set to project power into Syria and carve out their respective spheres of influence in Syrian territory. Turkey has demanded that Syria belongs to Syrian people alone — a thinly covered call for vacation of foreign military presence (Russian, American and Iranian.)

https://www.indianpunchline.com/winners-and-losers-in-syria/

Maybe it's the time to buy Toyota here.

It looks like $TLT has hit the bottom for now. Also notice the higher high and higher low formation. Time to accumulate US bond.