jdev - 2024-02-09


  1. debacle

    pep. I just (try to) read your `mod_web_push.lua`. As I don't speak Lua and don't know the internal APIs of Prosody, I'm not sure how it works: The client (browser) sends a subscription object to prosody, I guess? Which is stored where? In a PEP node?

  2. pep.

    debacle, the one I removed years ago?

  3. pep.

    I also don't remember this code, but my conclusion was that it's probably better to use 0357 for web push too

  4. pep.

    I don't know lua much either, it's always an adventure :)

  5. moparisthebest

    Just randomly change things until it mostly works? That's how I do Lua :P

  6. debacle

    pep. Yes, the removed one :-) I'm a little bit in the field of software archeology, I guess.

  7. debacle

    Let's see, how 0357 and web push go together...

  8. singpolyma

    I hav web push working with mod push2

  9. MattJ

    Please no new implementations of XEP-0357 :P

  10. MattJ

    But we do need to get Push 2 XEP'ed, implemented and deployed

  11. singpolyma

    I did the middle one so now we just need deployed rnd then xeped 😉

  12. mathieui

    singpolyma, and then make a subtle but incompatible change in the XEP that forces a namespace bump and requires all implementations to switch :D

  13. debacle

    What is push 2? An alternative XEP to 357?

  14. MattJ

    Yes

  15. MattJ

    Well, not a XEP yet, but that's the next step

  16. MattJ

    There's some feedback I still need to incorporate from the last (!) summit

  17. MattJ

    https://pad.nixnet.services/TRjHpDkUSrep9jqzcjY0uw

  18. debacle

    MattJ One year is a very short time. Thanks for the pointer!

  19. singpolyma

    MattJ: you could compare againt the version I put in the module repo too. it's very close of course