jdev - 2025-05-19


  1. halscode

    The README for my client has finally been updated so now you can see it with your eyeballs and see just what the progress is

  2. halscode

    The README for my client has finally been updated so now you can see it with your eyeballs and see just what the progress is: https://codeberg.org/spades/spades-flutter

  3. halscode

    > Enqueue some messages for that account, and then request them after login (also note there is a purge command that could be removing them) what precisely do you mean by "request them"? standard MAM query or something else?

  4. halscode

    I am getting them via MAM, but now if normal msgoffline-type messages are received they'll be duplicated

  5. Benson

    > The main thing is just finding a carrier willing to partner with us and with good access to the sms features etc that customers expect Would there be interest in Africa?

  6. singpolyma

    halscode: you can suppress offline type messages in a few ways, but realistically it is best to code to handle duplicates for a few reasons. If MAM is on you can dedupe incoming messages by mam ID since it gets stamped on most relevant incoming no matter how you get it

  7. bodqhrohro

    Hmm, how is this incorrect? Shouldn't the message be reflected back? It's shown duplicated somehow. https://dpaste.com/GBY44W9N8

  8. bodqhrohro

    I suspect the reason is might be that the client and the MUC component didn't negotiate the nickname, as the outgoing one is shown with a nickname `bqdiscord` while the component enforces `SÉCAM D/K (1382500964)`, and `bqdiscord` isn't even shown in the member list.

  9. bodqhrohro

    Nah, seems to be a Gajm bug, couldn't reproduce this in other clients. Possibly MUCs got confused with chats once again, and an outgoing message is displayed as if it would be a personal message, even though it has a "groupchat" type correctly.

  10. bodqhrohro

    Nah, seems to be a Gajim bug, couldn't reproduce this in other clients. Possibly MUCs got confused with chats once again, and an outgoing message is displayed as if it would be a personal message, even though it has a "groupchat" type correctly.