@arj Eh, who really needs that fancy-shmancy "userspace" anyway...sounds like a scheme by Big CPU to sell more operating modes.

@tedu I think it might be time to lawyer up -- looks like they're infringing on patented Honk hydration technology!

https://github.com/twitter/the-algorithm/blob/7f90d0ca342b928b479b512ec51ac2c3821f5922/product-mixer/core/src/main/scala/com/twitter/product_mixer/core/pipeline/recommendation/RecommendationPipelineBuilder.scala#L438

@cks Or alternately, getent services 548. (Assuming glibc, anyway.)

...and indeed, it's catching on!

https://fosstodon.org/@axboe/110079223973321590

Now we just need @monsieuricon to cook up some sort of lkml<->fediverse bridge for backwards compatibility.

@GeoffWozniak I assume we'll be getting some sort of explanation here once the dust settles?

@tedu But it's like 1.5 Scaramuccis!

@monsieuricon @chockenberry I'm almost tempted enough by this to create an account with one of these LLM things just to see what "...in the style of Bill the Cat" does to its output...

@th @Ange Though I should note that since I'm not actually running BSD I produced that via the version in the bsd-games package, which appears to be slightly different than OpenBSD's, at least: https://man.openbsd.org/bcd.6

(And which I'm only aware of due to this dredging up a memory of a @tedu blog post from a while back: https://flak.tedunangst.com/post/improving-bcd)

@Ange @th

 ________________________________________________
/A LA BSD'S BCD(6), PERHAPS?                     |
|]  ] ] ]   ]]]]     ] ]]                        |
|  ]     ]       ]  ] ]  ]                       |
|      ]  ]       ]       ]                      |
|]11]1111111111111111111]111111111111111111111111|
|22222]]22]2]2222222222222]2222222222222222222222|
|33]333333333]3333]333333333333333333333333333333|
|4444444]44444]4444444444444444444444444444444444|
|55555555555555]5]555]555555555555555555555555555|
|666666666666666]66666666666666666666666666666666|
|77777777]7777777777]7777]7]777777777777777777777|
|88888888]88888]8]]8888]888]888888888888888888888|
|999999999999999999999]99999999999999999999999999|
|________________________________________________|

@grawity @cks @gnomon GNU grep has included optimizations based on detecting its stdout being /dev/null since 2016, FWIW...

@barrelshifter In my experience it's basically okay when strictly constrained to the common C usage pattern of "only when combined with static" -- effectively macros plus type-checking.

Anything beyond that (extern inline and such that tend to pop up in C++? ugh...) is an abomination to be shunned with extreme prejudice IMO.

@cks I dunno, IMO this seems like it may be a situation where the time for non-violent solutions has passed.

@palmer Yeah, spring seats were my first thought...good luck!

@palmer Damn, just the right side then too? That's an interesting sort of stance...oog. Maybe you can just sorta shim it back up with some cardboard or something, like a rocky table with uneven legs.

@palmer Lowered front end?

@tedu Who said anything about computing it?? My program counters are determined by pure spur-of-the-moment artistic inspiration.

@tedu But calling through a function pointer implies saving a return address -- way too much performance overhead!

To really just do pc = address as efficiently as possible you need GNU C:

$ cat goto.c 
void dontlook(void* p)
{
    goto *p;
}
$ gcc -O2 -Wall -o - -S goto.c
    .file	"goto.c"
    .text
    .section	.text.unlikely,"ax",@progbits
    .globl	dontlook
    .type	dontlook, @function
dontlook:
.LFB0:
    .cfi_startproc
    jmp	*%rdi
    .cfi_endproc
.LFE0:
    .size	dontlook, .-dontlook
    .ident	"GCC: (GNU) 12.2.0"
    .section	.note.GNU-stack,"",@progbits

@tedu Well, however miraculously, in the time that's elapsed since I posted that Mr. Pinboard has smiled upon me with a reply to my support email (maybe I should frame it, like a Knuth check or something) and assuaged some concerns, so out of some combination of laziness and convenience I'll probably continue using that for the foreseeable future.

