# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 481
# self = https://watcher.sour.is?uri=https://social.kyoko-project.wer.ee/user/akoizumi/twtxt.txt&offset=81
# next = https://watcher.sour.is?uri=https://social.kyoko-project.wer.ee/user/akoizumi/twtxt.txt&offset=181
@eaplmx don't fall for it, fediverse as a whole is a joke
@prologic i saw a database dump I made from sqlite converted to mariadb myself...
and there are a lot of commas right there XD
@prologic when a certain web server software only makes a job harder than it'd be otherwise done quickly with something like nginx (or apache, or caddy), something is AWFULLY wrong
fuck it, i'm throwing the towel with this one, i'll be planning lots of breaking changes on shelltalk, i can handle that by myself
my progress:
* subdomain: done
* database: done (after a few tries because I somehow got it wrong in mariadb)
* config: done (more or less)
* user: done
* ssh: not yet done <- maybe where the issue lies because someone took port 2222 lol
* tls: acme-client going insane by itself isn't helping at all so skipped
wew lad, getting gogs to cooperate with httpd is driving me mad
@movq and that's why I just use nginx, it just works
@movq acme-client, httpd, and relayd
@prologic nope, but i'm logged in onto the VPS at all times
if my <insert exposed service here> is ever down, i'll notice it instantly, and probably get to know the issue already ;P
@movq their in-house solutions, in my particular case, three of them are a total mess, and they can't beat muscle memory from past experiences, lol
@tel i'd rather just use gogs (which I already have) plus an external issue tracker/mailing lists than that behemoth
Is it wrong to disagree with the OpenBSD way of doing things, as a system admin?
@prologic exactly, it's essentially a blackhole, everything that gets in, won't be able to get out
Just've been playing with my email server a little bit today, I've set up a honeypot address and got rid of admin@ passwd entry because i already turned it into a forwarding address anyway
@lyse
> public domain trees
this took a really weird turn
"le champagne gophère" ~shokara, 2022~
@prologic for shaming them publicly (and they deserve it)
I totally could have used my pastebin, but the files will be deleted once every week by crontab, lol
@prologic what an unexpected outcome, I'll admit
I did it
I DID IT
I BLOCKED OUTLOOK FROM MY SERVER
YEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAH
My hobby:
Everytime I make a mention of UNIX in uppercase, I always add the trademark notice afterwards.
This post is totally not an exception to the rule.
UNIX(TM) is a trademark of the Open Group
@prologic fortunately that's not the case for me, hell, they don't even know about my dark side (to be concrete, this one) so....
@abucci @movq well, RIP for him. Putting that aside, i'ven't been having issues with my self-hosted email either, I'd like to straight up block Outlook though ;P
@prologic aka GMT, because for some stupid reason, UTC is translated wrong in every language including English lol
nevermind I fixed it now lol
dev
2022/09/03 18:01:41 [FATAL] [...koizumi/gogs/internal/db/repo.go:134 NewRepoContext()] Failed to set git user.email(exit status 255): error: could not lock config file /home/git/.gitconfig: Permission denied
2022/09/03 18:38:59 [ INFO] Kyoko's Tea 0.13.0+dev
2022/09/03 18:38:59 [FATAL] [...koizumi/gogs/internal/db/repo.go:134 NewRepoContext()] Failed to set git user.name(exit status 255): error: could not lock config file /home/git/.gitconfig: Permission denied
2022/09/03 18:39:04 [ INFO] Kyoko's Tea 0.13.0+dev
2022/09/03 18:39:05 [FATAL] [...koizumi/gogs/internal/db/repo.go:134 NewRepoContext()] Failed to set git user.email(exit status 255): error: could not lock config file /home/git/.gitconfig: Permission denied
and that's why I'm unable to run gogs as unprivileged user
However it somehow turned out troublesome for some of my things, hence why I ended up with gogs
@mckinley it's written in python though.... >_<_
@jlj postgresql more like CursedSQL ;P
a minor issue of this gogs instance is that it's running as root
lol?
gitea was such an unbearable clusterfuck, so was gogs until just now.
DAMN IT
AAAAAAAAAAAAAAAAAHAHAHAHAHAHAHAHAHA
@prologic nope, nginx wasn't the issue at all, I guess it just happened to be a broken gitea build what went into openbsd packages or something
it's already too much of a bother for something that claims to be painless, how ironic lol
wew lad, installing gitea took a really weird turn
@prologic
pretty much:
yarnd -n .kyoko -O -R --api-signing-key [redacted] --cookie-secret [redacted] --magiclink-secret [redacted] -u https://social.kyoko-project.wer.ee -d /usr/local/yarn/data --disable-archive -A akoizumi -E koizumi.aoi@kyoko-project.wer.ee -t /usr/local/yarn/kyoko
yeah yeah I know about the env vars but i think beyond systemd it gets rather troublesome
PD: you should unfollow my old ID on the dead pod ;P
My /usr/local is at its limit again, but I don't really have to worry about this pod like earlier
well great the issue that I described in #980 also happens in qtwebengine (chromium) lol
Oh boy
update on the php thing, it was totally a chroot thing, and I disabled it woooo
heh, the twtxt dimension got real fun lately
again, kyoko.nerdpol.ovh is dead, lol
@prologic same, although I doubt it'd be any useful though. Heck, even someone on github had forked yarnd's predecessor lol
gotta love dino fucking up my mixer's volume every time I launch it
glitch in the matrix!
@jason test passed successfully
phew finally, this will be live on my pod shortly after I tweak it a little more
i.e. seems to work fine anywhere else but timeline
well shoo I totally ruined the pod's css now lool
@mckinley my github account is also flagged for the same reasons, I just think gitea is not good software just because there's no dogfooding as you just said. What a pity
I'm pretty sure it has to do something with (over)using chroots, which for my particular use cases at KyokoNet, don't fit at all (or rather, I can't make them fit)
OpenBSD and PHP only work together if you're using the built-in httpd(8), but when you want to use nginx instead, good luck... It won't work
@movq if the solution means just throw more hardware at the problem, then something is outright wrong.
that always happens.... \\_(:/)_/
opensmtpd email forwarding is so lovely... ^.^
wew lad, i'm trying to set up temporary file upload and linx is totally not collaborating lmao
Geez, I need to rewrite the network's wiki, again.
This is it, the first and only ephemeral Yarn pod, and I run it!
