going to just put last commit's authors note's here:
Turns out this project is starting to get indexed by search engines.
Hi crawlers! Kind of wish the SWFs were archived for the actual activities, though.
(If you have MSOL.swf I'd be glad to talk about it.)
Known Issues: Chrome 49 SUXX, as in it's not doing our beforeunload handler.
I guess I should add a ping/pong routine to the server that removes "dead clients".
Add "API" reference (basically just the bare minimum alternative for the Messenger Activity API .CHM file)
Authors notes:
Turns out this project is starting to get indexed by search engines.
Hi crawlers! Kind of wish the SWFs were archived for the actual activities, though.
(If you have MSOL.swf I'd be glad to talk about it.)
Known Issues: Chrome 49 SUXX, as in it's not doing our beforeunload handler.
I guess I should add a ping/pong routine to the server that removes "dead clients".
some things considered Channel_OnTypeChanged optional, grr.
Make fourCC a thing so people don't manage to get the wrong channel for their activities and then break stuff
a bit less extended and using stock error and ready instead of connect,<0,1,2>
this is semver breaking but we're in prerelease so i'm not touching package.json
... until it's considered at least mostly done
since the parsers work now, my bad
... I have a horrendous idea.
```js
/** pure evil **/
Object.defineProperty(window, "onload", {
set: function onload(fn) {
__messengerjs__onloadfunction = fn;
}
});
```
It may be sin... but it may fix usernames... commiting before i try it
yellows111
yellows111