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

help-circle

  • Oh SpaceX core business including their numbers are amazing, I agree! But they also disclosed the whole AI stuff, including the madness of “inference in space” - the physics is then only one search away. … PayPal was really cool and solved problems as well - and so did Tesla!

    I think Musk is like a reverse Midas, eversthing he touches becomes shit for everyone else :/

    SpaceX was by far the biggest exciting development in the last years for me … There’s still hope I’ll be wrong though - hoping for it!


  • 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!




  • Scipitie@lemmy.dbzer0.comtoLinux@lemmy.mlScreensavers on Wayland
    link
    fedilink
    arrow-up
    11
    arrow-down
    2
    ·
    3 months ago

    If there are any plans I don’t know but what I can tell you is that there’s currently no way to circumvent these “restrictions” - because there are none.

    Although from a user perspective it feels like something got taken away from Wayland perspective it’s the other way arou d: screensavers want rights that Wayland simply doesn’t provide to any user space application.

    A screensaver needs to track user interaction globally (for the timeout), overlay over existing apps, manipulate viewport properties, manage the session and similar things, depending on the details.

    Depending on what you want there might be ways to hack something together though.

    Then there’s of course the disclaimer that although I’m not ab LLM my training data (aka experience) might be out of date :D







  • 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…