Pinned post

📢 Descriptions of the GNU vulnerabilities I've found earlier this year are now public! 🎉

Read them here: This should be an interesting read even if you're not very familiar with the Hurd and 🙂

(phew, it took me quite some time to write, too!)

Pinned post

I've mentioned this a few times but never publicly announced it, so consider this the announcement.

Yes, I have ported (along with a few Weston clients and wl-clipboard) to the (that's what I wrote the epoll server for!)

I've also ported Owl, my Cocoa Wayland compositor, from OS X to the Hurd using GNUstep.

Here's a screenshot of weston-terminal and weston-flower, running on Owl on GNUstep on Hurd, with X forwarded from a QEMU VM via SSH.

Pinned post
Pinned post

I did it!!!!

TL;DR: I have ported to and written my own Wayland compositor using Cocoa 😎


Pinned post

I've made a mock-up to illustrate my ideas about the next-gen terminal experience!

• the pathbar
• username, hostname and git branch displayed in the UI, shrinking the shell prompt back to just a $
• commands as cards
• syntax highlighting, including graying out the output a bit to differentiate it from commands themselves
• autocompletion (displayed in a native widget)
• built-in error handling options
• the time each command took (on the right)

Show thread

📢 Important PSA: I'm being conscripted (or: drafted) for military service, starting next week (Nov 15th).

This means you won't see hot takes or obscure project announcements, nor free software contributions, nor any online activity from me for a whole year.

This is the reason I have rushed publishing those Hurd vulnerability details and the Owl source code.

I'll be back in a year, and I'm excited to see what amazing progress y'all are going to make in this time.

Show thread

Constants aren't. Variables don't. LISP does. Functions won't. Bytes do

@bugaevc I ❤️ that this is old school and so readable. Thanks for making it.

One part of my plan for 🦉 is that I'd like to make it not only the most portable Wayland compositor, but also the most documented one. You should be able to find all the relevant documentation about the inner workings of Owl and Wayland, both right in the Owl source code and in a wiki.

If you browse through the Owl source (which I encourage you to do!), you'll see I have made some steps towards this goal; but of course I'm far for having completed it. We'll get there someday!

Show thread

Now, I was hoping to get lots of things done & improved before doing the release, which is why I kept delaying it. I've managed to do a bunch of work — not as much as I have hoped to, but enough to bring Owl to a releasable state. And due to the circumstances, I cannot delay the release any longer.

So I really want to emphasize that there is a lot more to do here. What I'm releasing now is not the final state of the project, it's only the beginning.

Show thread

📢 Owl is now on GitHub! 🎉

After an unsigned long long wait, I'm finally releasing the source code of Owl, my portable compositor in Objective-C that runs on Mac OS X, the Hurd (and probably just about anywhere else thanks to the magic of ). Along with it, I'm also publishing the port of Wayland that runs on OS X.

Please note that Owl is still very much a work in progress. It's amazing that many things work, but naturally others don't. There's a lot to improve!

For my part, whenever I see a useful inlay hint, I make sure to specify the type or argument name there explicitly

Show thread

Unpopular opinion:

IDEs and editors that go above and beyond to provide the developer with more context & info that's not present in the actual source code, such as the inlay hints feature,

can be very helpful to understand things right here and now, but end up being harmful to code clarity & readability in the long term

"Forcing a rebuild of systemd on Launchpad fixed the issue" [of Steam conflicting with the DE on Pop!_OS]

(insert the "days it was since DNS" meme)

I’ve been making veiled comments about a situation in the Linux desktop community for a while, and I think it’s finally time to lift the curtain:

System76 has not been kind downstream, and they’ve made a habit of talking poorly about their upstream projects and then using that as a jumping point to market their own projects.



These vulnerabilities have been assigned CVE-2021-43412, CVE-2021-43413, CVE-2021-43411, CVE-2021-43414

(Thanks to Amos Jeffries for requesting the CVEs!)

Show thread

"Sergey just had his morning ☕" idle thought:

the sandboxing features of should be fairly orthogonal to its distribution features (runtimes, remotes, OSTree, manifests, ...)

so there should be a way to run most "system" apps "in a Flatpak sandbox" and reap all the security benefits without compromising on systems integration & stuff

Show older
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!