XMPP - Extensible Messaging and Presence Protocol (with Node JS and eJabberd)

แชร์
ฝัง
  • เผยแพร่เมื่อ 8 ก.ย. 2024

ความคิดเห็น • 79

  • @Algoritmik
    @Algoritmik 3 ปีที่แล้ว +32

    The way you make your videos by jumping directly to the most important part and code it live is simply amazing!

  • @angeldimitrov1353
    @angeldimitrov1353 2 ปีที่แล้ว +3

    Excellent tutorial as always - straight to the point and very clear!

  • @EddyCaffrey
    @EddyCaffrey 3 ปีที่แล้ว +4

    I’ve been waiting for this one . Thank you very much

  • @semperfiArs
    @semperfiArs 3 ปีที่แล้ว +3

    Your channel is gold. Happy I found it. Been following it since 3 months. Keep it up..you will reach 500k by year end

    • @hnasr
      @hnasr  3 ปีที่แล้ว

      ❤️❤️❤️

  • @thaboshikwambane
    @thaboshikwambane ปีที่แล้ว +1

    Love your work man. I'd see it randomly when I had basic questions with very little context but now my context is a lot better and the concepts that you teach are clicking. Really appreciate you. Thanks for all the work that you do and for sharing your knowledge. Lots of people become great and they never share the wealth in their brains.
    You've done a lot...
    You should consider links to your Udemy courses on your video descriptions too

  • @idrisAkbarAdyusman
    @idrisAkbarAdyusman 3 ปีที่แล้ว +1

    it is always sooo fun watching your videos, unlike any other that feels so boring

  • @julioprotzek4408
    @julioprotzek4408 3 ปีที่แล้ว +1

    That docker + node demo is

  • @maxjang
    @maxjang 3 ปีที่แล้ว +2

    Pretty good to understand XMPP Protocol! thx!

  • @rajpatel9406
    @rajpatel9406 3 ปีที่แล้ว +1

    superb explanation

  • @raoufaissaoui3754
    @raoufaissaoui3754 3 ปีที่แล้ว +1

    I have nothing to say but 1000 thanks

  • @konarkkapil9626
    @konarkkapil9626 3 ปีที่แล้ว +1

    ooh man you are a knowledge mine. hope to be like you someday 🙂

  • @autohmae
    @autohmae 3 ปีที่แล้ว +2

    8:53 I had always assumed it was called ejabberd, because it's written in Erlang. Even Wikipedia thinks so too

    • @hnasr
      @hnasr  3 ปีที่แล้ว

      You know you might be right. I might have been making things up. I know about jabberd. So I thought ejabberd is the encrypted version specially after I checked in wireshark

  • @baobozo
    @baobozo 3 ปีที่แล้ว

    great video!!! nice and clear, love the demo!!!

  • @DevDungeon
    @DevDungeon 3 ปีที่แล้ว

    Great presentation

  • @Mrwiseguy101690
    @Mrwiseguy101690 2 ปีที่แล้ว

    Wow perfect tutorial!

  • @talhakhaliq3458
    @talhakhaliq3458 2 ปีที่แล้ว +1

    Question: How can we view logs file of a server, like view how many users are online .their messages, and call history .Basically where and how we can find user logs in ejabberd
    .

  • @myselfstudy6477
    @myselfstudy6477 3 ปีที่แล้ว +2

    Can you please explain the difference between web sockets and xmpp ,please sir

  • @Eghizio
    @Eghizio 3 ปีที่แล้ว +1

    Let's play a game:
    Every time Hussein says PP and you laugh/giggle you take a shot. 😄

    • @hnasr
      @hnasr  3 ปีที่แล้ว +3

      You have no idea how many times I had to edit the giggles out in this video 😅

  • @chrislagos44
    @chrislagos44 2 ปีที่แล้ว +1

    Hello can you provide an example of building an xml stanza with the simple-xmpp library using node.js Thanks!

  • @Tiberiumgod
    @Tiberiumgod 3 หลายเดือนก่อน

    Is there any way to get all the messages sent from the Front-End to the Back-End side? I mean, if a message is sent to ejabberd, I want to be able to get every message on the nodejs side as well. Right now, as I see it, I can only receive messages sent to the user I use to connect to ejabberd on nodejs.

  • @DanishRaza-ji2du
    @DanishRaza-ji2du 3 ปีที่แล้ว

    Nice stuff

  • @s-guytech9160
    @s-guytech9160 3 ปีที่แล้ว

    You really interesting ....

  • @GuilhermeGavioli
    @GuilhermeGavioli ปีที่แล้ว

    If I were to change the client from NodeJs to a browser/mobile app, could I use NodeJs just to do the bridge between the client and the Jabberd?

  • @ravitejavankam2977
    @ravitejavankam2977 3 ปีที่แล้ว

    Can please example the technologies for realtime tracking like uber. How realtime location is updated for large user base. Do they use UDP.

  • @m.edrissaria5625
    @m.edrissaria5625 ปีที่แล้ว

    can you make a video how to register a user in ejabberd using node pleasssse

  • @adeoyeadefemio.8859
    @adeoyeadefemio.8859 ปีที่แล้ว

    Thanks so much for the guide. How do I set up the Ejabberd server to use RESTful API in creating a user account

    • @adeoyeadefemio.8859
      @adeoyeadefemio.8859 ปีที่แล้ว

      I want to be able to do something like POST /api/create-user

  • @MikeNugget
    @MikeNugget 3 ปีที่แล้ว

    Do you have any video about mtproto?

  • @saradaprasadbiswal420
    @saradaprasadbiswal420 3 ปีที่แล้ว

    Hello all, Amazing tutorial. But I am not able to run this in my local windows system. I am getting error message "XMPP authentication failure". Can anyone please help me out. Thank you in advance.

  • @mtnrabi
    @mtnrabi 3 ปีที่แล้ว +2

    Why use xmpp over something like web sockets?

    • @killDJuice
      @killDJuice 3 ปีที่แล้ว +1

      Cause the backend people are lazy and don't want to write the logic for creating a room etc. etc. Side note don't use xmpp it's a old blotted solution

    • @SamWhited
      @SamWhited 3 ปีที่แล้ว +3

      Websocket is a transport like TCP, XMPP is an application level protocol like HTTP. You can't just use websocket by itself, you have to have something to transport over it. XMPP can be one of those things (and in fact, it's often transported over websockets).

    • @SamWhited
      @SamWhited 3 ปีที่แล้ว +1

      @@killDJuice This is just not true, stop spreading fud without evidence please. I'm not saying XMPP is perfect, it has its problems sure, but I don't even know what you mean by "bloated", as far as chat protocols go XMPP works *very* well over limited bandwidth connections, and you can implement as big or as small of a service as you want because the core protocol is kept separate from all the various extensions that one service might want and another might not.

    • @killDJuice
      @killDJuice 3 ปีที่แล้ว

      @@SamWhited extension are the issue that makes xmpp un usable

    • @SamWhited
      @SamWhited 3 ปีที่แล้ว +1

      @@killDJuice do you know a protocol that doesn't work this way? At least Matrix and IRCv3 have pretty much the exact same thing. You don't have to implement every single one, you build your service or product like normal and use the extensions only for features you need, this way you can be compatible with other clients and services. If you didn't have them in 10 years the whole protocol would just be old fashioned and out of date when customer requirements have changed. Don't get me wrong, it can be confusing to know what to implement on the public network for the best experience, but stuff like the compliance suites can help there. I dunno, what to tell you, it's not that hard.

  • @rahulvanmali1406
    @rahulvanmali1406 3 ปีที่แล้ว

    Can you make a video on ffmpeg or shaka packagers

  • @conference_1
    @conference_1 3 ปีที่แล้ว

    Which one is better websock or xmpp

    • @SamWhited
      @SamWhited 3 ปีที่แล้ว

      They are different things, websocket is like TCP (a transport), XMPP is like HTTP (an application level protocol). In fact, XMPP is often transported over websockets.

    • @killDJuice
      @killDJuice 3 ปีที่แล้ว

      Xmpp uses websockets but I would recommend using socket.io if you just want a chatting application. But you will have to work a little extra to scale a system like that case of the long poling fall back

  • @khayryazzez
    @khayryazzez 3 ปีที่แล้ว

    can i use it to make chat video

    • @killDJuice
      @killDJuice 3 ปีที่แล้ว

      Nop use jitir instead

  • @AdityaPrakarsa
    @AdityaPrakarsa 3 ปีที่แล้ว

    hotmail.. you are old school brah...

  • @33athen
    @33athen 2 ปีที่แล้ว

    it doesn't work

  • @DarkKnight-ree
    @DarkKnight-ree 3 ปีที่แล้ว

    First

  • @killDJuice
    @killDJuice 3 ปีที่แล้ว +3

    A dead protocol
    I can talk at length why using xmpp is a bad Idea specially for morden web. And you should correct your statement google talk is long dead and stoped using xmpp before it was cancelled. And Facebook messager no longer users xmpp

    • @chetansharma6344
      @chetansharma6344 3 ปีที่แล้ว +1

      What are its modern alternatives and where are they being used?

    • @Algoritmik
      @Algoritmik 3 ปีที่แล้ว +1

      @@chetansharma6344 WebRTC, HLS, RTSP, RTMP, WebSockets, FreeSWITCH.

    • @AnikDas
      @AnikDas 3 ปีที่แล้ว +3

      You are absolutely wrong about the part that xmpp is dead. It may seem like it's not being used but whatsapp uses a modified version of the xmpp protocol. A lot of enterprise software also make use of this protocol. I agree that xmpp may not be good with choppy network but it's still useful for non chat or custom chat uses cases.
      As for the alternative mqtt, amqp etc are the alternative. On a side note you CAN use xmpp over we socket.

    • @killDJuice
      @killDJuice 3 ปีที่แล้ว

      @@AnikDas it's a bloated protocol. Working with XML is awkward enough using a bloated protocol on top of it is extra bit of complexity that frankly no one wants to enjoy. If you have bend over backwards to justify few use cases then the solution failed in my opinion. XMPP can use websocket but the experience is still not good enough. There is a better federated protocol called metrix chat used by element and I feel it's much better.

    • @killDJuice
      @killDJuice 3 ปีที่แล้ว

      @@chetansharma6344 if u want a ready to go solution that takes care of chat rooms etc out of the box is federated and does everything xmpp promises take a look at mertix chat