view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Taking a brief look at that blog post, the author doesn't know that wt can be set to only notify... Or that wt can be set to act at specific date or time... It's like they never looked at the wt env variables at all, just yolo defaults and then complain that it doesn't do what they want out of the box ('because my settings are the best and they should clearly be the default for everyone!'). For someone who spent much time exploring other options and complaining, they didn't take ~10 minutes to learn that the initial issue was indeed themselves.
(I use wt and set up many options to avoid these issues, successfully)
I think he looked at it.
Why did they spend 8 paragraphs of 'this is terrible' and then be like 'but you can change that, though I decided not to'. I dunno, the whole post is stupid, imo. It's complaining about something that has already been resolved, then suggesting a different solution.
shrug