logo

blog

My website can't be that messy, right? git clone https://anongit.hacktivis.me/git/blog.git/

2022 Summary.xml (5765B)


  1. <entry>
  2. <title>2022 Summary</title>
  3. <link rel="alternate" type="text/html" href="https://hacktivis.me/articles/2022%20Summary"/>
  4. <id>https://hacktivis.me/articles/2022%20Summary</id>
  5. <published>2022-12-30T13:00:00Z</published>
  6. <updated>2022-12-30T13:00:00Z</updated>
  7. <link rel="external replies" type="application/activity+json" href="https://queer.hacktivis.me/objects/50be9d37-dee6-4c69-818e-013fa3b010d0" />
  8. <link rel="external replies" type="text/html" href="https://queer.hacktivis.me/objects/50be9d37-dee6-4c69-818e-013fa3b010d0" />
  9. <content type="xhtml">
  10. <div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" class="h-entry">
  11. <p>
  12. Here's an incomplete summary of what I did in 2022 that I want to highlight. Notably absent are the various one-off contributions that are typically bugfixes and package maintenance in Alpine and Gentoo.
  13. </p>
  14. <h2>Pleroma</h2>
  15. <p>
  16. Start of the year was a mess, I left the project because of <a href="https://hacktivis.me/articles/Update%20on%20Pleroma%20Maintainance">Alex Gleason's behavior</a>, tried to do a fork that was quite a failure. But HJ regrouped most of us back to Pleroma with also having contacted lain (owner of the project), Alex Gleason got demoted so we went back to Pleroma. Later he got banned from the project's Gitlab for harassing a contributor.<br />
  17. This whole thing burned me out, I'm glad some people joined, specially tusooa who allowed me to lay back and heal while still guiding her and other contributors. Doing a new branch release took time, partially because we didn't want to simply revert Alex Gleason's controversial modification of granting a lot of power to moderators but instead to make it granular, which took time. But we got <a href="https://pleroma.social/announcements/2022/12/23/pleroma-release-2.5.0/">2.5.0 released on December 23</a>.<br />
  18. Would recommend checking out <a href="https://ebin.club/hj-blog/tags/pleroma/">HJ's blog posts about Pleroma</a> if you want more information.
  19. </p>
  20. <h2>Hare</h2>
  21. <p>
  22. <a href="https://harelang.org/">Hare</a> is a system programming language that got released to the public in early 2022. I would recommend trying it out, for me it ended up replacing Go and most of C (note: badwolf will stay in C, I strongly avoid bindings).
  23. I contributed some simple bits here and there to the standard library and tools:
  24. <ul>
  25. <li><a href="https://git.sr.ht/~sircmpwn/hare/commit/9f2a23b73fce3f0175de54939ad59655e9414fca">math: make absi* functions return an unsigned integer</a></li>
  26. <li><a href="https://git.sr.ht/~sircmpwn/hare/commit/1ac8e33e5a1d133f66d7aefab106a1f848f79eab">cmd/haredoc: Fix default HAREPATH</a></li>
  27. <li><a href="https://git.sr.ht/~sircmpwn/hare/commit/e295c34bda59ac3d22c2e971f5ab838578277228">strings: Fix dupall segfaulting on empty array</a></li>
  28. <li><a href="https://lists.sr.ht/~sircmpwn/hare-dev/patches/32032">cmd/hare: Do not set progress width to 0</a></li>
  29. <li><a href="https://lists.sr.ht/~sircmpwn/hare-dev/patches/32050">fs: Fix wrong bitmask for filetype test functions</a></li>
  30. <li><a href="https://git.sr.ht/~sircmpwn/hare/commit/0495f2ed4d921ad2c7dfffab19295c88a72a7765">os/exec: Make setenv return errors::invalid instead of aborting</a></li>
  31. <li><a href="https://git.sr.ht/~sircmpwn/hare/commit/1989e4a86d25e85aa548d84f68dbfa6c67315e84">os::exec: Add unsetenv function</a></li>
  32. <li><a href="https://lists.sr.ht/~sircmpwn/hare-dev/patches/33156">datetime: Fix parsing nanoseconds</a></li>
  33. <li><a href="https://lists.sr.ht/~sircmpwn/hare-dev/patches/33160">datetime: Add support for parsing timezone offset</a></li>
  34. <li><a href="https://lists.sr.ht/~sircmpwn/hare-dev/patches/33567">stdlib: Fix format::tar dependencies</a></li>
  35. <li><a href="https://lists.sr.ht/~sircmpwn/hare-dev/patches/34377">datetime: Add %F and %T to format</a></li>
  36. <li><a href="https://lists.sr.ht/~sircmpwn/hare-dev/patches/34962">strings/template: Give the missing parameter name in the error</a></li>
  37. <li><a href="https://lists.sr.ht/~sircmpwn/hare-dev/patches/37390">net/uri: Acknowledge the different allowed characters + net/uri: Fix decoding multi-byte percent-data + net/uri/+test: Use wanted/got wrapping for all str assertions</a></li>
  38. </ul>
  39. And the hare-wayland library + tools: <a href="https://lists.sr.ht/~sircmpwn/public-inbox/patches/37165">Makefile: Add `check` target + cmd/scanner: Use strings::template and merge interface+request+event</a>.
  40. </p>
  41. <p>
  42. I switched <a href="https://hacktivis.me/git/go-deblob/">go-deblob</a>, a tool to remove binary executable files, to an <a href="https://git.sr.ht/~lanodan/deblob">hare version</a>, which made it much more lightweight (Go binaries are huge) and probably much less bugged.
  43. Compared to the Go version which only detects ELF and IBM BIOS files, it got much more complete coverage of native executables, bytecode, and serialization formats that can lead to code execution (Perl Storage, Python pickle).
  44. </p>
  45. <p>
  46. <a href="https://git.sr.ht/~lanodan/bsyslogd">bsyslogd</a> is a not-yet-working syslog daemon I started a bit after realizing that syslog implementations out there are either log4j-like kitchen sinks with thousands of integrated native modules while typically running as root, or are too limited in how they store logs. Sadly it stalled after some months but I still plan to resume it.
  47. </p>
  48. <h2>New website pages</h2>
  49. <ul>
  50. <li><a href="/projects/">/projects/</a>: Lists some important projects in one place</li>
  51. <li><a href="/notes/bootstrapping">/notes/bootstrapping</a>: Similarly to <a href="/notes/pure-wayland">/notes/pure-wayland</a>. Here, I note the problems encountered and the current status of trying to have as much software build entirely from source.</li>
  52. </ul>
  53. </div>
  54. </content>
  55. </entry>