out of beta, and a call for new videos

The video site is now promoted to a production quality ocaml.og site, as discussed at the start of the year (doesn’t that seem like a long time ago?) For those interested, this means that the software stack is now part of the pipeline (see ocaml/infrastructure#23 and the infra@ocaml blogpost.)

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.

Thanks to @mtelvers @patricoferris @cuihtlauac @sabine for loads of updates as well to make this possible! That was lots of work, but now links to the site and each workshop page should be up-to-date back to 2012.


This looks like a great initiative, very useful.

Thanks to all involved.

Note that the service seems to be flaky or not working when opening the page with an iPhone.

It looks like it could be a device specific bug.

“Safari could not open the page…the server stopped responding”

While opening this same page works fine from my desktop

this is wonderful, let’s mention it once a month. Maybe the outreachy presentations can go there as well @patricoferris ?

Happy to say they already do ^^ (and will continue to do so)


The site doesn’t load for me. Looks more an issue on the host side because none of my devices are able to open the links.

Could you provide more details about the device, platform and urls you’ve been trying to access? Along with any other relevant details.

Ok the failure was so oddly random that it looked like it could be device related at first but it doesn’t seem so on second look.

This should help:

$ time http -v --timeout=10;ping -c 1
GET / HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
User-Agent: HTTPie/3.0.2

http: error: Request timed out (10.0s).

real	0m10.366s
user	0m0.316s
sys	0m0.020s
PING (2001:bc8:47e4:107::1)) 56 data bytes
64 bytes from 2001:bc8:47e4:107::1 (2001:bc8:47e4:107::1): icmp_seq=1 ttl=50 time=19.5 ms

--- ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 19.537/19.537/19.537/0.000 ms

I had thought it’d be a more widespread problem.

Attempts to connect to 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 But all my devices on wifi and cellular data fail to make a successful connection to Edit: well, I see it now on my gf’s iphone lol, but only on our wifi and not on cellular data. :exploding_head:

Success scenarios
girlfriend’s iphone 14, safari, wifi
browserstack’s phones of which i’ve tested 5 models for personal sanity

Failed scenarios
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

curl -v
*   Trying [2001:bc8:47e4:107::1]:443...
* Connected to (2001:bc8:47e4:107::1) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (OUT), TLS handshake, Client hello (1):

There was a problem with IPv6 connections. It should be working now.

1 Like

It’s all good for me, if you’d like a confirmation :ok_hand:

1 Like

Confirmed working. Thank you.

This looks great, I’ll be sure to link it around.

Minor nit: going to 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).

We have our latest external tech talk channel up, thanks to a request from Tarides for a new channel. Keep them coming, especially if you find historical videos that might otherwise disappear from the Interwebs (or are OCaml-related – ReasonML videos also welcome).

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.


I don’t think I have any cookies influencing this; I see the same when visiting in incognito (chrome and firefox), as well as via a mobile browser (chrome) I’ve never used to visit any OCaml sites. :thinking: :person_shrugging:

Do we need a link to on the main ocaml page? I didn’t know of its existence until recently.

I can also verify that the default option is “recent views”.

Same setup as my stated environments above. iOS and macOS safari on private windows and regular.

It’s linked on the “Community” page: The OCaml Community

Oh I missed that. Thanks. Maybe have the link somewhere else too? Either on the main page or on the Learn section? Personally I wouldn’t expect the page for videos in the Community section.

Using Mastodon to like, comment and subscribe is a pretty neat idea, but the UI makes it a bit more complicated than it should.

Looks awesome, congrats on putting this together.

If I want to upload the shows, It asks me for a login which I don’t have. How should I proceed? Assuming the conversations are worth publishing there.


1 Like