So GNUstep has this framework named DBus Kit, and it's pretty neat. It lets you use D-Bus as if it was another flavor of Distributed Objects — you call methods on proxies, and they are forwarded, with forwardInvocation:, as D-Bus method calls. Signals are mapped to NSNotification-s.
The best thing about it is that it would appear that unlike most GNUstep code, DBus Kit is not terribly tied to the rest of GNUstep. I believe it could be ported to run on OS X, and thus on Darling.
Mozilla's move to @matrix has officially been opened for the general public last night. Blog post here: http://exple.tive.org/blarg/2020/02/20/synchronous-messaging-were-live/
And if you missed my introduction to the #Riot web interface for screen reader users in December, here it is: https://marcozehe.de/2019/12/20/how-to-get-around-matrix-and-riot-with-a-screen-reader/
It's official - @firstname.lastname@example.org is fully live on Matrix! http://exple.tive.org/blarg/2020/02/20/synchronous-messaging-were-live/ Helping get Mozilla going has been a lot of fun, and we'll see a lot of improvements to Riot's UX in the coming months based on their feedback (turns out they know quite a lot about FOSS usability :D)
Shortwave Beta 2 is now available! 📻
@wjt Personally I've been slowly growing fond of using “whatever code formatting some tool enforces” and lately I'm even starting to think that merge requests should be accepter with whatever formatting the contributor sends it, and using some hook at merge time to run the tool over the code.
I wish the GNOME community would embrace one of two viewpoints:
- Code formatting does not matter
- Code formatting matters, and is *entirely* maintained and enforced by a tool (cf go fmt, rustfmt, black)
It's heartbreaking to see code reviews which ask only that the authors change things which have no semantic meaning. What a waste of limited time that we could spend on making the software work well.
That's @merge 's series i wanted to link to above: https://email@example.com/
Based on @merge 's accelerometer work (https://firstname.lastname@example.org/) and yesterday's work to hook iio-sensor-proxy into #phosh, enabling rotation is just a couple of more lines of code.
The video shows the #librem5 devkit but it is the same for the phone. Please excuse the low video quality.
Reviewing a merge request for phosh by Julian with some initial work on the quick settings: https://source.puri.sm/Librem5/phosh/merge_requests/425 #librem5 #DailyLibrem @purism
I finally got the time to finish the most basic things I wanted in Read It Later, my @wallabag client and released it today!
You can read a bit about it here https://belmoussaoui.com/2020/02/04/read-it-later/
After adding proximity sensor-support to #iio-sensor-proxy (https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/merge_requests/298) and adding runtime-pm support for the chip used in the #librem5 (and it's devkit) (https://email@example.com/) we can now wire it up to #phosh to fade the screen and prevent keyboard input:
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!