<feed xmlns='http://www.w3.org/2005/Atom'>
<title>feedreader.git/app/src/main/res/xml/network_security_config.xml, branch master</title>
<subtitle>FeeDreader — personal Android RSS reader
</subtitle>
<id>https://git.terst.org/feedreader.git/atom?h=master</id>
<link rel='self' href='https://git.terst.org/feedreader.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.terst.org/feedreader.git/'/>
<updated>2026-08-22T01:08:35+00:00</updated>
<entry>
<title>Cleartext exception for 2 feeds with no working HTTPS</title>
<updated>2026-08-22T01:08:35+00:00</updated>
<author>
<name>Peter Stone</name>
<email>thepeterstone@gmail.com</email>
</author>
<published>2026-08-22T01:08:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.terst.org/feedreader.git/commit/?id=3b8af4faeca81cb598ad3d366d64d8148534d150'/>
<id>urn:sha1:3b8af4faeca81cb598ad3d366d64d8148534d150</id>
<content type='text'>
webpolicy.org and bit-player.org are genuinely alive but have no
working HTTPS at all (confirmed live, not a config mistake -- see
AppDatabase's v7/v8 migration comments for the investigation).
Everything else stays cleartext-blocked, same as the platform default
with no config at all. Isolated to just this file plus the one
networkSecurityConfig line, so both domains (or this whole exception)
can be removed cleanly if these feeds are ever dropped.
</content>
</entry>
</feed>
