LOL. MEGA says "use Chrome to download large files because Firefox has a small buffer". Opened in Chromium… "unzoom or use Firefox because of a zoom rendering bug in Chrome/ium" :D

haha, Phoronix wrote about the stuff I posted on wayland-devel@. So yeah, I'm working on Rust bindings for libweston that would eventually allow me to write the best Wayland compositor ever :)

And fractional HiDPI scaling was pretty easy to add. Wayland apps look awesome. However, X11 apps are blurry now, and bypassing the scaling for Xwayland is not as easy… So I made some changes to my Ports fork to enable Wayland support in more apps. Turns out a lot of complex applications run fine — LibreOffice (!), Inkscape, MyPaint, RawTherapee, Darktable.

The Firefox Wayland support though… is not usable yet :( It looks awesome but EGL isn't working and, even worse, the screen doesn't refresh when it needs to — so you're typing and letters don't appear until you scroll or some time passes. Hopefully this will be fixed soon.

Mozilla finally approved Transmitter! Finally!

If that's the new "streamlined review process" I can't imagine how slow the old one was. Although I definitely got into the big initial wave of everyone publishing WebExtensions…

I made a WebExtension! It’s called Transmitter for Transmission. It lets me add torrents to the transmission-daemon instance running on my home server. And watch their status. I think Transmission actually allows you to expose the remote API in desktop versions as well.

tl;dr on WebExtensions: it’s Chrome’s extension API, but with Promises and it’s a W3C standard. Fully supported in Firefox. Chrome/Opera need a tiny polyfill for the Promise support. MS Edge can be supported too.

Publishing experience: Chrome’s store asks for $5 to get your stuff published (one time payment for up to 20 extensions) and there’s no pre-moderation. Addons.Mozilla is pre-moderated but the extension shows up on its URL before approval. Opera is pre-moderated and the extension doesn’t show up before it’s moderated.