Friday, April 15, 2022

patching fcitx or, how opinionated can I be when porting?

Recently I was surprised by the fact that fcitx by default will save
clipboard contents to disk, without confirmation/notification. I would
like to patch out this feature in my fcitx5 port and make it opt-in
instead of opt-out by default. (fcitx's upstream is unwilling to
change this)

In future I would also like to restrict fcitx's internet/fs access
using unveil and pledge, but that will break things like cloud inputs
(sending input strings to google/baidu in realtime)...

so the question is, what's the consensus on patching software to
remove subjectively harmful features?

No comments:

Post a Comment