<feed xmlns='http://www.w3.org/2005/Atom'>
<title>telegram/go.mod, branch v0.2.1</title>
<subtitle>Official cep.is Telegram bot - @cepisbot
</subtitle>
<id>http://git.cep.is/telegram/atom?h=v0.2.1</id>
<link rel='self' href='http://git.cep.is/telegram/atom?h=v0.2.1'/>
<link rel='alternate' type='text/html' href='http://git.cep.is/telegram/'/>
<updated>2026-07-28T00:12:05Z</updated>
<entry>
<title>Read the faixa from the client instead of fetching it again</title>
<updated>2026-07-28T00:12:05Z</updated>
<author>
<name>Murilo Ijanc</name>
<email>murilo@ijanc.org</email>
</author>
<published>2026-07-28T00:12:05Z</published>
<link rel='alternate' type='text/html' href='http://git.cep.is/telegram/commit/?id=97b49ae7081b989274b313532ff17c71694097a9'/>
<id>urn:sha1:97b49ae7081b989274b313532ff17c71694097a9</id>
<content type='text'>
cep.is/go v0.2.0 exposes the municipality as Error.Faixa, which is what
internal/lookup existed to work around: v0.1.0 discarded the 404 body, so
the bot re-issued the request just to read the block back.

The extra GET on the 404 path is gone, and with it the second timeout,
the body size cap and the "is it still a 404?" check that guarded it.
The replies are byte for byte what they were -- the formatting tests did
not change a single assertion, only the type they build.
</content>
</entry>
<entry>
<title>Initial import</title>
<updated>2026-07-26T18:18:21Z</updated>
<author>
<name>Murilo Ijanc</name>
<email>murilo@ijanc.org</email>
</author>
<published>2026-07-26T18:18:21Z</published>
<link rel='alternate' type='text/html' href='http://git.cep.is/telegram/commit/?id=3ca1d2c4370e8e79aba3940d5c8fe115960b75a8'/>
<id>urn:sha1:3ca1d2c4370e8e79aba3940d5c8fe115960b75a8</id>
<content type='text'>
</content>
</entry>
</feed>
