News for hackers. Stuff that matters.
Re:A Real World React – Htmx Port by singularity2001 on Sunday October 16, 2022 @02:18AM (#33221475)
Github does? Maybe that's the reason why I often get the error message: "page took too long to render" after ten seconds of waiting.

example: https://github.com/pannous/hieros/wiki/%F0%93%83%80 this is admittedly a complicated markdown file, however it often fails on much simpler files.

Re:A Real World React – Htmx Port by jpe90 on Sunday October 16, 2022 @03:33AM (#33221865)
that's a good reason to invest in self hosting! https://git.jeskin.net/hiero-wiki/file/%F0%93%83%80.md.html
Re:A Real World React – Htmx Port by singularity2001 on Sunday October 16, 2022 @02:57PM (#33226193)
oh, thanks for cloning! but [[links]] dont work and other (internal)[links] don't link to markdown.md.
Re:A Real World React – Htmx Port by jpe90 on Monday October 17, 2022 @01:30PM (#33236925)
gah, you're right. perhaps that could be fixed with a few clever grep/sed incantations. very interesting repo project if you're the author, by the way.
Re:A Real World React – Htmx Port by withinboredom on Sunday October 16, 2022 @04:19AM (#33222037)
I hate it when devs implement their own timeouts. That’s handled at the network level, and the socket knows if progress is being made. I was stuck using 2G data speeds for a couple of years and I loathed this behavior.
Re:A Real World React – Htmx Port by ahungry on Monday October 17, 2022 @06:31PM (#33240353)
Sometimes the infrastructure causes this. For a long time (and now?) AWS Api Gateway has a hard cap of 30 seconds, so the sum of all hops along the way need to remain under that.
Re:A Real World React – Htmx Port by withinboredom on Tuesday October 18, 2022 @03:55AM (#33244282)
A timeout at that level should mean “no progress” for 30s, not that a request/response needs to finish in 30s. An naive timeout that a dev randomly implements might be the latter and would be the source of my past frustration.