~nloomans

Amsterdam, The Netherlands

https://noahloomans.com/

I like symlinks and git.

I enjoy writing low-level C code, building servers, making webapps, and learning how stuff really works.

~nloomans/public-inbox

Last active 17 days ago

~nloomans/inbox

Last active 2 months ago

~nloomans/minishell

Last active 7 months ago

~nloomans/test

Last active 11 months ago
View more

Recent activity

Re: builds: information about which branch is being built 30 days ago

From Noah Loomans to ~sircmpwn/sr.ht-discuss

You could do something like this in your deploy script.

    # We only want to deploy when on master. We cannot check if
    # --abbrev-ref is master because the HEAD is detached.
    if [ "$(git rev-parse master)" = "$(git rev-parse HEAD)" ]; then
        # Deploy
    else
        # Do not deploy
    fi

Re: [PATCH] made memset significantly faster for very long strings. 2 months ago

From Noah Loomans to ~nloomans/inbox

Pushed, thanks!

To git.sr.ht:~nloomans/libft
   ec9beb4..8457a55  master -> master

Re: [PATCH] improvement: made memset faster for long sizes 2 months ago

From Noah Loomans to ~nloomans/inbox

It failed to compile for me:

[39/65] Compiling C object 'ft@sta/src_ft_memset.c.o'.
FAILED: ft@sta/src_ft_memset.c.o
cc -Ift@sta -I. -I.. -I../inc -Xclang -fcolor-diagnostics -pipe -Wall -Winvalid-pch -Wextra -Wpedantic -Werror -std=c99 -g -MD -MQ 'ft@sta/src_ft_memset.c.o' -MF 'ft@sta/src_ft_memset.c.o.d' -o 'ft@sta/src_ft_memset.c.o' -c ../src/ft_memset.c
../src/ft_memset.c:25:3: error: variable 'chunk' is uninitialized when used here [-Werror,-Wuninitialized]
                chunk <<= 8;
                ^~~~~
../src/ft_memset.c:19:26: note: initialize the variable 'chunk' to silence this warning
        unsigned long long      chunk;
                                     ^
                                      = 0
1 error generated.
[44/65] Compiling C object 'ft@sta/src_ft_strclr.c.o'.

Regression in PGP patch 2 months ago

From Noah Loomans to ~sircmpwn/aerc

Hey all,

I have found a regression when trying out the latest PGP patches.

Let's say I have an email which looks like this:

multipart/mixed
	multipart/mixed
		text/plain
		application/pgp-keys (some_key.asc)
	application/pgp-signature (signature.asc)

Before the PGP patch, trying to :save the application/pgp-keys file
worked fine. Now, I get the following error:

Re: Golang API CLI 3 months ago

From Noah Loomans to ~sircmpwn/sr.ht-discuss

This looks really interesting! I like the idea of creating pastes from
the terminal. I'll give it a try soon.

Side note: Cool to see a self-hosted sourcehut instance in the wild.

Re: Supporting user groups/organizations on SourceHut 3 months ago

From Noah Loomans to ~sircmpwn/sr.ht-discuss

On Sat, Feb 15, 2020, at 11:57, Simon Ser wrote:
> On Saturday, February 15, 2020 11:49 AM, Wolf480pl <wolf480@interia.pl> wrote:
> 
> > W dniu 15.02.2020 o 11:33, Noah Loomans pisze:
> >
> > > I wonder if groupnames are allowed to overlap with usernames? It could
> > > cause some confusion if both the user ~example and the group +example
> > > exist. Also, this could possibly be used for phishing as well. Imagine
> > > the group +example hosts their code at git.sr.ht/+example/project. Now
> > > an attacker could create git.sr.ht/~example/project, which looks the
> > > same but contains malicious code.
> >
> > Or they could creategit.sr.ht/+examp1e/project
> > or git.sr.ht/+exarnple/project.

Re: Supporting user groups/organizations on SourceHut 3 months ago

From Noah Loomans to ~sircmpwn/sr.ht-discuss

On 15 Feb 2020, at 3:06 am, Drew DeVault <sir@cmpwn.com> wrote:
> From a discussion on IRC going over the options for the group prefix
> character, the currently favored choice is +. Some examples:
> 
> Repo name:
> 	git.sr.ht/+sourcehut/meta.sr.ht
> 
> Mailing list address:
> 	+sourcehut/devel@lists.sr.ht
> 
> ACL:
> 	+sourcehut/committers/meta.sr.ht
> 
> Ticket mention:

[PATCH builds.sr.ht v2] fix job.html #bottom browser-compatibility 4 months ago

From Noah Loomans to ~sircmpwn/sr.ht-dev

document.body is as far as I can tell the non-standard and legacy
scrolling-element which is currently only used in IE and Edge. Firefox,
Chromium, and Safari have migrated to document.documentElement and
don't support document.body anymore.

Note that I couldn't directly test this change as I don't have a working
builds.sr.ht setup, but I did my best to test the modified line
on BrowserStack using all the aforementioned browsers.
---
I didn't include the project in the previous patch, v2 fixes that.

 buildsrht/templates/job.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
[message trimmed]

[PATCH] fix job.html #bottom browser-compatibility 4 months ago

From Noah Loomans to ~sircmpwn/sr.ht-dev

document.body is as far as I can tell the non-standard and legacy
scrolling-element which is currently only used in IE and Edge. Firefox,
Chromium, and Safari have migrated to document.documentElement and
don't support document.body anymore.

Note that I couldn't directly test this change as I don't have a working
builds.sr.ht setup, but I did my best to test the modified line
on BrowserStack using all the aforementioned browsers.
---
 buildsrht/templates/job.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/buildsrht/templates/job.html b/buildsrht/templates/job.html
index 4266fd3..0afb3e2 100644
[message trimmed]

[PATCH openring] allow custom date formats 5 months ago

From Noah Loomans to ~sircmpwn/public-inbox

This adds a new datef function instead of changing date function in an
effort to keep backwards compatibility.

datef is intentionally used in the example to make it clear to the user
that it is possible to set a custom date format.
---
 in.html     | 2 +-
 openring.go | 3 +++
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/in.html b/in.html
index d1437e8..a9f63e6 100644
--- a/in.html
+++ b/in.html
[message trimmed]