ilumos / lanager Goto Github PK

Configurable minimum length of time between shouts to prevent spamming.

The duration value in the playlist only shows minutes and seconds. Longer videos do crop up at our events so it would be nice to have them displayed correctly.

In order to improve the speed of adding content, setting up a lanager session for a new party, and to eliminate the risky practice of granting other admins access to the raw tables in MySQL, I think the following functionality should be added:

• An info admin page and an event admin page with the functionality for Creating, editing and deleting entries from within lanager. Such a page need be nothing more than a list of event/info records (likely ordered by the Title field) with "Edit | Delete | Visible" buttons by each entry, and a 'New' button above the list.
• Editing the entry would take the user to a form populated with the data for that entry, not dissimilar to the exisitng event creation form. Clicking 'New' from the list of entries would understandably take the user to a blank form, with a submit button.
• Only admin users should have access to these pages
• A collapsible frame alongside the Edit/New form would show a Markdown 'cheat-sheet' as a reminder for editors.
• The 'visibility' of events and info pages should be set-able, meaning that commonly-used items could be disabled, edited and re-used without removing them from the databse outright

Create a SQL script or admin page that allows authorised users to 'initialise' the database ready for a new party. Such a script should ideally perform the following actions:

• Archive all shouts
• Archive non-privileged users
• Disable (but not delete) events, perhaps marking them as invisible so commonly-used events (e.g. Food orders, award ceremonies, party open/close times) can be edited and reused (See issue #Num: #16 )
• As above, but with info pages
• Archive video playlist and initialise

'Archiving' would usefully have the option of either dumping CSV/SQL or outright deleting the deprecated records

Presently users don't actively look at the shouts page unless it's up on the big screen. I feel the following improvements would cause users to autonomously use the shouts page as a reliable means of keeping up with announcements that organisers make over the microphone (e.g. minimise the frequency of people coming up and asking "what did you just say about food orders/game x/beards?")

• Slight formatting emphasis on admin usernames for all of their shouts
• Timestamp for shouts (e.g. [Day name] [hour:minute] would be sufficient in my case
• Admins can 'sticky' any post to the top of the shouts list, as well as 'unstick' them or delete them. Stickied posts should have a formatting emphasis.

Clicking on a player's username on the 'Being Played' list returns 404. Tries to link to http://lanager/profile/<steam_id>

Steam login process is fine up until the user verifies their account, where the browser then drops back to a 404 page with localhost as the hostname.
The steam login button uses the URI https://steamcommunity.com/openid/login?openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=checkid_setup&openid.return_to=http%3A%2F%2Flocalhost%2Flogin&openid.realm=http%3A%2F%2Flocalhost&openid.ns.sreg=http%3A%2F%2Fopenid.net%2Fextensions%2Fsreg%2F1.1&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select

Simply substituting localhost for the hostname of the lanager server allows you to complete the login process.
A similar thing happens when logging out.

To help focus design and compatibility efforts

When completing a new event form, the list of managers doesn't correspond to the list of user ids. Either creates event with wrong manager, or throws a database constraint exception (i.e. invalid id).

http://lanager/event/create - database reports the user ids as 3, 2, 1 respectively

Currently a long unbroken block of text causes the layout to stretch horizontally

Two measures for improving the fairness and enjoyment of the video playlisting system:

• Limit number of times that a single video can be submitted to the playlist by anyone (flipping trolls m8)
• Limit number of consecutive video submissions from one user