XSF Discussion - 2022-06-12


  1. lovetox

    the whole timeorderer UUID thing that is now standardised, would this not be a good time to think about if we could use this as a MAM extension?

  2. lovetox

    or maybe first think about if this can be of use in xmpp

  3. lovetox

    since i know mam, i would wish that mam messages had some kind of ordering that does not depend of the order it is received

  4. lovetox

    something i can write to a database, and simply sort on that

  5. lovetox

    its non trivial to sync a archive to harddisk, while keeping the order, while allowing to only sync parts and not the whole archive

  6. MattJ

    lovetox: I think it's too late to mandate sortable IDs. Would it be useful if it was optional but the server indicates that sortable IDs were in use?

  7. singpolyma

    Are there even IDs?

  8. lovetox

    hm .. as messasges from different archives never mix in the same chat, i would simply store the feature beside the archive , and would know to treat this differently

  9. lovetox

    but the question would be if already active archives ever could switch

  10. lovetox

    probably not

  11. lovetox

    or they could if they have not a "forever" retention

  12. lovetox

    hm .. no that would be no good, if i have the messages on the harddisk and suddenly the server feature changes

  13. lovetox

    there is probably no upgrade path here

  14. lovetox

    singpolyma, what do you mean, of course we have MAM IDs

  15. edhelas

    https://support.google.com/talk/?hl=en

  16. moparisthebest

    Huh I thought that happened years ago

  17. TheCoffeMaker

    I even thoght it was before 2017 🤷

  18. singpolyma

    My dad has been using it still

  19. Zash

    They've been shutting down bits and pieces. Federation is long gone, but it worked for a long time after it was supposed to be turned off.

  20. singpolyma

    They're shutting down password auth on basically ball their apis, which is probably what this is