Agreed, and it’s on the list.
But let me point out that hundreds of companies have used Aerospike for exactly what you’re using it for, and no one has ever requested that feature. All of them prefer setting a specific TTL on each write, because they know when doing that write how long that information should be effective. That’s how everyone else does it. Your math and understanding of your data may be different, so that’s why the feature is now on the list, and you’ve got a work around.
If you’re super jazzed to do it yourself, you can submit a pull request. But you’ll probably have to upgrade the protocol because we’re low on bits, which means a fair amount of work.