Relatives of abductees urge Noa Argamani not to fly with Netanyahu: ''He is taking advantage of you.”

[NP]

Netanyahu in the Cabinet:

"The hostages are suffering, but they are not dying"

[NP]

Netanyahu:

I want to share two secrets with you:

1. The pressure I'm talking about should be directed at Sinwar and not at the Prime Minister of Israel.

2. Your pressure on me will not help  

[NP]

In the latest toll: 5 martyrs were murdered as the zionist occupation bombed a group of Palestinians while they were at an internet point, on Al-Bahr Street in the North Beach area, north of Gaza City.

[J]

The New York Times reports that the Zionist military leadership hopes for a ceasefire with Hamas, as it cannot fight on two fronts

"The occupation military leadership hopes to reach a ceasefire in Gaza, even if that would allow Hamas to partially remain in power, in order to focus instead on the cross-border fighting with Hezbollah", The New York Times reports.

[J]

“This is our Lord’s battle...and our Lord will grant us victory in the end.”💚✊


Part of the messages of one of the Qassam fighters during the preparation of the #sudden_ambush, which led to the killing and wounding of a number of occupation soldiers.

[G&T]

🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨Younis Tirawi’s report on the IOF’s maps has dropped - READ IT CAREFULLY and CIRCULATE WIDELY!

An interactive evacuation zone map, touted by the Israeli military as an innovation in humanitarian process, was revealed to rely on a subset of an internal Israeli military intelligence database.

The US-based software developer who revealed the careless error has determined that the database was in use since at least 2022 and was updated through December of 2023.

On Tuesday, July 9th, we discovered an interactive version of the evacuation map while examining a page on the IDF's Arabic-language website accessible via a QR code published on an evacuation order leaflet. The map is divided into "population blocks" an IDF term to refer to the 620 polygons used to divide Gaza into sectors that a user can zoom into and out of.

However each request to the site pulls not only the polygon boundaries but the demographic information assigned to that sector, including which families - and how many members - live there.

𝐃𝐢𝐬𝐜𝐨𝐯𝐞𝐫𝐲 𝐨𝐟 𝐈𝐧𝐭𝐞𝐫𝐚𝐜𝐭𝐢𝐯𝐞 𝐄𝐯𝐚𝐜𝐮𝐚𝐭𝐢𝐨𝐧 𝐌𝐚𝐩𝐬:

Evacuation maps have played a central role in determining which sectors of Gaza were deemed "safe", but repeated instances of Israeli bombing in "safe" sectors has prompted international bodies to state "nowhere in Gaza is safe".

To determine how these sectors have been affected over time, assess the presence of vital civilian infrastructure, and gauge the potential impact on the population following the military's evacuation calls to Gaza City residents, the latest of which was two days ago, our team created a map tied to a database using software known as a "geographic information system” with the help of volunteer GIS developers, our map of Gaza included individual layers for hospitals, educational facilities, roads, and municipal boundaries.

This endeavour took an unexpected turn earlier this week when we started to work on the layer of "evacuation population blocks" using a map shared by the Israeli military's Arabic site. Unlike static images, these maps responded interactively to zooming and panning.

A software developer suggested that dynamic interaction was possible because the coordinates of various "population blocks" were delivered to the browser with each request, potentially retrieving the coordinates of the "population blocks" in real time and overlaying them on the map we were building.

The software developer delved into the webpage's source code —a practice involving the inspection of code delivered to every visitor's browser by the website. The source code of every website is publicly available and delivered to visitors on every page request. It functions "under the hood" of the website and can be viewed without any specialized tools or form of hacking.


𝐏𝐚𝐫𝐬𝐢𝐧𝐠 𝐔𝐧𝐞𝐱𝐩𝐞𝐜𝐭𝐞𝐝 𝐃𝐚𝐭𝐚

Upon examination, the data retrieved by the dynamic evacuation map included much more than just geographical coordinates. The source code contained a table from an unknown GIS database with numerous additional fields labelled in Hebrew. These fields included population estimates for each block, details of the two largest clans in each block (referred to as “CLAN”), rankings based on unknown criteria and timestamps indicating when records were last updated.

Some data terms, such as "manpower_e," were ambiguous for us to interpret, possibly referring to either the number of fighters or the necessary personnel to maintain the area.

Using this information we determined that Block 234, Abu Madin was last updated on 27 April 2022. This suggests that Israel's effort to divide Gaza into 620 "population blocks" began one and a half years before the current Israeli offensive. Additional modification dates indicate that the military updated data in this field regularly throughout October and November, before formally publishing it on the arabic Israeli military webpage on December 1, 2023.

It appears that the IDF has accidentally published experience, security training, or are simply unwilling or unable to meet standard data security requirements for a project.

𝐂𝐥𝐚𝐧𝐬 𝐚𝐧𝐝 𝐀𝐝𝐦𝐢𝐧𝐢𝐬𝐭𝐫𝐚𝐭𝐢𝐨𝐧 𝐏𝐥𝐚𝐧𝐬

In January, Israeli security chiefs proposed a plan for "the day after" where Palestinian clans in the Gaza Strip would temporarily administer the coastal enclave. In this concept, each clan would handle humanitarian aid and resources for their local regions.

Israeli assessments of the proposal suggested such a plan would fail due to "lack of will" and retaliation by Hamas against clans willing to collaborate with the army. The plan has since been modified to include Hamas-free “bubbles,” (as reported by the Financial Times) where local Palestinians would gradually take over aid distribution responsibilities.

As this plan is to be initially implemented in Beit Hanoun and Beit Lahia. Al-Atatrah Area and Beit Hanoun, we have analyzed the information in the database assigned to those three areas Israeli army classified the Al-Atatrah area as region 1741, although there are only 620 'blocks' on the map. The registered population was listed as 949, last updated by the IDF on October 9th. We assume this represents an estimate by the IDF of current residents as of Oct 9th.

Residents of Al-Atatrah were among the first to evacuate following the initial bombardment on \October 7th and 8th and were not given a formal notification to evacuate. The Israeli military noted that the Abo Halima family comprised 54% of the block’s population in area west of the town Beit Hanoun, Israel had designated the Almasri clan as the largest in the sector, consisting 18% of the block's population. Second largest was the Hamad family, with11% of the block's population. This area were also associated with rankings, however without the criteria used to determine the ranking, these numbers are difficult to interpret.


𝐖𝐡𝐚𝐭 𝐝𝐨𝐞𝐬 𝐭𝐡𝐢𝐬 𝐢𝐧𝐟𝐨𝐫𝐦𝐚𝐭𝐢𝐨𝐧 𝐫𝐞𝐯𝐞𝐚𝐥?

Although some of the data were inadvertently truncated during publication, posing challenges for comprehensive interpretation, this database provides a valuable window into the Israeli military's perspective on Gaza.

For one, it prompts questions into why the military had already partitioned Gaza into 620 population blocks a year an a half before October 7th. This suggests an early inclination to implement a governance policy where clans would assume authoritative roles, as well as detailed population surveillance.

Tracking dense populations in the chaos of urban warfare is a difficult task. It may be that the QR code on the evacuation map actively collects the locations of people who scan it, allowing the IDF to collect real-time data on Palestinians in Gaza as they attempt to find safety.

Comment: do NOT USE THOSE MAPS UNDER ANY CIRCUMSTANCE – and spread the message to whoever you know in Gaza.

[RT]