The State of the "X" OSINT Community,
a message to the 'OSINT' accounts.
Let’s all take a step back and look at the broader “OSINT” community, especially after Elon Musk’s changes.
What do we actually see?
Engagement Farmers.
The majority of these accounts claim to do OSINT and even include it in their name. But most of them don’t do the work. At best, they’re bad news aggregators — copying and pasting information without citing sources, rewriting descriptions to grab attention, and shaping opinions based on unverified data. They chase attention, not accuracy. In other words, they’re engagement farmers.
These accounts make up most of what’s now labeled as “OSINT.”
News aggregators.
Then there’s a second group — the news aggregators who at least add some value. They collect and organize information into threads or perform basic analyses that make data easier to understand. Importantly, they also give proper credit to the original sources. For them, it’s not about being the first to post — it’s about gathering reliable information and presenting it clearly and responsibly.
OSINT.
Finally, there are the 'real' OSINT accounts.
A definition: "OSINT is the practice of collecting, analyzing, and interpreting publicly available information from open sources to produce insights for decision-making, threat assessment, and investigations."
The real OSINT accounts go beyond aggregation.
They verify locations, identify equipment types, and perform full investigations — turning raw data into actionable, verified insights.
Mistakes.
And yes, even OSINT accounts make mistakes. Why?
Because OSINT is only as accurate as the information available at the time of analysis. That’s why verifying the basic data used in any analysis must always be a priority. Crediting sources is equally important — it allows others to understand the reasoning behind the analysis and, if necessary, to verify the same sources independently.
When new information emerges, earlier conclusions may turn out to be flawed. It’s then the responsibility of the OSINT account to evaluate whether the new data impacts the final assessment. If it does, the correct course of action is clear: delete the original post and start again. Deletion is the only acceptable response when an error alters the conclusion.
GeoConfirmed.
We know where we stand:
GeoConfirmed is a verification community of more than 100 volunteers, dedicated to answering factual “where” questions.
Does that make us an OSINT account? That’s not for us to decide.
In four years, GeoConfirmed has made seven mistakes — just seven. Each time, we reviewed our verification process, because seven out of more than 60,000 published geolocations is still seven too many.
That’s the level of responsibility our admin team has committed to. We guarantee where something happened — not what happened, and not when. With the exemption for our 'investigations' where we used the geolocation as a basis for a further analysis.
And in every one of those seven cases, we deleted our tweets and posted corrections.
How many accounts, even 'OSINT' accounts, get fact-based feedback, even Community Notes, but never make corrections? For them, it’s not about the facts. The initial tweet draws attention — and that’s what matters most to them.
How to handle mistakes.
Everyone can make mistakes. There is only one correct response to a mistake: delete the tweet and post a new one with the correction.
Let’s be very clear about this. Accounts that post a “correction” in a follow-up tweet are still benefiting from the attention generated by the original post. They aren’t prioritizing facts — they’re preserving engagement. The correction will never reach as many people as the original tweet, meaning the misinformation or disinformation continues to spread.
Deleting the mistaken tweet and reposting it with the correct information is the only responsible solution.
---
So, if you call yourself an OSINT account, ask yourself this:
Am I part of the third group? Am I doing what should be expected from an OSINT account?
If the answer is no, then you are not an OSINT account and shouldn’t present yourself as one. Unless you take concrete steps to meet the standards of real OSINT work, you’re not contributing to the field: you’re merely chasing attention under a false label. That doesn’t make you an OSINT account — it makes you a fraud, using OSINT for attention, and adding noise instead of value.
---
Pictured:
GeoConfirmed’s admin team verified geolocations conducted by the GeoConfirmed volunteer community, as well as contributions from other volunteers, related to the Ukraine–Russia conflict.
Over 50,000+ GeoConfirmed locations where events occured.
(https://t.co/IJABboi2yG)
@usf_army@GeoConfirmed@UAControlMap
45.3346, 36.4662 0:11-0:32 Kerch oil terminal hit and on fire
see also:
https://t.co/Q1OQoUMHkD
https://t.co/R0vlfxAqLJ
🔥 USF Struck an Oil Depot, Gas Infrastructure, Radar Systems, and Enemy Logistics
During the night of June 21, operators of the Unmanned Systems Forces struck fuel infrastructure, radar assets, gas compressor stations, and enemy transport in the operational depth of temporarily occupied territories of Ukraine.
Operation highlights:
In Crimea, operators of the @1usc_army struck the oil depot of the Kerch oil terminal.
In Crimea, operators of the 1st Separate Center struck a Kasta-2E2 radar system near Kurortne and a Nebo-U radar system near Kerch.
In Crimea, operators of the 9th Kairos Battalion of the @414magyarbirds struck gas compressor stations near Aromatne, Zhuravlivka, and Kliuchi.
In Donetsk Oblast, operators of the @k_2army Brigade struck a fuel tanker carrying petroleum products near Horlivka.
In Zaporizhzhia Oblast, operators of the 412th Nemesis Brigade struck enemy logistics transport near Osypenko and Terpinnia.
Systematic strikes against fuel infrastructure, radar assets, and logistics reduce the enemy’s ability to sustain its forces, support movement, and protect facilities in temporarily occupied territories.
USF: One step ahead!
@Osinttechnical New footage confirms that an errant Russian surface to air missile was responsible for the tank roof toss at the Moscow Oil Refinery this morning.
POV 55.642442, 37.853616
Tank hit likely 55.652891, 37.809835
@GeoConfirmed@UAControlMap@AndrewPerpetua
GeoConfirmed conflictmap UKR.
Fire at a building building of the 126th Separate Coastal Defence Brigade, aftermath of a reported Ukrainian strike that was carried out using 2 missiles and 2 jet UAVs.
44.839836, 34.331322
R8QJ+MCW Chaikovs'ke
GeoLocated by @MikiValbuena
Reported involved units:
126th Separate Guards Coastal Defence Brigade ▸ 18th Combined Arms Army ▸ Southern Military District ▸ Russian Ground Forces
Geolocation:
https://t.co/g6b3I8MoMd
Location:
https://t.co/OBf7BsoO7T
Sources:
https://t.co/3zYiWdGngb
(1/4)
https://t.co/THv5kmrFEe
More information
https://t.co/Pk3vpf7XU3
Visit our map: https://t.co/g9OP1aPlGP
Additional footage & damage to a second barracks
on a Russian base, near Pereval'ne TOT Crimea
44.839227, 34.331089
R8QJ+MCW Chaikovs'ke
@GeoConfirmed@UAControlMap@AndrewPerpetua
Source: https://t.co/87HDM5TzN7
media 2/4 &3/4
GeoConfirmed conflictmap UKR.
Damaged building of the 126th Separate Coastal Defence Brigade, aftermath of a reported Ukrainian strike that was carried out using 2 missiles and 2 jet UAVs.
44.839227, 34.331089
R8QJ+MCW Chaikovs'ke
GeoLocated by @neonhandrail
Reported involved units:
126th Separate Guards Coastal Defence Brigade ▸ 18th Combined Arms Army ▸ Southern Military District ▸ Russian Ground Forces
Geolocation:
https://t.co/3QgNTcmBEG
Location:
https://t.co/qgBRzgZyJR
Sources:
https://t.co/vFoqNS2ONI
(2/4&3/4)
https://t.co/THv5kmrFEe
SAT
https://t.co/KddDqkjzm0
More information
https://t.co/Pk3vpf7XU3
Visit our map: https://t.co/g9OP1aPlGP
USF Struck a Svetlyak-Class Patrol Ship, a Pantsir-S1 Air Defense System, an RSBN-4N Navigation System, Logistics Assets, and Other Enemy Targets
Operation highlights:
🎯 In temporarily occupied Crimea, operators of the @1usc_army struck a Project 10410 Svetlyak-class border patrol ship used for coastal patrol and maritime surveillance missions.
• In Kherson Oblast, operators of the @1usc_army destroyed a Pantsir-S1 air defense missile and gun system, one of the key components of the enemy's air defense network.
• In temporarily occupied Crimea, operators of the @1usc_army struck an RSBN-4N short-range radio navigation system used to support enemy aviation.
• In temporarily occupied Crimea, operators of the @Raid_413 struck locomotives used to sustain enemy military logistics.
• In Donetsk Oblast, operators of the @k_2army Brigade struck transformers supporting enemy military infrastructure.
• Also in Donetsk Oblast, operators of the 1st Separate Center struck fuel storage tankers.
The operations were conducted in coordination with the USF Deep Strike Center.
The Unmanned Systems Forces continue to systematically degrade the enemy’s combat capabilities by targeting air defense assets, logistics infrastructure, and critical command-and-control systems.
USF: One step ahead!
GeoConfirmed conflictmap UKR.
Point of view looking in a northern direction - Fire and huge plumes of smoke at he Ust-Labinsk oil depot following a reported Ukrainian attack.
45.219355, 39.683064
6M9M+P6W Ust-Labinsk, Krasnodar Krai, Russia
GeoLocated by @neonhandrail
Geolocation:
https://t.co/WI5qdvxTzm
Location:
https://t.co/JrjGrvnCOZ
Sources:
(2/2)
https://t.co/dsxuhmImKb
(2/2)
https://t.co/tl1IzeP1Dd
More information
https://t.co/EqBZsBcDKD
Visit our map: https://t.co/g9OP1aPlGP
GeoConfirmed conflictmap UKR.
Reported Russian Pantsir-S1 air defense system being airlifted by a Mi-26 helicopter onto the rooftops of a high-rise building in Moscow. Another helicopter is visible in the video.
55.78822, 37.677713
QMQH+73P Sokolniki District, Moscow, Russia
GeoLocated by @Zeldamices
Geolocation:
https://t.co/b5MfV1w1Bq
Location:
https://t.co/Q6CSQhWh0m
Sources:
https://t.co/y3LhnhKA8m
Visit our map: https://t.co/g9OP1aPlGP
16º Cuerpo
Kamaz RU destruido. Puente sobre el río Vovcha el 3 de junio.
50.292920, 36.945975
Vovchans'k - Kharkiv Ob
@GeoConfirmed@UAControlMap@AndrewPerpetua
https://t.co/JhhGsmtcL2
El 16º Cuerpo🇺🇦 informa que el 3 de junio a las 5:00 los rusos intentaron montar un puente de pontones sobre el río Vovcha y no salió bien, lo evitaron con minas y drones y el vehículo quedó destruido
https://t.co/UHBCxkRb3r