Berlin | Edinburgh


Mediocre programmer extraordinaire [she/her] 🏴 Compilers are your friends. Sometimes I type things into computers to make them sad. I also do Rust things. Books are my drugs 📚

Feel free to send me patches to my public inbox or open issues to any of my projects on the meta tracker!

555F 2E4B 6F87 F91A 4110 669E 9073 4A9E 619C 8A6C


Last active 19 hours ago
View more

Recent activity

Project milestone 2 days ago

From Katharina Fey to ~qaul/community

just hit a bit of a milestone on the project.  The demo now (just in my
personal tree for now, will merge soon!) initialises three qaul stacks,
up to the text messaging service level, then send a message through the
entire stack.  On the reveiving end the message is stored in the message
store, then pushed out to a service listener for this service.

This is what that then looks like:


  Finished dev [unoptimized + debuginfo] target(s) in 3.85s
    Running `target/debug/qaul-linux`

[Katharina Fey] Git web UI 2 days ago

From Katharina Fey to ~spacekookie/public-inbox

Hash: SHA256

This is a forwarded e-mail from personal correspondence, archived here
for future development purposes.

- - Katharina

- -------------
From: Katharina Fey <kookie@spacekookie.de>
Subject: Git web UI
Date: Tue, 10 Dec 2019 02:53:21 +0100

Mesage generator framework 3 days ago

From Katharina Fey to ~qaul/community

I "finished" the message store API today (see e16af5) and it occured to
me that we should start thinking about message generators.  I wanted to
write some tests to make the API more robust, but writing messages by
hand is annoying.

@nora: considering you've been thinking about simulation stuff for a
while now, I was wondering what your take on this is.  I have some ideas
for a testing API (internal to libqaul or maybe exposed via a feature
flag?) that can generate random payloads (and maybe ever higher layer
payloads with a dictionary), but I don't know what the best way of
implementing this would be.

Feedback/ discussion appreciated!

[PATCH 2/2] docs/contributors: updating social documentation pages 5 days ago

From Katharina Fey to ~qaul/community

Previously we had some outdated links (such as GitHub), and the
Zulip.  This commit also makes sure the docs are written in the new
formatting style.
 docs/contributors/src/social/_intro.md        | 24 ++++++------
 docs/contributors/src/social/contributions.md | 39 ++++++++++++-------
 2 files changed, 36 insertions(+), 27 deletions(-)

diff --git a/docs/contributors/src/social/_intro.md b/docs/contributors/src/social/_intro.md
index 1db40a0..10382c9 100644
--- a/docs/contributors/src/social/_intro.md
+++ b/docs/contributors/src/social/_intro.md
@@ -1,6 +1,6 @@
-# Social Documentation
[message trimmed]

[PATCH 1/2] docs/contributors: adding documentation style guide 5 days ago

From Katharina Fey to ~qaul/community

The style guide outlines how documentation in markdown should be
written to be the most accessible, readable in both rendered output
and plain text, as well as easy enough to edit.  Many markdown styles
commonly used in projects these days make it hard to read the sources
as plain text, which can make it harder for people without access to
the required tools to read them.  Human readers are treated as a
byproduct and markdown becomes a purely machine readable format.

The idea behind these styles is to prevent this from happening.  A lot
of the documentation that we currently have is not written to these
stardards.  Yet I feel it's important to introduce a style guide now,
and work on improving the existing documentation styles, while also
applying them to new documents.
[message trimmed]

[PATCH 0/2] RFC: Documentation updates 5 days ago

From Katharina Fey to ~qaul/community

This patchset introduces a new way of formatting documentation, as
well as updating existing social documentation (where the code is
hosted, etc).  The style outlined in this series is a DRAFT and
subject to change.  Feedback on the general ideas of the style are
welcome as a reply to this patchset (i.e. the cover letter).

Once the style guide is merged, we should work on updating existing
documentation to the new style to be easier to approach and work with
in the coming weeks.

Katharina Fey (2):
  docs/contributors: adding documentation style guide
  docs/contributors: updating social documentation pages

Current project state 21 days ago

From Katharina Fey to ~qaul/community

Hello internet,

there's a few things that are going on.

For one, we will move away from using the zulip [1] as a public "long
post" platform and use this mailing list instead. Zulip is
interesting as a chat platform, but is a bit too unstable, is
_yet_ another app, and also doesn't allow for public anonymous
indexing (via search engines or archives) which makes it not
ideal for a qaul.net knowledge base.

We won't stay with sourcehut as a mail hoster forever either, the
plan is to get a mailman setup working at lists.qaul.net, at
which point we'll migrate this archive over.

[PATCH 1/2] Refactoring ratman internal channel initialisation a month ago

From Katharina Fey to ~qaul/community

 Cargo.lock            | 15 ++++++++++++--
 ratman/src/core.rs    | 38 +++++++++++++++++++----------------
 ratman/src/journal.rs | 46 +++++++++++++++++++++++--------------------
 ratman/src/lib.rs     | 22 +++++++++++++++------
 4 files changed, 75 insertions(+), 46 deletions(-)

diff --git a/Cargo.lock b/Cargo.lock
index c090e63..18ba6f2 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -61,6 +61,16 @@ name = "cfg-if"
 version = "0.1.10"
 source = "registry+https://github.com/rust-lang/crates.io-index"
[message trimmed]

[PATCH 2/2] Exposing `send` interface on Router structure a month ago

From Katharina Fey to ~qaul/community

 ratman/netmod/src/frame.rs |  1 +
 ratman/netmod/src/seq.rs   |  1 +
 ratman/src/core.rs         | 15 ++++++------
 ratman/src/lib.rs          | 49 ++++++++++++++++++++++++++++++++++----
 4 files changed, 53 insertions(+), 13 deletions(-)

diff --git a/ratman/netmod/src/frame.rs b/ratman/netmod/src/frame.rs
index 97e92dc..c832d56 100644
--- a/ratman/netmod/src/frame.rs
+++ b/ratman/netmod/src/frame.rs
@@ -22,6 +22,7 @@ pub enum Recipient {
 /// Because a `Frame` is usually created in a sequence, the
 /// constructors assume chainable operations, such as a `Vec<Frame>`
[message trimmed]

Re: [PATCH v2 2/3] docs: fix spelling of "contributors" a month ago

From Katharina Fey to ~qaul/community


> I've also corrected "contributors guide" to "contributors' guide"
> throughout.
> ---
>  docs/README.md                                      |   2 +-
>  docs/{contributers => contributors}/.gitignore      |   0
>  docs/{contributers => contributors}/README.md       |   4 ++--
>  docs/{contributers => contributors}/book.toml       |   0
> [ ... ]

this patch doesn't apply anymore, could you regenerate it with a
rebased master please?