“NaMi” — Fediverse search results on home.social

Astros fans will now see a pile of oversized baseballs in the home run train that runs along the upper left field wall of newly renamed Daikin Park. Gone are the pile of oranges from longtime ballpark naming rights holder Minute Maid.

https://www.houstonpublicmedia.org/articles/news/sports/2025/03/28/517115/houston-astros-train-unveiled-baseballs-daikin-park/

#Houston #Local #News #Sports #DaikinPark #HomeRunTrain #HoustonAstros #MinuteMaidPark

#houston #local #news #sports #daikinpark #homeruntrain

Houston Public Media @[email protected] · 2025-02-06 · 23:15 UTC

Construction crews on Wednesday began moving Minute Maid signage from the Houston Astros' 25-year-old stadium. Signs for Daikin, the ballpark’s new naming rights sponsor, started going up Thursday.

https://www.houstonpublicmedia.org/articles/news/2025/02/06/513225/minute-maid-signs-being-swapped-out-for-daikin-at-houston-astros-downtown-ballpark/

#Business #Houston #Local #News #Sports #DaikinPark #DowntownHouston #HoustonAstros #HoustonSportsTeams #MinuteMaidPark #NamingRights

#business #houston #local #news #sports #daikinpark

MotoGazer @[email protected] · 2025-10-01 · 18:24 UTC

KTM Racing and Tricolor Motorsports Unite for ISRL Season 2

KTM Racing and Tricolor Motorsports join ISRL Season 2 as naming rights and bike partner, bringing global pedigree to Indian supercross.

https://motogazer.com/ktm-racing-tricolor-motorsports-unite-for-isrl-season-2/

#automotive #automobile #autonews #news #autos #racing #race #dirtbike #motocross #indiansupercrossracingleague #IRSL

#automotive #automobile #autonews #news #autos #racing

Futurist Jim Carroll @[email protected] · 2026-05-11 · 10:06 UTC

"Your flaws are your most important assets." - Futurist Jim Carroll

--
Futurist Jim Carroll is writing a series, The Art of the Infinite Pivot, based on 36 lessons from his 36 years as a solo entrepreneur, working as a nomadic worker in the global freelance economy. The series is unfolding here, and at pivot.jimcarroll.com.
--

We're all talking about the importance of authenticity in an era of artificiality.

After all, in 2026, AI can generate almost anything. A photorealistic headshot of a CEO who doesn't exist. A polished podcast in your voice, on a topic you've never thought about, in under five minutes. A speaker highlight reel with fake audiences and fake standing ovations. Perfection has become cheap, instant, and infinite.

Here's the paradox of this new era: when perfection is everywhere, perfection stops counting. When everyone can be perfect, being perfect doesn't matter anymore.

What stands out now is the opposite. The stumble, the scar, the story too weird to be invented, the detail too specific to be faked, the mistake too painful to be generated. In a world full of synthetic perfection, your flaws are the only authentication signal that proves you are real. It might become the most important signal for your future success.

And in that context, I must confess: I didn't know I had been operating on this principle for most of my career! For 36 years, I've quietly leaned on my flaws without naming them as assets. It was just how I operated. Now, when everyone is talking about AI, I can see how important my flaws are.

An example? In 1995, I appeared on a VHS tape called The Family Guide to the Internet, presented by IBM. I billed myself as a "Global Internet Consultant" and walked a fictional family through the wonders of newsgroups and proper Internet etiquette. It is, hands down, the most embarrassing thing I have ever done. It still exists on YouTube. And get this - I often tell people about it and send them the link. Most people would have buried it, but don't try to hide from it. It's proof that I was actually there, in the room, at the moment the future was being figured out.

While not as interesting, there have been many other stumbles, errors, and foibles along the way.

So tell the embarrassing story. Quote the bad review. List the failed venture. Publish the rejected pitch. Show the wreckage.

Let the cracks show.

----
Futurist Jim Carroll is proud of his flaws and mistakes.

