Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Access to Message Metadata #88

Open
DakotaNelson opened this issue Dec 4, 2015 · 1 comment
Open

Access to Message Metadata #88

DakotaNelson opened this issue Dec 4, 2015 · 1 comment

Comments

@DakotaNelson
Copy link
Owner

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
@DakotaNelson
Copy link
Owner Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant