You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there's anything the NSA taught us, it's that metadata is important.
In this case, it would be great to be able to access the metadata from sneaky-creeper messages.
Data that would be useful:
Time the message was transmitted
... actually, that's all I can think of.
This perhaps lends itself to returning some sort of object/class from the modules - which would also enable None values for all of the entries (in case the module doesn't implement/can't access whatever metadata we put in place).
Perhaps something to the effect of:
# inside some hypothetical channel module
def receive(self):
# get the messages
toReturn = []
for message in messages:
toReturn.append(Message(message.text, message.timestamp))
# Message(message.text) is all that's required and timestamp is optional
return toReturn
The text was updated successfully, but these errors were encountered:
Also: part of the justification for doing it this way is that the platforms we're using to move messages (Twitter, Google Docs, etc.) have very, very good clocks, whereas if we were to rely on a hypothetical implant which uses sneaky-creeper to manually put a timestamp in all its messages, it might end up on machines with crazy unreliable/inaccurate clocks.
If there's anything the NSA taught us, it's that metadata is important.
In this case, it would be great to be able to access the metadata from sneaky-creeper messages.
Data that would be useful:
This perhaps lends itself to returning some sort of object/class from the modules - which would also enable
None
values for all of the entries (in case the module doesn't implement/can't access whatever metadata we put in place).Perhaps something to the effect of:
The text was updated successfully, but these errors were encountered: