profile
viewpoint

kutsuru/MitsakeCorrectru 2

Spell Checker in C++

Ppjet6/atomtopubsub 0

A little client that parse Atom feeds and send them on XMPP Pubsub Nodes

Ppjet6/awesome-xmpp 0

A curated list of amazingly awesome XMPP server, clients, libraries, resources - with focus on security.

Ppjet6/blitzloop 0

Open source karaoke software

Ppjet6/busybox 0

Prometheus Busybox Docker base images

Ppjet6/cedar 0

Framework for building functional-reactive applications

Ppjet6/chef 0

A systems integration framework, built to bring the benefits of configuration management to your entire infrastructure.

Ppjet6/codimd-cli 0

A tiny CLI for CodiMD

Ppjet6/converse.js 0

Web-based XMPP/Jabber chat client written in JavaScript

Ppjet6/debos 0

Debian OS builder

pull request commentxsf/xeps

XEP-0277: pubsub#type MUST be set in bare PubSub

On 2020/09/30, Peter Saint-Andre wrote:

Here the payload is Atom, right?

I'm saying I wouldn't define the payload as Atom, no.

From xsf@ yesterday:

Say I publish my new spec also using pubsub + atom with different but very specific rules about how to handle Atom stuff that is also different from how the Atom spec defines things, I can, right? It's my spec [and I'm telling others about it] Now I don't want microblog clients coming on my stuff and doing non-compliant things (as per my spec) And I guess they also wouldn't want that from me

-- Maxime “pep” Buquet

Ppjet6

comment created time in a month

pull request commentxsf/xeps

XEP-0277: pubsub#type MUST be set in bare PubSub

On 2020/09/30, Peter Saint-Andre wrote:

Hmm. We might need to clarify what pubsub#type means, then. I agree that the processing rules for data coming from urn:xmpp:microblog:0 nodes might be special, but the payload format is indeed http://www.w3.org/2005/Atom. It seems to me that the processing rules depend on the "node type" not the "payload type" in this instance. (And yes, "type" is one of the most overloaded terms in computing!)

