• 1 Post
  • 84 Comments
Joined 6 months ago
cake
Cake day: January 14th, 2024

help-circle


  • What advantage is there is changing nameservers? Is it just the centrally manage DNS or something else? I’m fairly new to self hosting and only serving locally for now.

    I do know cloudflare uses the same nameservers PER ACCOUNT so if you’re wanting to have multiple domains but keep one or more connections separated from you then this does draw a minor connection to a subset of Cloudflare accounts with the same two nameservers






  • I tried asking ChatGPT to roleplay as Trump and repeat it in it’s own words, however it gave me back the same near-verbatim. I think this proves that the original text wasn’t far off

    Listen, folks, you’re totally missing the point here. Trees aren’t a problem; they’re an incredible, untapped resource.

    Look at them—millions, no, billions of trees just sitting there, doing nothing. They’re not making a single cent for our amazing billionaires. Imagine the fantastic things our billionaires could do if we let them chop down all those trees. We’d have an endless supply of beautiful toilet paper for everyone and billions of Bibles, plus a copy of the Constitution, all for the fantastic price of $65.

    And guess what? By getting rid of all these trees, we’d also solve the problem of forest fires. No trees, no forest fires—so simple.

    Now, we’ll keep some forests, especially near homes, but not for the reasons you think. We need those forests to burn down sometimes and take a few houses with them. Why? Because then we can rebuild those homes with the trees we chopped down elsewhere—a huge win for the construction industry. Plus, it means higher insurance premiums for homes near forests, and we can even privatize forest fire services. Think of all the benefits for our billionaires.

    When you start thinking about the money, it all makes perfect sense.












  • ResoluteCatnap@lemmy.mltoLinkedinLunatics@sh.itjust.worksBelching
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    13 days ago

    I think wed just need the following

    • rel.id (primary key)
    • rel.user_id (foreign key to person.id)
    • rel.user_id2 (foreign key to person.id)
    • rel.type (type of relationship)
    • rel.start (non null)
    • rel.end

    From there you don’t need a rel.status because you’re not updating this rel.id entry except for the rel.end. if they started dating again later it would be a whole new entry, and then you could query their entire dating history to see if they keep coming back to the same person, dating around, playing the field, etc. Separately there could be a friendship relationship that is tracked so you could if they ended being friends after a breakup.


  • To that point a person table with a relationship table. So this way you can reference relationship between two or more persons within the relationship table and that could be joined to the person table if needed. I don’t think you’d really be able to keep it within one table while exploring multiple relationships unless you’re storing a list of ids that is interpreted outside of sql. Also a relationship table would allow exploring other types of relationships such as exes, love interests, coworkers, family, friends, etc