Viber is not responding.
Firefox is not responding.
Sublime is not responding.
Clients are not responding.
Motherfucking life is not responding.

I’m gonna make this profile picture on my Viber and WhatsApp.

The question goes straight to @linuxxx.

How secure is Viber? After an update recently, each conversation one starts says it's end to end encrypted.

How true is that?

Client sends an email after 5 PM. We all left for home.

Client: blah blah blah...We urgently need this app to be done by COB on Monday. Our CEO is going to launching it on Tuesday to the board of Directors.

––Boss forwards me the email––

Boss: Can you get this done by this weekend.

––On Viber––
Boss: I have sent you an urgent email. Let me know.

––My Reply––
Me: This can't be done in a day or 2. Looking at the scope of work, I need at least 8 weeks.

––Boss Replies back––
Boss: You are not performing at the best of your ability. Come and see me on Monday, I need to talk to you about your performance on urgent projects.

my retarded landlord upon finding out that I have neither Viber nor Skype started doubting that I'm working in IT

Announcing devRant 2.0! It is time for exciting overhaul, sponsored by our good friends at Tencent, that will bring life back to this amazing platform.
- elegant simplicity of Viber meets excellent minimalism of AWS
- custom avatars for ++ members
- exciting mini-games
- animated stickers
- ChatGPT integration for ++ members
What a time to be alive!

So, Viber says my friend was last online before she was born.

Another Developer: bro, shit hit the fan. The x web service is throwing some error. Can you take a look please. I want to go home. I'm tired.
Me: Yea sure bro no worries.
Another Developer: I go pee, after that I will delegate the ticket to you.
(Another Developer goes to the washroom)
Me: (04:59 PM) Oh time to pack-up and get the fuck out of here
Me: (05:08 PM) Receive a message on Viber from Another Developer. It reads "Fuck you, I'm going to rub my balls on your desk"

I prefer Telegram than facebook and viber. You?

A friend sends in reminder 3 time to me via Viber message to up-vote his Stackoverflow question.

Yeap bro we all have been there.

I want to fuck the whole Skype team until death for blocking my contacts and won't let me to make any call with my father and my family member. FUCK YOU SKYPE.

Happy new year to all devRanters !

"what about a messaging app, that has all the features of skype, whatsapp, viber, hangouts, fb messenger & co - everybody would use it over the others"

It might be interesting for you that Facebook and viber is somehow dead in iran and ME(since 2 years ago), the main social network in here is Instagram and chat app is Telegram

Viber.

Viber for Node: works with Express

But don't you dare to try using Express's default middlewares.

Don't you fucking dare

For some reason viber decides to update its self without asking!!!! And now I have to accept their new terms and conditions???? Why did you force update your product in MY machine without asking first????

Rant 1
---
Seriously what is the fucking difference between github gitlab bitbucket? Is it like the whatsapp/viber/signal shit?

Whatsapp was the first to create a system for free chatting? Then viber came along and copied the exact same fucking bullshit like whatsapp? Then signal came along and copied the same bullshit? And all other apps too?

Github was the first to create a system of GIT? And then gitlab came along and copied the exact same bullshit? Then bitbucket copied the same horseshit too?

Rant 2
---
1) echo "shit" > recruiter.txt
2) echo "shit" >> recruiter.txt

> Will create the file if not exists and OVERWRITE the text inside it

>> Will create the file if not exists and APPEND the text inside it

This is the only difference

Correct?

Rant 3
---
Fuck this devrant ass shit for making me wait 2h to post a new rant. What are we in 1995? Not even facebook has this stupid restriction. Not any social media app EVER in existence. This shit is whack. U fear someone spamming the shit out of the app. But thats GOOD FOR U because you then have active people creating content on ur platform. Put this restriction away before i slap my dick on ur face!

Following some new nextjs tutorial to learn how to efficiently build a web chat app, the guy built it very solid, but is it efficient?

Im having mixed feelings about this approach. The way he did it is, for example when you click on a user (imagine it as a list of users from your contacts), it actually calls a route, which stores that in database, and once its done Then the route triggers lets say socket.io event to notify the frontend to update the UI.

Not only that but each new message that gets sent it actually calls a route which stores that message in database and once that's successful Then it emits a socket.io event to the frontend to fetch that message.

As you can imagine constantly calling routes like this Does induce small delays. Creating conversations, navigating, opening someones profile and especially sending messages, is NOT instantaneous. When you do it theres a small delay, giving the impression as if the app is SO large that it lags

But it doesnt lag, it just needs a few ms to store that in db so it can return the socket.io bidirectional message event. Which does make sense because what if the internet broke and the user immediately gets sent a message, but the message fails to get stored in database? Or db storage gets fucked or something else fails but socket.io works while db doesnt? The data then may be inconsistent. This approach fulfulls the single source of truth principle

So thats why im having mixed feelings about this approach particularly because of small delays. It is not instantaneous like whatsapp discord telegram signal viber etc the input UI freezes until the message is successfully sent

---

Of course this can be a UI/UX decision and can be handled differently even if the backend works like that.

My concern is is this approach valid?

My question is... I had an idea what if i emit socket.io event to send the message while in the background also call the route to store that message in db? This way not only would it work asynchronously but the message gets sent instantaneously, and if the backend fucks up to store it in db then the UI gets updated with message failed to get delivered, switching the socket.io into polling state. Is this a good (proper, efficient, better) way to do it or not?