No there's no reason that would arise from a systems architecture standpoint. This most definitely was an additive thing, that requires more code than less, in

No there's no reason that would arise from a systems architecture standpoint. This most definitely was an additive thing, that requires more code than less, in order to reactivate after 30 days (not much more code, but it's not some side effect of some system). The only reason I could think it's like this for a technical reason is if they put the opt-out "ticket" into some high availability cache system that was hard coded to eject old entries after 30 days, but that would make no sense given YouTube has infra for persistent user configuration already.