I got a new job. whatsapp group (20 people) is migrating to signal because I don't use it.
I got a new job. whatsapp group (20 people) is migrating to signal because I don't use it.
I understand that it may be problematic sometimes but this was very smooth. I didn't even say anything.
A: what's your number for the whatsapp group Me: I don't have whatsapp because of facebook. B: ok, we have to use signal then A: ok
And that was it. Life can be very easy sometimes
You're viewing a single thread.
Why would a workplace need a group chat? Aren't there any enterprise tools in place to achieve that?
Small companies and startups like to save money
Cannot access work intranet (Teams etc.) from personal phones. Don't have work phones. They all use WhatsApp so reluctantly, so do I.
In these companies, does anyone check the licenses in details to make sure using them is ok for the company?
Meta will get at least the metadata: meaning they will record who was in which call connecting from where.
For example, if one member is visiting a client, Meta may be able to infer the relation between the 2 companies.
If any of the people in the room click "report", then the discussion is sent for review without the encryption protection
I'm pretty sure their user agreement translates to "you agree to let us do whatever the f*ck we want with the data you're purposely disclosing to us".
And last but not least: if Meta decides to wipe the archives, any info get lost?
There a reasons large companies ban unauthorized apps to talk about work.
Like I said, it's for us to talk about shifts and what have you.
I would never join a group chat like that. If they need to get ahold if me after hours, they can call me.
BTW Teams doesn't live on Intranet. There's no reason they wouldn't be able to open up Teams to BYOD beyond incompetence.
I know Teams doesn't live on the intranet, but I'm not going to put work software on my own phone. Policy needs it to set up a work profile and I then can't use fingerprint, face or a 4 digit pin. And all the shite that flows through Teams would be be piling up, just like it does on the PC at work, brilliant when you're only in a couple of days a week. They want me to use a phone? Provide one.
The WhatsApp group is for us to send updates about traffic, if someone can cover a shift etc. it's not an official work thing. I could of course not use it and just text people. That's really just making my life difficult whilst sat up here on my high horse with a self righteous look on my face, whilst I miss the chance of an extra shift.
Denying putting work stuff on your phone is absolutely valid. The company should provide a company device in that case. And if you do agree to put company data on your phone, they should give a monthly stipend towards your phone bill. That's how every org I've worked at has approached it.
Really depends a lot on the groupchat. I was apprehensive but it's quiet there and overall the things that get sent there are either in office hours (e.g. "internet might be out intermittently we are working on a fix") to links to pay for something someone paid for outside of work like food or drinks.
I don't mind it that way, maybe once a week a couple messages
That requires a business login on your personal device, which is typically against company policy.
Although, so should be sharing work info outside of corporate channels, so what do I know.
Emergency team chat when there is a outage of corporate systems
Chat for social work stuff like team building or off-site gatherings.
Being about to shit talk about corporate stuff off the reservation is nice.
It can be a big sms group chat, signal, discord, whatever your team likes.
…to which for privacy reasons your team shouldn’t like SMS, Discord, Telegram, Slack, and probably even Signal (somewhat for privacy, & more for accessibility)
What do you recommend?
XMPP. A business can self-host, there are public servers, or there are many businesses which offer customised xmpp hosting as a service.
I can be federated with other xmpp servers or be a locked-down work-only service, or federate with chosen other servers (such as a client company's xmpp servers).
The main problem is, you need to have someone good enough to setup a proper firewall when selfhosting.
Sure, it might not take $$$$, but it will take $, which is definitely more than nothing.
If that's the main problem then that's easy to solve! Simply use a free public xmpp server.
I mention the self- and paid-hosting options because businesses tend to like having a sevice agreement backed by a contract, and may have additional specialised requirements not provided by free services (xmpp or otherwise).
Snikket exists for this type of user. If money is an issue, since XMPP is actually lightweight unlike Matrix, you can host multiple things even on the cheapest VPSs so it isn’t dedicated to one taskl or self-host out of your home (which is what I do, but also with some small sites, a feed aggregator, Mumble, terminal sharing, Darcs/Pijul version control systems, & Nix remote builder).
Skill issue, not money issue.
But when you are a business, everything can be converted into a money issue.
skill issue
I don’t understand how. Snikket is fully boxed up & preconfigured for the lazy, & offers straight-up hosting for the the even lazier.
I say lazy since setting up ejabbered is already easy to set up with sane defaults, a web admin UI, & availability in like every package manager.
fully boxed up & preconfigured for the lazy,
I see that as solving the skill and effort issue.
I used to work for a small PPI claims management company. Our accounts team had a WhatsApp group for social discussion outside of work.
All of our internal work comms were handled through Slack.