Notices by Adrián Pérez (aperezdc@mastodon.social)

@mntmn noice! There's also ttyd if you want something that won't require a Go toolchain: https://github.com/tsl0922/ttyd — I've used it many times to share a tmux session for pair programming.

@mntmn no problem at all!

@mntmn in the RaspberryPi 4 the GPU has not evolved as much as the ARM cores, so for example H.264 decoding tends to go smoother in software because the status of V4L2 support is a bit spotty. Even for stateless decoders (which tend to work better) it's impossible to make e.g. the same video loop seamlessly when it reaches the end (there's a noticeable amount of milliseconds of decoder stall while restarting the video stream).

@mntmn I can confirm this, the VideoCore GPU was a-okay in the times of the RaspberryPi 2 & 3 and has a few niceties (like plenty of KMS planes, with support for hardware video decoding directly onto them) but it definitely struggles with certain workloads. For example it's impossible to hit 60Hz if you do complaining (e.g. run a Wayland compositor) and there are big surfaces which need pixel format conversion (e.g. tiled to linear). If one can hit direct scanout it can work decently.

@xerz

We still have further.improvements lined up, and some of the new things require tweaks to enable them for testing, but it's looking quite promising. Oh, and the GStreamer based WebRTC support keeps improving with each release... Getting there!

Also: we should write a blog post soon about all the goodies in WebKitGTK 2.40.x :thinkhappy:

@xerz
There has been quite a lot of improvements under the hood in @WebKitGTK, many related with performance and supported web features, but the GNOME release notes don't even mention that the GTK4 support was a major undertaking, and that we have everything lined up for zero copy operation, including accelerated media playback. This teaser was shared some days ago in Reddit: https://www.reddit.com/r/gnome/comments/11pav5t/gnome_web_44_leaps_and_bounds/

@brainblasted we have done this with @WebKitGTK in the latest years as well! For nontrivial API changes we often try it with Epiphany (our test mule!) during development, sometimes with Devhelp. We itere until the API feels right in a C application, then add documentation and auxiliary functions which might be needed for languages using introspection. It's more effort upfront, but the outcomes are better 🛠️

A few years back I had the chance of trying out a prototype for the @mntmn Reform and it was a blast, so if you're around #FOSDEM this year go and check out whatever Lukas has to show this time. The Pocket Reform sure is as cute in person aw it looks in pictures :BlobhajHeart: