Good day.
I would want your advise concerning project Blasta, an annotation
system based on XMPP.
The project Blasta https://blasta.woodpeckersnest.eu/ is utilizing the
specification Atom Over XMPP, and has insentivise me to think of a new
XEP that be similar to XEP-0277 (Libervia) and XEP-0472 (Movim), which
is the same without the content field.
Yet the discussion to standartize bookmark structure at the buku project
https://github.com/jarun/buku/discussions/795 and the structure which is
used by the linkding bookmark project https://demo.linkding.link/bookmarks
which does include a content field with the markdown format, which is
what Movim does, has led me to think of supporting the field "content"
of Atom Syndication Format.
Further, the publishing project Postmill https://postmill.xyz/ works
very similarly to bookmarks and forum systems, so comments, which
are part of XEP-0277 (Libervia) and XEP-0472 (Movim) are also valid.
Hence, I think that Blasra needs to be compatible with XEP-0277
(Libervia) and XEP-0472 (Movim) albeit its main purpose is to manage
bookmarks.
Please write your thoughts about this matter.
Kind regards,
Schimon
Good day to one and all!
I have been contemplating the idea of utilizing PubSub as a platform to
synchronize browser bookmarks, history and tabs. See article "XMPP For
Browsers" at The XMPP Newsletter of November 2024.
I have received crucial criticism by the Pale Moon developers due to
neglegence of encryption. It is not in my intention to neglegence
encryption, yet I do not intend to add encryption before a working
prototype.
Schimon:
> > There is no storage encryption yet. I do not know whether it is
> > necessary
Moonchild:
> Unacceptable.
> Nobody but the end user should be able to access the stored data.
> Encryption is required, and encryption should be set up in such a way
> that nobody aside from the end user (not even the server admin) has
> access to this data. Storing everything in plaintext in an XMPP
> service instance is ridiculous.
That said, the owner of the server must not have any access to the data.
However, I am thinking of encrypting the data, yet I do not how to
implement such system which will be possible to decrypt only by the
owner of the data, and I also do not know how to handle a situation in
which an encryption key was lost.
Links:
https://forum.palemoon.org/viewtopic.php?t=31900https://portal.mozz.us/gemini/woodpeckersnest.space/~schapps/journal/2024-1…
gemini://woodpeckersnest.space/~schapps/journal/2024-11-28-xmpp-for-browsers.gmi
https://xmpp.org/2024/12/the-xmpp-newsletter-november-2024/
Happy new year!
Schimon
Hi,
as a member of the SCAM Team¹ I’m proud to announce that the 27th XMPP
Summit will take place on Thursday January 30th and Friday January
31st 2025 in Brussels, Belgium.
As usual we picked the two days before FOSDEM² takes place in the same city.
https://wiki.xmpp.org/web/Conferences/Summit_27
If you are planning on coming please sign up on the wiki. (We have
somewhat limited capacity)
If you are unsure if the Summit is right for you, I (not in my
capacity as a member of the SCAM team) wrote a short thread on
Mastodon describing what the Summit typically looks like:
https://gultsch.social/@daniel/113385481055735606
See you in Brussels!
cheers
Daniel
¹: Summits Conferences & Meetups Team https://xmpp.org/about/xsf/scam-team/
²: https://fosdem.org/2025/
This message constitutes notice of a Last Call for comments on
XEP-0421.
Title: Anonymous unique occupant identifiers for MUCs
Abstract:
This specification defines a method that allows clients to identify a
MUC participant across reconnects and renames. It thus prevents
impersonification of anonymous users.
URL: https://xmpp.org/extensions/xep-0421.html
This Last Call begins today and shall end at the close of business on
2025-01-06.
Please consider the following questions during this Last Call and send
your feedback to the standards(a)xmpp.org discussion list:
1. Is this specification needed to fill gaps in the XMPP protocol
stack or to clarify an existing protocol?
2. Does the specification solve the problem stated in the introduction
and requirements?
3. Do you plan to implement this specification in your code? If not,
why not?
4. Do you have any security concerns related to this specification?
5. Is the specification accurate and clearly written?
Your feedback is appreciated!
Hi all,
Further to the note in the LC thread on XEP-0424, I'd really like to have a
document (XEP, probably) that answers these questions:
What are the risks of choosing an stanza identifier that is not unique?
Does this still matter if the stanza identifier is unique to the session?
To the sending jid? To the bare jid of the sender?
What about missing off the stanza id attribute entirely?
What about MUC? PubSub? Etc?
If people have opinions, write away, and I'll volunteer to collate these
into a XEP (or, possibly, a patch against XEP-0359).
My reasoning is that we seem to vaguely know things can get Bad, but I for
one can't find where we've documented these Bad Things. I'd be delighted to
be corrected, as ever.
Dave.
Version 0.1.0 of XEP-0502 (MUC Activity Indicator) has been released.
Abstract:
This specification provides querying entities an approximate
indication of the level of activity in a given XEP-0045 Multi-User
Chat room.
Changelog:
Promoted to Experimental (XEP Editor: dg)
URL: https://xmpp.org/extensions/xep-0502.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
Version 0.2.0 of XEP-0501 (Pubsub Stories) has been released.
Abstract:
This specification defines a way of publishing Stories over XMPP.
Changelog:
Add pubsub#item_expire in the node configuration (tj)
URL: https://xmpp.org/extensions/xep-0501.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
I have setup the membership application Wiki page for the application
period Q1 2025.
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the Wiki:
https://wiki.xmpp.org/web/Membership_Applications_Q1_2025
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
https://wiki.xmpp.org/web/Sysops
Apply now!!!
Thanks,
Alex
Version 0.1.0 of XEP-0501 (Pubsub Stories) has been released.
Abstract:
This specification defines a way of publishing Stories over XMPP.
Changelog:
Promoted to Experimental (XEP Editor: dg)
URL: https://xmpp.org/extensions/xep-0501.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
