XSF Discussion - 2023-03-01


  1. Daniel

    jcbrand: what are your plans for 425 moderation? Are you going to remove the usage of the 'retraced' element or are you going to keep it but just not in way that is compatible with 424 for the receiver?

  2. Guus

    Hmm.. Is it allowed for IQ stanzas of type 'error' to contain child elements other than the child element from the associated request, and an `error` element?

  3. jonas’

    no

  4. jonas’

    IQs are rather strict in that way

  5. jcbrand

    Daniel: I plan on incorporating the feedback soon. I'm a bit behind at work and need to focus on other things first. I lean towards the latter. Keeping the `retracted` element. I also think I'm going to put the `retracted` element back inside the `moderated` element. The reason being that I still believe moderation can be more general purpose than just retractions. For example in some cases one might want to allow moderators to edit messages, then you'd put a `replace` element inside `moderated` instead of `retracted`.

  6. jcbrand

    Or perhaps like the Twitter feature where they allow community-generated explanations/context to be added to certain controversial tweets.

  7. jcbrand

    You could perhaps attach something like that to a message.

  8. jcbrand

    Although I'm not sure that's a moderation use-case

  9. Daniel

    Retracted inside moderated sounds better to me than the other way round

  10. jcbrand

    Yes, I agree. I switched it around because I though (based on feedback) that we could get XEP-0424 support like that

  11. jcbrand

    Yes, I agree. I switched it around because I though (based on feedback) that we could get XEP-0424 compatibility like that

  12. jcbrand

    I no longer think trying to get XEP-424 compatibility is desirable

  13. jcbrand

    And doesn't look like it's feasible either

  14. Daniel

    OK. Yes I agree. And no rush. I just wanted to clarify that this PR is still being worked upon because I think the editor almost merged it yesterday

  15. Daniel

    Maybe put a draft label on it?

  16. jcbrand

    Well it has a `needs council` badge I see, although I don't think that's necessary since it's experimental

  17. Daniel

    It's not Experimental it's proposed. But council will vote on getting it back to experimental today

  18. jcbrand

    ok

  19. Daniel

    But after our vote today editor _could_ merge it hence the suggestion of flagging it as draft or something

  20. jcbrand

    Maybe I can make the changes today already but I don't want to promise it now

  21. jcbrand

    Yeah I marked both my PRs as draft now

  22. Kev

    If I've not screwed up too badly, my triage wrapper script should ignore draft PRs, so thanks.

  23. jcbrand

    Kev: If it's not like that already, I'd suggest that you also don't automatically merge PRs with unresolved threads.

  24. jcbrand

    Might mean that people need to be nagged to resolve their threads, but it prevents something that's still being discussed from being merged

  25. Kev

    Discussions shouldn't be happening on GitHub anyway, so that shouldn't be an issue.

  26. Link Mauve

    I think it was here that we talked about moderation and stuff; a reasonable improvement to clients would be to automatically hide all previous messages sent by a banned participant, while still letting the user display the messages somehow if they want to know the reason of the ban after the fact.

  27. Link Mauve

    Perhaps we should draft a new modernxmpp page about moderation workflows?

  28. Daniel

    I don't think all banning should lead to messages not showing

  29. Daniel

    Moderation and banning are two separate things

  30. Link Mauve

    Daniel, the only case I remember for users being banned without having sent bad messages were when they reconnect in loop and flood a room with presences.

  31. Link Mauve

    And in this case they get unbanned after they’ve fixed their setup.

  32. Link Mauve

    We don’t have any event for unbanning someone though. :/

  33. Link Mauve

    In every other case, the ban was in direct reaction to something they sent, so requiring a click to display the messages seems ok to me.

  34. Menel

    But if you moderate every message they send, how far do you go back? Really every message?

  35. jonas’

    I read that as a purely client side thing

  36. jonas’

    so it could be done ad-hoc when building the view

  37. Zash

    The moderate command of the clix tool basically takes a time range along with optional nickname and body contents to match on

  38. pep.

    Link Mauve: xmpp:abuse@joinjabber.org?join for moderation and more

  39. Link Mauve

    I don’t currently have the bandwidth to join many more rooms.

  40. Link Mauve

    But thanks for the invitation. :)

  41. jonas’

    :-O

  42. pep.

    Link Mauve not joining one more room :o

  43. pep.

    Anyway, that was also to say we're thinking about it at joinjabber

  44. Link Mauve

    pep., currently. :p

  45. jcbrand

    Kev: technical feedback on the diff can and does happen on GitHub

  46. ralphm

    Link Mauve: are you on 75 baud? Also, that should still be ok?

  47. ralphm

    :-D

  48. Link Mauve

    :D

  49. Link Mauve

    The mental bandwidth, should I add. :p

  50. jonas’

    ralphm, I'm fairly certain that 75 baud is not sufficient anymore for the amount of MUCs Link Mauve is in.

  51. Link Mauve

    People don’t write that much actually. :p

  52. jonas’

    Link Mauve, chat states, presence.

  53. Link Mauve

    This would all eventually balance, during night time for instance.

  54. jonas’

    you sure about that? 75 baud is really not a lot

  55. Link Mauve

    I have disabled systemd’s bandwidth accountance so I don’t have data any more. :(

  56. jonas’

    the text-only content of programming@ since 2018 is approximately 0.079 bytes/second

  57. jonas’

    (a bit less, because this includes the full timestamp, which is generally not included in messages)

  58. jonas’

    so 75 baud, with *only* text, would suffice for approximately 1000 MUCs

  59. ralphm

    Indeed

  60. ralphm

    Link Mauve: have a look at Netdata (shameless plug)

  61. ralphm

    (for your systemd metrics)

  62. MattJ

    Careful. Does it run on a Nintendo Switch?

  63. MattJ

    You don't know what you're getting into :P

  64. ralphm

    MattJ: likely yes. We have ARM support.

  65. edhelas

    Time to have XMPP Brotli compression XEP then

  66. Peter Waher

    (EXI is more efficient for XML I believe, BTW)

  67. Zash

    But with other complications

  68. Peter Waher

    (Thanks to complications & problems, we have work… What if there were no complications to solve?) Side-note about EXI: It’s ment for resource contrained networks, and is estimated to compress XML approx. 7 times more efficiently than LZW. Can be combined with UDP transport and DTLS, and thus create interesting alternatives to the more thightly coupled CoAP and LWM2M protocols. (Also permit huge amounts of connected resource-constrained devices to the same machine, as UDP & DTLS do not require socket connections.)

  69. Link Mauve

    Hey, I don’t run my infra on any Nintendo hardware atm!

  70. Link Mauve

    The last time I did that was like a decade ago, on a Wii.

  71. Link Mauve

    Ah no, I also had my Switch as a build server for my phone and other servers for a while, until I found out about Oracle Cloud.

  72. Link Mauve

    Might migrate some bits and pieces of that infra to a dedicated Wii U someday.

  73. jonas’

    Peter Waher, are there any free and open source libraries these days for EXI?

  74. jonas’

    which aren't java

  75. Link Mauve

    But I still have a few things to fix in the kernel before I can use it properly, for instance hardware AES-CBC-128 support is still not merged in the kernel.

  76. Link Mauve

    (It also isn’t really used any more…)

  77. Link Mauve

    ralphm, that looks cool, thanks!

  78. Daniel

    Peter Waher: do you have experience in running xmpp over exi?

  79. emus

    Hi, I wanted to discuss if we should consider Google Season of Docs for writing XEPs? https://developers.google.com/season-of-docs/docs/get-started?hl=en

  80. Kev

    I've pondered it in the past, but came to the conclusion that we're not in a position we could provide a sensible framework for it for XEPs. More likely would be providing user docs for individual projects, I think. (Others may disagree)

  81. Peter Waher

    Daniel: Yes, we have experience with XMPP & EXI.

  82. emus

    Kev: So you believe it only works for software?

  83. Peter Waher

    Jonas: Not that i’m aware. I personally work with a commercial broker and libraries, in C#.

  84. Peter Waher

    Jonas: Not that I’m aware. I personally work with a commercial broker and libraries, in C#.

  85. Peter Waher

    I mentored a master student to create a plugin to OpenFire a while back (Java), but not sure what happened to that project.

  86. Peter Waher

    Jonas: Not that I’m aware of. I personally work with a commercial broker and libraries, in C# (many of which are open source however, yet commercial for commercial use).

  87. Kev

    > : So you believe it only works for software? No, I don't think that's true. I don't think the XSF is is a position that it could sensibly support work on XEPs under that program - but I accept others might disagree. I think that the amount of domain-specific knowledge needed to work on XEPs in a non-trivial way is more than one would reasonably be aquired for the program.

  88. emus

    Kev: but they say you need to have a past of technical writing, so it can be one that has the domain knowledge already

  89. emus

    maybe lets ask in a differnet way: Can anybody think of how it could work in xmpp?

  90. Kev

    I meant XMPP domain knowledge, rather than writing knowledge - but I'm happy to accept that I'm being pessimistic about it if someone else can make it work :)

  91. emus

    Hmm not sure if I understand your concern. Maybe elaborate where the idea does not conform with us? > Google Season of Docs supports documentation in open source by: > Providing funds to open source organizations to use for documentation projects > Providing guides and support for open source organizations to help them understand their documentation needs > Collecting data from open source organizations to better understand documentation impact > Publishing case studies from open source organizations to share best practices > Google Season of Docs seeks to empower open source organizations to understand their documentation needs, to create documentation to fill those needs, to measure the effect and impact of their documentation, and, in the spirit of open source, share what they've learned to help guide other projects. Google Season of Docs seeks to bring more technical writers into open source through funding their work with open source projects and organizations.

  92. emus

    I see development of xeps also as a project or a type of documentation personally

  93. emus

    and btw, in google summer of code we may get 500-1500$ - in GSoD its 5.000-10.000$ - but I hope this is see as a positive side effect, not the intention^^

  94. pep.

    What would Documentation on XEPs consist of exactly?

  95. emus

    Anyway, even if it does not apply for XSF, it may apply for xmpp projects, here is some inspirational list from 2022: https://developers.google.com/season-of-docs/docs/2022/participants?hl=en

  96. pep.

    Does that require global understanding of XMPP or is it a set of tasks that can be achieved only by reading single documents at a time

  97. emus

    pep.: Id specificly know, what would we like to see would be a goof start?

  98. emus

    pep.: Id specificly know, what would we like to see would be a good start?

  99. emus

    > pep.: > 2023-03-01 03:18 (GMT+01:00) > Does that require global understanding of XMPP or is it a set of tasks that can be achieved only by reading single documents at a time I assume it certainly does, but the participation expects you have a writing history. its nor like GSoC for OS newcomers

  100. pep.

    It's not about the "Writing history" that I'm worried but about the "Knowing XMPP"

  101. emus

    pep.: but I assume we habe about 50 people here knowing xmpp, right?

  102. pep.

    « Hey, go read 6120/6121/6122 and then 0045, 0060, and also XX, YY, ZZ. Then we can talk"

  103. pep.

    emus, but this Google thing is only for students no?

  104. emus

    pep.: no, I dont think so

  105. emus

    Do you have technical writing skills and experience? Google Season of Docs is not intended to teach basic technical writing skills. Are you self-motivated and organized? Do you have time to participate during the six months of the program? Project sizes vary, but range from a commitment of 5-30 hours per week during the program. Are you interested in gaining experience working in open source? Are you willing to devote time to learning a project’s processes and community norms? Are you willing to work with the organization administrator to refine their project proposals, develop timelines, assess and compile metrics, and help the organization as a whole understand the value of technical writing?

  106. emus

    > - Do you have technical writing skills and experience? Google Season of Docs is not intended to teach basic technical writing skills. Are you self-motivated and organized? > - Do you have time to participate during the six months of the program? Project sizes vary, but range from a commitment of 5-30 hours per week during the program. > - Are you interested in gaining experience working in open source? Are you willing to devote time to learning a project’s processes and community norms? > - Are you willing to work with the organization administrator to refine their project proposals, develop timelines, assess and compile metrics, and help the organization as a whole understand the value of technical writing?

  107. emus

    That is something to discuss > You should also meet the program eligibility requirements, including being able to create an Open Collective account. Please note that you must be legally able to receive funds for work performed in your place of residence. The Season of Docs program administrators are unable to provide tax advice or answer questions about your work eligibility.

  108. pep.

    Ok, then it's already slightly more into XSF's reach. Maybe send a call on Mastodon and all to see if anybody is interested?

  109. pep.

    But what would that mean exactly, to work on specs as a technical writer

  110. emus

    > pep.: > 2023-03-01 03:24 (GMT+01:00) > Ok, then it's already slightly more into XSF's reach. Maybe send a call on Mastodon and all to see if anybody is interested? Letz maybe first start via members@

  111. pep.

    I'm not in there, you go ahead :)

  112. emus

    ok I see

  113. emus

    > But what would that mean exactly, to work on specs as a technical writer I cannot tell, everyone is invited to state their propsoals :)

  114. pep.

    I'm not 100% sure I know what a technical writer does.. Apart from writing technical things :/

  115. pep.

    Writer with a tech background? Documentation? That's not too reductive?

  116. singpolyma

    "writing technical things" is pretty much it yeah. It's a broad field :)

  117. singpolyma

    Writer who is able to talk to devs or other tech people to find out how things work then write coherently about that

  118. emus

    > singpolyma: > 2023-03-01 03:30 (GMT+01:00) > Writer who is able to talk to devs or other tech people to find out how things work then write coherently about that And I think thats what every author of a xep od tech doc is

  119. singpolyma

    Sure, it's what every xep is trying to be anyway. A description of how we tech works

  120. singpolyma

    Sure, it's what every xep is trying to be anyway. A description of how some tech works

  121. pep.

    Of how some tech should work*, or how we think it works (for "informational")

  122. pep.

    So.. a sponsored tech writer would.. do what? Improve existing spec's wording? Or rather think about how tings can be improved to present the information?

  123. pep.

    Is tagging also part of the thing? Now that it's possible to tag specs

  124. emus

    As said - no clue, we can come up with proposals

  125. pep.

    I guess for the presenting part it's more up to a designer

  126. pep.

    "we" who

  127. pep.

    If we have no clue

  128. emus

    maybe lets look at the summit 23 topics

  129. emus

    maybe lets look at the summit 25 (2023) topics

  130. emus

    Any can help me finding access to the twitterdeck legacy view? I didnt manage to find how I made it last time

  131. jcbrand

    emus: Do you mean https://tweetdeck.twitter.com/ ?

  132. emus

    jcbrand: yes, but its legacy view

  133. nicola

    @emus if I understand your point and it can be helpful, you can search via Nitter here: https://nitter.nicfab.eu/

  134. emus

    nicola: I don't fully get what you are suggesting?

  135. nicola

    @emus I understand that you need to search something on Twitter

  136. nicola

    If you need to search your tweets, you can use Nitter and put your account. The platform will list all of your tweets

  137. emus

    nicola: ok thats great - however, I actually need to send a remote tweet via tweetdeck

  138. emus

    but it does not work with the new interface anymore

  139. emus

    https://jabbers.one:5281/upload/hDg4xgTXY7g9hjhyfE9CsYQL/20230301_162054670_9856..jpg

  140. emus

    found it

  141. Wojtek

    @emus can't you switch to the old one?

  142. emus

    thanks for the hnt

  143. emus

    hint

  144. emus

    Wojtek: ^

  145. Wojtek

    yeah, saw your image after hitting send :-)

  146. Kev

    Sorry emus, I wasn't saying that the XSF isn't eligible (I haven't checked), but that I don't think we'd be able to manage it. But, again, maybe I'm wrong.

  147. emus

    Kev: But what does it require? I can do the application. what we cannot manage about writing xeps? 😅

  148. emus

    its not about getting new people onboard

  149. Kev

    I don't think we're in a position to suitably guide people on writing XEPs - what needs to go in them, etc. Maybe I'm wrong

  150. Zash

    Didn't we find that ChatGPT could do this for us? :)

  151. emus

    But how did we produce more than 400 xeps?

  152. emus

    noone was guided to write a xep really so far?

  153. Link Mauve

    emus, I think the main reason people write XEPs is to fix something lacking in the protocol, because they have an interest in there.

  154. Link Mauve

    Getting someone to write XEPs because they get paid to write documents, would require to describe a bunch of features we do want and teaching them all about XMPP, or something like that.

  155. Link Mauve

    Unless you manage to find someone already involved, that’s unlikely to be a good match imo.

  156. pep.

    I guess the whole point of this wouldn't be to write XEPs then but to improve things about them

  157. Kev

    I know I've got a couple of XEPs that I ended up needing to write after the Summit - but trying to tell someone else what needed to be in them would undoubtedly be significantly more work for me than writing them myself (and I'm struggling to find the time just to write them).

  158. pep.

    Because yeah I agree, it'd be weird to have someone write specs just because

  159. emus

    Well, leave the money point out and ask: - is there work most agreed or wish to be done? I remember there were 6-8 tech topics at the wall at the summit - Is anyone out there being capable to do without requirement to do so or was planned anyway? I mean, how many development things do we have in the pipeline? If we have absolutely no clue we might use the same track to study and outline this as GSoD seem to pay also for evaluation studies 😃 (Besides when people write xeps in their spare time why not use this chance when other got paid for it via their employer?)

  160. pep.

    If you want to get down in "what is important and what isn't, at the XSF" territory (to know where to spend the money) I think you're in for a lot of fun :)

  161. emus

    Well, I see there are many topics with different views, but I bet there is also a lot common sense, too --> thats what I look for

  162. Fishbowler

    Ooh, just spotted that Community > Service Providers on XMPP.org links to a dead page on xmpp.work

  163. Zash

    PR welcome ;)

  164. Fishbowler

    Definitely will, if nobody else gets there first.

  165. Zash

    Thanks!

  166. Fishbowler

    Is that the right place for "Service Providers"?

  167. Zash

    I think that section is just gone now

  168. Fishbowler

    It's more "if you're a service provider, you might get work here" :)

  169. Zash

    xmpp.work recently changed hands and got some updates

  170. Zash

    IIRC it was like listing XMPP consultants (like me!) and similar service providers

  171. Fishbowler

    PR is up

  172. emus

    Thanks!

  173. emus

    I posted about each project: Monal: https://twitter.com/xmpp/status/1631049299646709761 https://fosstodon.org/@xmpp/109950233974730123 Dino: https://twitter.com/xmpp/status/1631050907897978880 https://fosstodon.org/@xmpp/109950259189174110 Moxxy: https://fosstodon.org/@xmpp/109950267243301508 https://twitter.com/xmpp/status/1631051422597799936

  174. deimos

    would there be any interest in working with hello tux to get decent shirts with the xmpp logo? https://www.hellotux.com/

  175. deimos

    i've been working with hellotux to improve their shirt quality and/or do custom embroidered shirts on shirts I send them