Alternatives for --force-login

[GijsTimmers]

See this image:

This makes --force-login useless.

[GijsTimmers]

I've just checked. The maximum number of IPs at the moment is 2. That means that
there's still a use for --force-login or a derivative.

We need to decide, what IP should be logged out, though. Some ideas:

• Change --force-login behaviour: always log out all logged in IP addresses
• --force-login gets deprecated; if the maximum number of IPs is reached, --login will exit with an error code and show the currently logged in IP's. The user can then enter one of the following commands:
  • --logout-oldest: logout of the oldest obtained IP
  • --logout-latest: logout of the latest obtained IP
  • --logout:
    • --logout 10.92.32.43 logs out IP 10.92.32.43
    • --logout here logs out the current IP.
    • --logout logs out the current IP (if possible)

This change in Kotnet policy is great for users, but doesn't really come in handy for the project. We'll have to reconsider the project's design and roadmap.

[jovanbulck]

Yep indeed

I propose temporarily omitting the force-login option and currently focus on logging in/out with the current design in mind. As the implementation is currently upside down, getting the key features --login and --logout stable should be our core concern now, I think. Ommiting force-login for now will easy things somehow and allow a better integration in the end I think.

Adding some of the options you mentioned above should then be incorporated in the v3.0.0 roadmap. If so, we should change the label of this issue accordingly...