**#Flaws** **#Assets** **#Authenticity** **#Imperfection** **#Scars**

Original post: https://jimcarroll.com/2026/05/decoding-tomorrow-the-infinite-pivot-series-32-your-flaws-are-your-most-important-assets/

#flaws #assets #authenticity #imperfection #scars

Africa @[email protected] · 2026-05-14 · 11:42 UTC

https://www.europesays.com/africa/234275/ Kendrick Resources (KEN) Identifies 14Mt of High-Grade Surface Rare Earth Mineralisation in Namibia #DevelopmentRisk #Kendrick #KendrickResources #KendrickResourcesPLC #mineralisation #Namibia #RareEarth #ResourceEstimate

#resourceestimate #rareearth #namibia #mineralisation #kendrickresourcesplc #kendrickresources

Africa @[email protected] · 2026-05-06 · 22:03 UTC

https://www.europesays.com/africa/222212/ Kendrick (KEN) advances plans to accelerate Namibia rare earth projects toward production #DevelopmentStrategy #KendrickResources #Namibia #RareEarth #RareEarthMinerals

#rareearthminerals #rareearth #namibia #kendrickresources #developmentstrategy

Kevin @[email protected] · 2026-05-12 · 21:56 UTC

When two Hetzner servers died at the same time

On May 12, 2026, two of my Arch Linux + LUKS servers at Hetzner became unreachable at the same moment. Both had been running for 4+ months without issue. Both had received the same pacman -Syyu the day before, but had stayed on the old kernel until the morning the websites stopped responding. I rebooted — SSH never came back. nmap -Pn -p 22 showed filtered from anywhere. No ping. No banner. The Hetzner Robot panel insisted the hardware was fine.

Several hours went into hypotheses that turned out to be wrong:

The encryptssh initcpio hook referencing a /usr/lib/initcpio/udev/11-dm-initramfs.rules file that no longer exists. Real bug, no boot impact — the initramfs rebuilds anyway.
PermitRootLogin no in sshd_config. Real misconfiguration, fixed it, didn’t help. A refusing sshd shows closed, not filtered.
Predictable interface-naming drift after the systemd 260 upgrade. Patched the .network config to match by MAC. Useful hardening; not the cause.
Stale GRUB stage1 + core.img in the MBR. Arch never re-runs grub-install after a grub package upgrade. Refreshed it. Still filtered.
Kernel 7.0.5 regression. Downgraded to 6.18.3, the kernel that had run for 4 months. Still filtered. So the kernel itself wasn’t it either.

The clue was in the persistent journal: a single recorded boot from December 31 to May 12 10:13 UTC, and absolutely nothing after. Every reboot since the upgrade was failing before systemd-journald could flush to disk — so the failure had to be in the initramfs, before the root filesystem was even mounted.

What it almost certainly was

Hetzner Dedicated servers configure the initramfs network with ip=dhcp on the kernel command line. That depends on Hetzner’s DHCP server replying to whatever request format the current kernel sends. Somewhere between kernel 6.18 / iproute2 6.18 and kernel 7.0 / iproute2 7.0, the request format changed enough that Hetzner’s DHCP stopped responding. Effects:

Old kernel at runtime kept the interface already configured (Phase A — 32 hours of healthy operation after the package upgrade).
New kernel cold-boots, hits DHCP, never gets an IP, dropbear cannot listen, port 22 stays filtered.

Hetzner’s own documentation has been quietly moving away from ip=dhcp toward static IPv4 in the kernel command line. The fix is exactly that:

GRUB_CMDLINE_LINUX="cryptdevice=/dev/md1:cryptroot ip=A.B.C.D::GATEWAY:255.255.255.255:hostname:eth0:none"

One line in /etc/default/grub, grub-mkconfig, reboot. No more dependency on Hetzner’s DHCP responding to whatever your current kernel sends.

Why it matters for anyone running this stack

