Weekly plan #N+1

[PingWIN7]

Some stuff to remember

• [x] Replacing meeting session with something else
• [x] Use JavaScript to pass meetingId
• [x] Add a meeting closed warning in meetings
• [x] Implement GUID for user ID
• [x] Replace google charts with a simple button on host page
• [x] Fix the QRCode button not sending string

important optional:

• [ ] Implement secret code generating (for password based meetings/interface)
• [ ] Hold secret code in javascript (if it is possible)

meh optional:

• [ ] modify stat screen so it's no longer send user count
• [ ] store password hashed (or something)
• [ ] if storing pw hashed rewrite the QRCode url generator

[wilka]

if storing pw hashed rewrite the QRCode url generator

Why would hashing the password change the URL generating?

[PingWIN7]

I’ve put that line there in case we decide to store the passwords differently.
We do not need to rewrite the URL generator but we do need to change some code in case we do as at the moment we just pull out the attendee password from the meeting and pass it to the generator. (I’ve mainly using these weekly plans for myself so I don’t really explain a lot here or well enough.)