The "now" key of the Rumble API is currently unused, but I think it should be available at least. One caution is to be sure to never use it in the RumbleAPI().refresh() method, unless it is written to not rely on RumbleAPI().getitem(), or it could cause infinite recursion. Perhaps it should be a non-refresh-triggering value for other reasons: Why would you check the data timestamp to have it automatically cause a refresh of the data?
The "now" key of the Rumble API is currently unused, but I think it should be available at least. One caution is to be sure to never use it in the RumbleAPI().refresh() method, unless it is written to not rely on RumbleAPI().getitem(), or it could cause infinite recursion. Perhaps it should be a non-refresh-triggering value for other reasons: Why would you check the data timestamp to have it automatically cause a refresh of the data?