• 1 Post
  • 8 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle




  • I didn’t notice any downtime of course as I would have been asleep at the time haha. I just wanted to jump in here and say that I really appreciate all the work you put into running this instance and maintaining it’s content. I know it is early days and the lemmy software isn’t super stable or easy to work with, not to mention the monetary aspect of the costs of the server time.

    I’m just happy there’s somewhere non-commercial I can go now to see my strange combination of yiff, news, and memes. I’m sure we can all tolerate a bit of downtime here and there, so try not to worry about it too much when it happens. We know you can’t be available 24/7 so some downtime is inevitable, try not to fret about it too much when it happens. And for goodness sake don’t overwork yourself and get the burnout, I’m pretty sure that’s happened to several of the larger instance admins so far, I’d hate to see you befallen the same fate.


  • Not universal but it’s the unfortunate reality that people obsess over stuff they don’t like as a form of internalized repression. They better be careful though, looking at so many furry images while downvoting they may eventually catch the pathOwOgen.

    It’s nice that you can get this information by querying the database directly but it would be nicer still if it was built into the admin or mod interface somehow. Although I imagine in order to compile that information you used some sort of DB aggregation which could be unexpectedly resource intensive on larger instances so perhaps not.

    I wonder how possible it would be to create some sort of plugin system for lemmy to add functionality like this and more that would only be of interest to particular lemmy instances. That could help to keep the core of the server small and lightweight while giving people the option developing and installing server resident bots, additional functionality, and user interface enhancements as they see fit.


  • I had a peek at the source code and although I don’t actually know Rust it looks like that error comes from a check for character length in the function “is_valid_body_field”. Strangely it does the same check twice against two variables “POST_BODY_MAX_LENGTH” and “BODY_MAX_LENGTH”.

    The smaller of the two is BODY_MAX_LENGTH which is set at 10000, so I assume the max character limit is 10,000. There are no other checks in that function other than the character count and that’s the only place in the source code that the text “invalid_body_field” shows up so I assume it’s only sent as a response to too much text, but as I said I don’t actually know Rust so I could be wrong.



  • Did you try plugging it in initially after you disassembled it and reassembled it? I’ve found on chromebooks that the embedded controller doesn’t seem to wake up until the charger is plugged in after unplugging the battery. Could it be that you initially didn’t plug it in before trying it months ago, but months later you figured the battery would be low after all that time so you plugged it in finally starting the embedded controller?