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

Suggestion: Auto expire wormhole connections. #183

Open
artibyrd opened this issue Jul 14, 2015 · 3 comments
Open

Suggestion: Auto expire wormhole connections. #183

artibyrd opened this issue Jul 14, 2015 · 3 comments

Comments

@artibyrd
Copy link

It is possible to determine the maximum length of time that a wormhole of a given type will remain open. I think it would be a nice feature if eve-wspace could automatically collapse connections after that maximum amount of time has transpired since the connection was added. You could even use this same logic to automatically mark wormhole connections as end of life. This feature would not be 100% accurate but wouldn't risk prematurely closing connections, and would be more accurate than connections that never expire without user intervention.

@nyrocron
Copy link
Contributor

I think this is a decent idea and applying it to sigs somehow would be nice too.

@acdervis
Copy link
Contributor

Are the maximum despawn times for sigs known?

If so, this would be great. Edit: Realized you're talking about wormhole sigs only. Still, it would be useful.

@Yracka
Copy link

Yracka commented Sep 8, 2015

You could have a projected EOL based on the info available. So a connection could show somehow as 'Likely EOL but unconfirmed'.

There could be settings for individual maps that give times for auto-delete for the various connection and sig types.

Or how about a 2 stage auto-deletion process.

  1. Sigs marked as 'auto-deleted' after the sig ages past the life span time in the map settings.
  2. Sigs remain in the list until manually deleted by a user with appropriate permissions.
    And a toggle to show sigs flagged as 'auto-deleted'.

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

4 participants