Glocker schedules your sudo access so you cannot casually disable its blocks

Glocker takes the admin account away from the person most likely to sabotage the distraction blocker: the person who installed it. Root causes, meet root access.

Noufal Ibrahim’s project page describes a Linux utility built for his own habits. Its unusual control is a scheduled window for administrative access. A block becomes much harder to wave away when changing the blocker requires privileges you’ve deliberately put out of reach for the afternoon.

The repository’s instructions call this a “Sudo window.” The built-in configuration editor is available for changes during that window; without sudo, it opens read-only. That creates an appointment with your own settings. Your future, distractible self doesn’t get to reschedule it just because something irresistible appeared in another tab.

The broader design combines blocking with usage tracking. Website blocking uses the hosts file, application blocks target process names, and an extension handles page keywords. These are different mechanisms with different limits. A blocked domain and a prohibited phrase inside a page are different requests, however similar the temptation may feel.

Before adopting this on a personal Linux machine, the interesting question is how ordinary maintenance fits around the schedule. A system update and a craving for a distracting site can both arrive outside office hours. The utility needs to be judged against the machine’s real responsibilities, particularly if that machine also has a habit of becoming the family’s emergency help desk.

The uninstall path deliberately asks for a reason and a typing challenge. That is a concrete form of friction: it gives an impulse time to become a decision. It also makes the recovery path part of the purchase decision, even when the software itself costs nothing. A blocker that resists you is doing what you requested, right up until you urgently need it to stop.

Ibrahim describes more than a year of personal use on the site. That is a developer’s report of his own experience, not evidence that the same arrangement suits every Linux user. A short trial on a spare environment would answer more practical questions than an elaborate promise about becoming a new person by Monday.

This kind of software could become more useful by making its maintenance and recovery behavior as legible as the blocking rules. The developer has already made the escape route an explicit part of the design. Whether that bargain works depends on which version of you is holding the keyboard when the scheduled window closes.

Sudo can wait until morning.