I'll definitely keep an eye on inks though (I do see one fresh new commit!) and maybe play around with it a bit to have something on hand as a fallback plan if things in Pinboardland take another turn for the worse...

@petersanchez And after reading the explanation here -- instead of letting the abusers win and taking down the service entirely, couldn't that problem have been solved with...a firewall rule?

@jxs That's a lot of bytes...good thing it compresses well!

...and now after looking at it a moment longer than I did at the time, I discovered that the shifter cable had in fact not broken, but merely popped out of its little retainer bracket fork.

Annoying that I could in fact have easily fixed it on the side of the road and avoided a lot of headache, but glad that I procrastinated on ordering the replacement parts I wrongly thought I'd need (and that it was ultimately trivial to fix).

@blmt @th @bhtooefr @cynicalsecurity It's less er, ambitious (I guess) than OCP, but the Open19 initiative is roughly along those lines -- ~rack-level PSUs distributing 12VDC to servers with blind-mate connectors for power & network, all in standard 19" racks.

(I'm not personally involved in the project itself, but I work on the Open19 hardware my employer operates.)

@palmer Eh, no shame -- they're hard enough to find in reasonable shape regardless of transmission (I got pretty lucky when I found mine, and it still took 6 months or so of searching).

@palmer Yeah, for a minute I could still engage the odd-numbered gears, and thought maybe I could limp it home on just those, but then "three-speed transmission" quickly became "zero-speed transmission"...

@palmer Car twin! (Though I can't blame the road for mine, just a plain old component failure.)

@djm Don't think I saw the usual call for testing on the mailing list for this one, any particular reason that didn't happen?

@piggo If you're not opposed to toolchain-specific extensions, the gas .incbin directive is handy:

#include <stdio.h>
asm("sym: .incbin \"/etc/passwd\"\nendsym:");
extern char sym[];
extern char endsym[];
int main(void)
{
    for (int i = 0; i < endsym - sym; i++)
      putchar(sym[i]);
    return 0;
}

@arj Do you really want to approach the latter without some preparation via the former?

@petersanchez @icy @ols @knapjack Heh, that's my reasoning for using apache. nginx still seems all newfangled-like.

@tedu Hmm, never tried donking anything but images before; let's see how a .patch file works I guess?

Attachment: mz.patch webs patch to fix mentions bug

@tedu something like this maybe?

diff --git a/mz/mz_test.go b/mz/mz_test.go
index a2259ab60891..17f431fb802a 100644
--- a/mz/mz_test.go
+++ b/mz/mz_test.go
@@ -5,14 +5,18 @@ import (
 	"testing"
 )
 
-func doonezerotest(t *testing.T, input, output string) {
-	var marker Marker
+func doonezerotestwithmarker(t *testing.T, marker *Marker, input, output string) {
 	result := marker.Mark(input)
 	if result != output {
 	t.Errorf("\nexpected:\n%s\noutput:\n%s", output, result)
 	}
 }
 
+func doonezerotest(t *testing.T, input, output string) {
+	var marker Marker
+	doonezerotestwithmarker(t, &marker, input, output)
+}
+
 func TestBasictest(t *testing.T) {
 	input := `link to https://example.com/ with **bold** text`
 	output := `link to <a href="https://example.com/">https://example.com/</a> with <b>bold</b> text`
@@ -121,6 +125,16 @@ func TestImagelink(t *testing.T) {
 	doonezerotest(t, input, output)
 }
 
+func TestMentions(t *testing.T) {
+	input := "@foo@example.com @bar@example.org @baz@example.net are pals but @notamention isn't"
+	output := "foo@example.com bar@example.org baz@example.net are pals but @notamention isn't"
+	var marker Marker
+	marker.AtLinker = func(text string) string {
+	return text[1:]
+	}
+	doonezerotestwithmarker(t, &marker, input, output)
+}
+
 func TestLists(t *testing.T) {
 	input := `hello
 + a list

(Probably still whitespace-damaged...but one bug at a time.)

Fails without the prior regex patch; passes with it applied.

@tedu Having now learned how to copy/paste/modify a go mod edit -replace invocation, I can report that the following seems to work, at least in some cursory testing:

diff --git a/mz/mz.go b/mz/mz.go
index 90ce6ba39293..107d5cf82242 100644
--- a/mz/mz.go
+++ b/mz/mz.go
@@ -37,7 +37,7 @@ var re_lister = regexp.MustCompile(`((^|\n)(\+|-).*)+\n?`)
 var re_tabler = regexp.MustCompile(`((^|\n)\|.*)+\n?`)
 var re_header = regexp.MustCompile(`(^|\n)(#+) (.*)\n?`)
 var re_hashes = regexp.MustCompile(`(?:^| |>)#[\pL\pN]*[\pL][\pL\pN_-]*`)
-var re_mentions = regexp.MustCompile(`(^|[ \n])@[[:alnum:]._-]+@[[:alnum:].-]*[[:alnum:]]([ \n.]|$)`)
+var re_mentions = regexp.MustCompile(`(^|[ \n])@[[:alnum:]._-]+@[[:alnum:].-]*[[:alnum:]]\b`)
 
 var lighter = synlight.New(synlight.Options{Format: synlight.HTML})
 

@jk @verb @az With that kind of throughput potential, who needs forest fires?

@tedu That seems consistent with what I've seen -- when given three or more consecutively it appears to alternate between matching and non-matching I think. I don't know the go tooling well enough offhand to have figured out how to actually test this (given it being in a dependency rather than the honk codebase itself), but any chance something like the following in webs would do the trick?

diff --git a/mz/mz.go b/mz/mz.go
index 90ce6ba39293..72caa2fb8e43 100644
--- a/mz/mz.go
+++ b/mz/mz.go
@@ -37,7 +37,7 @@ var re_lister = regexp.MustCompile(`((^|\n)(\+|-).*)+\n?`)
 var re_tabler = regexp.MustCompile(`((^|\n)\|.*)+\n?`)
 var re_header = regexp.MustCompile(`(^|\n)(#+) (.*)\n?`)
 var re_hashes = regexp.MustCompile(`(?:^| |>)#[\pL\pN]*[\pL][\pL\pN_-]*`)
-var re_mentions = regexp.MustCompile(`(^|[ \n])@[[:alnum:]._-]+@[[:alnum:].-]*[[:alnum:]]([ \n.]|$)`)
+var re_mentions = regexp.MustCompile(`\b@[[:alnum:]._-]+@[[:alnum:].-]*[[:alnum:]]\b`)
 
 var lighter = synlight.New(synlight.Options{Format: synlight.HTML})
 

@carlmalamud I wonder how many additional hours of meetings and disclaimer clarifications could be incurred by pointing out the potential confusion that "remove before installing" and "warranty void if removed" logically combine to "warranty void if installed".

@tedu sobs into phone

Assuming this is the issue mentioned here, I'm guessing it's just some regex somewhere needing a tweak?

@oclsc @cks ...hopefully. Some BMCs will unconditionally power on the host during their boot sequence, so rebooting the BMC of a powered-off server might not leave it that way...

@bhaktishh @regehr Your first intro programming class was taught in...Haskell? Nevermind git, that seems like a bold move...after spending a length of time now comfortably measurable in decades writing code in various languages, lazy evaluation still regularly confuses the bejezus out of me.

@regehr @julesjacobs @djg Shuffle an array of bools? (Good chance it'd actually be less efficient in practice I'd expect, but arguably "elegant".)

@regehr I'm neither a compiler expert nor a testing expert, but I have a vague gut feeling it might be good to sprinkle in some non-power-of-2-but-low-Hamming-weight values? (e.g. 0xc0000000, 0x80008000, etc.) I guess maybe still "close to a power of 2", but by Hamming distance instead of arithmetically.

@tedu I've been seeing some slight wonkiness with usernames not all getting linkified with options.MentionAll enabled -- e.g. here and here.