Open ianmacd opened 2 years ago
Perhaps, but ideally I want to get away from the command-line tool entirely. Everything you can manage (aside from changing sogs.ini itself) should be controllable from within Session.
Perhaps, but ideally I want to get away from the command-line tool entirely. Everything you can manage (aside from changing sogs.ini itself) should be controllable from within Session.
That will never be convenient for processing multiple transactions, however. It's also not unthinkable that a SOGS operator may be just a service provider and not use Session himself. I, myself, operate several language groups that I am not a member of, for example.
There's also the unknown of just how long it will be before Session catches up with PySOGS.
Several times now, I've had to enter some unwieldy SQL queries to perform recurring tasks, like figuring out whether someone is still present in a room or has already left, or whether a user is banned, or just to unban a user banned in error.
I may have a stab at implementing these features myself. I opened the issues not to saddle you with work, but just to put them on the radar as it's something I keep meaning to do.
i was searching for how to do this, and the search led to this thread... It would be handy to get a list in the terminal. That could help (at least myself) identify the difference between people (on a bad day) spamming links, and those counterfeiting someone else...
--banned
would be nice to have in combination with--rooms
to list the Session ids of banned users in the given rooms.