XSF Discussion - 2020-11-29


  1. jonas’

    Neustradamus, no, the editor is not going to fake documents in the attic, that ship has sailed

  2. Neustradamus

    I did not say fake documents, it must be validated by XSF, it is a real solution.

  3. jonas’

    congrats, larma :)

  4. jonas’

    (<https://www.heise.de/news/Corona-Warn-App-in-Kuerze-bei-F-Droid-verfuegbar-4973701.html> sorry, schtrudel)

  5. emus

    wow - wouldnt expect they provide it really as more or less FOSs

  6. jonas’

    they don’t

  7. jonas’

    f-droid forked it and ported it to the microG libraries larma seems to have massively contributed to make happen

  8. emus

    yep - great step larma

  9. emus

    > Also hat sich Marvin Wißfeld, der Autor des microG Frameworks, erneut hingesetzt – und in wenigen Wochen im Alleingang das geschafft, was den Großunternehmen SAP und DTAG trotz staatlicher Bezuschussung scheinbar nicht gelungen ist Nothing more to say

  10. Link Mauve

    Hi, in XEP-0167 there are various non-dynamic payload types which don’t have their clockrate specified (for instance G729, defined as 8000 Hz in RFC 3551, but it’s not the only one), yet other ones always get their clockrate specified.

  11. Link Mauve

    Does that mean each implementation should contain a mapping between these payload types and the defined clockrate in order to generate valid SDP?

  12. Link Mauve

    Every implementation I’ve interacted with always specifies the clockrate, but the examples in the XEP don’t.