europesays.com/uk/263321/ Trump to meet NATO secretary general as plan takes shape for Ukraine weapons sales – National #DonaldTrump #EU #Europe #NATO #U.S.News #Ukraine

"Democrats shouldn’t be afraid to name names. How many more lives might have been saved if Texas Republicans hadn’t stopped their state from improving its emergency alert systems, and if the Trump administration hadn’t ordered drastic cuts to the National Weather Service? How many will be killed by those cuts moving forward?"

~ Kate Aronoff

#Trump #Republicans #Texas #NWS #NOAA #FEMA #ClimateChange
/1

newrepublic.com/article/197662…

in reply to William Lindsey

"How many fewer homes would have been destroyed if congressional Republicans hadn’t spent decades stopping bills to reduce planet-heating greenhouse gas emissions on behalf of their donors in the fossil fuel industry like ExxonMobil? How many more people will face homelessness or financial ruin because the Trump administration is gutting the Federal Emergency Management Agency?"

#Trump #Republicans #Texas #NWS #NOAA #FEMA #ClimateChange
/2

in reply to William Lindsey

Sen. Ted Cruz slashed $200M in weather and climate forecasting funds, then vacationed in Greece as deadly floods killed over 100 in Texas—critics say his actions weakened early warning systems, worsening the disaster and prioritizing Big Oil over public safety.

~ Aaron Parnas

#Trump #Republicans #Texas #TedCruz #NWS #NOAA #FEMA #ClimateChange
/3

aaronparnas.substack.com/p/new…

in reply to William Lindsey

"Two days after catastrophic floods roared through Central Texas, the Federal Emergency Management Agency did not answer nearly two-thirds of calls to its disaster assistance line, according to documents reviewed by The New York Times."

~ Maxine Joselow

#Trump #Republicans #Texas #TedCruz #NWS #NOAA #FEMA #ClimateChange
/4

nytimes.com/2025/07/11/climate…

in reply to William Lindsey

The names of the billionaires funding climate denial for personal & partisan gain.

Bradley, Koch, Coors, Scaife Mellon, Seid and Uihlein.
desmog.com/2024/10/25/project-…

And it's international
desmog.com/2025/01/21/mapped-d…

desmog.com/2024/06/12/mapped-t…

On C-SPAN's Book TV:

"Dr. Robert Malone talked about his book, PsyWar: Enforcing the New World Order, in which he argues that the U.S. government uses psychological warfare against Americans to control them."

c-span.org/program/qa/dr-rober…

Netanyahu Says Israel Eyes 60-Day Deal to Secure Return of Half of Captives #Palestine palestinechronicle.com/netanya…

Maybe the best post I have seen about the Kerr County flooding;
So Who’s to Blame?
Flash floods have always been part of life in the Texas Hill Country. We get those alerts on our phones - the kind that blare like Amber Alerts - nearly every time the skies darken. For most of us, it means avoiding low-water crossings, watching the rain gauge fill, and hoping maybe, just maybe, our thirsty lakes will drink their fill.
But this was different.
What came in the night wasn’t just rain, it was a reckoning. A violent, rising wall of water that didn’t knock, it broke down the doors.
Meteorologist Travis Herzog put it simply: flash floods are among the hardest weather events to predict. “No meteorologist could have told you with high confidence more than a few hours in advance that this much rain would fall in those exact locations,” he said. Even with double the normal staff at the monitoring station for our region, no model foresaw the worst, because what happened was beyond the worst-case scenario.
The atmosphere defied the forecasts. The storms exceeded even the worst projections of the computer models both in coverage and amounts of heavy rain. Still, the National Weather Service issued warnings as the event unfolded in real time. A flood watch went out at 12:41 a.m., forecasting up to seven inches of rain. Then, at 4:03 a.m., a flash flood emergency: Evacuate immediately. Seek higher ground.
But by then, in places like Kerrville, Hunt, Center Point, Streeter, and Ingram, tiny towns tucked in the folds of the Hill Country, it was already too late.
The Guadalupe River rose 34 feet in two hours.
Imagine that. Thirty-four feet. In darkness. While people slept. In homes tucked far from cell service, on land where neighbors are separated by acres, not fences. The water came with rage. A half foot higher every minute. Carrying trees, metal, cars, walls. It tore buildings from their foundations. It erased entire RV parks. It killed.
And now, more than 100 people are gone.
So who’s to blame?
That question has begun to echo across social media, in hushed conversations, in angry ones. People want someone to point at. Someone to hold responsible for the unbearable weight of loss. But I urge you to pause.
Because I remember a flood like this. Ten years ago, when my own hometown of Wimberley was ravaged in the night by another flash flood. Entire families swept away. Homes ripped off their slabs. Our beloved Blanco River turning into a monster.
And back then, we didn’t ask who was to blame.
We cried. We prayed. We showed up.
We linked arms - strangers, neighbors, friends. We searched the riverbanks. We rescued pets from crumbling homes. We passed out hot meals, clean water and diapers. We took in the displaced, fed the volunteers, wrapped the grieving in blankets. We were #WimberleyStrong, not because we looked for someone to blame, but because we looked for someone to help.
That’s the choice in front of you now.
You can rage. Or you can reach out.
You can look for fault lines, or you can look for someone to help.
This flood was no one’s fault. It was a freak convergence of nature’s fury - unpredictable, unstoppable, and unforgiving. But what happens next is in our control. That’s where our power lies.
So go. Volunteer with search crews combing the riverbanks. Give to organizations that are on the ground: The Community Foundation of the Hill Country, Mercy Chefs, The Cajun Army, Team Rubicon, Austin Pets Alive. Cook meals. Hold hands. Open your wallet. Open your heart.
Tell your children you love them. Tell your neighbors you’re here. Tell the broken they are not alone.
Tragedy has come. That part is done. What we do now - who we are now - that’s the story still being written.
Let it be one of grace. Of grit. Of fierce love in the face of grief.
Let it be the kind of story that proves: the Hill Country may flood, but it does not fall.
Say what you will about Texas - but when the rivers rise, so do we.
Not with blame. Not with bitterness.
But with boots on the ground, arms around strangers, and hearts wide open.
That’s the Texas I know. And that’s the America I believe in.
Authored by Bex Hale

