jdev - 2024-12-01


  1. jjj333_p (any pronouns)

    just throwing this out there, im (mostly just to friends ig) streaming me trying to start developing on xmpp from ground zero https://youtu.be/dhEHYhPGtAc

  2. jjj333_p (any pronouns)

    im running into ``` panic: Could not login - unmarshal <features>: expected element type <features> but have <error> ```

  3. jjj333_p (any pronouns)

    i suspect the issue is it connects and my server is returning something strange

  4. jjj333_p (any pronouns)

    figured it out, its because xmpp allows hosting multiple domains per server so you have to give the full jid

  5. jjj333_p (any pronouns)

    i was just giving the userpart

  6. zayd

    Is there any way for a server to see when the last logon of a user was? I think it'd be pretty useful to send emergency messages if a user goes inactive for an extended period of time, like if a relative dies and wants to make sure family knows

  7. zayd

    Is there any way for a server to see when the last logon of a user was? I think it'd be pretty useful to send emergency messages if a user goes inactive for an extended period of time, like if a someone dies and wants to make sure family knows

  8. moparisthebest

    Sure, but sounds like a good way to terrify family

  9. zayd

    > Sure, but sounds like a good way to terrify family I'd want to have it disabled by default and fully configurable for that reason

  10. zayd

    I'm guessing there is a way for servers to track logons, issue would be getting the server to then send a message, and also having it configurable by the user

  11. zayd

    Another possibly easier means of doing it could be having it done on the recipient's end, like "if this contact doesn't go online in x days, notify me"

  12. moparisthebest

    You can set up a cronjob to do that yourself no problem, I just think it's probably a bad idea

  13. ethereal

    Suggesting cronjobs as an alternative is stupid

  14. singpolyma

    ethereal: no call for that. Besides the original suggestion requires a timed job in order to implement anyway

  15. dwd

    > Another possibly easier means of doing it could be having it done on the recipient's end, like "if this contact doesn't go online in x days, notify me" That would have to be done on the recipient's server, I think. Unless the sender's server includes delayed delivery in offline presence responses to probes, and I can't remember if that's the done thing or not these days.