Add a timestamp field for Interaction object

[TheKing-OfTime]

I was very surprised when I didn't see this field in the Interaction object. I think this field will be very useful in many cases.

[Rapptz]

You can compute it from the snowflake ID.

[TheKing-OfTime]

Yes. i can. But then why does this field exist in the message object? timestamp can also be obtained from the ID. Now one part of the API is done in one way. Another part is done in a different way. I think this is bad and I also think the API should have a certain structure.

[Rapptz]

The message object is the exception, every other object with a derivable timestamp does not send it. Message objects have sent it since v1 of the API -- it's most likely deprecated legacy.

[advaith1]

#2065 (comment)

[amatsagu]

Being honest I don't get it why you would want do have it. In my opinion, timestamps from all objects you can potentially receive should vanish. Each object has own id and Discord's ids are snowflakes. You can get exact timestamp from snowflake.

Having extra timestamp field on each payload makes it only heavier. You may see it's not much which is true. But at scale - from just a few extra bites you may end up with megabytes of saved network. (very big bots may save up to GB)