8000 Packet triggers should be more identifiable · Issue #12 · errorinn/netsim · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Packet triggers should be more identifiable #12
Open
@apokusin

Description

@apokusin

It's hard to keep track of which packet triggers do what since they all look the same. Furthermore, it's unclear whether a new packet trigger is added to the top or bottom of the list, so I found myself clicking between each trigger to confirm I'm sending the right info. This was particularly important during the Man-in-the-middle attack.

My recommendation is to use a randomly generated color to identify each packet trigger. This color could also be used to identify the packet "orb" while in transit, making it easier to understand.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0