to state my opinion on the proposal, this is a "no-brainer" yes this "no SaaSS" requirement ought to be easy and painless for distros to follow; because whichever SaaSS client is in question, most often with SaaSS, the service is duplicating an "offline" tool which has existed for many years
so, by definition, there is probably some libre substitute which accomplishes that task and runs locally; and if that task is common or important, the distro probably already distributes a tool which accomplishes that task - so even if the SaaSS tool were acceptable, it is still redundant, duplicating functionality that the distro already has in this specific case for parabola, apertium was already in the repos - the decision to remove ydcv (and another similar tool which appeared around the same time 'translate-shell') was inconsequential - no functionality was lost from the distro in their absence my criteria would be, that in order for some SaaSS client to be acceptable, there must exist some known way to use that client with a compatible libre service, running locally or self-hosted; and that the client should not be able to access any specific remote service by default - it could be pre-configured for a localhost service by default, but be otherwise useless out-of-the-box, without a locally running service, pending manual configuration for any specific remote server that would be acceptable because, it is not SaaSS, except when configured for a specific remote SaaSS service
