<ill_logic>
but also why it's including part of sandstorm itself into the package
<isd>
Best guess: making the capnp schema available to the app.
<ill_logic>
ah. I think that might fix a problem I just ran into.
<ill_logic>
No, struct has no field named eventTypes, still.
<ill_logic>
wait I'm dumb I didn't put it inside the right substruct
<ill_logic>
Not sure where the edit notifications are supposed to show up. I don't see it for the old etherpad app either.
<isd>
Edit notifications? This feature is news to me.
<ocdtrekkie>
I suspect it should show up in the notifications dropdown in Sandstorm but it either wasn't finished on the Etherpad side or wasn't finished on the Sandstorm side.
<ocdtrekkie>
I'm kinda curious which it is. 👀
<isd>
I think probably the later? I can't remember ever seeing a notification from an app.
<ill_logic>
haha well I guess the new app will be ready if it ever comes out. not sure if you want the bell to ding every time someone types a word though.
<ill_logic>
afaik it's in the previous app. I think it's the only reason for the capnp node module requirement.
<ill_logic>
current app i should say
<ocdtrekkie>
It'd probably be interesting to poke the Sandstorm database and see if it has interesting activity events from Etherpad that just isn't presently displayed anywhere.
<ill_logic>
(there's also comment and reply notifications, which make more sense than edit)
<isd>
Yeah, you probably want to debounce edit notifications
<isd>
But it's moot if we're not displaying them anywhere.
<ocdtrekkie>
I assume it would be useful to know like once that someone has edited your document. But probably not every time someone edits it.
<ocdtrekkie>
I'm super curious what Sandstorm servers currently have in that activity feed though.
<ocdtrekkie>
I'm guessing it was implemented in Etherpad and such ahead of showing it in the Sandstorm UI and then that just never happened.