shinyoukai
neko.laidback.moeNo description provided.
↳
In-reply-to
»
Mu (µ) is coming along really nicely 🤣 Few things left to do (in order):
⤋ Read More
But hey! The read-eval-print-loop works!
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
Mikuru (みくる)
https://projects.laidback.moe/mikuru/
Happy New Year, nyoro- !!!!
@lyse@lyse.isobeef.org Do you have your client’s code hosted anywhere?
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
↳
In-reply-to
»
@lyse the funny thing about it? There's
⤋ Read More
os.UserCacheDir(), it seems that the Go devs hasn't acknowledged the $XDG_DATA_DIR yet
@lyse@lyse.isobeef.org You could always take a peek at the Go source
Posted from mikuru/0.0.3 @ NetBSD amd64
↳
In-reply-to
»
@shinyoukai Cool, I didn't know about
⤋ Read More
os.UserConfigDir() up until a few seconds ago! I always implemented that myself.
@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
Everything about the future is classified information
well, accidentally I did make a simpler yarn theme, in hindsight
Side effects of having a NetBSD server: I can use it to build things for my computer (also running NetBSD)
what would be funny is @prologic@twtxt.net writing things with his namesake (Prolog)
Once a bookworm, always a bookworm.
Man, I have no idea where the last build of the Yarn android client went to (even though it wasn’t all that good when I first used it, but it was relatively useful otherwise)
Yo @prologic@twtxt.net, apparently even ‘git clone’ is getting blocked by your Gitea or something (I’m using authentication, naturally)
くそっ、「会話」、このアプリは一体何なんだ？
↳
In-reply-to
»
@bender yeah, I've been reading through the documentation last night and it felt overwhelming for a minute... +1 point goes to GTS's docs. but hey, I'll be taking the easy route:
⤋ Read More
podman-compose up -d they provide both a container image and an example compose file in a separate git repo but I'm wondering why that is not mentioned anywhere in the docs, (unless it is and I haven't seen it yet)
@aelaraji@aelaraji.com not to mention you wouldn’t be able to, anyway (if you’re going to use the same domain between backends)
@prologic@twtxt.net
Interesting experiment for salty-chat, use the MQTT protocol instead of HTTP, in theory it shouldn’t make a difference, at least
The YAML forbidden knowledge of yarnd
Posting in anachronistic order, hah!
@prologic@twtxt.net do I just have to actually post the token into the twtxt timeline for the bridge?
(as in, for registration)
@prologic@twtxt.net Your gitea thinks the LICENSE file in the yarn repository is SSPL-1.0 instead of GNU AGPL 3.0,
and I can’t help but giggle at that
Alright, this yarnd installation has been properly fixed.
Shin’ya M. > doas npfctl table fail2ban list | wc -l
21
Up Next:
Twtxt feed support for Kosuzu
A simpler theme for Yarn, perhaps?
One day I’ll like to elaborate why I’m against the usage of Anubis (and its derivatives) for the rampant crawlers
Do not expect me to not hit other people’s nerves. You have been warned.
@prologic@twtxt.net I have returned