Talking Moose

Home of the famous Talking Moose. She makes me laugh.

Home of the Talking Moose

To Do List for Moose work

By

New Build Sept 19, 2018. Can now access One_Core Voices, but not yet ALL voices combined. Test Build, logs but hasn’t solved the crashes when my VPN is on. New Azure functions DLL. Main entry point Async.

Last updated this to-do list below: Sept 19, 2018.

  1. A “sign out” in Login.html is now clearing all the User.whatevers, which suprised me. How about 2 kinds of signout:
    1. Sign-out but keep User info locally (for someone deliberately intending to switch from Facebook to Twitter)
    2. Sign-out and clear user info from local files. (for someone intending to give the Moose to a friend)
    3. For testing plugins that need the cloud, I sometimes want to sign out, and test the messages I’ve coded, informing users they must be signed in.
  2. A New User Reset button chosen in green dialog, is incorrectly putting a name into the User.Email
  3. A New User Reset should get Country and language from Microsoft, and set those values in User.Country and User.Language
  4. A New User Reset, or Sign out, should reset User.everything with no value, to empty strings ”, not null, not undefined.
  5. Does Translate API on cloud have any Throttling, or overuse protection? We need something, perhaps count uses per minute
  6. FOUND ERROR, NOT FIXED YET. Something Crashes, if I begin running Moose, then activate my VPN which blocks internet access, it shows green error about thread exception not handled, then quits Moose.
  7. Related to above, when VPN is running, blocking internet access, if I run Moose, the Home.html is not shown until VPN is cancelled. Not talking, not fully initialized.
    • It’s waiting for connection to something presumably. It needs to be able to run Moose with no internet.
  8. Azure functions that keep our API keys hidden, and check users permission to use them.
    • Weather, because it’s easy.
      • It’s using a free key now, I’ll need a paid key for Beta testing.
      • Edit Weather.js to get it working.
    • Then Dialogflow v2 SDK into Azure,
      • for authentication tokens for the Chat.js plugin.
      • https://dialogflow.com/docs/sdks
    • Then Google Oauth API for google sheets.
      • For the Research plugin, maybe other stats.
    • Then a GeoLocation API, needed before Beta Test. Perhaps Azure’s
    • Then Zazzle, (according to their API, even though I don’t have a key for it yet.
    • Then SendTxt plugin uses Nexmo API. (ApiKey and ApiSecret)
    • Leftovers: Webhooks, Cloud-save settings.
    • Store the API keys, Call the functions and get authentication if paid to use that feature, so the plugins can keep-on calling the rest of the API.
  9. Terms of Service / License agreement, issues.
    • Ivan suggested that paid features and internet content plugins, should only download into the product after License is agreed.
      • Maybe C# has a list of these plugins, and over-rides their settings, to force them <isEnabled>false</isEnabled>
    • Ivan suggested that C# shows the Licence agreement, before plugins and home start running.
      • Ivan, can you use a Green C# window dialog, and re-create the Terms.html approximately?
  10. Related to Terms of Service, I think we may need a C# function that detects when the Moose seems to be running on a new machine.
    • Could be same user just got a new PC, threw out the old one.
    • Could be a new user at a new location.
    • In both these cases, it’s safest for me, to have them re-agree to the Terms of Service.
    • Home.html will use this, in it’s startup <script>, to hide menus and show button for Terms of Service.
    • Maybe it’s same user, at same IP address, who have already agreed to Terms of Service, then they get a new PC.
      • Do we store a duplicate IP address in the list? Do we store a duplicate user name in the list? Do we store a MAC address too? Does our cloud function check for duplicates, or just store them anyway?
  11. Make Microsoft One_Core voices viewable in Voices plugin list, and make them work, somehow.
  12. Have Moose.exe send an event, to all .html plugin views, coded into the 12_Pastels.js , to disable background gradient changing, during speech, and resume when speech is done.
  13. A C# function for the Voices plugin to use, to tell us which language is the PC set to, and then I can check if a matching Voice is available.
  14. For Twitter plugin, for New User Detected, I think we need a C# function logout and forget the previous user.
  15. Ivans idea: Sign out of Login.html, would clear out the User.Name, User.everything.
    • We might need a setting in UserInfo.html for whether User.everything is linked to the Azure Login, or where it’s local storage only. (some people may never want the login for internet)
  16. If Moose3D.exe doesn’t receive any movement commands via MMF at all, for 10 seconds or more, it should make the Moose disappear from view.
    • We need a setting to Enable/Disable this, for testing purposes. It can be disabled now and during early beta testing, but really does need this coding to be done.
    • We need some code that tries once or twice, to wake up Moose.exe, perhaps with forcing the mouse to move, and if that fails, relaunch Moose.exe
    • On Steve’s PC, it seems that Moose.exe can freeze up, (application not responding), but Moose3D.exe stays running. If that happens to other users, we SHOULD be hiding Moose3D.
    • This still happens to me. I return to my PC from being somewhere else in the house for a while, and the motionless moose is visible. It goes away when I start moving the mouse. But some plugins are still running, eg, fetching from Reddit and sending to the Buffer is still working. Things were accumulating on the Say queue too, not being spoken until I moved the mouse.
  17. Related to the above problem, of a motionless 3D moose, please investigate what could be halting/suspending or tight-inner-loop’ing the thread that:
    • Generates behaviors
    • Takes things off the Say queue for speaking. (Things get onto the Say queue, and renmain there waiting, until 3D moose starts moving again.
    • Ivan found some delays of 3 seconds for me, but 100ms for his computer.
    • Maybe check the code that pulls things off the Say queue, and the sequence of events that does a ShowMoose3D(), that generates MMF movement for speech. Perhaps something related to testing if there has been recent mouse movement or keyboard clicks- maybe it needs a timeout escape… like suppose it’s asking for information requiring “Marshalling” and low-level win32, which gets hung up until a mouse movement occurs.
  18. Remove the C# green window for “Said What”, available from the right-click systray menu. It’s no longer needed. The Said plugin is better now.
    • A few things don’t get into the Said plugin. For example, internet error messages. Please add the event Trigger to send internet error messages to the Said plugin.
  19. Moose.ExitApplication is called from Home.html. Please have it Empty the Say queue. I’ve experienced problems have having 2 long sentences on the Say queue, cause quite a noticable delay before the Moose finally says goodbye.
  20. Ivan says a new WebView with .NET 3 core, is coming.
    • It might be possible to code WebView now.
    • The Webpages.js plugin, which renders offscreen, needs a browser supporting Javascript ES6, because most popular websites worthy of scraping, are probably using JS libraries that use ES6.
    • later, after gaining familiarity with WebView coding, convert all plugin Views to use WebView instead of older WebBrowser.
    • Or Maybe use Chromium Embedded Framework and forget about Microsoft for this one.
  21. A C# function that returns a list of all plugins found in the plugins folder
    • So that Home.html can show them in a menu
    • After removing the ones that are already in other pre-made menus.
  22. Improve RunNextAt
    • Plugin.StopRun(); for the Habits.js and Home.js, so the Startup function can disable Run() without messing with RunNextAt.
    • Plugin.ResumeRun(); for situation where it was stopped, but RunNextAt is set to the future again, and it is restored into use.
    • Plugin.IsRunStopped() might be useful to call from function OnChanged(), if a setting just changed that gave a new reason to Run again.
    • Discussion, Currently RunNextAt can never be allowed to become “in the past”, it must always be reset to a future time, like midnight, otherwise, it disables the calls to Run, forever. My plugins currently use midnight as a work-around, but fixing this odd behaviour is good for 3rd party plugin developers.
  23. mail.halls.md added to certificate.
    • Install to all places, halls.md breast-cancer.ca, Azure, etc
    • But look into why your visestech is rejecting my emails as spam. Maybe I shouldn’t get deeply serious about mail.halls.md if some people will be blocked from receiving my emails.
    • Defer this item, until I eventually learn which SpamHaus-like service is actually blocking me. Maybe outlook?
  24. Activity functions for Calendar plugin and On-the-Hour plugin:
    • Problem: I’m out of the room, the Moose speaks a Calendar event, and I don’t hear it.
    • Function 1 Create a C# function that returns the time of the last activity results with mouse move or keypress or microphone audio burst or scrollwheel move
      • So the plugin can save the sentences until it is sure the user is nearby to hear it.
      • Calendar plugin .js can call this function periodically via Timers.setTimer(), but Ivan suggests using an event. I’d prefer a function, at the moment.
    • Function 2 Create a C# function that notices “inactivity” defined as no movement for 5 minutes or longer, sets IsInactivity true.
    • Function 3. A C# function notices when “activity” resumes after “inactivity” and sends an event to plugins.
    • Useful for:
      • Problem: Suppose its after bedtime, Quiet Hours is ON, but the user is staying up late, working on their PC.
      • The Moose can tell the user to Go to bed, at 1am, 2am, etc, but should only do it, if user activity is detected, like mouse movement or keyboard activity.
      • High priority can be used in Moose.Say()
      • So the activity function created above for the Calendar plugin, will be handy in the On-the-Hour plugin too.
  25. I still get AWS warning of high database usage.
    • Please look again at what is causing it.
    • I can’t remember getting one in July.
    • Got one August 16th. Ivan said he’s kill the database.
  26. I think we don’t need User.FacebookId anymore.
  27. Ivan to create a AWS login for himself, with 2 factor verification,
    • and Steve needs to do the same and improve his password.
  28. I’m not sure, hopefully my login for Microsoft Azure also has a 2 factor verification.
  29. Microphone for Ambient.     Don’t interrupt human speech
    • An On/Off that a plugin can change ambient microphone on/off. (different from speech recognition on/off). This is detect audio spikes
    • Need code that recognizes background sound volume, and recognizes volume spikes compared to previous.
    • Presence of volume spikes, means go ahead with save:activenear, useful for Webhooks and Calendar
    • Presence of volume spikes, means don’t Speak from Say queue, allow 3 secs of silence first.
    • Presence of volume spikes, turns on local microsoft speech recognition.
    • 4 minutes without volume spikes, turns off local microsoft speech recognition.
    • I think audio-spike detection is as simple as summing the Absolute Values ABS() of each data point in the audio soundwave. and comparing to a threshold.
  30. Microphone for chat.
    • For Chatbot, will need audio sentences to send to a Speech-to-Text API.
    • Will need an On/Off, for ALL speech recognition. that the Chat plugin can change.
    • When ON, the local microsoft speech recognition is not yet actually running. Lets make it actually turn on when a burst of audio, of any kind, is detected on the microphone. And lets turn it off automatically after 4 minutes without audio bursts.
    • When local microsoft speech recognition is ON and running, we can have it listen for a specific phrase like “Hey Moose”. ( plus a few others like “Thank-you Moose”.)
    • When “Hey Moose” is recognized by local microsoft speech recognition, it automatically switches to using Azure speech recognition.
    • We can let a plugin configure whether to use Azure, or Google, or a few other providers, but coded in C#.
    • We’ll turn off Azure speech recognition, if there’s 3 minutes of lack-of-speech happening.
    • Text received from speech-recognition is sent to the Chat plugin.
  31. Microphone for arbitrary lip-sync.
    • need multiple arrays filled with data, raw and from FFT, lots of sums, 256,128,64,32,16,8,4. and at at least 8 different time windows, probably more. Combining enough to get average of 20ms, 40ms and 80ms worth of speech.
    • The FFT size, 512 size.
  32. Microphone notes.
    • Reasons
      1. User talks into microphone, Moose mimics the correct mouth shapes, a “fun mode”, lets people record the Moose singing, or speaking sounding sad or mad or excited.
    • Steve will need a way to visualize the spectrograms, at various summated amounts, at various time-averaged amounts, and compare 2 sounds.
      • We will need to build a visualization tool, in order to efficiently analyze a few thousand different sound samples, while coding the logic.
    • Steves examples of Formant code: aescripts.com auto-lip-sync or Talking Head by Ryan Cashman, both for Adobe AfterEffects, A Mathworks module: https://www.mathworks.com/matlabcentral/fileexchange/45315-formant-estimation, http://geoff-morrison.net/ has a matlab source code for formants, near bottom of page.
  33. A flag created in Settings.txt, that can turn off all calls to our Azure and AWS cloud. If we detect someone abusing our cloud, we send a message to their Moose, turning off it’s cloud usage.
    • Code the flag in Moose.exe Settings.txt
    • Add tests of the flag around all places in C# that use cloud.
      • And look at plugins: Translate, PrivateChat, Login, Chat, GeoLocation, Research results storage,
    • Code Moose.exe to receive a message from cloud to disable the flag.
      • A hard-to-hack message so hackers can’t be sending “disable” messages to my user base.
  34. Twitter API limits, the C# calls to twitter must count calls in 15-minute windows,
    • and block excess, so we don’t get banned by Twitter.
    • The plugin’s Shutdown function also tries to reset timing of 1 minute or less, to longer values.
  35. The start times for Streams: Morning, Afternoon, Evening. Most Moose users will never change these, so all users will be starting at exactly the same times, and that could cause Web fetching by thousands of Moose users at exactly the same moment.
    • If a hundred thousand or million Moose users were doing Weather once in the afternoon, it would be an instant DDoS attack.
    • I think we need to give some randomness to the start times of these 3 streams.
    • This is done once at Moose.exe startup, set a flag for that. Any other instances when the next stream time is calculated, should be exact, so users doing editing aren’t confused.
    • How about adding Random(0,300000) milliseconds to those stream starting times.
  36. Twitter real-time Streaming.
    • For a new tab in the Twitter.html options bar.
    • It would show scrolling text results of the incoming stream, (not using Buffer), used for reading it, not Moose speaking it.
    • https://developer.twitter.com/en/docs/tweets/filter-realtime/overview
    • https://developer.twitter.com/en/docs/tweets/filter-realtime/guides/connecting
  37. PrivateChat has 5 friends, it checks if they are online when Moose starts up.
    • Ivan thinks using WebSockets is better than a flurry of XMLHttpRequests to the WebHook.
    • PrivateChat needs more improvements, things also may be different after the switch to Azure. What the best way to detect if a friend is online?
  38. Streams with only 2 plugins set, should use my Alternate12(), and with 3 plugins set, should use Alternate123() instead of Random(1,2) or Random(1,3).
    • I found that I prefer the predictable evenness, over the sometimes occurrence of getting the same plugin 3 times in a row.
    • It will solve a problem, of wanting to hear 2 “evening” plugins, once each.
    • Alternate1234, maybe even Alternate12345
  39. @data and @files and Web.LoadImage() should be restricted to only fetching local files within the Moose folder and it’s subfolders.
    • This is particularly important now that plugins are auto-detected.
    • @file: is preprocessed and replaced with a filepath starting at C:, and I’m worried about people putting filepaths to anywhere, like grabbing your passwords files and sending them with javascript to a hacker.
    • If @data and @file and Web.LoadImage() is forced to be only on the C: drive, lets fix that. If there’s anything preventing the Moose from running from a D: drive or USB stick, lets fix that.
  40. AWS lambda/database coded to have Maximum limits of stored messages. There’s risk of a user setting up a high-volume IFTTT applet, that does save:activenear, and stores a massive amount into the AWS database. If that user stops using the Moose, it could grow and grow and become a costly problem.
    • Let me know when stored messages limit is coded.
  41. The Moose.ShowNotifyIcon() function is not needed anymore.
    • Delete it.
  42. Encrypt shader files, decrypt into Memory.
    • A step to lessen easy piracy
    • Ivan won’t approve Beta testing until some of the code is protected
  43. Remove access to Moose Studio, for the version to go out for beta testing.
    • But I and Beta users would lose access to making video captures.
    • Ivan, why is this necessary? Isn’t hiding almost as good?
  44. Ivan had added logging which noticed that my main event loop could sometimes have 3 second delays, while his is 100ms. This was trying to understand why Moose3D sometimes freezes until motion of mouse occurs. Perhaps it’s time to remove that logging.
  45. Moose.SetVideoRenderBackgroundImage( theURL );
    • I need the ability to change the background image for video captures, automated within Plugins.
      • To elminate the clumsy visit into Moose Studio to change the image, and normal users won’t get access to Moose Studio.
      • So a plugin can automatically use a random different image each time, or slide to choose a desired image.
    • Able to use background image from local, or from a URL. 2 functions?
    • (below, are not urgent priorities right now. they are future ideas.
    • This might be useful to the Meme Maker code, if it can set the background image to be fully transparent.
    • It would be great to have code that automatically responds to facebook mentions of the Moose, by creating Meme-like static pictures, OR, rendered videos, with automatically generated text,
      and posting them to facebook. Would be good for marketing. Could make Happy birthday videos for all my registered users.
    • In the further future, ability to render onto a background video
    • Moose.Record(‘these words’) will be needed too.
  46. Chat in my-custom-functions.php improvements.
    • GreenSock + Scrollmagic for sliding animations of chats
    • Hover popup over moose saying ‘click’ for joke
    • Circle pictures to add box-shadow 50% radius
    • Circle pictures bounce animation when clicked, ie,
      • improve pulseClick and hopefully not have it disturb the position of anything else.
      • Mimic the bounce of Say Joke style of buttons in Home.html
    • Circle pictures to show cursor:pointer
    • Ad footer code
      • update Facebook to 2.11 version
      • serve the .js from moosefile instead of halls.md
      • Add some animation to text in the ad
  47. Need a checkbox option for Moose startup, to not show Home.html in the taskbar at all.
    • Ie, have it only accessible through the right-click systray.
    • This would be an advanced-user option.
    • I guess it needs a Get and Set function available in javascript and html
  48. To Escape from Cloud=”True”, we need a signal to set when manually editing a Settings.xml file, so that the edits aren’t erased from the cloud, next time the Moose starts up.
    • Putting Cloud=”Stop” in the setting, or just deleting Cloud=”True”,
      should prevent the Cloud from overwriting that setting.
  49. Back button, for plugin windows.
    • If the plugin designer chooses to place a link to a webpage, and that webpage is displayed in our green window, we need BACK navigation, somehow.
    • We don’t have a visible button on the frame, Can we add one?
    • At least we should act upon the keyboard press for going back, which is? ESC, or ALT-Left-arrow?
  50. WebMoose, for BMI results, give thought for a way to speak different sentences for BMI of 29.1, 29.3 etc..
    • Perhaps a webhook to a plugin that creates mp4 recordings, and sends them back.
    • I should write down the sub-steps to make this happen. But not code it yet.
  51. for Meme Maker and for creating Products for sale
    • Hotkey for Moose3D.exe to capture a Moose image (in big size, high resolution) and save it into a PNG format with alpha transparency shadow. To be subsequently used for creating sellable Moose products on zazzle.
      • Probably need several sizes, big and small, because eyelashes look bad after downscaling.
      • I don’t know the sizes needed yet, so an editable setting for sizes, would be nice.
    • (I tried using WebMoose output in Photoshop, but couldn’t figure out how to use it to create the transparent background PNGs that I need.)
  52. Add Geolocation API call in UserInfo or Login plugin or C# startup, or Cloud function for new user,
    • to some cloud service, providing location better than Facebook. Store location.
    • A feature available to me, (not all users), using google maps to show locations of moose users.
      • https://www.pubnub.com/tutorials/javascript/mapping-javascript-tracking/?utm_source=EmailBlasts&utm_medium=Content-Roundup&utm_campaign=CR-CY17-Q4-Content-Roundup-December-23
      • https://www.pubnub.com/tutorials/javascript/mapping-javascript-tracking/?utm_source=EmailBlasts&utm_medium=Content-Roundup&utm_campaign=CR-CY18-Q1-Demo-Email
      • I can’t begin Beta testing until I can KNOW who is using the Beta Moose.
    • Perhaps https://geoipify.whoisxmlapi.com/
  53. It would be cool to have a live count of Moose users.
    • For myself to know,
    • Maybe Home.html shows the total too, it might encourage people to share the Moose more.
  54. code a “Check if there is no internet” before asking for facebook login.
    • If I startup the Moose while my VPN is running, there is no internet. The Moose shows the “Logon with Facebook” window. The picture shows what happens if you try to use it, while there is no internet. It shows a blank page. Better behavior.
  55. Moose.SendWebHook(theJSON) might be better than plain XmlHttpRequest
    • For improving PrivateChat.js function SendPrivateChat
  56. Allow a plugin to have no javascript, ie, an empty <source>
  57. Not working, need fix: this.getResponseHeader(“Last-Modified”); and this.getAllResponseHeaders();
    • But I’m unlikely to use it in my WebRequest plugin.
  58. Mysterious problems that affect steve:
    • LockJSONparse() instead of JSON.parse(), because JSON.parse is suspected by Steve, of being a source of multi-entrancy problems. I can’t use Exports.Call to lock it, because those can’t return true JSON.
    • This might not be an issue anymore, Ivan eventually found a problem with his threading, and changed plugins to single-threaded.
  59. Need a test of javascript graphics speed
    • So that background pastel color changing can be omitted if too slow.
    • So that Notifications.html script can omit the character spacing animation if too slow
    • A count of open plugin windows could also be helpful. If more than 1 or 2 open, then fancy animations are stopped.
  60. Forwarding to Email and IFTTT, if the Moose can’t speak a message.
    • Fix to automatically use the email address obtained from Facebook.
    • subject used if source also present, for email subject.
    • Lambda has been doing orEmail but also leaving those messages waiting for Moose.exe to get them, I suspect it happens when Moose.exe or Lambda lose connection to each other
  61. {“andIFTTT”:”eventname”}. ( {“orIFTTT”:”eventname”} ). (for WebHooks API)
    • Later add {“andZapier”:”triggerURL”} or {“orZapier”:”triggerURL”} because Zapier is very awesome.
  62. For Toast style notifications
    • Ability to toggle the windowframe from our standard, to slim ( Although, the frame with 3D text shadows is starting to look good, so this is lower priority.
    • Commands to position the window offscreen, to various corners. ( But bouncing to land above the taskbar is probably going to be good, so this is lower priority)
  63. Ivan’s mouse gestures apparently don’t work
    • They don’t match the example in “About the Moose”
  64. For Steve: Nagging myself to work on this:
    • When New User signal happens, settings get reset, but things like User.Gender are still from the previous old user, which can lead to SayName generating Mr. instead of Ms.
    • Grey-out languages in Translate plugin, which do not have installed voices in the same language.
    • Try the Google Oauth code from Freelancer, for Research plugin google sheets
    • An APIs plugin.
      • Toggle for PUT or POST
      • Each slot has an On/Off.
      • Each slot has toggles for TimingOnOff, EventsOnOff, both can be On.
        • Ie, can be triggered by the Timing, or by an Event. Usually not both On.
      • Choices for setRequestHeader Content-Type, Accept.
      • A textedit input containing JSON body to send with the PUT/POST
      • Two types of eval() code depending on how triggered.
        1. Triggered by Timing
        2. Triggered by Event
      • When triggered by Timing, a textedit input containing Javascript that’s eval() to modify the JSON before sending.
        • It could put default values into the JSON using replace()
      • When triggered by Event, a textedit input containing Javascript that’s eval() to modify the JSON before sending.
        • It could put function parameters into the JSON using replace()
      • 3 or 9 slots, each has a predefined event name like: Events.OnEvent(‘APIs Slot 1’), 2, 3, etc
      • Each Events.OnEvent function can accept 3 parameters.
      • Each slot has a textEdit input for javascript code, called by eval() in onreadystatechange.
      • the onreadystatechange code can trigger an events to fire another API in slot 1-9.
        • This lets the results of one API get sent to the next API.
        • Or, it could call Moose.Say() (or TranslateAndSay() ).
        • It can use IF..ELSE.. logic to decide which slot to call next.
      • When a onreadystatechenge does eval() that has Events.TriggerEvent(‘APIs Slot 2’,result.apiKey,result.apiSecret,result.text
        • See 3 parameters. If they need more, they have to .join before sending, and .split when receiving the parameter. Luckily, each slot has 2 eval() places, at triggered step, and at result step.
      • I think this enables multi-step usage, and IF..ELSE logic, using IFTTT, but not paying for multi-step.
      • I need to think of one useful example, otherwise coding this plugin isn’t worth the effort.
      • Must have examples, otherwise nobody will use it. Examples could be:
        • A section for Oauth as first step toward using other APIs from Microsoft, Google, etc.
        • A section for Google APIs as a second step, passing an access_token obtained in the first step.
      • Maybe examples fill in 2 slots at a time: 1 for Oauth to get a token, 2 to send the token to the actual API
      • The plugin.js would have a OnWebHook = function(data) {} to receive things coming back from IFTTT via webhooks, which had specified {“target”:”APIs”}
    • Create a way, for one user to “gift” the Moose to another user, and have the new user be able to download the Moose with the new users name already set.
    • Say plugin to replace the green one.
    • Medical terminology plugin
      • https://www.health.harvard.edu/a-through-c
    • Use View.LoadImage(local file); or View.LoadImage(URL) to put dynamic images into the Meme plugin. and beautiful pictures on Home.html background.
    • Use Web.GetHTMLImageHash() in the Webpages.js plugin, for image area comparisons.
    • Delete the plugin WebPageRenderer, which is only for example code.
    • Create a PressKit plugin
      • https://www.bizmavens.com/media-kit-examples/
      • https://www.pinterest.com/twelveskip/media-kit-design-examples/
    • A Paid API Sales Plugin.
      • Continue to improve it
    • Research plugin.
      • Tell Before and After score to user.
      • Finish learning Google Sheets API.
    • More scraping examples and explanation in the internet plugins.
    • Check EVERY plugin and eliminate passing string dates into new Date(), because its unreliable.
    • Force the Spread plugin to remain on, (turn on at Shutdown) for at least a few days.
    • Space Station plugin,
      • using https://spotthestation.nasa.gov/sightings/view.cfm?country=Canada&region=Alberta&city=Edmonton#.Wr_muojwYcE
      • maybe fetching daily summary reports.https://blogs.nasa.gov/stationreport/2018/03/28/iss-daily-summary-report-3282018/ ( but they are too verbose )
    • Chat.js to use Dialogflow v2 api, needs SDK authentication figured out.
    • Window frame materials are at:
      • Dropbox\UI\Frame\Frame.ai and we have “skinner” app here: \Dropbox\Moose 115.0\DLLs\External\Skinner\Moosey.Controls.Media.Test.exe
      • skinner can only edit colors.
      • To edit objects, the Adobe Illustrator objects have to be exported to XAML, requring every AI path to be aligned to a frame coordinate system, then Ivan has to do further edits to put them into his COMPILED XAML and C# code, which uses ‘custom WPF controls’ code to provide the drag and click responsiveness. ie, I can’t do it alone.
      • Dropbox\UI\Frame\Generic.xaml is the file holding the XAML. see line 231:
      • Ivan wants a solid frame with no transparent spots. Learn about what can be done.
    • Dropbox\UI\Frame\Frame.ai is the Adobe Illustrator file.
    • In new user Home.html sequence, “The Moose is for every day use.” I should give them an auto-startup checkbox right there.
    • Twitter.html columns copied to Feeds,News,Webpages,Reddit
    • NewUserDetected reset better in Habits plugin.
    • When Timing switches back to Random, from Shared or Precise, if it’s not Recurring, have an animation to point at it, to help users notice.
    • When I chose New User login with Twitter, then looked at UserInfo plugin, it was showing a lot of my details from being a pre-existing user. Figure out correct order of things.
    • WHen I chose New User login with Twitter, then looked at Buffer, there was old stuff on the buffer, and in Said plugin, so I better also check all the logs and clear them in Logs plugin too.
    • When I used Login with Twitter, I chose I’m a new User,
      • then looked at Twitter plugin, the Home timeline was turned Off. It can be turned ON by default, because the whole plugin is Off.
      • The Weather plugin was Off (good), but it had my Edmonton location already there.
    • Home.html could have a method to display a menu of plugins that are not
      already in the major menus.

      • Ie, when 3rd party users add plugins to the folder, it would be nice to somehow display them from Home.html.
    • Read what Naudio provides.
    • Add minutes testing in on-the-hour
    • PrivateChat improvements.
      • remove data-setting for pass-phrase, manually do .change handlers.
      • PrivateChat OnOff setting to allow your friend to poll if you are online or not
        • Manual polling
        • Automatic polling at intervals, for 5 friends.
        • Expand from 5 to 9 friends, similar to web plugins.
        • Option to auto-generate a randomized substitution table, specific to each friend.
        • Option for peer-to-peer, option to use specific port #,
    • Add <translatedname> into all plugins Settings.xml,
      • for future use by theStream.ListAllPluginsOnThisStream()
    • I need to test what happens if someone else has used their Facebook login on my PC.
    • Learn to create SVG line-drawing of Moose, learn to GreenSock animate them.
    • Learn how to edit and alter the League of Le gends window frame.
    • Calendar plugin to use Timers.setTimer() and periodically, like very 5 seconds, calls a C# function, which returns the time of the last mouse-move or keypress. This has advantage of being able to be turned off, or easily adjusted, by the user. Give Calendar reminders an optional checkbox for whether to speak it immediately on time, or save it until there is recent user activity.
    • Plugin for listing names of applications and games and video players, that will be looked-for, and if they are foreground, then the Moose won’t speak.
    • Mug it, added to Said What
      • Waiting for me to incorporate a new business for this.
      • Waiting for my trademarks to get thru waiting period.
    • These plugins don’t yet have “User Identity Changed”: Chat, IFTTT, SendTxt, Tweet, Twitter, Weather, WebHooks.
    • Calendar plugin option to output dates into Google Calendar.
    • Overwolf plugin
      • Need to read more about it, but a barrier was a need for their approval.
    • A plugin Google Jobs API’s for new job openings.
    • A plugin for gmail push notifications, to say “you have mail”.
    • Steve must buy a stronger API key for OpenWeatherMap.org, so all the beta testers can use Weather.
    • Steve must get a microsoft Translate key suitable for large volumes, and hide it with security
    • Steve must get a GeoIP location paid plan.
    • Remote Kill 2nd copy of same user_id Moose on a different PC. Cloud.SendKillCommand()
    • Lateness (Habits) plugin future ideas
      • Do I need 2 shutdown times? one for leaving the office, another for bedtime?
      • A timing option available to all plugins, middle of the day, and before shutdown.
    • Add User.GetSecure for cloud APIs. Translate, Weather, Chat.
      • Needs Ivan’s attention to show me again how to do it correctly.
      • The major default API usage should actually be better done completely via cloud, so no secrets ever come to the local client.
    • Streams like evening.
      • If just 1 plugin on the stream, it fires once.
      • If 2 plugins on the stream, it fires one, then later the other.
      • Will be able to handle this when Ivan codes Alternate12(), Alternate123().
    • A plugin of Bloomberg financial information. https://intrinio.com/
      • Do my customers actually want this?
    • Use <include> instead of automatic loading of /scripts/
      • This is a big, scary job. To be done gradually.
      • Maybe I should just leave it all alone. The includes js are local, there are getting to be too many plugins to edit them individually anyway.
  65. Chat.js Azure refresh token, should keep track of last time something was chatted, and stop refreshing the token if > 20 minutes has passed. Clear instead.
    • Waiting for help with chatbot coding. It should be a dedicated max effort, not dabbling.
  66. Microsoft Azure, I can find the Verbs using https://westus.dev.cognitive.microsoft.com/docs/services/56ea598f778daf01942505ff/operations/56ea5a1cca73071fd4b102bb
  67. Periodic task run on Azure to find users who stopped using Moose for a while, and send them an email to remind or get feedback.
  68. At Shutdown, Moose says goodbye, the green points window gets frozen.
    • So, disable the green points display for the final goodbye speaking.
  69. For Toast style notifications
    • Ivan suggested using Moose3D to do the sliding motions of the window.
    • Hiding choppy animation, perhaps add slight delay from signal to motion.
    • A command to interrupt a Notification.Hide(), so it reverses back to fully shown. ( Notification.Hide(‘reverse’); ???
    • The Notification.Show() to add parameters for height and width, in pixels,
      that fit whatever the HTML believes are pixels.
    • For Notification.Show(), can the $(window).load function determine the actual height of internal content, and then adjust the window height to fit, and adjust the bounce onto top of taskbar accordingly. Is C# able to handle that, or must the <script> call a C# function to adjust the window height and bounce?
    • At the office PC, mysteriously, font sizes seem Zoomed, and manual un-zooming doesn’t persist across sessions. Causes problem, fonts are too big and they don’t fit the available window space.
  70. I need: User.CountryCode (for Holidays plugin)
    • I’d rather get this from Facebook, if available, than have Moose keep lists of country codes to look-up
  71. User.SaveChanges(); Ivan thinks it’s now redundant, but Ivan wants one plugin to still call it at Shutdown as a precaution.
    • Still needed? I think not needed, and confusing to exist.
    • Steve commented this out of UserInfo.js on July 9, 2018.
    • And not needed in August. OK, Delete this from the C# code, it’s no longer used.
  72. When an HTML view is window Minimized, Restored, adjust the JS code in abc/Scripts/12_Pastels.js to halt gradient changing.
    • A minimize from a taskbar click doesn’t succeed, so the Deactivate event is untrue and needs to be double-checked before telling plugins incorrect info.
  73. Need Voice.languagecode in javascript,
    • so the Voices and Translate plugins can check for incompatibility when translate language is changed.
  74. Limit active connections from plugin webrequests using XmlHttpRequest, likely similar logic that allows only 2 connections to AWS. Not done yet. Do we need to do this?
  75. Store points on the cloud
    • And needs arithmetic logic to detect if a hacked absurd value is being stored.
  76. Need a way to refresh a HTML view, in response to an Event, when resetting values for User Identity Changed. Ivan want automated, but I’d like to get a simpler refresh working first.
    • Perhaps using the new entry point in .html
      for OnOpen with a special parameter, and perhaps Save, Remove all the innerHTML from “body”, then add it back. Perhaps when last element is re-loaded into the DOM, use theElement.loaded()
  77. Periodic checking if monitors are added or unplugged.
  78. Allow moose recordings with Moose Location X and Moose Location Y to have negative number offsets.
  79. When opening “Open View” windows for plugins, add code that forces them to be smaller than the monitor they are on. I get problems, because my monitor #1 at home is landscape, my monitor #1 at the office is portrait mode. Sometimes, I Open View at home, and I can’t see the top or bottom window frame bars, which makes it very tricky to re-size them to be usable. I also discovered, that if I resize an “Open View” window for a plugin, then Close it, it will only save it’s new dimensions, if it was resized on monitor #1. It ignores my re-sizing on monitors #2 and #3.<- that seems weird behavior that will confuse users. We might have Beta testers who can't close html views, because I saved them too large on my PC.
  80. ScrollWheel UpDownUp gesture. Scrollwheel coding
  81. Need to somehow hide the Moose3D studio, so that Beta testers don’t enter it. Perhaps a password-protected splash screen when it opens?
  82. When Plugin.SetStream(null) is used, and it falls-back to using Scheduler Intervals, make sure it restarts a waiting timer and doesn’t generate a Run after 0 milliseconds. It needs to be a proper wait Interval before Run.
  83. For the Home window to function properly, when game points are earned, it will need change what is shown in the Home window.
    • Perhaps Events send the points and levels earned.
    • Either download or build-on-the-fly a HTML version that has another level added. Maybe the Event brings the new HTML code to add.
  84. Logs cleanup.
    • For example, this error is just logging something.
    • Ivan also added logs for diagnosing why Feeds using XmlHttpRequest were not receiving a callback to the timeout function. Remove these debugging logging code if no longer needed.
  85. When Voice is male, switch texture map of face and eyelashes to be the male version.
  86. If I’m working on Moose, testing phrases in plugins, and if it’s after midnight, then Quiet Hours happens, and makes it seem like the plugin isn’t working.
    • We should give some visual feedback, flashing the plugin taskbar icon, perhaps with something like a symbol of audio being off. I can supply an audio-if-off symbol to flash, when you are ready.
  87. Twitter and Paypal SDKs at this article, could give the starting point for accepting payments to add features.
  88. For all Streams (Minutes Channel, Hours, etc)
    • (I’m having second thoughts about this one.. maybe not needed right now). to have a setting to allow 1 or 2 things spoken each time. Therefore, I need a setting to specify “intervals/once(1)/once(2)/twice(1)/twice(2). “Once(1) would mean afternoon would only speak once, just one plugin. Once(2) would mean afternoon would speak once, but sentences from 2 plugins one-after-another. Twice(1) would mean speak once then wait for the interval to pass then speak one more time, a sentence from one plugin. Twice(2) would be speak two sentences from two plugins each time, for a total of 4 in the afternoon.
    • (I’m having second thoughts about this one.. maybe not needed right now)the Duration, if null, currently means it’s a 24-hour-a-day channel. I need a separate setting meaning Duration24hourAdayOnOff, to put into a toggle button. This will allow a numeric Duration value (non-null) to not get lost if the user toggles 24-hour-a-day on and off.
  89. Identify all the cloud functions that cause billable activity, and write up a plan for throttling, fast-loop and slower Run repeatedly loops. Include automatic temporary blocking of the user, automatic notification of an admin (my cellphone/email stored in a setting that can’t be easily changed)
    • Then, a separate to-do item to actually Code the cloud throttling protection. List & plan first, code later.
    • Even if these are internal C# functions, because they cost money, I want the assurance of having throttling on their usage.
    • Create a AWSbillingsOnOff settings, Whereby Moose users download an update with a setting that disables all things that cost me money on AWS.
  90. (Ivan wanted to wait on security bulletproofing. I hope my good ideas about setting limits and length-checking parameters isn’t forgotten.)
    • Idea to add deliberate slowdown to cloud functions involving user_ids or secret tokens, to thwart brute forcing.
    • Idea to check IP address stored with user_ID, and email or alert if new IP addresses suddenly appear.
  91. Need a way to store pronounciation errors. Perhaps in a filter plugin? I’ve remembered that /abc/VoiceRules.js gets called before the Moose generates animation. Maybe something similar can be implemented for pronouncication.. Ie, some Voice companies might allow embedded pronounciation, others might need different methods.
  92. Rename “Moose3D Studio v1.0.0.0” window to “Moose Internal Controls”, and can it have an alternate shorter Taskbar name like “Internal”.
  93. Fix “quite a few items to fix with recording on Moose.exe”.
    • Shh’ing and Cancelling recording, would cause errors. Need to fix this.
    • Moose can send Visiemes while recording, which would put Show/Hide Moose commands out of order.
    • Stop recording button ignores part of the recording process and sends MMF messages directly to Moose3D without calling Speech or Animation services.
    • A brief flash of the Moose, after recording ends.
  94. If a plugin has an error, you currently disable it, until the next restart of the Moose. That’s OK for active developers, but for normal users, I think we should show a one-time message on the next restart, saying it was disabled and would you like to re-enable it?
  95. If a plugin causes Moose.exe to CRASH or EXIT silently, we should show a one-time message on the next restart, saying the plugin was disabled, and would you like to re-enable it.
  96. The javascript error dialogs, I can’t change the size of the window frame. I’d like to be able to play with that.
  97. Need new webmoose code, so it works also on mobile browsers. For my websites
  98. In a plugins .html file, if I use <form>…</form> it causes an error after clicking a button. Maybe it’s trying to do an ‘action’ like ‘get’ or ‘put’.
    • I think there are forms in the Streams.html. I should check if they error.
  99. Perhaps GitHub “EasyHook” for dll injection to hook the Notifications of win 10, so moose can speak them. However, this investigation thinks that the API isn’t exposed.
  100. Sign up or 30 day trial of IBM watson, and test it out. Need networking working first
  101. The Green windows, for the X, -, and wrench buttons, they need to have hover and click effects.
  102. <RunNextAt> is being saved in Settings.xml Question: Is it also being restored on the next startup? If so, how does that logic work, if it’s past due date at the next startup?
  103. When Moose.exe crashed ( and was terminated in Task Manager), Moose3D.exe was showing a green error message saying “Invalid Protocol”, which is referring to an MMF problem. Lets change that message to something more helpful like “Moose3D.exe is still running, and found corrupt data on the MMF, suggesting that Moose.exe quit unexpectedly. Try closing Moose3D.exe in the Task Manager”.
  104. Shh’ing twice. The VB6 moose had a feature, if you SHH’ed 2 things in a row, then it would keep the Moose silent for 30 minutes. If the user SHH’es the first thing spoken after 30 minutes, then it won’t speak again for 2 hours.
  105. Watching a Movie, Playing a game, YES, I’ve always intended to have a feature, a list of processes, such that if that process is running, the Moose will keep silent. We’d supply a decent list, and be able to update it remotely, and learn what other users are adding to their custom lists.
  106. The weather plugin, my worldweatheronline API expired. Now it’s using OpenWeatherMap.org API, which is fine for small volumes. We just need to bundle these APIs into some kind of “user paid for cloud services package”.
  107. Also in Weather, I put jsonpath into it’s folder, but haven’t used it yet. It’s a jason parser. Check if it’s useful.
  108. Stimulus sound, Probably later, a feedback method: a Right-Left gesture after hearing the stimulus sound, could be a way of teaching the Moose, that the stimulus interval was annoying and needs to be lengthened longer than 10 minutes, and maybe we automatically increase it to 15 minutes.
  109. Earning badges. Float up a little symbol of a badge earned, and store it someplace where people can look at them later. ( this is an idea for later. Don’t code badges now. I just don’t want to forget it.)
  110. Quiet Hours improvement. Ideas.
    • Quiet doesn’t start until there is about 5 minutes of inactivity of keyboard and mouse movement.
    • It can wake-up during the Quiet hours, if keyboard happens, or if mouse moves more than 20 pixels in 1 sec (ie, not slow gradual drift).
  111. Moose.Quiet.temporarilyTalkingBecauseOfActivity.
    • Quiet Hours is supposed to be suspended, when there is computer activity, typing or mouse movement. it should audibly talk. But I think it rarely works, maybe never.
    • When it does get working again, I’d like to show some feedback about this status, in the Quiet Hours plugin.
    • This will be important feedback so users will understand WHY the moose is still talking after they just turned Quiet mode ON.
  112. Detect if MSAA is supported on the graphics card, disable anti-aliasing if missing. I don’t want our first beta testers to have GPU errors/exceptions. I think this might be coded now, but Ivan asked to improve it by running some text graphics, and comparing the pixels that result, to a saved standard.
  113. Moose’s eye sometimes jitter at the start of Moose saying the first Hello after startup.
    • I think a backlog of eye micromotions is being played super-fast to get caught up.
  114. I’d like to reward Button clicks inside plugins, with random bonus game points. Like, clicking “Say anti-anxiety”, or “Say weight-loss” buttons. But how?, I don’t want a public function visible inside Javascript that could be run in a loop. Maybe we can automate it. If an HTML plugin page has a button that calls Moose.Run, then the Run() gets Plugin.RunType == “Action”. Perhaps we can do a Bonus points if Run() calls Moose.Say(), maybe show those points even before the speech queue starts talking. It will probably need some time limits, or maybe it won’t become active again until after a moose Say is completed.
  115. I’m wondering if the Green window for game points, if it should be javascript on HTML. Then I could use GreenSock for moving things, animating SVGs, clipping it so the sys tray shows.. But what would happen to the beautiful fonts?
  116. Try seeing +48 Bonus Points float up as soon as the gesture succeeds, instead of waiting till the end of speaking.
    • It would probably be more encouraging that way.
  117. When making a recording, sometimes the Moose tries to speak something that just happens through normal timing, and it messes up the end of the recording, so a huge recording of idle motions happens, which then chokes the file system.
    • We need a flag to disable regular talking until recording is fully over.
    • We need a flag to disable recording until regular talking is over.
    • (This is similar to disabling talking until auto-saving is over.
  118. Files named like Settings_2f2fe1ba-9965-80e5-3dcf-89f996cb5594.txt contain saved window locations. These unusual filenames are hard to read. They *were* necessary because of sharing files on dropbox. They don’t need to be saved to the cloud. They also contain a list of voices on the PC. Lets separate those functions.
    • WindowLocations-Hallshome-2f2fe1ba-9965-80e5-3dcf-89f996cb5594.txt
    • Voices-Hallshome-2f2fe1ba-9965-80e5-3dcf-89f996cb5594.txt
  119. Plugin HTML view windows are supposed to toggle between minimize and show, when you click on their taskbar name. It opens correctly, but doesn’t minimize correctly when the taskbar is clicked again.
    • Ivan says it’s because our View .html windows are actually 2 windows superimposed, one for the frame, the other for the web browser content. To fix this, would require some low level OS hooks and messing with OS messages.
  120. The Say window, should I re-create it with an HTML plugin? It would need a C# function to make recordings. On the topic of recordings, It would be handy to have more quick direct access for changing the background image, like a drag-and drop area.
  121. A plugin UI to create templates for subject and body, that can be stored on the cloud and used, similar to how IFTTT lets templates be edited.
  122. Other notes about websockets / Webhooks.
    • L) MQTT needs some limits-checking.
      • Limit of queued messages. 5 or 10 at most. (personally I can only tolerate 3 spoken tweets in a row.)(Do we discard the first to arrive and keep the most recent, or visa versa?)(Do we look at &priority to decide what to keep or discard?)
      • Limit of time duration saved. (discard messages that are more than 2 weeks old?)
      • Limit of userid time abandonment. (if userid doesn’t login for 2 months, assume they deleted the Moose, so delete the userid)
      • Limit of 2048 bytes for messages sent. ( I’d get billed 4 times 512)
    • H) If &target=NotValid is not recognized, we need a way to display that problem to the user in the WebHooks html view.
      • Perhaps the OnWebHook handler in WebHooks.js receives all the NotValid targets too, and that .js code will always check few status things like: if ( Moose.webhooks.connected == true ), if ( Moose.webhooks.lasttarget != Plugin.name )
    • Future ideas
      • ‘Render’ could make my Moose.exe to record a video and send it back to a webpage or cellphone app
      • ‘(some 2048 byte encrypted code)’ for various internal uses. (needs rate limiting and only from whitelist IP addresses, other security ideas, etc)

Things hopefully fixed, that I haven’t re-tested yet.

  • Scene.xml sometimes gets written badly, basically wiped out, like after a crash, and then the Moose is un-usable. We need to prevent this disaster.
    • Please look at the code that saves Scene.xml, and create a success flag, and don’t let it write-to-file unless it succeeded getting everything ready to write.
    • You told me this was fixed, but it wasn’t. PLEASE code protection, so that when a crash happens somewhere else, and Moose.exe closes suddenly, it won’t cause an empty Scene.xml file.
    • Re-iterating: This item isn’t about finding and fixing a crash. It’s about making sure that ANY crash can never corrupt Scene.xml (or any Settings.xml files)
  • Don’t begin speaking (taking a phrase from Say queue) while an HTML plugin view is opening.
    • Should solve the problem of “Hello” having bad lip sync, while Home.html is opening.
    • Ivan changed Moose.OpenPluginView() to not do threading context switching, ( plugin to UI for Open View, then back to plugin ). Instead, now the UI deals with Open .html view requests from a queue when other main-event-loop things are settled down. Saved 400ms.
  • Hello out-of-sync lips and sound.
    • This magically got fixed in build 101.
    • New Idea: It’s Home.html view opening, that causes Hello lip sync problem.
    • Old idea: Code Moose.Say to not remove the very first item from the Say queue, until all startup has settled down.
    • Ivan previously suggested it was due to auto-saving, but now denies it. (Steve thought garbage collection, because why would disk activity halt C# sound, but allow C++ animations to continue.)
    • Code these AutoSaving improvements:
      • No Auto-saving while speaking is happening.
      • No Speaking allowed to begin until Auto-Saving is inactive.
      • Time-of-previous-auto-save set to current time, before Hello plugin runs, so it won’t trigger an auto-save right away.
    • (Build, try the above for a while, maybe out-of-sync lips will be solved, which means the items below about garbage collection are not needed.)
      • Force .NET GC.Collect once, at the end of initialization and before Hello plugin Run()s
      • Apparently, you can RegisterForFullGCNotification and check if it’s soon pending, maybe we can force collection before speaking anything, if it’s pending.
  • Captions text gets cutoff. Reproduce problem: Set Moose size Small, quit. restart. Set Moose size Normal, quit restart. Hello will have caption text partly cut-off, because it created invisible window size of Small, even though the rest of the Moose is going to be Normal size thereafter.
  • The Size plugin uses Moose.SetWidth(400,true); might be responsible for this problem of captions cut-off. I also tried reproducing this problem using Moose Studio -> Moose Size, and it does not happen. So probably Moose.SetWidth() needs to reproduce the steps used by Moose Studio -> Moose Size.
  • User.Birthday = theDate; causes an error in <script> .html, but it works in theplugin.js file.
    • Facebook’s format of MM/DD/YYYY needs to work, but if we receive only YYYY or MM/DD but no year, then these variations must clear User.Birthday
  • This crash occasionally happens, and is often followed by discovering that Scene.xml got corrupted too.
    • Can you find this section of code, and add some alerts that provide additional debugging information.
    • Add range checking of visemes, like, they are numbered 1 to 21 for speech. (maybe 0 too) Test that range, alert with plenty of info if it’s out of range. Same idea for smile and blinking. Test and alert if out of range, before trying to use a morph.
    • My theory, Moose exiting can interrupt the work of behavior generator threads, which sends bad data on MMF to Moose3D.exe. Ivan says not a problem.
  • Threads creating behaviors to send to the MMF, might have been sending incomplete messages and getting killed when the Moose.exe quits, resulting in Moose3D.exe having errors. Please code this:
    • Set a flag when beginning write of behaviors to MMF, Clear flag when complete, don’t let Moose.exe quit if the flag is set.
    • Set a flag when Moose.exe wants to quit, don’t let behavior generators create new behaviors if the flag is set.
  • Had this error, after creating a new plugin, on new Island PC with only default voices, (defaults to David voice), but Settings probably still say Julie voice.
  • DONE. This error occurred when receiving a big batch of Webhooks.
    • Done. Ivan thinks it’s solved by escaping everything automatically that goes into settings. We shall see.
    • Causes corruption of /Error/Settings.xml, which was saving raw JSON data. (I’ve stopped saving raw JSON into the error log)
    • Perhaps bad unicode, or perhaps when truncating the logs to be under 31000 length, it might cause truncated unicode with unpredictable results.
    • Ivan suggests a fix, to write logic to handle invalid XML when saving settings.
  • DONE. Make a button to test it out. Kill Moose remote command. Cloud.SendKillCommand()
    • If I accidentally leave the Moose running at work, and then run it at home, 2 copies cause conflicting copies of Settings.xml files.
    • Ivan suggests using WebSockets, automatically kill the 2nd copy of the Moose with the same user_id and/or using the same dropbox files. An On/Off setting for the killing.
    • Cloud.SendKillCommand() is available now in .js, but Ivan says further work needed.
  • DONE. Hopefully fixed with cloud-saving. Another cause of Conflicting copy of Settings.xml files is when Moose autostarts before dropbox is sync’ed. The damages can be reduced by cloud-save and restore of settings.
    • Automatic, Cloud=True saving and restoring of settings. Code that aggregates all the things being saved/restored, and sends it to cloud using the least HTTPS requests.
  • Got an error, when a plugin accidentally created some random unicode characters that looked Chinese, but probably had illegal characters. When the Moose was quitting, and saving it’s settings, it apparently choked when trying to add those characters to a <TextLog>. The problem: it halted the subsequent saving of everything below it.
    • Fix needed: If something chokes, it’s better to NOT SAVE, than to save a partial file.
    • This fix could as easy as writing it all into 1 string, and if that succeeds, then writing the 1 string into the Settings.xml file. Could test by testing if </Settings> is at the bottom of the string.

Notes about Notifications

Because notifications on the Windows 10 desktop are not very useful, and could be enhanced by having the Moose speak them sometimes.

Regarding hooking into Notifications in win10, according to a freelancer yassineAzxmani, using ApiMonitor, this graphic shows that Notifications are located in ntdll.dll, and use a thread with CSRSS. And that suggests it may not be possible to inject into that.

Here’s an alternate hook library. It’s very unlikely the Moose will ever hook things directly, because I want a perfect reputation. But add-on products with their own DLLs could still be possible.PolyHook Hook library

Previous Builds

Previous Build August 26, 2018. Translate plugin completed to use cloud-hidden API secret. Got a more generally-extendable framework for cloud API secrets and calling APIs, so future work on other plugins should go faster. The Keep Settings button no longer clears the User.everything, but Sign-Out sadly, does.

Previous Build August 22, 2018. Renamed functions to License.Accept() and License.IsAccepted(). Fixed New User Reset with UserInfo. Translate and Weather plugins now have secrets on cloud, but those plugins are not fully javascript fixed yet.

Previous Build August 16, 2018 Got Events.OnEvent(“Authorized”,OnAuthorized). Most libraries were changed. Got License.AcceptedLicense(); and License.IsLicenseAccepted() which are available in .js but not .html.

Previous Build August 2, 2018 <Authorizer>s accumulating fixed.

Previous Build July 31, 2018: Cloud.GetSocialProvider() and User.CheckLogin(). Cloud.EnableCloudSettings() and Cloud.DisableCloudSettings(). Re-signed all DLLs. Saves Azure tokens for re-login, for multiple PCs (home/office/etc) of same user, and automatically re-login unless 30 days of inactivity. (This is a great feature.)

Previous Build July 22, 2018: cleaned-up error reporting, add centralized threading for all Azure API requests and Plugins’ XmlHttpRequests. Using new .NET 4.7.1. Redid dynamic loading of DLLs. Azure SDK caused a linking mess, cleaned up. Webhooks user_id will be more secure only in JSON (no longer visible in URL). Automatic re-login next session.

Previous Build July 9, 2018 Fixed a few bugs in build from 2 days ago. Got Facebook, Twitter and Microsoft,Amazon, Google logins. Azure messages using IoT/WebSockets will automatically be discarded after 48 hours.

Previous Build July 7, 2018 Almost completed switch to using Azure. But Moose is not back to AWS capabilities yet. Compiled in new Visual Studio with all new libraries. Fixed sometimes too-loud initial audio. Cloud API functions now have must-be-logged-in security.

Previous Build June 17, 2018. Partly switched from AWS to Azure, implemented Azure social media login.

Previous Build May 24, 2018: Got

  • document.getElementById(‘TestingBackground’).src = View.LoadImage(localFilename or URL)
  • document.getElementById(“testBack”).style.backgroundImage = ‘url(‘ + View.LoadImage(“bluepic.jpg”) + ‘)’;

( This automatically adds in mime type stuff like “data:image;base64″+theBase64). Got better plugin window size saving.

Previous Build May 22, 2018. Added a ‘script’ parameter for these 3 functions: theHTML = Web.GetHTML(), theHash = WebGetHTMLImageHash(), and new theBase64 = Web.GetHTMLImage(). This base64 is VERY USEFUL for doing this: document.getElementById(“image”).src = “data:image/bmp;base64,” + theBase64; Also added logging to look for main loop behavior-generator thread delay, to investigate times when 3D moose seems to freeze until the mouse moves. Removed an alert/error if a file-busy happens when auto-saving or shutdown.

New Build May 20, 2018 Discovered limits of # of open WebBrowsers, prevented a certain error message. Got Web.GetHTML and Web.GetHTMLImageHash with added parameters for delay and image sizes.

Previous Build May 16, 2018. Fixed problem of windowframe buttons sometimes needing 2 clicks. Got offscreen rendering of URLs for scraping in Webpages plugin, but not working as needed yet.

Previous Build May 9, 2018. Writing-to-file of Settings.xml of plugins given protection against becoming corrupted by a bad setting. Pushover plugin removed. Wording of New User reset dialog improved. Home menu option added to systray menu.

Previous Build May 2, 2018. Installed security certificates on halls.md and breast-cancer.ca. AWS released new SDK “.Net Core 2.0 for lambda”, had 2 memory leaks to fix. Many compile errors to fix. Gives oauth_request_token and oauth_access_token. Avoids using database, so much cheaper. AWS changed WebSockets timeout to 20min instead of 30min, so we were having high database usage for re-logins. Fixed. AWS began charging for Websockets connection time, and we’ve realized a need to switch from AWS to Azure. There was also a callback URL bug that was fixed, related to AWS use. Facebook changed recentCalenly, our login was being treated as “mobile” and forced us to re-login at every restart, now fixed. Got error reporting in JSON when using Twitter.Search, Twitter.GetTweets, etc. Got Twitter login for user authentication (haven’t tested it yet). Twitter API used by Twitter plugin is now sending requests to AWS first, where the application secret is appended. Changed to use Facebook graph API of v2.12. Generic login so Moose can accept all Oauth providers.

New Build May 3,2018. Fixed timeout callback of XmlHttpRequest for Feeds plugin. Got Moose.ClosePluginView(‘Login’) and Moose.IsViewOpened(‘Research’). Fixed bug of Refreshing a View would cause OnOpen function to fire again, with a parameter from a previous call to OnOpen.

Previous Build April 15, 2018. Got improved Twitter functions, long length, language, recent, count.

Previous Build April 10, 2018. Got Twitter functions for the Twitter plugin.

Previous Build April 3, 2018. Got JS.GetSyntaxError();, which is very useful for testing a webpage scraping script prior to executing it. Fixed a minor problem with Success sounds on Up-Down-Up gestures.

New Build March 27, 2018. Changed Security.Hash() so that string comparisons will work. Got Moose.EnableWiggleSuccessSound(), Moose.DisableWiggleSuccessSound(), Moose.EnableWiggleFailureSound(), Moose.DisableWiggleFailureSound(). Got Plugin.RanLateDueToSleep (true/false). Added Naudio, and a FFT from Accord. Fixed a hard-to-find bug, a keep-alive timer for AWS, was triggering the wrong thread. This fixed the problem of Moose.exe “going to sleep” for 6 minutes at a time in evenings. Scene.xml has added protection to not get wiped out from a crash.

Previous Build March 20, 2018. AWS changed to be single-threaded. WebSockets sometimes was being dropped by AWS, sometimes send bad data, Moose coded to detect and re-connect. Got Security.Hash(theString,64) for use in Webpages plugin to compare for changes. Changed interval of silence between speaking, lengthens if lots of talk in last 2 minutes. Moose.exe coded protection against overflow of messages incoming from AWS or elsewhere. Made sure OnWebHook gets called AFTER Hello runs.

Previous Build March 6, 2018. Up-Down-Up gestures send Event to Run whatever the Wiggle plugin specifies. C# functions for Moose.EnableShhingGesture(), Moose.DisableShhingGesture(); Moose.EnableWiggleGesture(), Moose.DisableWiggleGesture(); Moose.EnableWhistleWiggleGame(), Moose.DisableWhistleWiggleGame(). Moose.EnableGamePoints(), Moose.DisableGamePoints().

Previous Build Mar 3, 2018. Moose.Shh(), Moose.ClearSayQueue(), Security.Encrypt(), Security.Decrypt()

Previous Build Feb 27,2018. Finished single-threading plugins. Startups finish before Runs.

Previous Build Feb 21, 2018. VoiceRules working again, fixed a few visemes for David & Zira. Closed caption now sent word by word. Single-threaded the plugins and added plugin timing diagnostics. Gestures Shhh work properly again.

Previous Build Feb 14, 2018 Moose.Say now truncates to 600 characters. MMF sets aside 1/3 space for behavior commands, lets 2/3 hold Closed Caption images.

Previous Build Feb 9, 2018. Now sending closed caption images on MMF before speaking. Added C# setting for slight 20ms delay on lip sync motions. Tolerates 2000 words (but future will truncate to 600.

Previous Build Feb 1, 2018. Moved FacebookAppId into C#, allowing Home plugin to be improved. Can now check login status User.IsAuthenticated periodically. Using OnAuthenticated entry point.

Previous Build Jan 24, 2018. C# dialog buttons perfected, resizable window, ‘New User Detected’ event received in all plugins. Capped Say queue at 4, move excess to Buffer. Flood prevention limit of 7 arrive on Say queue. Empty Moose.Say(”) doesn’t error anymore.

Previous Build Jan 22, 2018. C# dialogs now use fancier buttons, similar to .html style.

Previous Build Jan 17, 2018. C# dialogs can now have linebreaks.

Previous build Jan 12, 2018. Moose.exe C# at startup decides if New User, Seen-before User, and Maybe-new-uncertain, and shows C# dialogs accordingly.

Some time off, Christmas to New Years, then Sick (flu) asked for a week, turned into 1.5 week, resumed work Jan 11.

Previous build Dec 26, 2017. Fixed broken Green Error dialogs. Created new .html entry point OnOpen – function() {}. Used OnOpen in UserInfo.js to signal new user. Added line# of javascript error to Green Error dialogs. Reduced wrappers when passing info between .js, .html, and C#.

Previous build Dec 20, 2017. Plugins close and restart well now, fixed entry points like OnWebHook, exports, etc. C# knows better when it’s a new user based on Facebook info, sends event to UserInfo plugin. Removed ‘steven’ folder and shifted subfolders upward. Special-case code sends new user event to a closed UserInfo plugin view.

Some time off after catching a cold. Some time off related to mother, napping into long sleeps.

Previous build Nov 28, 2017. Fixed a problem when using cloud saving of settings from ShutDown() function when using Cloud=”True”.

Previous build Nov 22, 2017. Plugins are auto-detected, can make new by copy,paste,edit. (All settings about the plugin are now stored within the plugin settings). Fixed Voice.SetVolume(). Removed unused Strings.xml files from plugins.

Previous build Nov 15, 2017. Prevented Scene.xml from becoming corrupted during saving. Got Moose.IsCornerJumpingEnabled (true/false) and Prevented Moose from continuous jumping around the corners.

Previous build Nov 10, 2017. A big clean-up of code, so Quitting is improved. Now it closes all pending XMLHttpRequests, Events, setTimouts and Export function calls. Solved a JINT problem by using some private variables in JINT, ( it was losing all global variables when just 1 JINT thread is forced to close). Upgraded to latest version of JINT. Reduced plugins from using 4 threads, to just one per thread, which saves A LOT of memory usage. The Moose has become much more quickly responding, so it is executing javascript much faster. Now it speaks Goodbye when quitting.

Previous Build Oct 30, 2017. Got a Moose3D that fixed making WebMoose recordings. (which allowed me to record a lot of jokes, now with anti-aliased quality.)

Delays from: “moved to Florida”, “margin call”, “visiting family”, “adjusting schedule”, and lots of “code cleanup” while coding the clean shutdown of the Moose.

Previous Build Oct 2, 2017. Got Resources.Settings.GetLength(‘Safe’,’Strings’); and Ivan did improvements to Cognito tokens expiring. He apparently made minor changes to UserInfo plugin.

Previous Build Sept 22, 2017. Cloud saving of settings finally completed. Plugin.Run() from HTML script no longer uses the main UI thread. All Settings are now escaped to XML standards before saving, which might cause problems for newline character. Shufflers were re-worked and index saved. Cloud.SendKillCommand() ready for testing.

Previous Build August 13, 2017. Got a lot of background work on saving settings to the cloud. Partial readiness for remote Kill 2nd copy of same user_id Moose on a different PC. Cloud.SendKillCommand(). Partial work on ideas for cloud saving of Shufflers, with an API. Stopped asking “Save Changes?” at quitting.

Previous Build August 5, 2017. Got cloud function to supply a token for using Microsoft Cognitive services (bot framework, LUIS), and Ivan code WebSockets in Chat.js for using Microsoft’s bot framework.

Previous Build July 25, 2017. Fixed User.Age calculation, but not available yet in .js files. Got: User-specific cloud storage of API keys and secrets, Auto-startup control of delay times , Open file manager Startup folder, WPA microphone app.

Previous Build: July 24,2017. Mouse-tracking was re-written with more direct-from-hardware, giving much better speed, and stopping a lot of context-switching that was slowing down movements of sliding Notification windows and javascript animations. And hopefully fixed Ivans problem and letting gestures work for him.

Previous Build: July 15,2017. Got better threading to <script>’s running in HTML windows, so my heavy javascript CPU-usage for background color gradients animating, foreground text animating, does not slow down the mouse, as much as before. Side-Effect: gestures need changing. Fixed: all windows back to normal without bouncing.

Previous Build: July 11, 2017. Notifications window moves smoother and bounces as requested. But problems: choppy hiding. All windows bounce by mistake.

Previous Build: July 2, 2017. Fixed problem of Cognito token expiring, but/and also it does a soft reset of Facebook’s token too.

Previous Build: June 23, 2017. Fixed to limit active connections to AWS to just 2. Got Events.OnEvent(‘SlideStarted’) and ‘SlideEnded’ for smoothing the Notifications motions.

Older Build: June 8, 2017 Got Timer.setTimeout in .js files. Some incomplete exploration of Toast window movements.

Older build: May 25, 2017. Got Lambda webhook code converted into compiled C#. Fixed AWS blocking the Moose after a while. Got <include src=”@file:MoreCode.html”><include>

This post was created July 2, 2015. Build details prior to May 2017 were not saved. Ivan has been coding much earlier than 2015.