• 0 Posts
  • 49 Comments
Joined 3 years ago
cake
Cake day: December 25th, 2023

help-circle


  • You’re mixing two things:

    First, you’re right this file I personally would not trust and keep quarantined.

    I don’t know Malwarebytes but Windows Defender back in the day only would get active on files you or your system interacted with -> would make sense that you only get one alarm. In addition, windows was notoriously bad with multiple virus scanners as they themselves show infection patterns in their behavior,(who else than a virus and a scanner wants to access literally everything you do?). So: i would err on the side of caution.

    But then there’s the question about the source. And here I can only ask you to be more careful: never trust a source more than your own defense layers. Even the most reputable file sources will have things that will harm you - including the Microsoft Windows updates themselves by the way.

    But here it’s more critical: don’t trust pirate sites. Ever. No matter how good their reputation.

    Oh and yadda yadda Linux blah but someone else will give that talk I assume ;)

    Stay safe!



  • Sounds reasonable. I’d you, like me, need to protect yourself from sabotaging your own system you could even make NAS documents read only to force a manual step in before editing there.

    For me the amount of items that should be there are zero following my own concept … But for some (especially shared sheets specifically) I’m too lazy.

    Perhaps I should listen to my own advice here zzz


  • Paperless specifically: yes, shoving everything in it.

    But I have honestly no idea what kind of data you have that are suitable for paperless AND have different versions.

    I just checked mine, for me it’s… Zero. Not a single item, by definition, is in Paperless that can receive an update.

    If it’s updatable personally I have everything version controlled - and I mean EVERYTHING, from CV over tutorials to construction ideas - hosted locally on forgejo.


  • Hey, Welcome! You’re having a wonderful and sometimes exhausting journey in front of you :)

    I’ll just brain dump based on your questions and my associations. Hope something useful is in between!

    First the basic setup options because they tie into how to handle your date flow:

    basic Most popular I think is docker compose: here I suggest splitting it into one compose file per service though with one file holding your port config. This prevents you yourself getting confused by your port mappings :)

    Second in line is a proxmox setup - similar vein and I lack the hands-on experience to talk about the difference.

    Then there’s the “everything native” approach where you don’t rely on containers but manage it yourself or via a dedicated OS that makes life easier (after the learning curve) like nixos.

    DATA

    All this foundational stuff is important because it changes your approach. In general: don’t fear data duplication. Duplicate it until you learn where you want your data to life and only then define your flow.

    Specific example: after I got used to paperless I don’t look into my opencloud anymore, at all. I still duplicate them there but as distributed backup, not for consumption.

    If a dataset has a clear place ten it’s easy. If not then your options are different depending on your setup: For the *arr stack the official recommendation is to use one shared folder and mount that into each part for example. I personally don’t like that and have hard links for everything - that’s basically a pointer to the file that looks like the file itself everywhere. As long as one pointer exists the file still stays on your drive but when the last pointer is gone, the file is effectively deleted. On Linux, you can think of every file this way but by default only one pointer exists (which often people test as synonymous to “the file”. Drawdown: this only works really well if you manually keep either track of which tool links where or you don’t containerize everything.

    Again a specific example: My downloaded torrents never get moved - instead hard links are created into whichever path and naming scheme I defined for each consumer - this way, out of murdrrbot_07.mp3 a new author/series/booktitle.mp3 was created, both pointing to the same data and seeing it as a proper file.

    But then there is one more thing: I suggest you split your thinking into data consumption and manipulation - because for the first, data duplication doesn’t matter. Especially for documents you’re talking about a ridiculous small amount of disk space and if it’s only reading/watching/hearing you as manager have no problem that data might exist multiple times.

    If you want to keep it clean by design then you’re leaving the starter mode self holster - welcome to system design and infrastructure architecture! Here your approach could be to define lifecycles for each data type that you have. What a “data type” is in this context btw is a user term, NOT the underlying tech stack. You need to understand and document how an invoice should be treated and consumed by you differently than an invitation or a informal letter. Only then do you map file types, incoming channels, transformation steps, etc etc.

    In my opinion: huge overkill to this upfront.

    In short: spin everything up, observe how you use it and only then decide where things need to stay unique and cleaned up. Don’t break your head over something that’s actually quite easy to repair!



  • With the author and de facto owner being a translator who says it isn’t enough. He is dependent on engagement more than anything else I suspect.

    To be clear: I’m not suspecting him of having been bought to write this - but he clearly has a hate boner for anything AI, isn’t from a software background and wrote an opinion piece with several statements that a re factually incorrect to reinforce a point he’s trying to create to get exactly posts like this.



  • Just curious, what makes you think this is a lot?

    Red cross, doctors without borders, Firefox are three that jumped into my mind. I don’t know their legal constructs in detail but Médecins Sans Frontières in their finance report 2024 described half a billion in available assets.

    The Linux Foundation is quite small compared to the amount of projects they coordinate in my opinion and I’m surprised to read that you perceive this amount as a lot - that’s why I’m curious where your feeling comes from! (Note: im trying to learn,not bias to “it’s not a lot” is quite weird to me as well, talking about millions of dollars after all)



  • oh you’ll get this reply from me in any community that you’ll attack without attempting to join.

    MAM is one of the friendliest places in existence and instead of interacting with the people and just asking for help the statement is “you all suck”.

    we’re not taking about elitist bullshit but about entitlement. My tone was way more friendly than the one OP chose after all, consciously though.

    If they’d said “I don’t know what to do” the answer would’ve been very different.

    Your comment is just … fitting. Calling me a representation for a cancerous behavior that I called out in OP: unreflective entitlement “my ways are correct”.

    I don’t engage with private tracker communities beyond mam for that reason:

    single sentence judgments, no explanations, blaming others…



  • Or is the quintessential immutability.

    Yes.

    It’s also a completely different way to handle … everything.

    Do not think about nixos if you want to know what to try for gaming.

    Do look at it id you want to learn the ins and outs of … Well, to be honest nixos. But I’ve learned a lot about standard paths that everyone expects to be there and hell’s loose if they aren’t.

    Python runs amok if it can’t write into it’s beloved lib folders, nginx is utterly confused why it can’t generate certificates on startup (read only folders), deployment dependencies are absolutely visible - and if you fick up the whole system just goes “nah, take a step back and think about what you just did”.

    I’m now pushing two years on my server and I’m still not sure if I’d recommend it - but I for sure enjoy it!



  • That’s sich a Mac answer it’s unbelievable.

    Describing “A project aimed to be agnostic of it’s environment” as a design mistake and not a inherent flaw of the OS is… Just wow.

    Remember in this thread it’s about the pro and con of Macos as interference hardware. This is a major flaw which comes baked into the hardware. I tested it and find it an unacceptable limitation. It’s important for others to know.

    To state “containerization is the issue” though… Just wow.



  • This got way longer than expected but the tldr is: foreign exchange is super complex and depends on a lot of factors which don’t matter to you as money user. I tried to give a few examples below.

    Plus: You’re mixing up two very different concepts:

    Fiat evaluation and purchasing power.

    First, money;

    “More worth” is a natural instinct but doesn’t reflect how the money market works: it’s a question of how much of that money is in circulation as well for example:

    1107650 CHF Million 19396,90 USD Billion

    (Source tradingeconomics.com ).

    So while it’s the CHF is slightly over value when compared one to one the picture is different when you look at total money available. Then you look at production capacity, glue creation and supply and demand for those currencies. All of this will flow into the price.


    The minimum wage discussion is a completely different one: here you need to compare minimum wage to the purchasing power of the area you are looking at and take into consideration how the tax and financial situation changes to be able to compare it.

    There’s for example concept called big Mac index which is a crude way of showing the difference: how much does MacDonald’s charge for their bullshit? They are everywhere and quite good at finding a acceptable local price.

    If you want to dive deeper a key word to look for is the Gini Index with which the wealth distribution is quantified. I’m not good enough to explain it well though.


    Now for the colors: design of money is the job of the nations (or unions) main bank to decide usually. The US seem to have the creativity of a washed down rock while others are more creative.

    The Euro money for example is designed with guardrails by each member country but color, size and form are fixed and optimized to be easily recognized even with various visual impediments, which I personally really like.