It'sintended to be used when the cookies are actually required for the app to work. For example, to preserve your login, you need a cookie, no way around. Unfortunately, as mentioned by others, it's often abused

Does "Database > Merge from Database" not work for your case? I remember it helping when I had a similar situation

Secure boot means only signed code can run in the kernel/ring 0. Grub, as the loader, needs to be signed as well. Basically anything with system privileges needs to be signed. If I remember right you need to enroll the signing key on installation, and the rest is handled automatically, but you can't use any custom kernel or kernel drivers.

Not a problem if you stick to Ubuntu packages. All packages in the default apt repositories contain signed stuff, so you can install drivers (graphics, virtualbox, ...) like normal. I had it accidentally enabled when I initially installed and only noticed when I tried to build custom drivers myself.

When everything closes, are you sure that's the lock screen and not the login screen? It sounds like cinnamon is crashing, which means you're automatically switched back to the display manager (login screen). This can sometimes show the boot logo while it's switching, happens on my laptop as well, noy sure why that is. If it is crashing, you might find the cause in the logs, run journalctl -e and dmesg to check for errors

555 is still in beta, so I wouldn't be surprised if something doesn't work. That said, I haven't experienced what you have (on GTX 1070 TI), though using 555 causes lots of kernel errors for me. Checking dmeg might reveal something in your case as well.

Usually we don't distinguish between many2one and one2many, since it's the same just viewed from the other entity.

There is one more class though, which is one2one. That is, the entities have a direct relationship. Sometimes this also includes the case where you have zero or one, i.e. the relation is optional on one side. This can be accomplished with an FK plus unique constraint or by merging the tables.

With git. Every time we start work, we pull. After every commit, we push (and pull/merge/rebase) if necessary.

We do, for two 2-3 person projects, where no code reviews are done. This is mostly because (a) it's "just" a rewrite and (b) most new functionality is small and well-defined. For bigger features a local branch is checked out and then merged back later. Commits are always up-to-date, which makes it much easier to test integration of new featues.

Pretty sure the commenter above meant that the their RAM was advertised as X GiB but they only got X GB, substitute X with 4/8/16/your amount

Can confirm, I'm using a dock (from Razor) daily without problems. Hot switching doesn't work though, you need to restart X/your display manager to connect or disconnect the eGPU. I'd recommend the gswitch utility to configure the graphics card to be used (on X11). Haven't tested much on Wayland, but I know that at least Gnome (Wayland only) has trouble mixing eGPU and the internal display if that is important.

Jerboa doesn't have anything to do with it, it is the app you use to access the fediverse/lemmy.

Lemmy has upvotes, downvotes and the tally of those two. Karma is a step further; on reddit, every user has a total tally (Karma) as well, where all up/downvotes of every comment and post are added together as a "score" for the user. So people post popular stuff to get upvotes and thus have a higher score (which some subreddits required to post).