Data infrastructure is scattered, siloed, excel sheets and google sheets stored in various places (personal g drives, company g drives, some network share somewhere, an ms sharepoint site, sometimes in development git repos or various wikis)
Reporting infrastructure is manual massaging and lots of powerpoint.
My company isn't that large, but bigger than you'd think for such a "system".
It's an interesting paper, for sure. I think this only works in reality if 1) there's a clear reason the content was removed that a user could take steps to avoid in the future, and 2) you're willing to admit that reason to the user.
With so much content moderation these days coming from machine learning (violates #1), personal vendettas from human moderators (violates #1 and #2) and quasi-legal threats from third parties (violates #1 and #2), there's not much room for user education left.
I've seen sciter come up in discussion on quite a few threads related to Electron and other web browser embedding systems, but I've never seen a good answer for "why not sciter", so I'll try to put some points out here:
1. Electron is open source, sciter is free as in beer only.
2. Electron implements the exact same javascript as the web, sciter implements its own js-like language. Harder to find developers with experience, and harder move your app from sciter to some other engine down the line.
3. Electron implements the exact same html/css as the web, sciter implements html/css from a few years back plus its own proprietary bolt-ons. Same problems as #2.
Reporting infrastructure is manual massaging and lots of powerpoint.
My company isn't that large, but bigger than you'd think for such a "system".