3 ms·
Cool, how about you let me use this with an open source client so I know the client isn't phoning the decrypted data home now.
by DrillShopper 2y ago
Cool, how about you let me use this with an open source client so I know the client isn't phoning the decrypted data home now.
- ronsor 2y agoNo, because half their premium features are dependent on them controlling the client. Even excluding relatively new things like client theming, a custom client could enable custom emojis everywhere, or make it easy to offload storage to another site to avoid paying for nitro. As long as a service is free(-to-play), there will always be a somewhat adversarial relationship between the user and the company.
- mrinfinitiesx 2y agoAh yes, the selling of emojis and simple file storage. I miss the GameSurge IRC and caleague with Mumble days.
- Gigachad 2y agoWhat do you want them to sell? Personally I’m glad the paid features are trivial rather than core functionality.
- LelouBil 2y agoDid you read the article ? > To that end, the protocol is detailed in our whitepaper[0] and open-source library[1] [0] https://github.com/discord/dave-protocol https://github.com/discord/dave-protocol [1] https://github.com/discord/libdave https://github.com/discord/libdave
- rcxdude 2y agoThat doesn't mean much when the discord TOS forbids use of anything but the official client to connect to their services. They seem to turn a blind eye to the various unofficial clients mostly, but also do occasionally ban a subset of their users occasionally despite no other TOS violations.
- arielcostas 2y agoHow can I possibly trust the Discord client is actually using that library and not a modified version that calls home? The whole point of using open source is being able to see the entire code of the program, and compile it yourself