jdev - 2021-12-25

  1. lovetox

    pep. depends i think

  2. lovetox

    how the muc servers default config is

  3. lovetox

    give me a moment i have to look something up

  4. lovetox

    <status code='201'/>

  5. lovetox

    means the room has just been created

  6. pep.

    oh, right, I remember now

  7. pep.


  8. lovetox

    yeah and that is also the first paragraph of "creating a room" in the MUC xep

  9. lovetox

    so ...

  10. pep.

    Yeah I skimmed a bit fast

  11. jonas’

    lovetox, my avatar stuff should now finally be resolved

  12. Zash

    stuart.j.mackintosh, https://xmpp.org/extensions/xep-0425.html has some implementations now, re spam & abuse management

  13. Zash

    jonas’, what avatar stuff and why don't you have an avatar anymore?

  14. stuart.j.mackintosh

    Zash, 👍️

  15. jonas’

    Zash, I tried to erase it a while ago and failed at doing it

  16. jonas’

    now I managed to erase it completely

  17. edhelas

    how is the usage of pubsub#type for you currently ?

  18. edhelas

    Holger ^

  19. edhelas

    to me it's a way to define the namespace that should be used in the Pubsub node items

  20. Zash

    PSA to client devs: https://github.com/xsf/xeps/commit/028f852c595e857410083697750cd0493d7698dc

  21. nephele

    I'm not sure I understand, it looks like a semantic correction to one XEP?

  22. Zash

    Servers still advertise PEP it the old way. Some clients still check the old way. Thus it works until someone wonders why we're advertising support for something on an address different from where all other queries in that protocol are directed, notices that the current version of the XEP has no trace of that and fixes their server. Then 3 years later, clients break.

  23. lovetox

    MattJ, about sentry which you mentioned last time

  24. lovetox

    i had also troubles to get it working because the install script depends on a docker compose version 1.x, and 2.x broke that api

  25. lovetox

    aso its in my opinion quite a heavy tool

  26. lovetox

    its like 20 containers

  27. lovetox

    for a small open source project i think its quite overblown

  28. MattJ

    lovetox, yes, it's heavy

  29. lovetox

    Gitlab has error tracking integrated and is sentry compatible

  30. lovetox

    but its at the moment a little bit to minimal

  31. lovetox

    you can only report the error, without any context

  32. lovetox

    so not even client version or anything

  33. lovetox

    but i feel there should be a simpler solution than sentry

  34. MattJ

    Yeah, I did write something custom, based on Prosody's issue tracker code. But it's not an official project and I'm not actively using it, so I don't think I can recommend it :)

  35. lovetox

    it should be pretty easy to write something like that yourself

  36. lovetox

    i thought that too

  37. lovetox

    the problem for me is the web stuff

  38. lovetox

    i cant be bothered to write that :)

  39. MattJ

    Yeah, that's why I just reused the Prosody issue-tracker frontend :)

  40. lovetox

    its really sad that i cant get into web development

  41. MattJ

    Maybe. Consider yourself lucky :)

  42. Zash

    you mean it's really nice that you manage to stay away from web development

  43. Zash

    MattJ: We should have gone with mod_bugs!!

  44. MattJ

    May yet. Crash reports from the Snikket Android app still go to /dev/null currently