• 9 Posts
  • 118 Comments
Joined 2 年前
cake
Cake day: 2023年7月9日

help-circle



  • Worth noting is that “good” database design evolved over time (https://en.wikipedia.org/wiki/Database_normalization). If anything was setup pre-1970s, they wouldn’t have even had the conception of the normal forms used to cut down on data duplication. And even after they were defined, it would have been quite a while before the concepts trickled down from acedmemia to the engineers actually setting up the databases in production.

    On top of that, name to SSN is a many-to-many relationship - a single person can legally change their name, and may have to apply for a new SSN (e.g. in the case of identity theft). So even in a well normalized database, when you query the data in a “useful” form (e.g. results include name and SSN), it’s probably going to appear as if there are multiple people using the same SSN, as well as multiple SSNs assigned to the same person.


  • I’ve had the same problem with HeliBoard learning garbage. I just changed my settings though, and I think it should help:

    1. Open HeliBoard settings
    2. Open Text correction settings
    3. Scroll all the way to the bottom, and turn off “Add words to personal dictionary”

    If you scroll all the way to the top again, you can manually manage the personal dictionary, including adding words you do want, and deleting any junk that was added by mistake, before switching that setting off.












  • I just saw it today. Can confirm - it’s bad. Bad enough I’m upset it exists, because it practically taints the first.

    The plot is pretty weak, and to make it worse, sporadically there are flashes that make you think it’s finally building towards something, and then it just fizzles.

    With very few exceptions, the songs are bad both in terms of the music and the lyrics, and they slow the movie to a crawl.

    Additionally, Lady Gaga’s lip synching is shameful, especially considering she’s most famous for music. Her performance is otherwise fine, but it feels like they could have put anyone in there. She didn’t bring anything to the role.

    Joaquin Phoenix’s performance is pretty good, and the cinematography is good. But… Don’t see it. Definitely don’t pay for it. I wish I had my money and my time back.



  • I’ve personally lived in places where the closest convenience store was 2.25 km, and the grocery store was nearly 18km, as well as places where a convenience store was literally a part of my building, and grocery stores were walkable distances.

    The U.S. is enormous and varied. Take a look at truesizeof and compare the U.S. and Europe (don’t forget to add Alaska and Hawaii - they won’t be included in the contiguous states). Consider how different London is from rural Romania.




  • This ignores the first part of my response - if I, as a legitimate user, might get caught up in one of these trees, either by mistakenly approving a bot, or approving a user who approves a bot, and I risk losing my account if this happens, what is my incentive to approve anyone?

    Additionally, let’s assume I’m a really dumb bot creator, and I keep all of my bots in the same tree. I don’t bother to maintain a few legitimate accounts, and I don’t bother to have random users approve some of the bots. If my entire tree gets nuked, it’s still only a few weeks until I’m back at full force.

    With a very slightly smarter bot creator, you also won’t have a nice tree:

    As a new user looking for an approver, how do I know I’m not requesting (or otherwise getting) approved by a bot? To appear legitimate, they would be incentivized to approve legitimate users, in addition to bots.

    A reasonably intelligent bot creator would have several accounts they directly control and use legitimately (this keeps their foot in the door), would mix reaching out to random users for approval with having bots approve bots, and would approve legitimate users in addition to bots. The tree ends up as much more of a tangled graph.