this post was submitted on 10 Jul 2024
3 points (100.0% liked)

Privacy

4160 readers
21 users here now

A community for Lemmy users interested in privacy

Rules:

  1. Be civil
  2. No spam posting
  3. Keep posts on-topic
  4. No trolling

founded 1 year ago
MODERATORS
iopq
3
Using Slack without local device invasiveness? (slrpnk.net)
submitted 3 months ago by [email protected] to c/privacy
4 comments fedilink hide all child comments
 

I may need/benefit from using Slack for "work stuff".

Yeah, sucks totally, but network effect is a thing.

What is the best way to use it, on Android and on Linux, from people that use it often.

Do they have a webapp? How do they do their servers, is it centralized? Any wrappers for anything I should think of?

Using it in the work profile (GrapheneOS), getting the APK from APKpure is the option I would consider as last resort.

you are viewing a single comment's thread
view the rest of the comments
[–] c10l 4 points 3 months ago (1 children)

The web app works fine. The desktop app is Electron-based but works fine. Yes, it is all centralised on their servers.

In which sense do you fear it will be invasive? Other than Slack seeing your messages on Slack, I don’t see what else you could be worrying about. They will always have that kind of access regardless of what you do locally since it’s not E2EE, so really this question just feels like paranoia.

Don’t say things on Slack that you don’t want Slack to know about. That should be all, really.

If you don’t want Slack to see any of your messages, don’t use it.

[–] [email protected] 4 points 3 months ago

Proprietary Android apps are incredibly bloated nowadays. Like 400MB for a random single purpose app.

I dont trust them a single bit.

All android apps can communicate with each other via IPC, if both apps agree to it. This risk accumulates the more proprietary garbage you have on your phone.