• 0 Posts
  • 43 Comments
Joined 11 months ago
cake
Cake day: December 25th, 2023

help-circle


  • For me it’s very simple: NSFW can’t have a general acceptable definition because it depends on culture, background and personal beliefs. There is no way for a collection of communities to have a common definition and even if they would have: enforcement and interpretation is still done by volunteers.

    Therefore All is never safe for work unless I know that my tolerance is lower than all communities within lemmy AND I’m fine with an accidental penis or breast due to human error.



  • Who should do this vetting though? The internet was built up with the idea of technical neutrality - everything else came on top. TLDs came later and were used to either describe the origin of a page or its intended(!) use. That leads to the case that not only can a propaganda outlet mark itself as “info” - it’s actually historically correct to do so as it’s about what the host wants to communicate.

    ICANN, the organisation behind the TLDs, actually always struggles with this btw. A more recent example was the decision which domain should be reserved for local name services. It took y long time (I think years overall) to get to: .internal (edited, brainfart)



  • User perspective:

    If you want something big I’d pitch nixos. As in the core distribution. It’s a documentation nightmare and as a user I had to go over options search and then trying to figure out what they mean more often than I found a comprehensive documentation.

    That would be half writing and half coordinating writers though I suspect.

    Another great project with mixed quality documentation is openhab. It fits the bill of more backend heavy side and the devs are very open in my experience. I see it actually as superior in its core concepts to the way more popular home assistant in every aspect except documentation!

    That said: thanks for putting the effort in! ♥










  • Uhm I don’t know your cultural background but at least around where I am the “own limitations” part is a crucial element of the therapy aspect. Accept your own limits to and work with your strengths.

    Managing and accepting restrictions is what is thought here for therapists (at least the fields I’m in closer contact with.

    This “widely knowing” people are at least not scientists as the last meta study I am aware of basically says “not enough data”: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7265021/

    That said: there is a high risk of discussing local variations on various therapy approaches and it’s even highly likely I’d guess that you’re absolutely correct for your medical cultural background and my lense is highly dissorted (from your pov) by my own.


  • Edit: I missed some complexity as suspected! I’m not sure how this process would handle hard and symlinks. Would add an experiment for that before going with the nix and root folders (it shouldn’t harm log at all).

    Original text: Perhaps I’m missing some complexity in your setup but from my understanding it’s really straight forward:

    The main caveat is that you need twice the space of your largest future sub volume. A garbage collect - d and any manual cleanup can help you there. I’d gets that approach with /var/log and when that works move over to the more critical systems.

    • You create the subvolumes within the partition you want to keep.
    • Mount them at a temp location and copy the files over.
    • alter your hardware.nix or whereever you’ve set your mount points to use the subvolume.
    • rebuild switch and reboot.

    If everything is working as expected, write a run book for every step and repeat with /home (i.e. have every step written up). Home is the second least critical folder for this.

    Once you have your runbook repeat the process and when you run out of space resize as needed. (e.g. https://btrfs.readthedocs.io/en/latest/btrfs-filesystem.html#man-filesystem-resize)

    That said: as you aim for the fully ephemeral root I personally would actually go the reibstwllwtion/reinstall route and write up everything I needed to do by hand. But that needs even more spare space (I’d prefer even a second disk for stuff like that to have a fallback).

    Good luck!