I’ll see you from yume.laidback.moe!

Nyon!

Nyon!

Nyon!

[a block of smoked cheese hung up further upwards, beyond the reach of the person who wants to eat it]

Nyoro~n :(

But hey! The read-eval-print-loop works!

Damn it, Postfix! Plan B! https://termbin.com/y1vf

I actually had to verify /usr/include/sys/syscall.h on my own for this one, even if they’re the same

Image

it’s going to be a cold day in Hell before I’ll ever get into ARM again

I mailed you a patch (at least my mail server caught notice of it), should be arriving any time soon

nyoro~n

@prologic@twtxt.net

Shin'ya M. > ./bin/mu
panic: native backend does not support syscall platform netbsd/amd64

goroutine 1 [running]:
git.mills.io/prologic/mu/internal/native/arm64.init.0()
        /home/shinyoukai/mu/internal/native/arm64/emitter.go:45 +0x7bf

…that was supposed to be the interpreter?

@prologic@twtxt.net well I ran into a panic() in netbsd/amd64 so there’s that

I was soundly proven wrong

@prologic@twtxt.net the bytecode shouldn’t be a problem beyond Mac though?

I mean, since the current implementation is in Go

@bender@twtxt.net Interoperability is cool and all, but if it’s half-baked, don’t do it

@bender@twtxt.net I was even there when yarnd had the bespoke ActivityPub feature, I didn’t like it then, much less now, even if it’s separate

There is a slight possibility that I might move neko.laidback to another subdomain (I’ll leave 301s in place should that happen)

@prologic@twtxt.net

Shin'ya M. > grep bridge.twtxt.net /var/log/pleroma.log
14:01:33.937 path=/api/v1/accounts/B26ukWUhEh8kKl0oPw/follow user=shinyoukai [error] Follower/Following counter update for https://bridge.twtxt.net/users/c350a5e5fb9d9457 failed.
14:01:35.541 path=/users/shinyoukai [error] Could not decode user at fetch https://bridge.twtxt.net/keys/bridge, :not_found
14:01:38.286 path=/users/shinyoukai/outbox [error] Could not decode user at fetch https://bridge.twtxt.net/keys/bridge, :not_found

Targeting just Mastodon will get anyone nowhere

I certainly can do a lot of things when I don’t comply to society

Image

Image

@prologic@twtxt.net ultimately anyone can be at their 100% if left to their own devices

Work kills the soul

# $YakumoLabs$
# yarnd service file for https://github.com/davmac314/dinit
type = process
command = /usr/pkg/bin/yarnd -b 127.0.0.1:6446
env-file = /usr/pkg/etc/yarnd.conf
working-dir = /var/db/yarnd
restart = on-failure

and yaml is pretty bad with storing very large svg+xml within the hidden settings file, too

what did I miss, the logo breaking again, and apparently I cannot rid of it if I don’t want it, yikes

@movq@www.uninformativ.de rebuilding only httpd from CURRENT

@movq@www.uninformativ.de there’s the third option

@movq@www.uninformativ.de by 7.9 or use CURRENT 🤣

@prologic@twtxt.net porting SQLite would be kick-ass

@prologic@twtxt.net “AI” companies are clearly to blame

@eldersnake@we.loveprivacy.club

Mikuru (みくる)
https://projects.laidback.moe/mikuru/

@movq@www.uninformativ.de well, emojis in the TTY (as in, what we’re used to now, not actual teletypes) are simply rendered as tofu boxes or not at all

@movq@www.uninformativ.de that’s a huge no about the last part, but you know what will happen?

The 20th anniversary of the Haruhi Suzumiya anime series, that’s what!

(Also I was told YOTLD was actually 11 years ago and everyone joining it after that is pretty much late)

@javivf@adn.org.es

Happy New Year, nyoro- !!!!

@lyse@lyse.isobeef.org Do you have your client’s code hosted anywhere?

Likewise!

still stuck in the past

@lyse@lyse.isobeef.org •́⁠ ⁠ ⁠‿⁠ ⁠,⁠•̀

I do not plan to implement all the features of the reference client, though. But I might be writing an offline part that will be isolated from Yarn at some point.

Things I’ve learned along the way:

1. Writing self-contained and barely tied up programs didn’t go as well as I’d have thought
   
2. Reverse engineering (to put it that way) an open source library
   
3. Acceptance of non-Make build systems

@lyse@lyse.isobeef.org to be fair, that’s nothing, really

the logo used to be way larger and occupied the entire header, up to obfuscating the menu at my computer…

I do have a nitpick though, the logo isn’t transparent so it will look off in dark themes.

I can track users’ feeds now

@prologic@twtxt.net I’d happily write API documentation for go.yarn.social/client

It turns out doing such a thing all at once can obliterate one’s bandwidth if unchecked.

Also I was greeted with the most non-explanatory compiler error to date:

go build -v -o mikuru ./cmd

no errors

echo $?
1

I’m going to write the T.P.D.D. subcommand for Mikuru now

@movq@www.uninformativ.de the ‘writing a Yarn client’ thought goes all the way back to my ‘novaburst’ days in Yarn.social, but with the other pod apparently being gone, there’s no proof of it, except on everyone’s minds.

Test from v0.0.5

There might be a slim chance for me to end up using spf13/cobra for v0.0.5

In less than two days time, laidback.moe will be opened to the public.

It’s very likely I might have to host Mai again, simplytranslate.org isn’t cutting it anymore.

Sometimes I think RMS should just shut the hell up.

Why the hell do I have to git add everything!? Is it not enough for the file(s) to be already checked in from the get go?

Git = G(od damn)it

@lyse@lyse.isobeef.org You could always take a peek at the Go source

Posted from mikuru/0.0.3 @ NetBSD amd64

@lyse@lyse.isobeef.org the funny thing about it? There’s os.UserCacheDir(), it seems that the Go devs hasn’t acknowledged the $XDG_DATA_DIR yet