• 0 Posts
  • 12 Comments
Joined 6 months ago
cake
Cake day: January 14th, 2024

help-circle
  • ResoluteCatnap@lemmy.mltoLinkedinLunatics@sh.itjust.worksBelching
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    5 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




  • ResoluteCatnap@lemmy.mltoSelfhosted@lemmy.worldSelf-hosted diary
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 month ago

    Id set up a static website with Hugo. You can preview and build locally. Or put it on your home network and vpn in if you need remote access to make an entry.

    In your content folder you could do content/[year]/[month]/[day]/index.md, and have a _index.md in the year and in month folders so there would be pages with automatic collection of articles under that year/ month. You could also subdivide the content folder into health/ general/ shower thoughts and other “types” of journals

    They have support for tags, categories, and custom taxonomies. So if you wanted to have “people” category you could, and then a “thing” category or any other sort of way to tag the content.

    https://gohugo.io/





  • If you haven’t already, check out https://choosealicense.com/licenses/ . This gives a broad overview of the common open source licenses. And if you’re just starting out, one of the first things you’ll want to learn is that the licenses fall into either a permissive or copyleft category. You’ll want to make sure you understand the difference between those broad categories.

    Shortly, permissive have less to no strings attached to use their code, and copyleft requires you to retain the same licensing terms meaning if you publish under GPLv3 then someone using/ modifying your code needs to also publish under GPLv3. Copyleft licenses ensure that open source code stays open source.


  • Sounds like this was “resolved” on HN and CEO said this was an error, but I’m not so sure. The CEO’s response seems to imply that that communication to/from service reps is true and not made up. The original post shows they have a business practice for cases like this. Plus if the company was willing to settle from their business practice of 20% down to 5% (which in this case was 15k) then that very likely isn’t a decision a service rep could make, so you had some mid to upper level manager make that approval to write-off the $15k and decide that $5k was still owed to the company.

    As far as I can tell the only error here is that someone posted about it.

    Not to mention the CEO’s response from HN just says this shouldn’t have happened on free accounts, but that begs the question of would this have been any different on non-free accounts where Netlify failed to mitigate a DDoS as advertised?