Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
This is going to vary by program and no solution is guaranteed to be perfect even if tailored for a specific time-sink program (TSP henceforth).
Would you be OK with the TSP being force-closed and potentially losing all progress and/or work, like a grumpy parent yanking a power cord?
What's to stop you from simply re-opening the TSP again? Or opening the TSP outside the control of whatever's supposed to tell you "no more"? (Related to "snooze" and "don't even bother setting the alarm" hacks for more regular alarm clocks!)