vanitasvitaeFor the next issue: https://discourse.igniterealtime.org/t/jsxc-web-client-now-available-as-a-plugin-for-openfire/88467
emusPersonal reminder to add:
Linuxfr.org user Space_e_man proposed his short overview of [Quicksy the easy XMPP based libre instant messaging platform](https://linuxfr.org/users/space_e_man/journaux/quicksy-la-messagerie-instantanee-libre-basee-sur-xmpp-facile). While the article itself concentrates on the reasons why it should be prefered to other proprietary solutions, the comments of linuxfr.org users, as usual, bring a lot of various points of view, as well as alternatives.
> A new TURN server called [eturnal](https://eturnal.net) has been [published](https://www.process-one.net/blog/eturnal-v1-0-0-say-hello-to-a-new-stun-turn-server/). eturnal is a straightforward alternative to servers such as Coturn which can be used for offering STUN/TURN services to A/V clients using [external service discovery](https://xmpp.org/extensions/xep-0215.html).
wurstsalat: Is the XEP section done from your side?
Licaon_KterMonal 4.7 both iOS and macOS is live on App Store so the text can be changed a bit, I'll try a PR later.
emusLicaon_Kter: that would be nice. Maybe you can also summarize other new features, I think there is already an entry for monal
> Despite the small version number update, this is a large upgrade. Among the many changes in this release:
1.New title bar in chat
2.Show when user was last seen online (XEP-0319: Last User Interaction in Presence)
3.Show typing notification (XEP-0085: Chat State Notifications)
4.XMPP blocking (XEP-0191: Blocking Command)
5.Fixed ui glitch that shows incorrect unread mesages
6. Many other Ui and stability improvements
peetahemus: the linuxfr quickly overview is a news covered in last month newsletter
emuspeetah: ok thx
peetahis'nt a bridge like whatsxmpp considered as an xmpp client ?
emushmm, I think putting it into others is the best category. I dont see that this a client 🤔
peetahtechnically it is a client
peetahit takes a data sent by an XMPP server and process them or send data to the XMPP server
etapeetah, as the person who wrote it, it's definitely not a client
etawhatsapp is not an XMPP server
Licaon_Ktereta: not anymore?
peetaheta: I understood that it was a bridge between Whatsapp web and and XMPP server : am I wrong ?✎
peetaheta: I understood that it was a bridge between Whatsapp web and an XMPP server : am I wrong ? ✏
emuseta: What else is whatsapp in you describtion
SouLA bridge is not a client
peetahin my understanding, a client is a something talking to a server, hence a bridge is a client. Please, explain where I'm mistaking.
peetahcould someone with understanding of the XEP-0313 update review the last commit of my last PR so that I do not introduce inexact information ? thanks
emuseta, you said its not xmpp anymore. I was jsut interested what else it is in your view?
etapeetah, a client is designed to be used by a human
pep.a bot is a client
pep.Well a bot can be a client
etaemus, I'm not actually sure - I think it's xmpp with some space optimizations
pep.It can also be a component
etaemus, whatsxmpp does not speak the whatsapp protocol though, it speaks the whatsapp web protocol
pep.peetah, there's multiple ways to implement a bridge, generally it'll be either component or client (component being really close to a client but on the server and with a namespace for it to use)
peetahIn the PoV of the newsletter, I understand that it is not a client as end-users would understand it, but does it justify that whatsxmpp related news should be put in another section ✎
peetahIn the PoV of the newsletter, I understand that it is not a client as end-users would understand it, but does it justify that whatsxmpp related news should be put in another section ? ✏
emuspeetah, I don't think this is a bad thing, it just a category for things which is, like this software, between the lines
emusAre you still editing?
emusI want to do some edits as well
peetahnope, go for it
emusOk, I think if eta says its okay to put it in the Other section we can stick to it. Everyone interested will see it there. But thanks for your PR, will merge
emusHello everyone, the August PR is open for you contributions! https://github.com/xsf/xmpp.org/pull/756
emusLicaon, do you still want to add something for July?
Licaon_KterThe GSOC section is huge, and parts of it were covered before too, right?
emusYes, it is my intention to show the process
Licaon_KterUmm, I'm not against, just noticed it's so much bigger 😉
emusYes, I take the responsibility 🙁
emusI hope wurstsalat is not on holidays 🏖️ - otherwise I would be happy if someone may review the XEP section