If you run Arch on Hetzner Dedicated with full-disk encryption and remote unlock via dropbear, the ip=dhcp shipped by installimage is a latent bug. It can keep working for years and then break overnight, on every machine you have, after a routine pacman -Syyu. The static-IP version is what Hetzner now recommends and removes the entire dependency.

Tooling

While debugging, I turned the whole rescue / chroot / diagnose / fix workflow into a Python CLI (hal) — including hal fix static-ip, which derives the static cmdline directly from your existing systemd-networkd .network file:

→ github.com/kevinveenbirkenbach/hetzner-arch-luks

Single command, idempotent, reversible (the original /etc/default/grub is backed up to .hal-backup). If you’re on this stack, switch to static IP before the next kernel upgrade catches you.

#ArchLinux #bootFailure #debugging #DevOps #DHCP #Dropbear #fullDiskEncryption #GRUB #Hetzner #initramfs #kernelUpgrade #Linux #LUKS #mkinitcpio #pacman #postmortem #PythonCLI #serverOutage #sysadmin #systemdNetworkd

#archlinux #bootfailure #debugging #devops #dhcp #dropbear

Kevin @[email protected] · 2026-05-12 · 21:56 UTC

When two Hetzner servers died at the same time

On May 12, 2026, two of my Arch Linux + LUKS servers at Hetzner became unreachable at the same moment. Both had been running for 4+ months without issue. Both had received the same pacman -Syyu the day before, but had stayed on the old kernel until the morning the websites stopped responding. I rebooted — SSH never came back. nmap -Pn -p 22 showed filtered from anywhere. No ping. No banner. The Hetzner Robot panel insisted the hardware was fine.

Several hours went into hypotheses that turned out to be wrong:

The encryptssh initcpio hook referencing a /usr/lib/initcpio/udev/11-dm-initramfs.rules file that no longer exists. Real bug, no boot impact — the initramfs rebuilds anyway.
PermitRootLogin no in sshd_config. Real misconfiguration, fixed it, didn’t help. A refusing sshd shows closed, not filtered.
Predictable interface-naming drift after the systemd 260 upgrade. Patched the .network config to match by MAC. Useful hardening; not the cause.
Stale GRUB stage1 + core.img in the MBR. Arch never re-runs grub-install after a grub package upgrade. Refreshed it. Still filtered.
Kernel 7.0.5 regression. Downgraded to 6.18.3, the kernel that had run for 4 months. Still filtered. So the kernel itself wasn’t it either.

The clue was in the persistent journal: a single recorded boot from December 31 to May 12 10:13 UTC, and absolutely nothing after. Every reboot since the upgrade was failing before systemd-journald could flush to disk — so the failure had to be in the initramfs, before the root filesystem was even mounted.

What it almost certainly was

Hetzner Dedicated servers configure the initramfs network with ip=dhcp on the kernel command line. That depends on Hetzner’s DHCP server replying to whatever request format the current kernel sends. Somewhere between kernel 6.18 / iproute2 6.18 and kernel 7.0 / iproute2 7.0, the request format changed enough that Hetzner’s DHCP stopped responding. Effects:

Old kernel at runtime kept the interface already configured (Phase A — 32 hours of healthy operation after the package upgrade).
New kernel cold-boots, hits DHCP, never gets an IP, dropbear cannot listen, port 22 stays filtered.

Hetzner’s own documentation has been quietly moving away from ip=dhcp toward static IPv4 in the kernel command line. The fix is exactly that:

GRUB_CMDLINE_LINUX="cryptdevice=/dev/md1:cryptroot ip=A.B.C.D::GATEWAY:255.255.255.255:hostname:eth0:none"

One line in /etc/default/grub, grub-mkconfig, reboot. No more dependency on Hetzner’s DHCP responding to whatever your current kernel sends.

Why it matters for anyone running this stack

If you run Arch on Hetzner Dedicated with full-disk encryption and remote unlock via dropbear, the ip=dhcp shipped by installimage is a latent bug. It can keep working for years and then break overnight, on every machine you have, after a routine pacman -Syyu. The static-IP version is what Hetzner now recommends and removes the entire dependency.