Boy 'raped by teacher from the age of 14 comes forward' Boy 'raped by teacher from the age of 14 comes forward' dailymail.co.uk/news/article-1…

BBC -Donald Trump has formally accepted an invitation from King Charles III to join him and Queen Camilla for an unprecedented second state visit, set to take place Sept. 17-19. The US president will be hosted at Windsor Castle. bbc.com/news/articles/c4g25ne7…

04:52 Palestinian Ministry of Health: The death toll from the Israeli aggression has risen to 58,026 martyrs 138,520 injuries since the beginning of the assault on Gaza. english.masirahtv.net/news/368…

What if vaccines do not increase or decrease autism rates but there is a correlation between the personality or genetics of the type of parents that accept or refuse vaccines and that personality influences the choice of whether or not the child is vaccinated but also influences whether or not the child gets a autism diagnosis. And whether or not the child gets a diagnosis depends on the parents attitude towards autism testing.

Pro vaccine parents do not tolerate unique children as often?

So if they are trying to eliminate diseases then why don't they give everyone pills to eliminate parasites like intestinal worms or pin worms or tape worms or hook worms

If worms are so rare they do not need to test for them then they should be easier to eliminate from the world

But I ask you, how easy would it be to spread poop based worms in India or for Indian visitors to spread them?

#Flaming Ember flashback
My Pa is with his moonshine friends
Drinkin Deacon Jones' bathtub gin
Deacon Jones (L.A. Ram lineman back then) preachin' about savin' souls
Yellin' out how the whole town is full of sin
But like Pa and all the rest
He tries to look down Bobbie Sue's low-cut dress
...............Westbound number 8
youtu.be/vO0v8p6rSTU?si=XbDg3h…

Eyewitness to History: The 1980 Eruption of Mount St. Helens


Author note: This article contains the memory of my great-grandfather Charles Mulvey who was working on the Hanford Site near Richland, Washington when Mount St. Helens erupted. A few days after the eruption, he wrote this short essay about his experience. It was recently found by my aunt Diane Izzo when she was looking through family effects. The text provided below has no alterations from the original.

May 20, 1980

Well, the Spirit Mountain did as the Indians have been telling us it would do. It spoke real loud and was heard as far as Spokane anyway. It seems Mount St. Helens still has a lot of life left.

So I guess I’ll make an attempt to give some of the sights, impressions, and feelings which I observed and felt during and after the eruption which occurred this past Sunday, May 18, 1980.

Ingalls Weather thanks the support it gets from donors. Please consider making a small donation at this link to help me pay for the website and access to premium weather data.


Mount St. Helens has been gradually changing from its former inactive status to active with mostly relatively mild eruptions and steam, ash emissions. The officials concerned and those persons observing the volcano have repeatedly given warning of the serious potential of a major eruption.