Thinking about it, (and that's how I justified this to myself originally), I'm enclined to say http://www.w3.org/2005/Atom is not the payload type here but urn:xmpp:microblog:0 is (or whatever NS used to designate microblog).

I don't think "payload format" is defined to designate the serialization format, (which would be XML and not Atom), and I'd rather have microblog say nodes contain Atom items.

What would be the point of having Atom defined as a payload type exactly?

Tools wanting to read Atom in a somewhat generic fashion can still go through nodes and see that there are Atom items in there (shaped respecting the microblog rules, which the tool might know about or not).

-- Maxime “pep” Buquet

Ppjet6

comment created time in a month

pull request commentxsf/xeps

XEP-0277: pubsub#type MUST be set in bare PubSub

With this said, I'd consider microblog a payload type anyway, it's not like Atom was a serialization format, there are rules associated with it. Microblog is mandating behaviour in the node (where I'm setting pubsub#type) and in each individual atom payload (required Atom XML elements, etc.)

Ppjet6

comment created time in a month

pull request commentxsf/xeps

XEP-0277: pubsub#type MUST be set in bare PubSub

Yes the payload type is actually http://www.w3.org/2005/Atom but rules applied to that payload are those of microblog.

Maybe I'm just assuming something on pubsub#type that isn't true, it's not that well defined in 0060 after all. The only normative text there is about it is “Payload type”. We can also find in examples:

  • “Specify the type of payload data to be provided at this node”
  • “The type of node data, usually specified by the namespace of the payload (if any)”

There is no such thing as “just” pubsub + atom, is what I'm trying to point out here, and I'd like to have a place to express this.

Ppjet6

comment created time in a month

push eventPpjet6/xeps

Maxime “pep” Buquet

commit sha ba753b8082efa27250d562860852fda8677c1415

XEP-0277: Add a note about pubsub#type in the node configuration section Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

view details

push time in a month

PR opened xsf/xmpp.org

Newsletter: Link to JoinXMPP to help find people to take over

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+1 -0

0 comment

1 changed file

pr created time in a month

create barnchPpjet6/xmpp.org

branch : news-joinxmpp

created branch time in a month

PR opened xsf/schemas

Https urls

Fixes #6. Thanks @onacit for the report.

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+154 -154

0 comment

115 changed files

pr created time in a month

create barnchPpjet6/xsf-schemas

branch : https-urls

created branch time in a month

pull request commentxsf/xeps

XEP-0060: Add integer-or-max datatype to use with Data Forms Validation

Standards thread: https://mail.jabber.org/pipermail/standards/2020-September/037753.html

Ppjet6

comment created time in a month

push eventPpjet6/xeps

Maxime “pep” Buquet

commit sha 02b21cedfd2953795e90f15b349a0df4a9898b99

XEP-0060: Add integer-or-max datatype to use with Data Forms Validation Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

view details

push time in a month

push eventPpjet6/xeps

Maxime “pep” Buquet

commit sha 1051b5e8b5a5a831a007456367af9ac17d14235e

XEP-0060: Add integer-or-max datatype to use with Data Forms Validation Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

view details

push time in a month

push eventPpjet6/xeps

Maxime “pep” Buquet

commit sha 243d8a561ddb32bf53d0f09f0a020248e518d39d

XEP-0060: Add integer-or-max datatype to use with Data Forms Validation Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

view details

push time in a month

push eventPpjet6/xeps

Maxime “pep” Buquet

commit sha a440eb734555efdc0b092f80140f8adb83268c87

XEP-0060: Add integer-or-max datatype to use with Data Forms Validation Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

view details

push time in a month

PR opened xsf/xeps

XEP-0060: Add integer-or-max datatype to use with Data Forms Validation Needs Council

I'd like to have council's opinion on how to handle this.

Seems like the datatype requires a prefix, where to define it? where do I put things so that they end up in https://xmpp.org/registrar/xdv-prefixes.html ? In 0060 as well?

Should this type be its own spec? And then referred to and given meaning in 0060?

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+27 -0

0 comment

1 changed file

pr created time in a month

push eventPpjet6/xeps

Maxime “pep” Buquet

commit sha dcbb771034bff841fd4f8ad4fb68173f93e9c414

XEP-0060: Add integer-or-max datatype to use with Data Forms Validation Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

view details

push time in a month

create barnchPpjet6/xeps

branch : 0060-integer-or-max-type

created branch time in a month

PR opened xsf/xeps

XEP-0277: Add atom:generator element in examples to encourage its use Editorial Changes Needs Version Block Ready To Merge

As the title says, I'd like to encourage the use of the atom:generator element, at least make developers aware of it. Just adding it there as we all know copying examples is how things work. No need for keywords I think.

I haven't added a version block in case #986 would get in at the same time.

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+2 -0

0 comment

1 changed file

pr created time in a month

push eventPpjet6/xeps

Maxime “pep” Buquet

commit sha bb021c4d08201b1275ddfe8ca410aa0e2154faa9

XEP-0277: Add atom:generator element in examples to encourage its use Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

view details

push time in a month

create barnchPpjet6/xeps

branch : 0277-generator-ex

created branch time in a month

PR opened xsf/xeps

XEP-0277: pubsub#type MUST be set in bare PubSub Needs Council

Not entirely sure it's valid as is (breaking change?). I'd appreciate council guidance.

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+7 -1

0 comment

1 changed file

pr created time in a month

push eventPpjet6/xeps

Maxime “pep” Buquet

commit sha 84a7c925ce12d50be321d109e1a2ab7b085d40eb

XEP-0277: pubsub#type MUST be set in bare PubSub Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

view details

push time in a month

push eventPpjet6/xeps

Maxime “pep” Buquet

commit sha cdae40ae5a0fbc707abbfb6f6b6c38c99252294f

XEP-0277: pubsub#type SHOULD be set in bare PubSub Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

view details

push time in a month

create barnchPpjet6/xeps

branch : 0277-pubsub-type

created branch time in a month

delete branch Ppjet6/xeps

delete branch : 0060-set-max-max-items

delete time in a month

PR closed xsf/xeps

XEP-0060: Change placeholder to set server maximum for pubsub#max_items Needs Council

Standards thread: https://mail.jabber.org/pipermail/standards/2020-September/037743.html

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+15 -9

1 comment

1 changed file

Ppjet6

pr closed time in a month

pull request commentxsf/xeps

XEP-0060: Change placeholder to set server maximum for pubsub#max_items

Retracting the PR. See standards thread.

Ppjet6

comment created time in a month

PR opened xsf/xeps

XEP-0060: Change placeholder to set server maximum for pubsub#max_items Needs Council

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+15 -9

0 comment

1 changed file

pr created time in a month

create barnchPpjet6/xeps

branch : 0060-set-max-max-items

created branch time in a month

PR opened modernxmpp/modernxmpp

MUC: typo

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+4 -3

0 comment

1 changed file

pr created time in a month

create barnchPpjet6/modernxmpp

branch : muc-typo

created branch time in a month

PR opened modernxmpp/modernxmpp

Groupchats clarifications

As discussed in the channel. Clarifications on the use of realjids and how to detect groupchats.

I can split if necessary

+12 -0

0 comment

1 changed file

pr created time in a month

create barnchPpjet6/modernxmpp

branch : groupchats-clarifications

created branch time in a month

fork Ppjet6/modernxmpp

Modern XMPP usage guide for client and library developers

https://docs.modernxmpp.org/

fork in a month

PR merged xsf/xeps

XEP-0060: Add missing querytype 'retrieve' action and 'item' key to registry submission Needs Council

As discussed in this mailing list thread the PubSub specification is missing registry entries for the 'retrieve' action and the 'item' key. This PR adds those to the query type registry submission.

+21 -1

1 comment

1 changed file

vanitasvitae

pr closed time in 2 months

PR merged xsf/xeps

XEP-0060: Fix minor typo in form example Editorial Changes Needs Version Block Ready To Merge
+1 -1

1 comment

1 changed file

lnjX

pr closed time in 2 months

push eventxsf/xeps

Linus Jahn

commit sha 4675f44a13b971dd885dea26b707af3f785d9e25

XEP-0060: Fix minor typo in form example

view details

Jonas Schäfer

commit sha f33f609b1b0e6a44d35e84a1e5ff13a95368f74c

XEP-0060: re-add revision block

view details

Paul Schaub

commit sha 387cc1e151fff03909079d75cd41fcac68e0b529

XEP-0060: Add missing querytype 'retrieve' action and 'item' key to registry submission

view details

Jonas Schäfer

commit sha ed292eab5df186c2c5d8bfdd7ec2a213316cc6a0

Merge branch 'feature/xep-0060-2' into premerge

view details

Jonas Schäfer

commit sha 96df927111b42aab80d3e5ec8f99ebd600542cf3

Accept inbox/xep-mam-prefs.xml as XEP-0441

view details

Jonas Schäfer

commit sha fc8526d02b14d6d9b704410de50f5f84f4d27fdc

Accept inbox/xep-pubsub-mam.xml as XEP-0442

view details

Jonas Schäfer

commit sha 023964abe6e66c33b8702cd142ca432dfca54c6d

Merge branch 'premerge' into 'main' Premerge See merge request xsf/xeps!16

view details

Maxime “pep” Buquet

commit sha c7166ab94a3ca34f00a38b8f0c0ac48d47f0fb15

Merge remote-tracking branch 'gitlab/main' into master

view details

push time in 2 months

PR opened xsf/xmpp.org

Link mission statement from “The XSF” page

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+13 -11

0 comment

1 changed file

pr created time in 2 months

create barnchPpjet6/xmpp.org

branch : link-mission

created branch time in 2 months

PR opened xsf/xmpp.org

extensions: Fix JS file url -- thanks Tedd

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+1 -1

0 comment

1 changed file

pr created time in 2 months

pull request commentxsf/xmpp.org

Renew profanity

See also https://xmpp.org/2017/03/new-xmpp-software-listing-rules/

Ppjet6

comment created time in 2 months

pull request commentxsf/xmpp.org

Renew profanity

It makes you appear in the following list: https://xmpp.org/software/clients.html

Ppjet6

comment created time in 2 months

PR opened xsf/xmpp.org

Renew profanity

@jubalh, can I get an ACK please :)

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchPpjet6/xmpp.org

branch : renew-profanity

created branch time in 2 months

PR opened xsf/xmpp.org

Renew Dino

@fiaxh, @mar-v-in, can I get an ACK plz? :)

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchPpjet6/xmpp.org

branch : renew-dino

created branch time in 2 months

PR opened xsf/xmpp.org

Renew Movim

@edhelas, can I get an ACK plz? :)

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchPpjet6/xmpp.org

branch : renew-movim

created branch time in 2 months

PR opened xsf/xmpp.org

Renew Conversations

@iNPUTmice, can I get an ACK please? :)

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+1 -1

0 comment

1 changed file

pr created time in 2 months

create barnchPpjet6/xmpp.org

branch : renew-conversations

created branch time in 2 months

PR opened xsf/xmpp.org

Update poezio and slix last_renewed date

Signed-off-by: Maxime “pep” Buquet pep@bouah.net

+2 -2

0 comment

2 changed files

pr created time in 2 months

create barnchPpjet6/xmpp.org

branch : update-poezio-slix

created branch time in 2 months

push eventPpjet6/hugo-theme-kiss

Maxime “pep” Buquet

commit sha 0fdde2560e0d655878c457311276a156320b411c

Add markdown format Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

view details

push time in 3 months

more