[Falkon] [Bug 505362] Extending Falkon capabilities with XMPP, SamePlace, and WebXDC
Schimon Jehudah
bugzilla_noreply at kde.org
Mon Jun 9 16:56:17 BST 2025
https://bugs.kde.org/show_bug.cgi?id=505362
--- Comment #9 from Schimon Jehudah <sch at fedora.email> ---
XMPP is not a niche. XMPP is the internet which big organizations try to
conceal in favour of a perverted HTTP which is saturated with ECMAScript (i.e.
JavaScript) to harvest our information, and our kids information, and is
designed to keep us frivolously engaged.
However, XMPP is similar to HTTP, just better, and it is easier for you, me,
and even out kids and grandmother to utilize XMPP, provided that we have the
proper means to engage with XMPP.
>From an article of Mr. Jack Moffitt.
> How do we survive without them? Here are some of the ways:
> Web frameworks may offer a lot of functionality, but XMPP has a excellent, diverse set of extensions that offer a higher layer to application developers. Web frameworks are still essentially stuck on basic protocol plus ad-hoc commands. XMPP provides pubsub, presence, discovery, and much more.
> Communication is done via XMPP through Strophe instead of polling a database or using work queues. This is a step up in efficiency.
> Configuration is stored in pubsub nodes instead of relational databases. One awesome consequence of this is that all subscribers get instant notification of configuration changes, sort of like a broadcast SIGHUP.
Front end apps, administrative code, and internal utilities are all just
JavaScript. This makes them trivial to develop and test locally, and we don’t
need any special deployment code.
> The whole system is more decoupled because there is no middle interfacing layer. The backend speaks XMPP, the frontend speaks XMPP, and they both use standard XMPP layer protocols to do work.
Source: https://metajack.im/2009/01/25/we-dont-need-no-stinkin-web-frameworks/
Involving XMPP in our software, not for messaging, but for storage of
information is something that we all need, from publishing of information, to
push notifications, to synchronizing of data.
For what it's worth, XMPP can be even utilized to synchronize Linux
installations.
I did just that for a VPS company, of which I was a legal counsel of, after the
manager feared of utilizing BitTorrent and IPFS for that purpose.
XMPP more than messaging. Forget the messaging part of it, and concentrate on
the stractural sense of XMPP.
Hence, please consider to consider XMPP as a keyword.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list