Now that this is done, it’s a good time to put a call out to any other interested OCaml meetups, workshops or conferences that also want to host OCaml related content. See the watch/about page for more information about how that works. If you do have a stream of videos (historical, or recent, both are good), then we can mirror it there or host it directly. As a reminder, anyone on a ActivityPub-compliant service (such as Mastodon) can follow channels hosted on the service and leave comments.
Attempts to connect to watch.ocaml.org consistently fails to resolve any request. It hangs on specific devices. It seems @benjamin-thomas ran into this issue too. I just did some light testing on browerstack’s devices. They were all able to reach watch.ocaml.org. But all my devices on wifi and cellular data fail to make a successful connection to watch.ocaml.org. Edit: well, I see it now on my gf’s iphone lol, but only on our wifi and not on cellular data.
girlfriend’s iphone 14, safari, wifi
browserstack’s phones of which i’ve tested 5 models for personal sanity
chrome, safari, firefox on m1 mac, wifi
ipad mini 2nd gen, safari, wifi
iphone 12 pro max, safari, wifi & cellular data
gf’s iphone 14, safari, cellular data! (now this is funny. consistent issue, sample size of 10 attempts)
curl request hangs with logs below
Minor nit: going to https://watch.ocaml.org/ lands me on a view that is sorted by “Recent Views”, which is pretty nonintuitive. I would personally always expect a reverse-chronological view to be default, maybe with a single row of pinned/“trending”/etc videos at the top (called out as such).
Thanks for these reports @benjamin-thomas and @dangdennis. The good news is that our mobile networks seems to have joined the 21st century and are now IPv6-enabled by default. The bad news is that the specific way in which we now deploy the services (using Docker Swarm) doesn’t support IPv6 without workarounds. Mark has applied a workaround, but the eventual solution is to switch away from Swarm mode and into direct container mode which supports IPv6 fine. If an intrepid (and Go-curious) hacker would like to fix the underlying problem with Swarm, you can visit moby/moby#24379.
The instance is configured to show ‘trending’ by default. I wonder if you have a session cookie from a previous visit, as I changed that a few months ago for the same reasons you cite.