Sunday morning at approximately 0830 a.m. Mount St. Helens erupted with an explosion which blew the top 1300 feet off of the mountain and formed a horseshoe shaped crater. A huge cloud of ash and debris was reportedly blown to an altitude of 60,000 feet.

Type your email…

Subscribe

I was at work and doing my job assignment this day. I heard the blast and thought that that was no sonic boom but possibly a large dynamite explosion. The time is not definite but seemed to be just before 0900 a.m.

There was earth movement reportedly felt by others, however I felt no movement of which I was aware.

I continued with my work routines and sometime near 1000 I noticed the western sky getting dark and appeared smoky as if the fruit growers in the Yakima Valley were fogging to save the fruit crop. Of course, the day had started out clear, sunny and warm. Fruit fogging was out of the question.

The sky continued to darken rapidly and a radio transmission was heard telling all listeners that Mount St. Helens had erupted. More information would be transmitted as it was received.

By 1030 the sky was rapidly being covered with a huge, flat bottomed cloud which eventually covered all visible horizons completely blacking out the sun.

My job assignment was partly the responsibility of watching a pumping operation and the recording of operational data. At the 1100 time for a check of the pump and data the cloud had covered the sun and the northern and southern horizons and all except the east portions.

The westward facing field lamps were being activated. These field lamps light up with detection by a photo cell of approaching dark conditions.

By the time I had completed my periodic check of the pump operation and returned to the building, full darkness had occurred and the fallout of volcanic ash was underway. The darkness was equal to that of a moonless, starless, possibly cloudy stormy night.

During the next two hours the ash fall continued, with an appearance of a dry rain, if such were possible. The particles of ash ranged from a fine powder to a coarse sand. The coarse, sandy material was heavy, and the fine powdery material is extremely light, almost a talcum powder.

At the 1300 time check of the pump, the ground and all horizontal exposed surfaces were covered with ash to a depth range from one-eighth to one-quarter inch deep. The ash was evenly distributed and created considerable dust when vehicles were driven.

Light conditions at 1300 required use of a flashlight to observe numbers and dials. The pump incidentally was stopped at 1315 hours due to the hazardous conditions.

The ash fall continued heavy until approximately 1430 when the sky lightened again to daylight. A light dust ash fall continued. A dusty haze filled the air and it was necessary to don dust filters or face masks for working outside. Some samples of ash were taken for souvenirs at this time.

The light ash fall continued for the remainder of the day and possibly throughout the night. A souvenir ash sample of this light ash fall was taken the following morning from a surface which was clean at the time the initial ash fall samples were taken.

The volcanic ash fall covered a large area of eastern Washington. Roads and highways were closed due to extremely dusty conditions which made driving very difficult. People were warned to stay off the roads and to stay indoors.

The severity of the ash fall was relevant to the depth of the ground cover. This ranged from a trace to several inches. Towns and cities within the fallout area have encountered difficulty with removal of the volcanic ash.

The bus which picked us up at work and transported us home was a casualty of the dusty conditions. Dust clogged the filters and was pulled into the motor which failed due to the abrasive ash. Only the front part of the bus was visible as it approached. It was lost in dust back from the front wheels.

A light ash fall continued the following day with extremely dusty air conditions. Only essential work was being done, and usually only necessary stores (grocery, etc.) were open.

High winds have swept the area since the eruption which continually creates more dust conditions.

The featured image is of the eruption column from Mount St. Helens on May 18, 1980. (USFS)

#Geology #History #TriCities #Volcano #wawx

This entry was edited (2 months ago)

What lesson many Jewish Nazi families "learn" when Nazi goons they sent to commit genocide in Gaza & are sent to burning pits of hell by resistance?

Desire for more Slaughter & Theft

Not even "German" Nazis did these sorts of funerals telling everyone how they'll slaughter & steal

No other group in contemporary society other than Jews can get away with saying Nazi shit like this yet allowed in normal circles.

xcancel.com/ireallyhateyou/sta…

@palestine @lebanon @iran @israel @anarchy @anarchism

This entry was edited (2 weeks ago)

Introduction - Steve's Tutorial on Jujutsu, an alternative front-end to git


Jujutsu is essentially an alternative front-end or "porcelain" to git, both magnificiently simplified and powerful.

I tried it after using Emacs Magit for about six or seven years, and jujutsu is really easier to use than git and useful if one wants a tidy public history of changes (with "tidy" and "public" as Linus Torvalds recommends). Plus it is fully compatible to git as backend - other contributors will not even note you are using it.

This entry was edited (2 weeks ago)
in reply to paequ2

Another useful property is that while jujutsu does have worktrees, like git, in many cases where one would use git worktrees (for example when writing accompanying documentation ) it is just easier to use another line of changes (what is a branch in git).

