Hurray! A new microserver at home, with a new and all-fresh #honk instance.

I should probably go and give the #teamtinyhonkers trophy back to @knapjack

@grunfink @gyptazy @stesnac @stefano 🎉 I'm going to have to change #TeamTinyHonkers to #TeamTinyFedi.

@tedu I have a #TeamTinyHonkers problem, backend gets killed intermittently due to out-of-memory conditions:
2023-12-29T09:29:20.66571 kern.info: [960567.169381] oom-kill:constraint=CONSTRAINT_NON E,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=honk,pid=17449,uid=1000
Do you think using GOMEMLIMIT would keep the reaper at bay, and if so would setting that environment variable at launch affect the backend process or would I need to edit proc line in backend.go?

My honk host is currently an old Moto G4 running Termux, which was extremely stable for months but lately implodes about every five or six days. Upcoming landing pad:
OS: Void Linux armv7l Host: Raspberry Pi 2 Model B Rev 1.1 Kernel: 5.15.72_1 Uptime: 22 mins Packages: 131 (xbps-query) Shell: sh Terminal: /dev/pts/0 CPU: BCM2835 (4) @ 900MHz Memory: 37MiB / 923MiB
#TeamTinyHonkers

Man down on #TeamTinyHonkers, again. Termux keeps coredumping. This might be the weekend to migrate to @postmarketOS

We're back. #TeamTinyHonkers

Boo. My #HonkNet on ramp crashed twice in the last 24 hours or so. Might be time to reboot the host, upgrade, do some basic maintenance. #TeamTinyHonkers