Admiral Patrick

I learned to play the guitar growing up as a young rapscallion in Mississippi. But things didn’t really take off until I moved to Memphis. There I met the Colonel and the hits just kept coming. Unfortunately, the fame went to my head, I gained a lot of weight, started wearing a white jumpsuit, and ate tranquilizers like they were trail mix. Then, in 1977, I died on the toilet.

Or did I?


I also develop Tesseract UI for Lemmy/Sublinks

  • 912 Posts
  • 6.53K Comments
Joined 3 years ago
cake
Cake day: June 6th, 2023

help-circle













  • I don’t really have one myself, but there was a lady I knew growing up who made, hands down, the best chili ever. She wouldn’t reveal her recipe or secret ingredient to anyone and swore she’d take it to her grave.

    Years later, she and her daughter got into a fight and the daughter posted her mom’s chili recipe on Facebook to spite her. The secret ingredient was, apparently, grape jelly.







  • Cool, thanks. I’ll give that a read and see if I can make it work cleanly. At this point, it’s just an experiment, but I’ve wanted to have some mechanism for a standardized machine-readable community rules for a long time, specifically to put into the report and moderation workflows. If I can make it work cleanly, and if it’s not something already planned for Lemmy 1.0, I’m absolutely willing to make that a Tesseract feature.



  • What’s the significance of this syntax with regard to it not rendering?

      [//]: # (r1: Posts must be ...)
      [//]: # (r3: Posts must not be ...)
      [//]: # (r2: Posts must be ...)
    

    I’ve long wanted a somewhat standardized way to define community rules so I could do exactly what you were describing in your issue, but I’m not clear on how/why that syntax doesn’t render.

    I tried it in Tesseract, which admittedly use a different markdown renderer than other apps, and the first line shows but the second and third don’t.

    If other apps can get on board with that, then I may need to understand what’s happening in that syntax to make sure it doesn’t render.


  • Somehow the description of the filter differences for mods and admins got lost, so here’s that:

    Filter Behavior for Mods and Admins

    Depending on your account’s role in relation to the content’s, the filters behave differently and some functionality is reduced or disabled.

    Admins: There are two different types of admins recognized by the filter processor: local and remote.

    • Local admins when the content is on the same instance as your account
    • Remote admins when the content is from a federated instance

    For local admins, all filtering is disabled for posts and comments to local communities, and submissions cannot even be collapsed into a stub.

    For remote admins, content from remote instances can be collapsed into a stub but NOT hidden.

    Moderators: All filtering is bypassed in communities you moderate. Nothing posted or commented in your moderated communities can be filtered or hidden.

    This behavior was chosen in order to prevent moderation blind spots.


  • Found the first post-release bug, but it’s mostly just the wording.

    The imported groups will merge with any existing groups

    That is not true at all. It was when I wrote the description for that, but I changed the importer behavior to completely replace your current config. When you import groups through the group editor, they will merge, but not through the settings importer.

    The reason for that change was so that copying your settings between devices would move the entire application state (minus profiles, for security/safety reasons).