Tooling

While debugging, I turned the whole rescue / chroot / diagnose / fix workflow into a Python CLI (hal) — including hal fix static-ip, which derives the static cmdline directly from your existing systemd-networkd .network file:

→ github.com/kevinveenbirkenbach/hetzner-arch-luks

Single command, idempotent, reversible (the original /etc/default/grub is backed up to .hal-backup). If you’re on this stack, switch to static IP before the next kernel upgrade catches you.

#ArchLinux #bootFailure #debugging #DevOps #DHCP #Dropbear #fullDiskEncryption #GRUB #Hetzner #initramfs #kernelUpgrade #Linux #LUKS #mkinitcpio #pacman #postmortem #PythonCLI #serverOutage #sysadmin #systemdNetworkd

#archlinux #bootfailure #debugging #devops #dhcp #dropbear

Kevin @[email protected] · 2026-05-12 · 21:56 UTC

When two Hetzner servers died at the same time

On May 12, 2026, two of my Arch Linux + LUKS servers at Hetzner became unreachable at the same moment. Both had been running for 4+ months without issue. Both had received the same pacman -Syyu the day before, but had stayed on the old kernel until the morning the websites stopped responding. I rebooted — SSH never came back. nmap -Pn -p 22 showed filtered from anywhere. No ping. No banner. The Hetzner Robot panel insisted the hardware was fine.

Several hours went into hypotheses that turned out to be wrong:

The encryptssh initcpio hook referencing a /usr/lib/initcpio/udev/11-dm-initramfs.rules file that no longer exists. Real bug, no boot impact — the initramfs rebuilds anyway.
PermitRootLogin no in sshd_config. Real misconfiguration, fixed it, didn’t help. A refusing sshd shows closed, not filtered.
Predictable interface-naming drift after the systemd 260 upgrade. Patched the .network config to match by MAC. Useful hardening; not the cause.
Stale GRUB stage1 + core.img in the MBR. Arch never re-runs grub-install after a grub package upgrade. Refreshed it. Still filtered.
Kernel 7.0.5 regression. Downgraded to 6.18.3, the kernel that had run for 4 months. Still filtered. So the kernel itself wasn’t it either.

The clue was in the persistent journal: a single recorded boot from December 31 to May 12 10:13 UTC, and absolutely nothing after. Every reboot since the upgrade was failing before systemd-journald could flush to disk — so the failure had to be in the initramfs, before the root filesystem was even mounted.

What it almost certainly was

Hetzner Dedicated servers configure the initramfs network with ip=dhcp on the kernel command line. That depends on Hetzner’s DHCP server replying to whatever request format the current kernel sends. Somewhere between kernel 6.18 / iproute2 6.18 and kernel 7.0 / iproute2 7.0, the request format changed enough that Hetzner’s DHCP stopped responding. Effects:

Old kernel at runtime kept the interface already configured (Phase A — 32 hours of healthy operation after the package upgrade).
New kernel cold-boots, hits DHCP, never gets an IP, dropbear cannot listen, port 22 stays filtered.

Hetzner’s own documentation has been quietly moving away from ip=dhcp toward static IPv4 in the kernel command line. The fix is exactly that:

GRUB_CMDLINE_LINUX="cryptdevice=/dev/md1:cryptroot ip=A.B.C.D::GATEWAY:255.255.255.255:hostname:eth0:none"

One line in /etc/default/grub, grub-mkconfig, reboot. No more dependency on Hetzner’s DHCP responding to whatever your current kernel sends.

Why it matters for anyone running this stack

If you run Arch on Hetzner Dedicated with full-disk encryption and remote unlock via dropbear, the ip=dhcp shipped by installimage is a latent bug. It can keep working for years and then break overnight, on every machine you have, after a routine pacman -Syyu. The static-IP version is what Hetzner now recommends and removes the entire dependency.

Tooling

While debugging, I turned the whole rescue / chroot / diagnose / fix workflow into a Python CLI (hal) — including hal fix static-ip, which derives the static cmdline directly from your existing systemd-networkd .network file:

