Artemis Neko @Arteneko@queer.party

Welp, today marks the day I deleted my dev.to account.

Been a mod for a while on it, but I ultimately dropped activity after being increasingly tired of seeing it *filled* with marketing and aggressive advertisement bullshit for which the other mods and comms managers seemed pretty comfortable with.

It's become an empty platform, filled with nothing but "buy buy buy".
No more actually interesting complex tech articles.

I'm out of there.

@stolas@elekk.xyz "LGBT", "Political protests", yeah no, the only politics at play here are people who want to stomp on other people's right to exist and love.

twinkle twinkle little star, why is drawing an eye so fucking hard

To help each other grow, step by step, with full trust and openness.
No fear to have when we're together.
I chose to follow you because I think you're worth it, and I'm gonna spend my life doing my best to help you see yourself this way too.

blue went red blue went red blue went red~~~

Finally finished working on GitMgr, will try to deploy it on my prod server now.

Once this is out of the way, setting up automated backups, then starting to develop my own CI software!

The weirdest part is that the weird bug that inserted a rogue `<` in the page if two lines were right after the other without a blank line is also gone.

For some fucking weird reason, this TCP early-close bug only appears if my git branch has a certain name.

Staying on the main branch, with the same exact patches, works fine.

Huh.

aaaah how do I love overtly sexist course material in tech-related uni.

OK, since I'm a huge dumbass, I didn't do the very stupid test of "what exactly happens on the HTTP level when the generated HTML template is cut".

And, without any surprise, well... The connection's been closed by force at the same exact response size every time.

Which means that the template system isn't faulty. But I'm having a broken code somewhere that forcibly closes the requests.

I love how unreliable golang's HTML template library is.

Oh sure, we're in the middle of a link that has literally been rendered fine in the 15 previous entries. Let's randomly break here without any error and not generate anything more.

Impossible to combine multiple tcp listeners together in go... Damn.

Welp, I guess my systemd support will only take the first found listener