Last active a day ago


Last active 11 days ago
View more

Recent activity

[PATCH builds.sr.ht] images/freebsd: set IGNORE_OSVERSION=yes for CURRENT a day ago

From Simon Ser to ~sircmpwn/sr.ht-dev

Otherwise failures like [1] are happening.

[1]: https://builds.sr.ht/~sircmpwn/job/156487
 images/freebsd/current/functions | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)
 mode change 120000 => 100644 images/freebsd/current/functions

diff --git a/images/freebsd/current/functions b/images/freebsd/current/functions
deleted file mode 120000
index c0b5bcc1b52d..000000000000
--- a/images/freebsd/current/functions
@@ -1 +0,0 @@
[message trimmed]

Re: [PATCH] msg/reply: fix address comparison 8 days ago

From Simon Ser to ~sircmpwn/aerc

On Sunday, February 16, 2020 9:19 PM, Reto Brunner <reto@labrat.space> wrote:

> + if strings.ToLower(address) == strings.ToLower(us.Address) {

Just as a side note: Go has a function for case-insensitive string
comparisons: strings.EqualFold.

Re: Content encoding 8 days ago

From Simon Ser to ~sircmpwn/aerc

aerc has custom encoding code. This isn't handled in go-message.

Re: Supporting user groups/organizations on SourceHut 10 days ago

From Simon Ser to ~sircmpwn/sr.ht-discuss

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.

[PATCH builds.sr.ht 1/2] images/freebsd: fix indentation 11 days ago

From Simon Ser to ~sircmpwn/sr.ht-dev

 images/freebsd/functions | 40 ++++++++++++++++++++--------------------
 1 file changed, 20 insertions(+), 20 deletions(-)

diff --git a/images/freebsd/functions b/images/freebsd/functions
index 4eb62918fbf0..5d297ddf934d 100644
--- a/images/freebsd/functions
+++ b/images/freebsd/functions
@@ -20,28 +20,28 @@ boot() {

install() {
    shift 1
[message trimmed]

[PATCH builds.sr.ht 2/2] contrib: generate freebsd/current from itself 11 days ago

From Simon Ser to ~sircmpwn/sr.ht-dev

Add a flag to submit_image_build to override the source image used
to generate the target image. Use it to generate freebsd/current from
itself instead of freebsd/latest.

Generating freebsd/current from freebsd/latest causes issues because
the CURRENT user-space will try to use syscalls not yet included in
freebsd/latest's kernel.
 contrib/crontab            | 2 +-
 contrib/submit_image_build | 8 ++++++--
 2 files changed, 7 insertions(+), 3 deletions(-)

diff --git a/contrib/crontab b/contrib/crontab
index 1c87744573d9..3501a97bf715 100644
[message trimmed]

Re: [PATCH] Overhaul conformance tests 11 days ago

From Simon Ser to ~emersion/mrsh-dev

> This introduces comprehensive conformance testing for section 2.2 of the
> POSIX shell standard. However, note that mrsh does not currently pass
> these new tests. For what it's worth, neither does dash.

Thanks a lot for this new test infrastructure. I really like the idea. Pushed
with some minor edits.

> diff --git a/test/conformance/2.2-quoted-characters.stdout b/test/conformance/2.2-quoted-characters.stdout
> new file mode 100644
> index 0000000..5815032
> --- /dev/null
> +++ b/test/conformance/2.2-quoted-characters.stdout
> @@ -0,0 +1,14 @@
> +|&;<>()$`\"'

Re: [PATCH core.sr.ht v4] Replace misaka (hoedown) with mistletoe 13 days ago

From Simon Ser to ~sircmpwn/sr.ht-dev

Maybe having a simple counter (e.g. "this is the 7th checkbox") would
be enough?

Re: wev keycodes don't match 15 days ago

From Simon Ser to ~sircmpwn/public-inbox

The discussion on the Wayland merge request highlight that:

- The raw keycodes printed by wev are platform-specific, they are Linux
  event codes "by chance" on our machines
- The only way to interpret an opaque keycode is to feed it to a keymap
- The XKB text format V1 (the only XKB keymap format) takes keycodes
  with an offset of 8

It may make sense to print both the raw keycodes in any case, and to
also print XKB keycodes in case the keymap has the right format.

Re: [PATCH lists.sr.ht] process: add configuration option to bounce messages back to their author 18 days ago

From Simon Ser to ~sircmpwn/sr.ht-dev

On Friday, February 7, 2020 12:57 PM, Ariadne Conill <ariadne@dereferenced.org> wrote:

> Some people depend on this behaviour to provide synchronization between
> several MUAs. If you think about it, it makes sense: if the MUA makes
> a copy locally on the local computer, instead of in IMAP or similar,
> then the root of the thread (or some leaves) will be missing on other
> MUAs, such as your phone.

To me, this reads as "if the MUA doesn't upload outgoing messages to
the IMAP server, then other MUAs won't be able to access these

Well, that's just normal behavior. Consider the case of not writing to
a list, but instead writing to a single recipient. If your MUA doesn't