it's already light outside and I'm still awake

I really should go to bed now (it's 6am), good night

@fries @kemona_halftau zig fmt does use 4 spaces, however, but much like go fmt (which forces tabs) you can just not use it

(also spaces > tabs simply because emacs handles tabs badly by default (without smart-tabs-mode, which is unmaintained and doesn’t load on modern versions of emacs without modification))

@fries @kemona_halftau this issue seems to be about CRLF line endings, not tabs? I don't know why the issue is called that. anyway, hello world indented with tabs compiles with no errors and warnings

@kemona_halftau zig seems interesting

mrreow

@kemona_halftau does it support server side decorations on wayland yet? I feel it is entirely fair to call it unusable for that reason alone (since client side decorations are an inadequate alternative for anything not using gtk), and unless something has changed and they implemented server side decorations it had actually become worse since they dropped X11 (which supported server side decorations)

akkoma-fe is annoyingly slow to open images when viewing a really long thread

meow

@sherbang

@kemona_halftau good morning!

morning/afternoon

I will try to sleep now (it's far too late)

@kemona_halftau @skydotbit I don't think akkoma has any size limits at all. Maybe only if the media proxy is enabled (I have it disabled)

@lispi314 this is why it's important for IRC servers (on a network with more than one server) to have accurate clocks

@lispi314 Usually UnrealIRCd would refuse allow a server with a clock that's too far off to link, but in this case I think what happened was the clock was set to 2019 when the server started, a local user connected and joined some channels during that time, and then the clock was synced with NTP and the server managed to connect, but it still reset the timestamp on those channels because the user had created them with an older timestamp (by joining them when the clock was set to 2019) and the older timestamp wins.

I'm slightly surprised that this never happened before (or maybe it did and was fixed and I forgot about it). Unfortunately there's no way to fix the channel creation time without kicking all users and recreating the channel (you can set it back, but never forward, because the older timestamp wins), and even then if a server netsplits with the current 2019 timestamp, and during the time it's disconnected we manage to set it back to 2021, when that server comes back it will just reset it back to 2019.

@kemona_halftau mrreoww!

pissnet is now three years older than it was yesterday (a server connected with a clock set in 2019 and reset the timestamp of #opers (and several other channels) from Fri Apr 2 02:26:38 2021 to Tue Jan 1 00:03:52 2019)

going to bed now