What
Every GitHub request shares one 15-second timeout. That was sized for small JSON reads; opening a pull request (#167) now sends file contents through the same path, and a large binary on slow venue wifi can exceed it.
Why it matters
The failure reads as "no connection to GitHub" — wrong twice over: the network is fine, just slow, and by then earlier files have already uploaded. Contributor Day wifi is the normal environment, not the edge case.
Idea
A longer ceiling for uploads than for reads, sized to content length rather than one constant for everything.
What
Every GitHub request shares one 15-second timeout. That was sized for small JSON reads; opening a pull request (#167) now sends file contents through the same path, and a large binary on slow venue wifi can exceed it.
Why it matters
The failure reads as "no connection to GitHub" — wrong twice over: the network is fine, just slow, and by then earlier files have already uploaded. Contributor Day wifi is the normal environment, not the edge case.
Idea
A longer ceiling for uploads than for reads, sized to content length rather than one constant for everything.