Alas, that jujutsu does not store local change sets automatically on a remote git repo (this happens only when you update and push a git branch), means that still-mutable local changes are not automatically transferred to another computer you work on. And unpublished changes are naturally mutable in jujutsu. But you can safely copy a jj repo via rsync, as changes in jj metadata are thread-safe and atomic. The other way is of course to push a work-in-progress ("WIP") git branch which can mutate and is therefore not allowed to be merged by other people.

This entry was edited (2 weeks ago)
in reply to HaraldvonBlauzahn

That’s not really how one would use worktrees in git. Worktrees are useful in the case when e.g. you are working on version 0.15 of your software that has many breaking changes to version 0.14 (perhaps even on a build system level) and you need to release a 0.14.1 patch. Worktrees separate directories which means you don’t need to stash or do a wip commit, nor clear you 0.15 build artefacts. Just cd to a different worktree, checkout the 0.14 branch, create and checkout the 0.14.1 branch, clear build artifacts in a different directory from your main development one, and start working.

When done, just cd back and keep working again without switching branches, clearing artifacts, or doing full rebuilds of the in-development 0.15 version.

Plus, git does not store change sets or branches or anything on any remote unless you push them either, so if you’re having that problem just stop pushing things you don’t want to push. You can totally rsync a git repo, just ensure it’s at rest. Otherwise do what you should be doing anyway: set the repo on another machine as a remote of the other repo, so you can git pull my_private_machine feature/my_private_branch without needing to push to a central repo.

I’m sure jujutsu has many advantages, but it also reads to me like you’re misunderstanding the git model. Which can be a fair critique of git to be fair, but then we would need to talk about what about the git model people have trouble with, why, and how to address those issues, and so far I haven’t seen any kind of research in that direction from jujutsu (not that I’ve been looking particularly hard)

This entry was edited (2 weeks ago)
in reply to ugo

One difference between using worktrees and branches in git is that in git you usually have uncommited stuff that's not finished, and worktrees are a way to avoid committing this. And you want to avoid committing early because it is hard to clean-up later. This hesistsnce to commit is not necessary at all in jujutsu - any change to the source files is already captured and will be restored once you go back to that changeset. There are other cases where you use worktrees in git e.g. to isolate a build and an hour-long integration test running it in parallel to your ongoing work, and in thar cases, you'd use workspaces in jujutsu like you'd in git.

but then we would need to talk about what about the git model people have trouble with, why


Too many commands that do subtly and irreversivly things on the repo, with potentially messed-up interim states, only to do the conceptually much simpler task to edit and manipulate the directed acyclic graph of commits.

In short, jujutsu is a commit graph editor and does the same with perhaps 10% of the complexity of git. The man pages on the git reset, branch and merge commands are already larger than the whole - and detailed!- documentation of jujutsu.

Steve Klabnik explains this much better than I can here in his blog that I posted.

This entry was edited (2 weeks ago)
in reply to HaraldvonBlauzahn

It is simply not my experience that cleaning up commits after committing early is difficult in git. Amending a commit is a single -a flag away from the git commit command. The opposite problem is when you do too much work and want to split it into multiple commit rather than a huge one, in which case git add -p is again a single flag away from git add.

In general, git’s entire model is to allow you to work first, and do administrative tasks (including tidying up your commit history etc) later.

And almost nothing is truly destructive in git, the vast majority of cases can be fixed by judicious use of git reflog.

The only cases I’ve ran into where git repos became corrupted were caused by external tools, mainly GUIs that label buttons with git commands that do something different when clicked (like the button labeled push actually doing git push —all for no good reason, and such things) with users that have no idea how git works that have been trained just by telling them “click this to save your work, click this to get the last version of the code”

in reply to paequ2

Technically true - but it looks like jj does a lot of history re-writing which would require a lot of care to be taken when working on a shared codebase.

The page on remotes has some cautions in it.

We need the --allow-backwards flag to set the trunk branch to the previous commit because it is a dangerous operation: if we had pushed trunk, things would get weird when we try and push now. We've kept it all local, so there's no issues with doing this.
in reply to HaraldvonBlauzahn

Hrm... It looks interesting but it seems too dedicated to crafting "the perfect commit".

Changing our description changed the commit ID! This is why we have both IDs: the change ID has not changed, but the commit ID has. This allows us to evolve our commit over time, but still have a stable way to refer to all versions of it.


I don't want to "evolve a commit" - I want to capture my changes over time. If I decide later that I want to prepare the commit for merging I will.