→ github.com/kevinveenbirkenbach/hetzner-arch-luks

Single command, idempotent, reversible (the original /etc/default/grub is backed up to .hal-backup). If you’re on this stack, switch to static IP before the next kernel upgrade catches you.

#ArchLinux #bootFailure #debugging #DevOps #DHCP #Dropbear #fullDiskEncryption #GRUB #Hetzner #initramfs #kernelUpgrade #Linux #LUKS #mkinitcpio #pacman #postmortem #PythonCLI #serverOutage #sysadmin #systemdNetworkd

#archlinux #bootfailure #debugging #devops #dhcp #dropbear

Kevin @[email protected] · 2026-05-12 · 21:56 UTC

When two Hetzner servers died at the same time

On May 12, 2026, two of my Arch Linux + LUKS servers at Hetzner became unreachable at the same moment. Both had been running for 4+ months without issue. Both had received the same pacman -Syyu the day before, but had stayed on the old kernel until the morning the websites stopped responding. I rebooted — SSH never came back. nmap -Pn -p 22 showed filtered from anywhere. No ping. No banner. The Hetzner Robot panel insisted the hardware was fine.

Several hours went into hypotheses that turned out to be wrong:

The encryptssh initcpio hook referencing a /usr/lib/initcpio/udev/11-dm-initramfs.rules file that no longer exists. Real bug, no boot impact — the initramfs rebuilds anyway.
PermitRootLogin no in sshd_config. Real misconfiguration, fixed it, didn’t help. A refusing sshd shows closed, not filtered.
Predictable interface-naming drift after the systemd 260 upgrade. Patched the .network config to match by MAC. Useful hardening; not the cause.
Stale GRUB stage1 + core.img in the MBR. Arch never re-runs grub-install after a grub package upgrade. Refreshed it. Still filtered.
Kernel 7.0.5 regression. Downgraded to 6.18.3, the kernel that had run for 4 months. Still filtered. So the kernel itself wasn’t it either.

The clue was in the persistent journal: a single recorded boot from December 31 to May 12 10:13 UTC, and absolutely nothing after. Every reboot since the upgrade was failing before systemd-journald could flush to disk — so the failure had to be in the initramfs, before the root filesystem was even mounted.

What it almost certainly was

Hetzner Dedicated servers configure the initramfs network with ip=dhcp on the kernel command line. That depends on Hetzner’s DHCP server replying to whatever request format the current kernel sends. Somewhere between kernel 6.18 / iproute2 6.18 and kernel 7.0 / iproute2 7.0, the request format changed enough that Hetzner’s DHCP stopped responding. Effects:

Old kernel at runtime kept the interface already configured (Phase A — 32 hours of healthy operation after the package upgrade).
New kernel cold-boots, hits DHCP, never gets an IP, dropbear cannot listen, port 22 stays filtered.

Hetzner’s own documentation has been quietly moving away from ip=dhcp toward static IPv4 in the kernel command line. The fix is exactly that:

GRUB_CMDLINE_LINUX="cryptdevice=/dev/md1:cryptroot ip=A.B.C.D::GATEWAY:255.255.255.255:hostname:eth0:none"

One line in /etc/default/grub, grub-mkconfig, reboot. No more dependency on Hetzner’s DHCP responding to whatever your current kernel sends.

Why it matters for anyone running this stack

If you run Arch on Hetzner Dedicated with full-disk encryption and remote unlock via dropbear, the ip=dhcp shipped by installimage is a latent bug. It can keep working for years and then break overnight, on every machine you have, after a routine pacman -Syyu. The static-IP version is what Hetzner now recommends and removes the entire dependency.

Tooling

While debugging, I turned the whole rescue / chroot / diagnose / fix workflow into a Python CLI (hal) — including hal fix static-ip, which derives the static cmdline directly from your existing systemd-networkd .network file:

→ github.com/kevinveenbirkenbach/hetzner-arch-luks

