21–30 of 127 posts
Earlier quoted context omitted.
Just let each client index locally
How big is your hard drive? How about on your phone? I guess there's also the problem of how to let a new joiner view previous messages. Can that be done with e2e encryption?
First thought: who the hell would be interested to read thousands of lines of discussions like how to name a field in REST response or notifications of someone making a build xD
If you think "I have nothing to hide" you're lacking in imagination.
What if all your search history were leaked? What if all your text messages were leaked? What if all your emails were leaked? I guess those things aren't trendy enough to worry about. For a long time I have noticed what I would call 'ankle biting journalism'. Basically take whatever is trendy, make only the most obvious observations about it (things that someone who only rudimentary knowledge would come up with in a…
First thought: who the hell would be interested to read thousands of lines of discussions like how to name a field in REST response or notifications of someone making a build xD
Yes, 99.9% of what you do or say in your daily life is likely of no consequence. But every now and then you may do or say something that could be used against you, and someone who has many years worth of data collected on you can probably find quite a few such bits of info.
Among all of your internet "transactions" probably less than 0.1% are with your bank, for instance (sending your credentials, etc). You want end-to-end encryption and good security to protect that 0.1% of your data, not for the other crap.
> Right now, Slack stores everything you do on its platform by default — your username and password ...
I would be extremely surprised if they store plaintext or even encrypted passwords. Maybe the author means usernames/passwords sent in messages, but that's not unique to slack.
First thought: who the hell would be interested to read thousands of lines of discussions like how to name a field in REST response or notifications of someone making a build xD
I'm sure the Gawker employees thought the same thing, until their chat logs were brought up in court http://nymag.com/intelligencer/2016/03/what-hulk-hogan-taugh... https://splinternews.com/the-gawker-hulk-hogan-trial-and-the...
What if all your search history were leaked? What if all your text messages were leaked? What if all your emails were leaked? I guess those things aren't trendy enough to worry about. For a long time I have noticed what I would call 'ankle biting journalism'. Basically take whatever is trendy, make only the most obvious observations about it (things that someone who only rudimentary knowledge would come up with in a…
"In hindsight, complying with the company's Document Retention Policy (which at Netscape was basically, ``shred anything within 90 days unless you can't get your job done without it'') might have been a good idea." [1] Do companies no longer have Document Retention Policies? That seems like the bigger piece of the story here. [1] https://www.jwz.org/gruntle/rbarip.html
To be clear, when I use Slack I assume private chats will remain private, but if they don't, well... screw it. It's not like I paid for it so how am I entitled to anything? No vendor can promise they won't get hacked. What if your Linux OS got hacked due to a zero-day bug and all your DB data was leaked?
I've been spending all these years holding my tongue because as a matter of principal I don't write anything I don't want a permanent record of and it would be nice to see all that overhead pay off or more accurately, it would be nice to see people get burned for being sloppy. So no, I wouldn't really stand to lose anything if everything I ever said on company chat was published in an easily searchable format online.