I hate it because it's different - but even trying to give it a "benefit of the doubt" I really can't see this as better. It's not like it's difficult to create a "tidy" commit with git as is.

And as far as "easier to use goes"... well... Here's how you get a list of anonymous branches

jj log -r 'heads(all())'

And since they eschew branches with names you get to memorize hash strings instead of branch names that describe the thing you were doing?
jj new pzoqtwuv yykpmnuq -m "merge better documentation"
# vs. 
git merge my_branch_Name

I'm unconvinced. Though jj undo looks neat (and also crazy dangerous unless you can undo an undo?).
This entry was edited (2 weeks ago)
in reply to atzanteol

And since they eschew branches with names you get to memorize hash strings instead of branch names that describe the thing you were doing?


No trouble, you can still name branches if you want. And no, you don't have to type the whole changeset hash, the first one to three letters are usually sufficient.

Also, branch names are not a permanent thing, they disappear after you merged them.

If you want, to can put an empty commit with the description of what you want to do at the top of your changes, and then use "jj split" to move changes to different commits before it.
There are several common work flows which are explained in Klabnik's blog post.

in reply to HaraldvonBlauzahn

If the readability of the commit history really does not matter to you - for exsmple, nobody needs to read this code again - it’s possible that jj does not give you enough advantage. Everyone works different.


I mean... It does and I will use git to manage commit histories as necessary. I don't see jj as solving that problem or even making it easier. Doing a single squash-commit or a rebase -i when I merge a branch is relatively trivial.

And from what I can tell it's much easier to do a git pull upstream master than to do jj new skdfsld dskfjas since you'll likely have to lookup those hashes? I mean I wouldn't remember them.

in reply to HaraldvonBlauzahn

One takes them from the last commit log and uses the first few letters


So - it's not the length of the random garbage that is the issue it's the fact that it's random garbage that I have no chance of remembering after 5 seconds and switching between branches. All my branches are instead random hashes that I'll need to lookup or remember.

I've read through the blog. It sounds like they've taken the minor inconvenience of doing a git merge --squash and distributed that pain across every-single-commit you're ever going to make instead. All to get "tidy commits" which were possible before anyway.

I was actually rather interested in the idea of jj being something that made history-rewriting easier (e.g. for removing bad commits with passwords and the like). But the fact that it almost completely throws out the entire concept of working on named branches (yes you can have them - but "One interesting thing about branches in jj that's different than branches in git is that branches do not automatically move." - genius) is just ridiculous. And to claim that it's now simpler just seems like gaslighting.

#Flaming Ember #55 years
Give my mind to you with a love that'll never grow old
You are my smiles the last tears
You are my days, my weeks, my years
You are the flowers beneath my window sill
You are everything beautiful everything that's real
I give my love to you all my body and soul
youtu.be/5M91JHi3gZc?si=rjpNOL…

If you still think that #Apple cares for the #privacy of its paying customers:

Apple Gave #Governments Data on Thousands of Push #Notifications
404media.co/apple-gave-governm…

With companies like that, you're the product although you pay premium money.

#iOS #iPhone #security

Looking for a music player


I'm looking for a music player on Pop!_OS that supports playlists, repeating a single track while still being able to swap tracks in the playlist, and also supports fading between songs and when stopping playback. And ideas on what to try?

So far I've tried VLC, Audacious, and Rhythmbox, but none of those seem to support all of those requirements. (Rhythmbox was close but the repeat one from the toolbar plugin doesn't work.)

Edit: Got it working in Rhythmbox after toggling the repeat options a few more times. Still curious if there are other options out there though.

This entry was edited (2 weeks ago)

Johan Messely
#art, #peinture #Johan-Messely
Fraicheur sous la varangue...

I'm pro-union and pro-international workers associations for better conditions or anticapitalist antifascist activism, this government deliberately trying to gaslight workers at fault for something caused by bosses/ceos/governments internationally, riots are a language of the unheard and downtrodden.

abc.net.au/news/2025-07-14/qld…

#cfmeu #classwar #queensland #qldpol #qldgov #qld #australia #humanrights #eattherich #ausgov #auspol #tasgov #taspol #politas #antiwork #antislavery #fuckwork #slavery

My aunt is currently in the middle of a major
sundown" episode due to a relief caregiver not giving her her meds at the right time.

I am home in Fort Worth and am in contact with the caregiver and a really good neighbor who are with her. There is nothing we can really do until she settles down (law will not allow anyone to force medication on her).

If you have the time, please pray for the caregiver and the neighbor friend as they deal with this.

Thank you in advance.

reshared this