Single command, idempotent, reversible (the original /etc/default/grub is backed up to .hal-backup). If you’re on this stack, switch to static IP before the next kernel upgrade catches you.

#ArchLinux #bootFailure #debugging #DevOps #DHCP #Dropbear #fullDiskEncryption #GRUB #Hetzner #initramfs #kernelUpgrade #Linux #LUKS #mkinitcpio #pacman #postmortem #PythonCLI #serverOutage #sysadmin #systemdNetworkd

#systemdnetworkd #sysadmin #serveroutage #pythoncli #postmortem #pacman

Kevin @[email protected] · 2026-05-12 · 21:56 UTC

When two Hetzner servers died at the same time

On May 12, 2026, two of my Arch Linux + LUKS servers at Hetzner became unreachable at the same moment. Both had been running for 4+ months without issue. Both had received the same pacman -Syyu the day before, but had stayed on the old kernel until the morning the websites stopped responding. I rebooted — SSH never came back. nmap -Pn -p 22 showed filtered from anywhere. No ping. No banner. The Hetzner Robot panel insisted the hardware was fine.

Several hours went into hypotheses that turned out to be wrong:

The encryptssh initcpio hook referencing a /usr/lib/initcpio/udev/11-dm-initramfs.rules file that no longer exists. Real bug, no boot impact — the initramfs rebuilds anyway.
PermitRootLogin no in sshd_config. Real misconfiguration, fixed it, didn’t help. A refusing sshd shows closed, not filtered.
Predictable interface-naming drift after the systemd 260 upgrade. Patched the .network config to match by MAC. Useful hardening; not the cause.
Stale GRUB stage1 + core.img in the MBR. Arch never re-runs grub-install after a grub package upgrade. Refreshed it. Still filtered.
Kernel 7.0.5 regression. Downgraded to 6.18.3, the kernel that had run for 4 months. Still filtered. So the kernel itself wasn’t it either.

The clue was in the persistent journal: a single recorded boot from December 31 to May 12 10:13 UTC, and absolutely nothing after. Every reboot since the upgrade was failing before systemd-journald could flush to disk — so the failure had to be in the initramfs, before the root filesystem was even mounted.

What it almost certainly was

Hetzner Dedicated servers configure the initramfs network with ip=dhcp on the kernel command line. That depends on Hetzner’s DHCP server replying to whatever request format the current kernel sends. Somewhere between kernel 6.18 / iproute2 6.18 and kernel 7.0 / iproute2 7.0, the request format changed enough that Hetzner’s DHCP stopped responding. Effects:

Old kernel at runtime kept the interface already configured (Phase A — 32 hours of healthy operation after the package upgrade).
New kernel cold-boots, hits DHCP, never gets an IP, dropbear cannot listen, port 22 stays filtered.

Hetzner’s own documentation has been quietly moving away from ip=dhcp toward static IPv4 in the kernel command line. The fix is exactly that:

GRUB_CMDLINE_LINUX="cryptdevice=/dev/md1:cryptroot ip=A.B.C.D::GATEWAY:255.255.255.255:hostname:eth0:none"

One line in /etc/default/grub, grub-mkconfig, reboot. No more dependency on Hetzner’s DHCP responding to whatever your current kernel sends.

Why it matters for anyone running this stack

If you run Arch on Hetzner Dedicated with full-disk encryption and remote unlock via dropbear, the ip=dhcp shipped by installimage is a latent bug. It can keep working for years and then break overnight, on every machine you have, after a routine pacman -Syyu. The static-IP version is what Hetzner now recommends and removes the entire dependency.

Tooling

While debugging, I turned the whole rescue / chroot / diagnose / fix workflow into a Python CLI (hal) — including hal fix static-ip, which derives the static cmdline directly from your existing systemd-networkd .network file:

→ github.com/kevinveenbirkenbach/hetzner-arch-luks

Single command, idempotent, reversible (the original /etc/default/grub is backed up to .hal-backup). If you’re on this stack, switch to static IP before the next kernel upgrade catches you.

