yah thats what i meant.

in a way.

noice thanks.

luks will also prevent or uphold the encryption if e.g. the power is pulled?

+this means that if someone breaks in, cuts the cables during running decrypted the data is still safe?

you mean that even if the next user formats it you make sure that leftovers/artefacts cannot be read right?

asking out of curiousity: what benefits does encryption have here?

as long the server runs everything is decrypted right? so you are encrypting for the case when someone actively steals your hardware?

edit: stealing as in taking away. but this would mean accessing during runtime is nonetheless possible in a decrypted way?

https://getgreenshot.org/

sitting in the sam boat at work. I like it even more than flameshot at home.

thats pretty common, in my country as well.

like a two factor authentication. but without TOTP. but with a proprietary app by the bank provided.

is this unrelated to https://jan.ai/?

I just love how they giving you a link on an disfunctional pc. und do not mention which process died.

but damn this one must be important.

paywall free version?

edit: https://huggingface.co/openai/gpt-oss-20b

i feel that. Hetzner support has a special place in my heart

discords is the worst. i dont get it. really.

haha me too. although it was ported to fortran 4, 77 and 2003 respectively. still the logic remained in its core.

But i must admit. working on such organic grown is harder then doing yourself. comments was devils work at that time. variables shortened to 3 chars for memory sake. really a pain in the ass.

most user friendly? cough cough. I doubt. for this - as in works as is - the journey is still long.

for such things like shared documents/database entities also a shared test dataset should be available.

Then they cannot play around and modify those outputs anymore without noticing of others. (because their unittests would fail)

my assumption here is only an example. I dont know what youre dealing with.

While I understand the rant. And am on your side regarding those jerk moves. its a management issue. even when they do not act, its up to you to bring this to attention if this seriously conflicts with your work.

And in the long run its a win win for everyone.

edit: I am working myself in early development and despite being an engineer by background Im coding. So I know quite well how difficult it is to make it properly instead of quick and dirty.

this readme is very nice.

how come that they can circumvent them?

merge is only allowed after passing the pipeline.

unittests have to be in place else merge is also cancelled.

they should simply dont get that far to make troubles for other parts of the codebase

company wide policies.

building a proper ci/cd goes with that.

rules and delegations for each teammember.

some has to be the head and reviews.

time consuming probably. but professional in the long run.

the plot seems so random that it probably fucks. In a good way

while I had my doubts when seeing the thumbnail, i think this has potential to be quite fun.

the textures look kind if poor, but I guess that rolls with the concept of the game.

the dessert looks like straight from breaking bad, so I guess you can fetch some storyline quirks from there.

but really. put some work into the cover image. based from the image I thought this would be another generic low effort mobile game ad.

we built this shit. thus we are always to blame.