• 1 Post
  • 29 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle



  • Hallucination thought does fit.

    It’s a term in the context of a source that implies untrustworthy, not authoritative and/or imagined.

    Lots of examples in every day usage or scenarios that come to mind.

    “And then I saw the defendant punch the victim and then I was blinded by the sunlight”

    Are you sure you didn’t hallucinate the entire episode? It was night after all.

    Or

    “Somebody please get these ants off of me”

    Doctor writes: Hallucinations of ants on skin





  • Mostly storage space and ease of updating records.

    Let’s say you have records of users who watch a TV show.

    You could keep users as a key and shows as an array. Where each array entry is a record of the TV show title, release date, and other info such as time watched by that user.

    In this case you’re duplicate the strings for shows like “Fallout” and the release date thousands of times. And then if there’s an update such as a title change or the streaming service or channel where it’s found you have to find those thousands of subrecords and update them.

    Keeping a reference to another key/json file by some ID makes it easier to do such updates and reduces storage for that data. Except now you have to correlate that data when doing things like reports of what shows were watched by what users.




  • It does but it also makes sense. This way people can’t have “family” member alt accounts for cheating with the primary as a parachute.

    But… I’d like to see something like “if a family member gets banned then their access to sharing is blocked and you will get a temp ban”

    This way I can rain down hell on whoever screwed up and the penalty for trusting them isn’t permanent