#ArchLinux #bootFailure #debugging #DevOps #DHCP #Dropbear #fullDiskEncryption #GRUB #Hetzner #initramfs #kernelUpgrade #Linux #LUKS #mkinitcpio #pacman #postmortem #PythonCLI #serverOutage #sysadmin #systemdNetworkd

#archlinux #bootfailure #debugging #devops #dhcp #dropbear

Africa @[email protected] · 2026-04-25 · 14:43 UTC

https://www.europesays.com/africa/204727/ East Rand veteran relives 1986 missile strike survival #BreakingNews #LocalNews #Namibia #news #NewsHeadlines #Springs #SpringsNewsHeadlines

#springsnewsheadlines #springs #newsheadlines #news #namibia #localnews

Nonilex @[email protected] · 2025-08-15 · 14:38 UTC

About time!

#WashingtonDC sues to block #Trump #federal #takeover of its #police department as crackdown intensifies

The nation’s capital sued to block Trump’s takeover of its PD in court on Friday, hours after his admin escalated its intervention into the city’s law enforcement by naming a federal official as the new *emergency* #PoliceCommissioner.

#law #MilitaryState #authoritarianism #autocracy #tyranny #coup #TrumpCoup2
#DC #DCAG #MPD #PamBondi #MurielBowser
https://apnews.com/article/washington-dc-trump-federal-police-takeover-lawsuit-eacd387053520c9e3640c2f91924deeb?utm_source=onesignal&utm_medium=push&utm_campaign=2025-08-15-Breaking+News

#washingtondc #trump #federal #takeover #police #policecommissioner

🇩🇪 🇺🇦 🇨🇦:nonazis: @[email protected] · 2026-05-13 · 11:31 UTC

#Diplomacy ??? Really?

"Pentagon considering renaming Iran war ‘ #Sledgehammer ’ if ceasefire collapses ~ A White House official tells NBC News says any new military combat operations against Iran would be conducted under a new name and operation."

#News #Politics #Nato #War #USA #Escalation #Europe #EU #Incompetence #Canada #INFLATION #Economy #Consumer #Finance #Poverty #Food #Democrats #Iran #OilShock #Cars

https://www.nbcnews.com/politics/national-security/pentagon-considering-re-naming-iran-war-sledgehammer-ceasefire-collaps-rcna344630

#diplomacy #sledgehammer #news #politics #nato #war

Afrika @[email protected] · 2026-05-13 · 07:25 UTC

https://www.europesays.com/afrika/16520/ Namibia: Vier Deutsche sterben bei Flugzeugabsturz – „Keine Überlebenden“ #Dieter(Unternehmer) #Flugzeugabstürze(Geo:Absturzort)(ks) #Kaufland #Lidl #Namibia #Newsteam #Schwarz #texttospeech

#texttospeech #schwarz #newsteam #namibia #lidl #kaufland

Afrika @[email protected] · 2026-05-12 · 10:42 UTC

https://www.europesays.com/afrika/16243/ Keine Überlebenden: Nach Flugzeugabsturz: Trauer um Familie aus Bad Rappenau #Afrika #BadRappenau #DieterSchwarz #Flugzeugabsturz #Heilbronn #Katastrophe #Kaufland #Namibia #RichardLohmiller #SilkeLohmiller #Urlaub

#urlaub #silkelohmiller #richardlohmiller #namibia #kaufland #katastrophe

Afrika @[email protected] · 2026-05-12 · 01:06 UTC

https://www.europesays.com/afrika/16052/ Deutsche sterben bei Flugzeugabsturz: Kontakt brach fünf Minuten vor Landung ab | News #DieterSchwarzStiftung #Flugzeug #Flugzeugabsturz #Flugzeugabstürze #Kaufland #Namibia #TeamFirst

#teamfirst #namibia #kaufland #flugzeugabsturze #flugzeugabsturz #flugzeug

Afrika @[email protected] · 2026-05-13 · 04:26 UTC

