Achievement unlocked: fixed a bug in the core logic of @haiku's kernel thread scheduler, which provided a nice 10% performance boost in some benchmarks (and fixed a recent whole-system-hang regression) 😀 https://github.com/haiku/haiku/commit/8dc67def4b11c4f93af85b51ec1e9b2de6973f92
@waddlesplash has an high dpi display and the default font for @haiku kernel debugger looked much too small. For a while we used @fcambus Spleen font in that case, but we really like our original font designed by Brian J. Swetland (name of the font unknown, investigation in progress).
So today I made a larger size version of that font. It will require some tweaks, but I think it's a nice start!
I finally got an overconfidently negative Hacker News comment about something I did (Xlibe, the Xlib/X11 compatibility layer for Haiku) that I got to fisk. What fun! (https://news.ycombinator.com/item?id=31192099)
Now on the @haiku blog: a February Contract & Activity report, from me, featuring USB WiFi support, a slew of kernel fixes, and more. https://www.haiku-os.org/blog/waddlesplash/2022-03-07_haiku_activity_contract_report_february_2022/
Forum thread for further discussion: https://discuss.haiku-os.org/t/support-for-realtek-usb-wifi-adapters-now-in-nightlies/11981
Great news everyone: @haiku nightlies now have initial support for USB WiFi adapters! (Realtek devices only at present, but more should come later.) Upgrade to hrev55907+ and make sure they're plugged in before booting if you want to try it out.
(GTK3 was "ported" via an X11 compatibility layer, which implements the Xlib APIs on top of the Haiku APIs without the need for an X11 server. More details on that: https://www.haiku-os.org/blog/waddlesplash/2022-01-10_haiku_contract_report_december_2021/)
By the way: @haiku 's first GTK3 applications, Inkscape and GIMP, are now available in the package repositories...
Last month was my first (almost) full month working full-time on @haiku. So, of course I wrote some 2900 words about what I did, and what I'm planning to do next: https://www.haiku-os.org/blog/waddlesplash/2021-10-02_haiku_contract_report_september_2021/
At last – Haiku R1/beta2 has been released! 🎉
Hardware & boot testing has begun for R1/beta2! Can you help us out by trying one of the builds, and reporting how @haiku functions on your hardware? https://discuss.haiku-os.org/t/help-wanted-r1-beta2-boot-hardware-testing/9511
@haiku ... and I'm just getting started on the optimizations: for instance, merged last night is a patch that will improve inode write performance by a minimum of 10x-20x (on HDDs) and potentially up to *200x* (on SSDs)!
It used to be like this everywhere, but now only on @haiku : a list of all running processes with none (including the web browser and window server!) using over 65MB of RAM. (And launch_daemon's RAM usage is in the hundreds of KB!!)
Librem.one, Moderation Discussion
Admins: perhaps you should consider blocking social.librem.one. This instance’s policies could affect the safety of many of us on the fediverse. The instance automatically rejects both local and remote reports, meaning there is no way to bring bad users and content to the attention of their moderators. See here: https://source.puri.sm/liberty/smilodon/commit/9cae431902a2c0ce6438c6722a3a901e279c78fc
In discussion within their chatrooms, I received this response:
quick note about reporting (copied from other chat room): this is correct, after deep deliberation we have concluded that no company should control speech - we have a “stay safe” guide in the pipeline, but briefly, block bad users and report illegal content - in the long-term federated, community-managed blocklists are likely the answer
This does not seem right to me - if we’re subjected to their users, the only action admins can take is to block their server rather than have our issues addressed. This makes for a poor member of the fediverse.
It is proven! I am waddlesplash on Keybase: https://keybase.io/waddlesplash/sigchain#0e06b8299bbed2d4a5b59314460c064cd522f39210319587874d97700a2b105d0f