<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Physical-Security on Suspicious Bytes</title><link>https://suspiciousbytes.com/en/tags/physical-security/</link><description>Recent content in Physical-Security on Suspicious Bytes</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 09 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://suspiciousbytes.com/en/tags/physical-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Brandhaardjes: protests and riots on a map, collected by AI</title><link>https://suspiciousbytes.com/en/posts/brandhaardjes/</link><pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate><guid>https://suspiciousbytes.com/en/posts/brandhaardjes/</guid><description>&lt;p&gt;It started with a discussion about physical security. You have a meeting at a client, a visit to an office, or just a day out. Then it turns out there&amp;rsquo;s a protest at the front door that afternoon, a blockade on the route, or worse: riots nearby. Business or private, it affects your visit. Why do we usually only find out once we&amp;rsquo;re already there?&lt;/p&gt;
&lt;p&gt;So I built &lt;a href="https://brandhaardjes.nl"&gt;brandhaardjes.nl&lt;/a&gt;. As a test, really just a test, but also to brush up my programming skills. The name is Dutch for &amp;ldquo;little hotspots&amp;rdquo;.&lt;/p&gt;</description></item></channel></rss>