XSF Discussion - 2017-10-31

  1. moparisthebest

    jonasw, fyi https://code.moparisthebest.com/moparisthebest/xmpp-echo-self

  2. SamWhited

    gogs looks nicer than I remember

  3. moparisthebest

    no it's not bad, I kind of wanted a 'de-facto' URL for my projects that I can guarantee will never change

  4. moparisthebest

    github seems unstoppable now, but so did sourceforge and google code etc etc :)

  5. Zash

    Having your nickname in the path seems kinda redundant tho :)

  6. moparisthebest

    unless I let other people use it, but agreed :)

  7. dwd

    I'm still amused by using XMPP URIs as XMLNS. But I can't persuade anyone to do that.

  8. SamWhited

    dwd: I hadn't seen that until you used it in an example yesterday, seems like a good idea though

  9. SamWhited

    If you have a few little personal extensions

  10. moparisthebest

    then if people want to know what it is they have to bug you

  11. moparisthebest

    vs opening a link in a browser

  12. Zash

    dwd: But, all our things that use xmpp:prosody.im .. :)

  13. dwd

    Zash, Really? Awesome.

  14. Zash

    dwd: Apart from unfinished and unpublished projects, there's this thing: https://modules.prosody.im/mod_host_status_heartbeat.html

  15. Zash

    xmlns = "xmpp:prosody.im/heartbeat"

  16. moparisthebest

    well I got the client-side component hacked in and running in this one nasty POC commit https://github.com/moparisthebest/Conversations/commit/3048d3aaa315343c72c4a16ec6b5e2d2e929cc47

  17. moparisthebest

    I can get SMS on all my xmpp clients now

  18. moparisthebest

    so this client-side component thing could fix other problems too, like, enable screen-scraping type gateways for when protocols are too terrible to implement (lync)