XSF Discussion - 2024-06-26

  1. stpeter

    People interested in SFU integration might also look at how Jitsi does things.

  2. Guus

    (please don't use a hidden muc occupant to orchestrate things though - assuming they still use that 'focus' occupant)

  3. stpeter

    Heh yeah.

  4. stpeter

    I was thinking more about the backend XMPP integration / orchestration.

  5. stpeter

    And if you can track down Fippo, he’s a great person to talk with. 😊

  6. edhelas

    Would it be interesting to add a small <expiration> tag to HTTP Upload ?

  7. edhelas

    Where the client can dictate when to delete the picture, if the expiration is < the max configured on the server

  8. moparisthebest

    You mean an http header?

  9. moparisthebest

    Telling the XMPP server when you want the http server to do something doesn't sound that helpful

  10. edhelas

    I'm having a look at https://xmpp.org/extensions/xep-0264.html and having pictures that stays only like 1h on the server should be enough

  11. edhelas

    No basically, when you ask for a HTTP upload slot you say "I want this put and get url to be available for 3600s"

  12. edhelas

    Then I can start to also differenciate the features in Movim, images uploaded for blog posts will stays indefinitely, for chat discussions, something like 3 months

  13. singpolyma

    I agree it makes sense to do this at http level not xmpp level

  14. edhelas

    Is there a HTTP header for that ?

  15. singpolyma

    Expires though I'm not sure if I've seen it used on PUT specifically, but I don't see why not

  16. moparisthebest

    > No basically, when you ask for a HTTP upload slot you say "I want this put and get url to be available for 3600s" Right but these are often different servers that can't communicate with each other ↺

  17. moparisthebest

    Well maybe not can't but don't currently :)

  18. singpolyma

    Well they *have* to communicate with each other a little bit due to the tightly coupled way http upload is specified

  19. moparisthebest

    No, they don't at all

  20. singpolyma

    I agree it would be nice if they didn't have to but I don't think you can implement current spec without it

  21. moparisthebest

    It's been implemented like this from day 1 :/

  22. moparisthebest

    singpolyma: https://hg.prosody.im/prosody-modules/rev/c2cf5b40b66d 2016, external http server with no communication

  23. singpolyma

    Hmm, I guess one could call that not communicating. But you could use that same strategy to communicate the expiry info without communicating

  24. Zash

    They're communicating via the URL stuffs

  25. singpolyma

    Indeed

  26. moparisthebest

    eh I wouldn't call that communicating but I can see where you are coming from