Re:Five Open-Source Slack Alternatives
by derefr on Monday November 02, 2015 @08:13PM
(#10496704)
There's just an inherent conflict there, because your DMs are indexed+searchable just like any other message, and really, you want them that way.
The only obvious solution, right now, is running your own private server if you want private indexes.
But the One True Way to solve this problem, in the fullness of time, is for every enterprise to run their own little PaaS with a standard API, and for SaaS providers to launch their app instances into the enterprise's PaaS using that API. This would be the cloud equivalent of the SaaS-provider selling the enterprise an "appliance" they can keep within their data-center. The enterprise gets full control of the data: their PaaS can be set up to not allow the SaaS-provider any way to exfiltrate the data the app creates, to determine rollout schedule for new app versions, etc.
(And note that when I say "enterprise", I could just as well mean that any individual user could own their own completely-automated black-box micro-PaaS, living "across" various IaaS providers and migrating to new ones as necessary, brought into existence for them by the first SaaS vendor to try launching something into it. Effectively, the ultimate evolution of a personal VPS, providing you with a "management interface" that looks like a cross between Heroku's dashboard and the Windows "Programs and Features" pane.)
The only obvious solution, right now, is running your own private server if you want private indexes.
But the One True Way to solve this problem, in the fullness of time, is for every enterprise to run their own little PaaS with a standard API, and for SaaS providers to launch their app instances into the enterprise's PaaS using that API. This would be the cloud equivalent of the SaaS-provider selling the enterprise an "appliance" they can keep within their data-center. The enterprise gets full control of the data: their PaaS can be set up to not allow the SaaS-provider any way to exfiltrate the data the app creates, to determine rollout schedule for new app versions, etc.
(And note that when I say "enterprise", I could just as well mean that any individual user could own their own completely-automated black-box micro-PaaS, living "across" various IaaS providers and migrating to new ones as necessary, brought into existence for them by the first SaaS vendor to try launching something into it. Effectively, the ultimate evolution of a personal VPS, providing you with a "management interface" that looks like a cross between Heroku's dashboard and the Windows "Programs and Features" pane.)