Do you ever miss important client messages because everything’s scattered?
from InsightSeeker@thelemmy.club to programming@programming.dev on 20 Mar 04:04
https://thelemmy.club/post/46192190
from InsightSeeker@thelemmy.club to programming@programming.dev on 20 Mar 04:04
https://thelemmy.club/post/46192190
Not sure if it’s just me, but I’ve been running into this quite a bit.
My client conversations are spread across different messaging platforms, and sometimes important or more detailed discussions just get buried or overlooked.
It’s not even about the number of messages, it’s the fragmentation that makes it hard to keep track of everything in one flow.
Anyone else dealing with this? How are you keeping track of conversations without things slipping through?
#programming
threaded - newest
www.beeper.com
Matrix client that lets you bridge a variety of chat apps. I imagine you’re using slack and at least one of the other messaging apps they support
nice, a single pane of glass for law enforcement or other marketing firms to see all your communications!
Fair point, but it’s really about simplifying scattered conversations for productivity, not creating a surveillance dashboard.
Like any matrix client, it uses their e2ee before hitting the matrix home server.
I also prefer this approach, but the greatest difficulty lies in integrating GChat, especially after its latest security policies (github.com/mautrix/googlechat/issues/115). Do you also face this issue? Any tips/ suggestions for me.
I actually haven’t used beeper in ages. I don’t use many of the chat apps with official bridges other than signal and discord, and Instagram (when I had it) hated that I was bridged and threatened to ban me. Since I’m on iPhone open bubbles bridge isn’t worth setting up for me so I’m not gonna bridge iMessage either. Best of luck with chat and beeper though !! :)
How does it integrate Slack and WhatsApp, given they don’t have official APIs? All reverse engineered?
Sounds like you need WUPHF: youtu.be/uRoCMde-Cm8
Well, sounds like the issue is that important specification details aren’t part of the specification but clarified on the fly in some random chats.
At least it should be added to the issue/ticket description and not just as an appendix but a coherent text. Ideally, there should be a lot being clarified before even starting