<feed xmlns='http://www.w3.org/2005/Atom'>
<title>cgithub.git/views/redirect.eta, branch main</title>
<subtitle>GitHub alternative frontend</subtitle>
<id>http://git.mou.fo/2026/cgithub.git/atom/views/redirect.eta?h=main</id>
<link rel='self' href='http://git.mou.fo/2026/cgithub.git/atom/views/redirect.eta?h=main'/>
<link rel='alternate' type='text/html' href='http://git.mou.fo/2026/cgithub.git/'/>
<updated>2026-08-11T15:57:29Z</updated>
<entry>
<title>Redirect to GitHub with a meta refresh</title>
<updated>2026-08-11T15:57:29Z</updated>
<author>
<name>Joe Mou</name>
<email>dev@mou.fo</email>
</author>
<published>2026-08-11T15:39:01Z</published>
<link rel='alternate' type='text/html' href='http://git.mou.fo/2026/cgithub.git/commit/?id=0a39a7a981f619ac64fdeb26294c7cfd4f110a1a'/>
<id>urn:sha1:0a39a7a981f619ac64fdeb26294c7cfd4f110a1a</id>
<content type='text'>
A browser extension redirects github.com to cgithub with declarative net
requests. Its rules match our HTTP redirects back to github.com too, so
those bounce straight back here and loop forever. A meta refresh makes
cgithub the initiator origin instead, which the extension's rules can
exclude, and its delay leaves a page the user can stop on.

Co-Authored-By: Claude Opus 5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
</feed>