https://www.europesays.com/afrika/16483/ Keine Überlebenden: Vier Deutsche bei Flugzeugabsturz in Namibia getötet #AA #Desert #DieterSchwarz #Flugzeugabsturz #Heilbronn #Lidl #Namibia #Propellermaschine #Reise #SilkeLohmiller

#silkelohmiller #reise #propellermaschine #namibia #lidl #heilbronn

Africa @[email protected] · 2026-05-13 · 20:54 UTC

https://www.europesays.com/africa/233331/ Evolve Royalties Announces Closing of Previously-Announced Acquisition of Tin Royalty on the Uis Mine in Namibia #Acquisition #announces #closing #Evolve #in #MINE #Namibia #of #on #PreviouslyAnnounced #royalties #Royalty #the #tin #Uis

#uis #tin #the #royalty #royalties #previouslyannounced

Paria sans portefeuille @[email protected] · 2025-08-05 · 04:42 UTC

#UncivilizedMedia | A History of Forced Starvation, Explained

a #documentary by Tala Kaddoura

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

#film #courtMétrage #Gaza #GazaGenocide #GazaFamine #Palestine #Ireland #GreatFamine #IrishFamine #Namibia #HereroAndNamaGenocide #WarsawGhetto #Holocaust #colonialViolence @film @palestine @israel

#courtmetrage #uncivilizedmedia #documentary #film #gaza #gazagenocide

Paria sans portefeuille @[email protected] · 2025-08-05 · 04:42 UTC

#UncivilizedMedia | A History of Forced Starvation, Explained

a #documentary by Tala Kaddoura

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

#film #courtMétrage #Gaza #GazaGenocide #GazaFamine #Palestine #Ireland #GreatFamine #IrishFamine #Namibia #HereroAndNamaGenocide #WarsawGhetto #Holocaust #colonialViolence @film @palestine @israel

#uncivilizedmedia #documentary #film #gaza #gazagenocide #gazafamine

Paria sans portefeuille @[email protected] · 2025-08-05 · 04:42 UTC

#UncivilizedMedia | A History of Forced Starvation, Explained

a #documentary by Tala Kaddoura

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

#film #courtMétrage #Gaza #GazaGenocide #GazaFamine #Palestine #Ireland #GreatFamine #IrishFamine #Namibia #HereroAndNamaGenocide #WarsawGhetto #Holocaust #colonialViolence @film @palestine @israel

#uncivilizedmedia #documentary #film #gaza #gazagenocide #gazafamine

Martin Junius @[email protected] · 2026-05-11 · 16:08 UTC

Oddball Planetary Nebula https://photo.m-j-s.net/blog/2026/05/oddball-planetary-nebula/

PGC 49877 / Fr 2-8 - Galaxy / Planetary Nebula in Centaurus - OSC v1

Imaged at the IAS Hakos Observatory, Namibia with the 20" Philipp Keller Cassegrain at full focal length of 4500 mm, f/9, this oddball object is listed both as a galaxy (PGC 49877) an...

#astrofotografie #astronomie #astronomy #astrophotography #Centaurus #EN #Fr2-8 #hakos #ias #namibia #PGC49877 #photoblog #PlanetaryNebula

#astrofotografie #astronomie #astronomy #astrophotography #centaurus #en

Martin Junius @[email protected] · 2026-05-11 · 07:25 UTC

Cometary Globule CG 19 https://photo.m-j-s.net/blog/2026/05/cometary-globule-cg-19/

CG 19 - Cometary Globule in Centaurus - OSC v1

Results from the second night at the IAS observatory on the Gamsberg plateau with the 28 inch Newtonian "Wolf-Peter-Hartmann-Teleskop", adding to my growing catalog of cometary globules.

Alas, sky flats at dusk did...

#astrofotografie #astronomie #astronomy #astrophotography #Centaurus #CG19 #CometaryGlobule #EN #gamsberg #ias #namibia #photoblog

#astrofotografie #astronomie #astronomy #astrophotography #centaurus #cg19

Search