XSF logo XSF Communications Team - 2019-10-03


  1. afp has joined
  2. emus has joined
  3. emus has left
  4. afp has left
  5. afp has joined
  6. emus has joined
  7. emus has left
  8. emus has joined
  9. emus has left
  10. emus has joined
  11. winfried has left
  12. winfried has joined
  13. winfried has left
  14. winfried has joined
  15. winfried has left
  16. winfried has joined
  17. emus has left
  18. winfried has left
  19. winfried has joined
  20. winfried has left
  21. winfried has joined
  22. winfried has left
  23. winfried has joined
  24. winfried has left
  25. winfried has joined
  26. winfried has left
  27. winfried has joined
  28. winfried has left
  29. winfried has joined
  30. winfried has left
  31. emus has joined
  32. winfried has joined
  33. jcbrand has joined
  34. winfried has left
  35. winfried has joined
  36. winfried has left
  37. winfried has joined
  38. LNJ has joined
  39. winfried has left
  40. winfried has joined
  41. nyco of course
  42. nyco let's give it a try, that's my opinion, so how do we proceed if we reach a consensus
  43. nyco ?
  44. debacle has joined
  45. Martin What do you mean? Introduce a 'call for help' section in the wiki and see if it gets filled. Maybe send a message to some ml so devs get aware of it.
  46. nyco not only devs
  47. nyco who tweeted that? https://twitter.com/xmpp/status/1179671137506209792
  48. nyco that's cool and all, but some select few complain to see newsletter work priori to making it public, but it does not seem to work the other way around
  49. nyco I propose we co-write and co-schedule the tweets together
  50. nyco I repeat, the commTeam is not (yet) a team cooperation/collaboration needs continuous effort, but the outcome is far better
  51. Martin nyco: Maybe pep. as it is his blog.
  52. Martin Afaik
  53. SouL nyco, problem with twitter is many people have access to it, I think SCAM has access. So I'm guessing pep. or somebody in SCAM did it
  54. pep. Daniel and I did it
  55. pep. nyco: it's original content, not sure what's wrong with that
  56. Daniel has joined
  57. pep. It's not like we retwitted the same thing
  58. SouL pep., I think it is cool but he probably wanted to say to be in sync before tweeting, so everybody knows
  59. nyco nothing is wrong about OC, please re-read above I am suprised that it is not OK that I tweet, but it is ok for some other persons
  60. nyco if we are a team, then let's be a team
  61. MattJ pep. wasn't tweeting about the sprint over and over again
  62. nyco we opened up the process of the newsletter workflow, because people asked for it so be it it's better now, and keeps improving, thanks to collective intelligence let's do that as well for Twitter, please
  63. MattJ so I think that is the difference, not who or what is being tweeted
  64. MattJ But I agree, some policies clearly need documenting
  65. nyco like scheduling campaigns
  66. MattJ so that everyone agrees on what is acceptable and what is not, and what needs consensus and what does not
  67. nyco for consistency and coherence
  68. nyco and peer to peer trust
  69. debacle has left
  70. nyco well, I beg to differ for this particular tweet, as this points to a personal blog
  71. nyco I agree with the content though
  72. MattJ I don't see a problem with tweeting links to interesting XMPP articles - personal blogs or large organisations, as long as it is relevant
  73. nyco legitimacy
  74. nyco if it's coming from a community, it has higher image
  75. nyco anyway, please share the tweets drafts let's copywrite all together
  76. nyco for example, why the hashtag #Stockholm ? :)
  77. nyco and btw, blog post written and published, also tweeted, but still not in the newsletter: why?
  78. nyco now it is, you're welcome
  79. nyco "do what I tell you, but don't do as I do"
  80. nyco you all know this as community devs
  81. nyco this is no code, but same stuff
  82. nyco we should have fun doing all this, this must be exciting we have to combine our strengths, for the better good of the community, and it shining bright outside
  83. nyco oh, btw, we are there again... there is nothing wrong with repetition if as a Twitter user, this is not your habit, then so be it, please unfollow, we don't need you, thanks Twitter is a very specific platform, with with the good/best practices indeed in a blog, you don't repeat posts in LinkedIn, you don't double-post on email, you don't twice the same content just paraphrased but on Twitter you just do because that's how Twitter works it is a overly-massive continuous, high-speed flow so you post twice or three times the same content
  84. nyco https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/SD63vZk61AgQv7aQp5AjSX6jlAWLfTB8dN7ZMO9x/Capture_d_e_cran_2019-10-03_a__13.59.16.png
  85. nyco https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/4NmNT1e3g7AL2fsR1RDUP4QV4jFeDkEf6e9Ew2g3/Capture_d_e_cran_2019-10-03_a__13.59.51.png
  86. nyco https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/hzizwv62849PCqEcsdwXzRKZnbvDXquD9MyJI1CY/Capture_d_e_cran_2019-10-03_a__13.59.58.png
  87. pep. > nyco> and btw, blog post written and published, also tweeted, but still not in the newsletter: why? I still have a month for that
  88. nyco done
  89. nyco you're welcome
  90. nyco I mean it is not consistent
  91. pep. nyco: I'm not sure what you're getting hot about. Also I don't have time to fight back right now sorry
  92. nyco it is exactly NOT about fight
  93. nyco just complainers doing exactly what they complain about from others
  94. pep. I agree about getting some kind of policy up and running
  95. nyco Good.
  96. nyco So, policy
  97. nyco let's share idea, co-construct the scheduling of Twitter content
  98. nyco because the current process of the newsletter is clearly documented, and feedback is taken into account
  99. pep. This article has nothing to do with the newsletter, yet
  100. nyco I'd say, let someone come up with a tweet idea, let that person propose some content (copy-writing), let that person share it with the commTeam, let that person schedule the tweet to the next day if people of the commTeam react and provide feedback (when time allows), then let's adapt if people of the commTeam do not react, then the tweets is scheduled anyway obviously, we trust each other we are each one of us benevolent
  101. nyco now, it is is in the next newsletter, unless we reach a consensus not to include it
  102. nyco so for the tweet contributor, we have one lead, showing example
  103. nyco again, a tweet is better when composed of text, link, hashtag, image
  104. nyco that's for OC
  105. nyco for curation, the "tweet with comment" can't be scheduled, afaik
  106. nyco I have worked in teams producing content for social media, I am confident we can create a real, cool, fun space for collab here
  107. nyco I speak for myself, but I never tweet immediately on @xmpp, I always schedule tweet, so the team can view it
  108. pep. And you bark intensively when we ask why you're retweeting the same thing and tweet nonetheless :x
  109. pep. That's my own opinion
  110. Martin BTW, you got a new newsletter subscriber after I shared it to twtxt. IMHO as xmpp community you should also support some decentralised stuff like twtxt/mastodon/whatever 😃
  111. winfried has left
  112. winfried has joined
  113. pep. Martin: agreed
  114. nyco saiyng some barks, when you bark yourself? not a good example
  115. nyco yep, Mastodon, please someone do it
  116. nyco do we have the LinkedIn page back?
  117. Martin I'm always annoyed by the amount of twitter stuff shared in mucs as it sometimes forces you to three times reloading the website till it shows the content. They bully people not using a client.
  118. nyco let's just make the commTeam a team
  119. nyco pep, seems like you don't read, or do not listen, or just don't care repeating the way on Twitter, you are not the target, please unfollow, and don't bark again
  120. pep. I am exactly the target
  121. nyco the goal of using Twitter is to reach out talking to internal members, that's done over our mailing list
  122. Martin I am only active in twtxt, as I said I shared the newsletter and will continue. I don't know if you want to set it up for the xsf as it is the smallest microvolt niche I guess.
  123. Martin I am only active in twtxt, as I said I shared the newsletter and will continue. I don't know if you want to set it up for the xsf as it is the smallest microblog niche I guess.
  124. nyco that is what you assume, you are not the target on Twitter pep
  125. pep. You can't market a protocol to users, at least not the way you're doing it, I'm not sure who else you're targeting
  126. nyco what in "reach out" don't you understand... "out"? that out of our current, present, inner circle you are already informed
  127. nyco so many issues, errors, wrong assumptions
  128. pep. As a developer, I am the target
  129. winfried has left
  130. winfried has joined
  131. emus has left
  132. Daniel > who tweeted that? https://twitter.com/xmpp/status/1179671137506209792 I tweeted that on behalf of SCAM. The Stockholm Meetup was a scam event. The tweet has been reviewed by two members of SCAM. The blog post itself was run by multiple participants of the Meetup. Including again two members of SCAM
  133. nyco > You can't market a protocol to users it is not just about the protocol, it is not just about users > at least not the way you're doing it do you think you hold The Ultimate Truth? I am re-using good and best practices, by experts that you are not, and you showed up to not know what you are talking about > I'm not sure who else you're targeting not sure yet either, let' have a conversation about that... let's try: developers, users, decision makers, policy makers? what else can you think of?
  134. nyco thx Daniel for clarifying
  135. emus has joined
  136. Daniel > who tweeted that? https://twitter.com/xmpp/status/1179671137506209792 I tweeted that on behalf of SCAM. The Stockholm sprint was a scam event. The tweet has been reviewed by two members of SCAM. The blog post itself was run by multiple participants of the sprint. Including again two members of SCAM
  137. nyco again pep: don't fight, just help, go in the same direction don't complain, just please feedback benevolently
  138. nyco we're not benevolent here
  139. nyco it's a constant fight, a big mess
  140. nyco we're a sum of individuals with differing agendas
  141. nyco can we sync at least a bit, make some effort ?
  142. emus > let's give it a try, that's my opinion, so how do we proceed if we reach a consensus > ? I think the best way is maybe to specifically go to developers or server maintainers. explain them the idea, and then put it in the next newsletter + first a small description of the idea
  143. nyco many have asked me to open up the newsletter process, which I did, still lots of improvements to come
  144. nyco emus good idea, can you please lead this
  145. nyco ?
  146. emus nyco: ok
  147. pep. I still wonder how many people need to ask you why you retweet things before we do something about it.
  148. nyco see this example? don't complain about this idea just feedback share concerns build solutions but don't block someone's initiative that's quite villain, low level
  149. pep. I also don't think "impressions" is the right metrics
  150. nyco that is wrong
  151. nyco and metrics are not only about impressions
  152. pep. Maybe you can explain why
  153. nyco why would you focus on that?
  154. emus > I also don't think "impressions" is the right metrics are we talking about my call thing, or something else?
  155. pep. emus: nope
  156. emus ok
  157. nyco I have already explained, many times, happy to do it again when you are mentally available and open minded about it
  158. nyco > I still wonder how many people need to ask you why you retweet things before we do something about it. retweet what? what you talking about?
  159. pep. Ok I think I'll give up for today and try another day. This discussion is only getting worse
  160. nyco I don't retweet on behalf of @xmpp, are you freely accusing me publicly ?
  161. nyco getting worse thanks to you pep
  162. nyco just be positive
  163. nyco it's not you job nor expertise obvioulsy
  164. emus > I don't retweet on behalf of @xmpp, are you freely accusing me publicly ? > getting worse thanks to you pep > just be positive > it's not you job nor expertise obvioulsy Guys, whats going on with you.... chill down
  165. nyco impressions help you have the "brand" exposed in many screens
  166. nyco does not mean people see it, right
  167. nyco > Guys, whats going on with you.... chill down I'd love that, but the tone is wrong, always has been, does not seem to improve
  168. nyco leaving the chat does not help
  169. nyco when I post metrics, it is not just the impressions
  170. nyco see what I have analysed about the engagement, and what it means
  171. nyco but what ever the numbers, the ratios, the growths... we are just not there, 1.5k followers we are just not seen
  172. emus > but what ever the numbers, the ratios, the growths... we are just not there, 1.5k followers we are just not seen let me help you a bit but I dont see any reason for accusation, in no direction. but I`m here only since a few days
  173. Daniel > but what ever the numbers, the ratios, the growths... we are just not there, 1.5k followers we are just not seen> if as > if as Twitter user, this is not your habit, then so be it, please unfollow, we don't need you, thanks Those statements seem to contradict each other. But I'm not comm...
  174. nyco pffff... muahahaa
  175. nyco please explain
  176. nyco anyway, I don't see individuals retweet @xmpp content very much
  177. MattJ "we need growth" is the opposite sentiment to "unfollow us, we don't need you"
  178. Daniel As a member of SCAM I target mostly tech people. I have some interesting in keeping a few of them
  179. Daniel If comm wants growth that's fine. But please not at all cost
  180. nyco don't look for what's wrong in statements, you will always find things like anyone can do for each other that is malevolent rather seek what's meant in that one unfollower is ok, growth is not about have one more followers, but many time, continuoulsy
  181. MattJ 1+1+1+1+1+... == many
  182. nyco if commTeam wants growth, well I'm not sure we align around that
  183. nyco keeping the techies in the loop, that's sound cool to me but also not at the cost of other targets, assuming we have more, which has not been clarified
  184. nyco MattJ what's your point? I mean if we lose 5 members, I'm fine with that but if we manage to pass the 10k followers over time (in two or three years), I'd be glad
  185. nyco that needs a continuous effort, and a single person cannot hold the burden alone, that's why teaming is better
  186. nyco I raise the question: SCAM and commTeam what are the common stuff? what are the differences? => one thing in common is we are using the @xmpp Twitter account I'd say Twitter is comm, it is about pushing info
  187. Daniel If those five followers that you are willing to loose are the target audience of SCAM we do have a little bit of a conflict of interest here.
  188. Daniel Not saying you should stop
  189. Daniel But please do keep scam interests in mind
  190. nyco lose, not loose I am not willing to lose them, never said that, never wrote that, never intended that I say it's ok to lose 5 if we get others 100 back
  191. arnaudj has left
  192. nyco SCAM and commTeam have the same interests, techies are definitely a target group, not one objects to this known, obvious fact
  193. MattJ Then we should tweet a broad range of stuff that is relevant to all the different types of people we want to attract
  194. nyco yes
  195. nyco and how do we handle that?
  196. nyco I call a meeting
  197. nyco we should progress slowly but surely
  198. nyco if techies is the target group we start with, then let's continue provide content for them, that's called nurturing
  199. nyco we have very few OC, many curation
  200. nyco that's the 99% of the newsletter and our @xmpp account
  201. Daniel nyco: you said multiple times that you don't care about the techies that get annoyed by repeating content. But I'm going to assume that you didn't mean what you said. In that case everything is fine and we don't need to continue the debate
  202. nyco we can definitely do OC, like once in a month a blog post, that's quite achievable
  203. nyco Daniel still shutting me down abruptly like that, I'm fed up with explaining and justifying over again we are dealing with 5 persons max here... will we really care about 5 dudes?
  204. MattJ Yes, if they are potential attendees at a sprint (which is composed of <10 people usually)
  205. Daniel > Yes, if they are potential attendees at a sprint (which is composed of <10 people usually) That
  206. emus omg guys, this is a newsletter AND twitter... there is always infornation people are not interested in.... please stop fight so harsh (counts for both of you)
  207. nyco no, you don't have to use Twitter for those persons you use different channels to reach them, "probably" XMPP
  208. nyco MattJ and Daniel and pep. : do we agree as commTeam, SCAM and XSF members that we should reach out? that we should open up not only to techies? like users and decision makers for example?
  209. nyco I want that as a proof: the landing page for users that has been started at the latest XMPP sprint in Stockholm
  210. Martin FYI, I am no dev, maybe a techie (I am operating my own xmppd) and I am always interested to read stuff like sprint reports to see what might come soon. Even if I don't understand all details. Otherwise I agree with emus. The discussion is too heated up. Both parties should pause, reflect and try to put themselves in the others shoes and come back later. You're in the same boat and want roughly the same although it might differ in some details.
  211. Martin Also here are people from different countries/cultures talking in english which is not the mother tongue for most of us. So it's easy to sound more harsh then intended or take something as offense which wasn't meant to be one.
  212. winfried has left
  213. winfried has joined
  214. arnaudj has joined
  215. nyco you're right Martin
  216. pep. nyco: as I said above, as a developer, not especially xmpp, I count myself as a target, and it's relevant for scam. So yes I care if we lose this kind of followers.
  217. pep. Also, you seem to be confused about your target(s), maybe it would be good to define them before spamming twitter with the same repeated content
  218. pep. I'm happy to help
  219. nyco no, you're not helping: I have asked many times who you think are the targets, I'll wait (and you're not in the commTeam, but we'll listen)
  220. pep. I'm obviously not saying I don't care about users, after all it's why I'm doing all I'm doing
  221. nyco ah, good
  222. nyco so what type of users?
  223. pep. I don't think @xmpp is for users though.
  224. nyco (there, we finally start to co-construct)
  225. pep. Here, I said it again
  226. nyco noted, as it was years ago
  227. pep. Well, users, of the protocol :)
  228. nyco so what type of users?
  229. pep. Developers.
  230. nyco so, trying to follow you and translate/paraphrase: protocol users are techies?
  231. nyco ok, so we don't move, we don't reach out to different populations?
  232. pep. Don't make me say what you're trying to say, get to the point
  233. nyco that's exactly what I'm doing, you might not get it
  234. nyco so please?
  235. nyco no meta-discussion :)
  236. nyco @xmpp's target is only developers and techies to you pep ?
  237. pep. That's not what I'm saying, please read again. You talk about not leaving other targets aside but you don't seem to have any
  238. nyco please explain again
  239. nyco do not assume
  240. nyco no meta-discussion
  241. nyco I've said targets I have proposed, happy to repeat: users, decision makers, policy makers
  242. pep. Explain what
  243. nyco no meta discussion
  244. nyco please explain your proposed targets for @xmpp
  245. pep. I am proposing that we keep developers as a target
  246. pep. Additionally to those you added, if you like
  247. pep. And that requires not getting them to leave
  248. nyco good, understood, at last you seem to be clear, thanks
  249. nyco we keep developers, I agree
  250. nyco consensus on that, the two of us
  251. nyco more targets: it is not if *I* like, I'd prefer the XSF to agree first, that means the commTeam comes up with the new targets and content for them that may mean proposing this to the Board
  252. nyco when you send content on a given channel for two different targets, you lose some of both when you have more than three targets, you lose potential for each that's the way
  253. nyco for now, we have only two channels: Twitter and the newsletter
  254. pep. And I'd rather prioritize developers for the time being
  255. nyco we cannot profile the newsletter subscribers, because Tinyletter does not provide that data
  256. nyco I'd rather not
  257. nyco devs are not paying nor funding anything decision makers do
  258. nyco so we can add more channels as we progress
  259. nyco like Mastodon...
  260. nyco if someone takes care of it
  261. nyco I won't
  262. pep. Devs are the ones making this protocol move forward
  263. nyco like LinkedIn, we we can get it back
  264. pep. I don't see any decision makers in sprints
  265. nyco decision makers are funding for it
  266. nyco :) sprint are for developers, of course decision makers are not there
  267. nyco please organise a meetup or some kind of event for them, and then promote it, they will come like on any digital channel
  268. winfried has left
  269. winfried has joined
  270. pep. Maybe decision makers should be kept to LinkedIn. And I'm happy to delay as long as we don't have access to it
  271. pep. (Delay targeting them*)
  272. emus I personally suggest to treat xmpp not as a dev only thing. I get the point, but already stateing this will exclude thinking past the horizon. as there is nothing which reviews the jabber network (with all parties), xmpp might give some credits to every side in general. and I wouldnt suggest to create more newsletters
  273. nyco decision makers are on LinkedIn, right developers may not be on LinkedIn, or don't use it that way, right but Twitter is not reserved for devs, decision makers are also there, as well as users, and policy makers so ou account should not frighten them
  274. nyco btw, to @all, what are your opinions on the new section about specs? we've done that for the last two months
  275. MattJ I like it
  276. nyco so, links are not clickable this month, so they won't be counted on the click ratio
  277. nyco this month, we have a normal size newsletter, last month we had a double newsletter (July, August) so our click ratio was lower 1. because of the long size 2. because of the new sections
  278. nyco my assumptions
  279. nyco at the end of the month, we'll have enough data to inspect and analyse, and probably draw some conclusions and/or new hypothesis
  280. nyco Daniel pep. SouL Martin emus > btw, to @all, what are your opinions on the new section about specs? > we've done that for the last two months I believe no XMPP clients implements the "@all" thingy so sorry for this...
  281. Martin I liked it but I was irritated why the URLs were no links.
  282. nyco ok, thx
  283. pep. I'm personally ok with that section. But that might not be the case for all of our targets
  284. pep. We should probably ask them
  285. nyco thx for your taste what makes you assume that for our targets,
  286. nyco ?
  287. pep. I don't assume anything, I don't know
  288. pep. Hence my suggestion to ask
  289. nyco a survey is definitely to be designed and scheduled some time in Nov or Dec
  290. pep. K
  291. nyco though, I'd prefer to make it generic on the newsletter, not only on one section
  292. nyco two days after sending it, we have: (no definitive numbers, still a rough precision that is worth observing)
  293. emus > Daniel pep. SouL Martin emus > I believe no XMPP clients implements the "@all" thingy > so sorry for this... I actually can only say that I like it (maybe conpress it a bit) but as I am not a developer it is not my section of interest. still I read it and think it is good for devs.
  294. nyco thx!
  295. nyco https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/aMYY9vsuNFzXKYeLIl06t7yhLLKsajzDpQR25nDC/Capture_d_e_cran_2019-10-03_a__16.22.53.png
  296. nyco the trends are the same, months after months:
  297. nyco subscribers count growth
  298. nyco open rate and click rate decrease
  299. emus I migjt also think it is very good for non devs. Because people see that there is something like a standards process and yes, xmpp is a protocol of arrangeing interoperability in a decentral network. even if I dont know the details I understand something of the background. I think its very good now 😂
  300. nyco as we grow in subscribers, the rates will decrease I guess it is due to the success of a newsletter attracting people: some are just not interested, they just subscribe because it's cool, but actually never open it
  301. nyco how to improve open rate? I think by "optimising" the title/subject and the first sentences (previewed part in some email clients)
  302. emus nyco: Do you also track the RS. feed
  303. emus RSS
  304. nyco that's why I asked for help this month
  305. nyco no, the RSS feed and the website are not tracked, afaik
  306. nyco Tinyletter track very few things
  307. emus I will send you the translations this weekend. I just hear fron a few germans they dont read it because its english, what I personally didnt understood
  308. emus ok, I wouldnt go so harsh for the numbers now
  309. nyco so on the newsletter title/subject, I suggest we try to drop "The" in "The XMPP Newsletter" probably even shorted like "XMPP: ..."
  310. emus I would put a logo to the top or so:
  311. nyco for the click rate, we may improve the working and which words are clickable
  312. nyco yes, images were inserted in this month newsletter for the first time only two images for now
  313. emus https://xmpp-share.mailbox.org/upload/mailbox.org/cf9b0bfb1642efa7ddd6e519af9dbaa1ccd6e42c/1S0Ay601kIb106gLUN39hL6X73HFyxw92cWl7i7A/RGfOTf53Taal2Y3O0VbLWA.jpg
  314. emus Looks a bit unrelated
  315. nyco a logo at the top, I am not sure I'd rather have text at the top, for email previews
  316. emus Then make the first sentence a more header thing
  317. nyco agree
  318. nyco I'll need your help at the end of the month
  319. emus no rush
  320. emus https://xmpp-share.mailbox.org/upload/mailbox.org/cf9b0bfb1642efa7ddd6e519af9dbaa1ccd6e42c/CE78igNYpeSA5mgIzEdsdGwX0nMpCNGKTJVvuD71/DjiXnLGpRDyXJTSu3M3bZA.jpg
  321. emus the earlier ones had a logo
  322. emus I think its proper like this
  323. nyco oops...
  324. nyco emus > I will send you the translations this weekend. I just hear fron a few germans they dont read it because its english, what I personally didnt understood that's awesome! thanks a lot!
  325. arnaudj has left
  326. nyco where will you publish it? on jabber.de?
  327. emus nyco: JabberES people says their website is shit, so I ask the jabber.de people to publish the spanish translations as well. once there is a proper website we can migrate
  328. emus ja, jabber.de
  329. arnaudj has joined
  330. emus yes*
  331. nyco that's gonna be Spaman or Gernish :)
  332. Martin > the trends are the same, months after months: > subscribers count growth > open rate and click rate decrease I block tracking pixels and my browser removes tracking parameters so I will be invisible. 😃
  333. emus has left
  334. emus has joined
  335. emus Sí sí
  336. emus ja ja
  337. emus nyco: thunderbird also by default restricts remote content
  338. arnaudj has left
  339. arnaudj has joined
  340. Daniel has left
  341. Daniel has joined
  342. Daniel I think we are just on a agree to disagree on how to run Twitter. That's nothing personal. That's just how it is
  343. arnaudj has left
  344. emus I for long time watched the xmpp newsletter. was wondering why they barely post stuff. now I saw like many posts which was more that the previous year (feeling). but was okay As i see the discussing, I recommend going away from reposting eveything and rather create own posts. but not all with pictures.
  345. emus about the "Promoting open communication." If the communication should rather be a dev only thing, that doesnt really suit anymore. Still, I like the expression!
  346. emus nyco: the newsletter needs reCaptcha?
  347. emus nyco: we might should mention that there is also the rss feed. people were asking about this
  348. arnaudj has joined
  349. emus Ah sorry, didnt saw the rss comes via planet jabber to me
  350. pep. emus: what's the context for recaptcha?
  351. emus I think they have a problem with google and dont see the necessarity to use Google there
  352. emus I personally would also prefer to use something apart from google. but, I see the problem
  353. emus I mean, mailchimp is also not the datas paradise I guess
  354. emus 😃
  355. emus One thing xmpp could communicate aswell in the twitter feed, or also the newsletters are the different mucs you have on different topics. that would be self-generated content
  356. arnaudj has left
  357. arnaudj has joined
  358. winfried has left
  359. winfried has joined
  360. winfried has left
  361. winfried has joined
  362. winfried has left
  363. winfried has joined
  364. winfried has left
  365. winfried has joined
  366. emus has left
  367. winfried has left
  368. winfried has joined
  369. debacle has joined
  370. emus has joined
  371. nyco > I think we are just on a agree to disagree on how to run Twitter. That's nothing personal. That's just how it is it is not about agreeing, it is about doing the right thing, experimenting, progressing I don't tell you how you should use Twitter, but there are many things to say...
  372. nyco > nyco: the newsletter needs reCaptcha? I don't think so
  373. nyco > nyco: we might should mention that there is also the rss feed. people were asking about this oh really? some people still care? I'm glad so yes, maybe a reminder can help you create an entry in the draft newsletter, or link collection?
  374. arnaudj has left
  375. emus https://xmpp-share.mailbox.org/upload/mailbox.org/cf9b0bfb1642efa7ddd6e519af9dbaa1ccd6e42c/psqT9wXPfvffblQTTDQn0cxwCTlnGakNCcBiaQYc/LDckTiYPT2KXDHzc7OuJbw.jpg
  376. arnaudj has joined
  377. nyco > As i see the discussing, I recommend going away from reposting eveything and rather create own posts. but not all with pictures. yes, retweeting is not optimal at all retweeting with comments is much better posting OC is definitely something good, but we don't have writers what we can do is schedule tweets, pointing to our pages I proposed that a few days ago
  378. emus but schedule it on a quarterly basis I suggest
  379. nyco that a huge task, and I don't believe free scheduling tools allow that many tweets
  380. nyco I suggest we start to work in a team, we produce like 4 tweets, that we schedule every Wednesday, for example
  381. afp has left
  382. afp has joined
  383. emus But I think that is too often. I would reduce it a bit. If people see a new twitter account they read the last tweets anyway if they are interested. Would risk spamming the feed. But you might better know
  384. emus nyco what do you think about the captcha
  385. nyco what's the pb with the captcha?
  386. emus Google
  387. emus trakcing
  388. emus One question: MongooseIM 3.4.1 is out now with an important security upgrade, fixing a vulnerability that allowed any logged in user to crash the node with malicious stanza on certain (but popular) configurations.
  389. emus The link you provided there is: https://www.erlang-solutions.com/resources/download.html
  390. emus Is that intentional?
  391. nyco well, Tinyletter tracks emails as well
  392. nyco yes, why?
  393. nyco their download page lists everything they provide
  394. emus Maybe we should look for a different provider
  395. emus People in XMPP care a lot more about privacy I think
  396. pep. > nyco> it is not about agreeing, it is about doing the right thing Then yes it is about agreeing on what the right thing is..
  397. emus Technical question: Message Fastening is NOT about acceleration, but stability? or hardening? Anyone of the germans can help to translate?
  398. Daniel emus, can i get the full sentence?
  399. emus Proposed Message Fastening Abstract: This specification defines a way for payloads on a message to be marked as being logically fastened to a previous message. URL: https://xmpp.org/extensions/inbox/fasten.html
  400. emus I made to: Zusammenfassung: Diese Spezifikation definiert eine Möglichkeit, wie Nutzlasten in einer Nachricht als logisch an einer vorherigen Nachricht geknüpft werden können.
  401. emus an eine*
  402. Daniel that sounds alright
  403. emus cool - then the first translation to German is done! 🙂 Good thing on the German unification day 😀
  404. emus fyi nyco
  405. emus looking forward to drop it that it can go online. if some wants to cross-check feel free
  406. emus no, please give me a hint so I can send it to you
  407. emus Y ahora yo trabajo por la translation en espanol! xD no worries, I will let cross check a native speaker. She hates XMPP (Monal 🤡️) but is happy to help
  408. jcbrand has left
  409. emus Daniel, can then translate Message Fastening still with "Nachrichtenbeschleuning" ? (Keine Sorge kein Arbeitsbegriff nur einmal in Klammern für den unbedarften Leser)
  410. emus And the first spanish draft is done 🙂
  411. winfried has left
  412. winfried has joined
  413. ldkjgoiwe has joined
  414. debacle has left
  415. ldkjgoiwe > can then translate Message Fastening still with "Nachrichtenbeschleuning" emus, it's fastening as in attaching, not as accelerating. so "anheften", not "beschleunigen".
  416. LNJ has left
  417. ldkjgoiwe And you probably want to go with "Inhalte einer Nachricht" instead of "Nutzlasten einer Nachricht" for the summary 😉
  418. afp has left
  419. emus yes, wasnt sure about payload
  420. emus thanks
  421. emus has left