Admiral Patrick

I’m surprisingly level-headed for being a walking knot of anxiety.

Ask me anything.

Special skills include: Knowing all the “na na na nah nah nah na” parts of the Three’s Company theme.

I also develop Tesseract UI for Lemmy/Sublinks

  • 91 Posts
  • 778 Comments
Joined 3 years ago
cake
Cake day: June 6th, 2023

help-circle










  • An optional field was added to the userdb to allow storing birthdate. That’s it.

    The systemd project merged a pull request adding a new birthDate field to the JSON user records managed by userdb in response to the age verification laws of California, Colorado, and Brazil.

    This is the same record that already holds basic user metadata like realName, emailAddress, and location. The field stores a full date in YYYY-MM-DD format and can only be set by administrators, not by users themselves.

    An optional field in the userdb JSON object. It’s not a policy engine, not an API for apps. We just define the field, so that it’s standardized iff [sic] people want to store the date there, but it’s entirely optional.

    –Lennart Poettering

    https://itsfoss.com/news/systemd-age-verification/



  • Speaking from recent experience, the smaller thing can, and often does, turn into a larger thing all on its own and always at the worst time.

    For the last 3 years, I knew my water heater was on its last legs. I kept putting it off until two Saturdays ago I had a wet basement and no hot water. The kick in the ass was that it wasn’t that hard to replace the unit: 2 hours of labor to install and 2 hours to drain, remove, and clean around the old one. Cost me just under $650 including same day delivery which was awesome because I would have had to rent a truck and drafted someone to help me load/unload it otherwise.

    So my advice is when you allocate time to address the small problem, give yourself double that in case it turns into a bigger project. It’s always easier to deal with big stuff when it’s not a surprise.




  • Definitely could, but I won’t hold my breath waiting for a feature to make it to the API. There’s enough 3rd party app support and enough people using flairs in the [flair] format, even though it’s not “officially” supported in Lemmy-UI, that I think we’d be safe implementing this.

    And should an API-level flag ever happen, then all apps would need to do is look for that boolean attribute in the Post object rather than checking the title for the spoiler flair - the rest of the handling logic can remain the same. So it’s not like we’d have to make major changes if we ever get an official spoiler flag. It would also be easy to support both so there could be backwards compatibility or for other platforms that may lack an official spoiler flag.