~spacekookie

Berlin | Edinburgh

https://spacekookie.de

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

~spacekookie/public-inbox

Last active 11 days ago
View more

Recent activity

Re: Voice-Chat Meeting, Monday 20 Jan 2020, 17:00 UTC 8 days ago

From Katharina Fey to ~qaul/community

Hey,

> Our next voice-chat meeting will take place this Monday, 20
> January 2020 at 17:00 UTC .

Just as a heads up, I won't be able to make the meeting this week.  I'll
try to leave notes for you in the pad by tomorrow evening!

~k

[PATCH v2] ws/kitty: setting default shell to tmux 12 days ago

From Katharina Fey to ~spacekookie/public-inbox

---
 modules/workstation/kitty/kitty.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/workstation/kitty/kitty.conf b/modules/workstation/kitty/kitty.conf
index ab8c6a059f7..3fbb8fa98c7 100644
--- a/modules/workstation/kitty/kitty.conf
+++ b/modules/workstation/kitty/kitty.conf
@@ -1,10 +1,10 @@
font_size 10
font_familt twemoji-color-font

open_url_modifiers ctrl+shift
open_url_with default
[message trimmed]

Re: [PATCH 2/2] ws/kitty: setting default shell to tmux 12 days ago

From Katharina Fey to ~spacekookie/public-inbox

A comment on this commit:

> --- a/modules/workstation/kitty/kitty.conf
> +++ b/modules/workstation/kitty/kitty.conf
> @@ -1,10 +1,11 @@
>  font_size 10
> -font_familt twemoji-color-font
> +font_family twemoji-color-font

This was a typo before but I think we don't really want this feature
anymore, because all the font integration stuff is broken anyway.  I
think it'd be better to remove this line and then add it again when it
becomes relevant again.

[PATCH 2/2] ws/kitty: setting default shell to tmux 12 days ago

From Katharina Fey to ~spacekookie/public-inbox

---
 modules/workstation/kitty/kitty.conf | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/modules/workstation/kitty/kitty.conf b/modules/workstation/kitty/kitty.conf
index ab8c6a059f7..65c2ed15e7b 100644
--- a/modules/workstation/kitty/kitty.conf
+++ b/modules/workstation/kitty/kitty.conf
@@ -1,10 +1,11 @@
font_size 10
font_familt twemoji-color-font
font_family twemoji-color-font

open_url_modifiers ctrl+shift
[message trimmed]

[PATCH 1/2] ws: adding gpg submodule by default 12 days ago

From Katharina Fey to ~spacekookie/public-inbox

---
 modules/workstation/default.nix | 1 +
 1 file changed, 1 insertion(+)

diff --git a/modules/workstation/default.nix b/modules/workstation/default.nix
index 077eae4bbc8..e330a801484 100644
--- a/modules/workstation/default.nix
+++ b/modules/workstation/default.nix
@@ -24,6 +24,7 @@
  };
  
  imports = [
    ./gpg
    ./graphics
[message trimmed]

[PATCH 0/2] The best patchset in the universe 12 days ago

From Katharina Fey to ~spacekookie/public-inbox

(if you have no idea what the fuck this thread is, don't worry - I'm
doing a humour on my blog)

To who it may concearn,

I have created the most magnificent patch set in the history of the
universe and I really think you should merge it because otherwise
you'd be a git.

Cheers,
me!


Katharina Fey (2):

Re: Documentation feedback: technical intro 12 days ago

From Katharina Fey to ~qaul/community

>> My suggestion would be to call it http-api over which you can access the
>> data via JSON:API.
>
> Yeah, Calling it JSON:API would be very confusing, since that's also the
> name of the protocol the API is built on top of.

For what it's worth I was cosindering the string "http/json:api" to be
one term, not to be taken to mean "http / json:api".  The reasoning
behing that was that maybe in the future someone might want to add
"http/json-ld".  Http here is only the transport layer, the second part
is the actual protocol encoding.

But also, maybe it's too verbose and we should just call it
"libqaul-http" or "http-api".

Re: Documentation feedback: technical intro 14 days ago

From Katharina Fey to ~qaul/community

> I'm very confused here -- I didn't mention security at all?

I think what happened here is that I heartbleeded myself.  Woops.


> I just said that, as an outsider, it was surprising to me to discover
> that there was a shared daemon, and that the documentation should spend
> a bit more time on explaining why that is, since the reasoning was not
> obvious (at least to me), and that as I recall there's more to it than
> sharing resources.

The reasoning is indeed not obvious and I'm gonna look into how to word
it better!

Re: Documentation feedback: technical intro 14 days ago

From Katharina Fey to ~qaul/community

>> The idea behind the variety of IPC interfaces is that your application
>> can bundle it's own copy of libqaul, to provide the network backends
>> required to join a mesh network, however it can also connect with a
>> running instance if one is available.  This way resources can be
>> shared.
>
> There are technical reasons for this beyond just "resources can be
> shared", right?  Having a daemon shared by multiple applications is the
> part of the architecture that surprised me the most, and so I think some
> more rationale would be helpful here so people understand why it works
> this way.

I mean, that's true, the technical reasons are there, but there's also
the usability aspect of it.

Re: Documentation feedback: technical intro 14 days ago

From Katharina Fey to ~qaul/community

> I agree. This entire section is only about libqaul so makes sense
> to not talk about other layers in the entire stack.
>
> [...]
>
> If you are asking about the title "Layers" then I do think the
> section can be renamed to libqaul with the three subsections
> as they are (minus "libqaul:" in front since it is redundant?).


Oooh, yes okay now I understand what you mean :) Yes, that's a good
idea.

Actually thinking about it, there should be a later section about Ratman