my concerns. The "linking" case is not handled at
all, and the "collections"/"leaf" distinction makes it hard to use as an
afterthought for things like XEP-0277 blogs/comments (how would you apply
XEP-0248 here in a simple way and without breaking backward comp
em). With an explicit flag,
we don't have any problem.
Regards,
Goffi
signature.asc
Description: This is a digitally signed message part.
___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-le...@xmpp.org
to collaborate on this or a
similar specification, please reach out so we can avoid duplicating efforts.
Currently, I'm quite busy and won't be able to submit an updated proposal
within the next several weeks.
Thanks.
Regards,
Goffi
signature.asc
Descri
Le mercredi 21 août 2024, 17:17:47 UTC+2 Goffi a écrit :
> Le mardi 20 août 2024, 18:35:52 UTC+2 Stephen Paul Weber a écrit :
> > >I have already indicated my willingness
> > >to evolve the proposal towards a single Jingle session
> >
> > Once it uses a single
a server component based on Galène.
Regards,
Goffi
signature.asc
Description: This is a digitally signed message part.
___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-le...@xmpp.org
r note, while I understand that both the editor and council have
heavy workloads, it would be beneficial if the results of council votes were
shared on this list, possibly accompanied by relevant log excerpts.
Thank you once again.
Best regards,
Goffi
signature.asc
Description: This is a d
one is acceptable as starting point,
and is very easy to implement.
On another topic, several people have informed me that there was a copy/paste
error with the "overview" section appearing twice, it would be nice to remove
one of them but I don't want to modify the protoXEP
sable with both, as both use cases
are legitimate, in which case it could be describing the data to share and the
fields to use in a Data Form, which could then be used either as attachment in
a blog item (e.g. with XEP-0470), or directly with XEP-0346.
Best,
Goffi
Le vendredi 7 juin 2024, 12:5
of (or
whatever name used for filtering.
Also, if several rules are allowed, we have to manage conflict: what if I have
something which tell me to notify me for a room on mobile, and just after
something telling me the opposite? I suppose that the latter one must be used,
but it should
comment. But this is not about this protoXEP, it's about PEP
native bookmarks which only accept so far.
Anyway it's a good start, and it's simple which is good.
Best,
Goffi
signature.asc
Description: This is a digitally signed message part.
_
y issue with OMEMO (and A/V).
For the wider community: please gather non working scenario, so we can work on
them.
Best,
Goffi
signature.asc
Description: This is a digitally signed message part.
___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-le...@xmpp.org
Hi Marvin,
Le mardi 4 juin 2024, 17:29:00 UTC+2 Marvin W a écrit :
> Hi Goffi,
>
> Thanks for your message.
>
> I know I'm not particularly good with words and my language sometimes
> tends to be perceived as aggressive or exclusive. I did not intend to
> attack or ins
Le mardi 4 juin 2024, 12:18:34 UTC+2 Marvin W a écrit :
> Of course there are three kinds:
> (a) Those that consider the protocol ready for use in production
> software and thus use in production software
> (b) Those that consider the protocol not ready for use in production
> software, but don't
l (my
client does it), and clients will eventually do so when the need arises. There
are already several clients implementing OMEMO:2.
> XSF can go as far and say "Client X is not compatible with XMPP as it
> implements a protocol that is still Experimental". We do
to developer how they should present
features, and to tell them (beside current indicators) what to implement or
not.
> 4. We should not have any bar for Experimental except for basics,
> because Experimental means nobody should implement it in production, so
> there is no harm in publ
le implement experimental specifications, they should be
prepared to update regularly.
Ultimately, the final decision on the relevance of a specification will be made
by implementers and users.
Best,
Goffi
signature.asc
Description: This is a digitally signed message part.
___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-le...@xmpp.org
kflow is for). I'm also worried about implementing stuff
based
on snippets scattered around the internet, or missing super interesting
features because they are not properly specified or I'm not aware of them.
I'm not sure what the best solution for this is, but I wanted to provide
for remote control, I want by design to keep
the desktop screen sharing separated, and under XEP-0167 (or any future
specialised XEP if proven better).
- If I can't find a good alternative, I'll evaluate the use of
instead of current CBOR based data, maybe in a separated XEP.
- I'll ev
Le lundi 27 mai 2024, 10:54:25 UTC+2 Goffi a écrit :
> And that makes sense: it's not the pointer coordinate that's important, but
> rather where the focus is. You can change focus with a keyboard, for
instance.
Correction here, after testing (I should have done it before
Le mercredi 22 mai 2024, 16:46:47 UTC+2 Marvin W a écrit :
> Hi Goffi,
Hi Marvin,
Seeing the proposition rejected is definitely disappointing, and I would like
to have a clear statement of the reason why the Council thinks this work is
"unacceptable".
For now, the biggest critic
Le mardi 21 mai 2024, 16:39:28 UTC+2 Marvin W a écrit :
> Hi Goffi,
>
> On Tue, 2024-05-21 at 12:47 +0200, Goffi wrote:
> > I know that, I've just ruled out using through the server
> > as it has
> > been proposed in another feedback.
>
> Why do you
Hi Marvin,
Le lundi 20 mai 2024, 22:48:42 UTC+2 Marvin W a écrit :
> Hi Goffi,
>
> See inline comments. Sorry for the wall of text and if it overlaps with
> one of the mails you wrote since I started writing this.
>
> On Mon, 2024-05-20 at 16:51 +0200, Goffi wrote:
> >
y presses during the event, which
are obtained through the `keyboard` device in the specification. Only the
necessary data are kept.
You are right that this should be explained in the specification. If the
protoXEP is accepted, I'll add a section to explain that.
I hope that I have helped
using other protocols. But XMPP itself could certainly be
used directly in many modern devices, potentially with some optimizations.
I hope that I have answered all your feedback.
Regards,
Goffi
signature.asc
Description: This is a digitally signed message part.
___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-le...@xmpp.org
, maybe it's just pubsub implementation thing, and a more general `read-
only` option to prevent accidental config change could be interesting. The
current behaviour with 2 rounds config change is already overriding stuff
anyway, so this question is probably out of topic for the change you'
7;s do some override, as long as nobody is deleting my
blog posts by setting `max_item=1` instead of `max` this way.
Best,
Goffi
Le mercredi 28 juin 2023, 13:26:02 CEST Matthew Wild a écrit :
> Hi folks,
>
> Pubsub's is an important part of the protocol, e.g.
> to ensure that
for attaching multiple files to (and pubsub).
A new version of XEP-0447 is to be expected at some point with those changes.
Regards,
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-uns
t rid of this restriction.
Le mardi 21 mars 2023, 11:44:13 CET Goffi a écrit :
> Hi,
>
> Libervia is currently implementing XEP-0447 instead of SIMS as it is
supposed
> to be a reiteration of XEP-0385. However, it can't currently handle multiple
> files in the same message be
but which one should we chose? I propose to
move on XEP-0447, transfer author from XEP-0385 there, and deprecate XEP-0385.
Thanks,
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
to
> create an implementation :)
For the record, I have already made an implementation in Libervia (along with
OpenPGP for XMPP Pubsub, and Pubsub Target Encryption). Normally the current
specification are complete enough.
Goffi
___
Standards maili
Hi Paul,
sorry I forgot to answer, I've got a lot on my minds these days…
Le mercredi 9 novembre 2022, 14:01:27 CET Paul Schaub a écrit :
> Hey!
>
> Thank you Goffi for creating this proposal. Cross-reading it, some
> points come to mind:
>
> In the glossary under &quo
Thanks for your message. I got it and it indeed a useful feature-but it needs
to specified in XEP-0060.
Kind Regards
Goffi
Le 5 novembre 2022 14:33:37 GMT+01:00, Maxime Buquet a écrit :
>On 2022/11/02, Goffi wrote:
>> 'pubsub#type' would be "http://www.w3.org/2005/At
I'd advise to define a pubsub#type that is actually
> 'urn:xmpp:microblog:0' (there
> https://xmpp.org/extensions/inbox/pubsub-social-feed.html#profile_microblog)
> and not 'http://www.w3.org/2005/Atom' then I know that the node is
> actually a bit more than &qu
60 (only seen in examples),
and it should get the namespace of the item payload, i.e. "http://www.w3.org/
2005/Atom" in our case, so you should use (create?) an other metadata field to
handle "profiles".
Also, your proposal is using verbatim stuff from XEP-0277, I believe that
original XEP-0277 authors should be quoted somewhere inside your specification.
King Regards
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
m not exactly sure
what is the best option here.
- what is this "Gallery profile" thing ? It looks like a terrible way to do
photo galleries, ignoring all the work done by stuff like XEP-0447. Please, I
see no good reason to have this.
- style remark: quotes (notably in
)
Hi Debacle,
I'm currently working on an other protoXEP that I should submit later today or
tomorrow to handle the signing case, and it will support signing both plain
text and e2ee items.
There is a passage in security notice highlighting this.
Cheers
Goffi
_
u for what you have done
so far and your responsiveness, it has been very much appreciated.
Regards
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
Le vendredi 30 septembre 2022, 13:35:17 CEST Maxime Buquet a écrit :
> Thanks Jonas!
>
> Thanks Goffi!
> I have skimmed over the spec, and here are a few comments that shouldn't
> pose any issue for the move to experimental.
Hi Pep,
>
> > § 5. Events Nodes
> >
events.html#extra) is for. We
just need to map explicitly iCal metadata to the propose data form field type.
Thus nothing is lost here
Thanks for the feedbacks, and I hope that my points make sense to everybody.
King regards
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
re voting I was criticised. Thus
I'm not sure if it's good to do it before council vote, but if you ask me, I
have nothing against it and can do it sure.
Regards
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listi
ch is used, and A doesn't
exist anymore).
Regards
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
Ps are in Draft
state", and indeed when you're not aware of the workflow, it seems like
nearly nothing is usable (that's still true with many XEPs used widely
which are in Experimental or Deferred state, but that's an other s
bt if the item is remaining, and client has to do an extra and
probably useless request each time.
Regarding the lack of feedback I suppose that all implementation in the
wild are removing all items, and if the PR is applied then letting 1
item should be reported as a bug IMO.
Regards
Le 2021-08-11 17:35, Jonas Schäfer a écrit :
Hi goffi,
Thanks for proposing this. The council has today vetoed the advancement
for
this ProtoXEP to Experimental, but I'd like to give you some feedback
because
I think the problem you're trying to address is real. The bottom of
e syntax doesn't prevent
to mention it and to explain how exactly the feature is attached (e.g.
what does it mean using Order-By with Pubsub, and how to use it).
I would love to see feedbacks here, I think that the problem we are
trying to solve is affecting a couple of XEPs and many peop
abstract is not the right one: it's "This
specification provides a way to indicate that a feature is implemented
for a specific namespace".
Thanks for the quick minutes even during summer.
Goffi
___
Standards mailing list
Info: https://mail.jab
mmunity agrees
to do this fix.
Thanks
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
policy
in those cases, and can be unblock the currently concerned PRs?
Thanks!
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
0413.html#disco
I've just published a new version of the XEP (with a namespace bump), I
think I've addressed all feedbacks (yours and older ones), I've added a
full Pubusb with RSM example and some direction for SQL based
implementations.
Let me know if you&#x
/xmpp.org/extensions/xep-0060.html#subscriber-retrieve-returnsome
)
Thanks for the feedbacks, I'll try to update it this week.
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
I'll
soon publish a blog post with more details, and of course I'll reach
standard@ in time to discuss that.
And yeah, this will open the doors to many, many interesting things.
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailma
elieve that it's a useful tool to have for any
XMPP
dev, admin, or even user.
That's it but there is more (see my blog for details). The project
website is
at https://salut-a-toi.org (the website will probably move to
libervia.org at
some point, but this address will still work)
ould like to be sure
that it is still happening.
Thanks!
Goffi
P.S.: this should be probably on summit@ mailing list, but the original
thread was here.
Le 2021-01-30 17:12, Tedd Sterr a écrit :
Due to forseen circumstances, this will be postponed until 20-21
February.
I was trying to fit it
. Other option would be of course
Jitsi Meet, depending of number of attendees.
I can write also a paragraph about what I'm working on, and would be
interested to do a short talk too.
Regards
Goffi
___
Standards mailing list
Info: https://mail.ja
Le 2020-05-25 15:01, Tedd Sterr a écrit :
But there is no way to know if the text is formatted or not, there
is no
marker, discovery, or anything to indicate that styling syntax is
used.
The assumption is that styling is always present and enabled, and so
it's always applied to all text -
s MUST be kept
Your feedback is appreciated!
Thanks for the work done, but I'm really concerned with this specific
extensions, and I think that a proper discovery/flagging mechanism would
be the bare minimum to make it usable (but even with that, I'm more in
favor of a proper sep
e the notes showed in hover
tooltips in the rendered XEP, that would avoid to go down and up just to
read them.
I hope this will be useful
Regards
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
" category, with at least XEP-0277. It's a
category that we are improving a lot, and a badge would help potential
user to see which client support that. Too late for 2019 suite, but
would be nice to think about it for 2020.
Thanks for the work to all people involved.
Regards
Goffi
Le 2019-03-29 18:24, Jonas Schäfer a écrit :
On Freitag, 22. März 2019 08:43:01 CET goffi wrote:
Hello,
about a year ago, Daniel's proposition to encrypt files with OMEMO has
been rejected (proposal:
https://xmpp.org/extensions/inbox/omemo-media-sharing.html, council
rejection:
if anybody is
working on some alternative (which would ideally work with OMEMO and
OX)?
Also note that at least Conversations and Gajim use this non standard
aesgcm scheme, which is causing compatibility issues for other clients.
thanks
Goffi
___
nce of the XEP. The ML discussion has shown that this is a
> hot and complex topic, and I'm interested in seeing how it develops.
>
>
>
> Georg
Thanks. I've promised an update but I'm currently overwhelmed with FOSDEM
preparation, so I'm post
e to see back to
experimental (in the case of experimental means "nobody cares", otherwise I
don't mind that XEPs are in Deferred state).
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
.
In the first case, maybe there should be a way to change/extend the authors
after some time (for instance edhelas or me could work on the XEP-0277).
For the later case, Deferred is a state that is OK for me, but I would not see
the XEPs being killed (it's usable and used), I'm letti
; Dave: +0 (reserve the right to change that while others are still on-list)
For the record, I've answered to the concerns raised by the council at
https://mail.jabber.org/pipermail/standards/2019-January/035646.html . I hope
this helps.
Thanks
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
Le dimanche 13 janvier 2019, 12:53:51 CET Evgeny a écrit :
> On Sun, Jan 13, 2019 at 2:40 PM, Goffi wrote:
> > Future XEPs may extend this, but in case where it's too complicated,
> > implementation has always the choice to not implement it, or to have
> > differe
Le dimanche 13 janvier 2019, 12:28:09 CET Evgeny a écrit :
> On Sun, Jan 13, 2019 at 2:16 PM, Goffi wrote:
> > For Pubsub services based on SQL or NoSQL databases, it should not be
> > too hard to implement as ordering is most of time a part of API.
>
> Note however, that
Le dimanche 13 janvier 2019, 12:24:45 CET Evgeny a écrit :
> On Sun, Jan 13, 2019 at 2:16 PM, Goffi wrote:
> > a XEP for XPATH like syntax
>
> And the server will process this XPATH query?
> Not sure if you're serious...
This is a future plan, not concerning the curren
ever you're using) on the new item when you have an ID conflict, before
destroying the old item, nothing fancy.
That's it, I hope I have convinced you. Anyway this is experimental, time will
show where it goes.
++
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
would need a simplied XPATH like syntax, so a other XEP for that.
If I can find some time today (I'm overwhelmed, so it's not sure at all), I'll
try to update the protoXEP with all the insightful feebacks I've had sor far.
Thank you all for those comments :)
++
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
Le lundi 7 janvier 2019, 21:00:42 CET Evgeny a écrit :
> On Mon, Jan 7, 2019 at 8:28 PM, Goffi wrote:
> > Are you talking about the fact that "date of modification" (as
> > defined in the protoXEP) could be out of sync between clusters?
>
> No, from the discus
s ordered, we end up with a simple list of items.
> - In contrast to what Philipp thinks, I think that using multiple
> elements (and having their relative order be significant) is fine; As goffi
> mentions, pubsub itself is a valid precedent for that, and I think even a
> XEP-0004 nee
Hi Evgeny,
Le lundi 7 janvier 2019, 09:30:26 CET Evgeny a écrit :
> On Mon, Jan 7, 2019 at 10:44 AM, Goffi wrote:
> > Is there any implementation in the wild which would have issue with
> > node order?
>
> Sure, any clustered database will have issues with
> su
his is such a difficult thing to do, but it doesn't seem needed.
Is there any implementation in the wild which would have issue with node order?
When you get the result of a pubsub get query, the order of items is also
significant.
++
Goffi
; Unsubscribe: standards-unsubscr...@xmpp.org
> ___
>
Just a precision because after talking on xsf@ it doesn't seem clear: the order
affect the whole archive, not just a result set, pretty much like ORDER BY in
SQL. I&#
dating an item.".
It seems logical to me too, but this is a problem in several use cases
(blogging, or experimental features I'm working on like tickets).
To fix this, I've just submitted a new XEP, "Order-By", that changes the
business logic. It should
gt; Unsubscribe: standards-unsubscr...@xmpp.org
> ___
>
Hi,
That's a great idea. Not sure about XEP-0157, but if nothing better arise, why
not.
In addition to status page, it would be great to have a way to get future
planed maintenance (at
nt one, and in the case of
OMEMO bundles, this can quickly grow.
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
Le vendredi 27 juillet 2018, 19:21:22 CEST Goffi a écrit :
> An (animated) picture worth thousand words :)
>
> https://repos.goffi.org/sat_docs/raw-file/tip/screenshots/0.7/
> language_filtering.gif
>
> The experimental language detection put aside, I'm using xml:lang
Le vendredi 27 juillet 2018, 17:24:27 CEST Peter Saint-Andre a écrit :
> On 7/27/18 8:03 AM, Goffi wrote:
> > Hello,
> >
> > I'm currently working on OMEMO implementation in Salut à Toi thanks to
> > the work of Syndace (https://github.com/Syndace/python-omemo), a
l, and if singleton is needed (which is the case), it should be
indicated in the XEP-0384 in my opinion.
> So my question would be, how do you get into a situation where a server
> sends you all items of the Node?
It's not in my notifications, I'
item.
That's all for now, thanks
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
mandatory expiration date returned by
servers, in the same way as size limit can be returned.
It would be even better to be able to list existing files and delete them
on request, but this can be done in a separated XEP.
Thanks
Goffi
Le samedi 23 juin 2018, 18:08:32 CEST Goffi a écrit :
> Did you
Dave: [pending]
> Georg: [pending]
Did you read my feedback about this? In particular what about my remarks on
expiration date? I would like to have an answer on that, it's particularly
important in my opinion. Thanks!
Cheers
Goffi
___
Stan
written?
yes, redaction is good and spec is well explained.
additional notes:
- there is no validation schema in section 11
- there is no short name
++
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
nsible consider when
> and if this will change.
> [SNIP]
Interested in implementing MIX in SàT, but not a priority (and lacking
resources). We have already blogging, comments, shared files and pictures
based on pubsub/jingle.
Goffi
___
Standa
ich would like to give a try to
XMPP, I'm not sure how I would consider XSF serious with this kind of
stuff.
Note that I appreciate the work done, and this is not talking about the
content of the spec itself.
OK I can put my red nose again
++
Goffi
body or at least most of people (developers and users).
Cheers
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
y to classify links, like
keywords, hierarchy, or anything else.
We have been thinking for a while with Edhelas about writting an
alternative proposal for bookmaks actually, but that's an other topic.
Goffi
Le mercredi 7 mars 2018, 20:17:24 CET Jonas Wielicki a écrit :
> The XEP Editor would
ually find the idea
really good, it's a clean separation between content and style, which means
that there is not need to send a text version as we have too with XHTML-IM.
XEP-0393 on the other hand is totally mixing style and content, that's why
I r
trieve a file in a
list returned by XEP-0329 potentially big.
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
have large files and/or a lot of files. Using path or UUID
would be a good solution, but we need to be able to specify them in
XEP-0234 (either by allowing "/" in name, or by using an other element).
Goffi
___
Standards mailing list
Inf
ath+filename.
My question is if we have only the filename or the hash (even if payload
will be the same with single hash, metadata like name or date can differ)
> The XEP hints at the possibility of requesting a file by name only (sans
> path), but only when this will be unique; I suggest
Le samedi 24 février 2018, 18:25:26 CET Kim Alvefur a écrit :
> On Sat, Feb 24, 2018 at 09:12:30AM +0100, Goffi wrote:
> > currently thumbnails are transmitted using http(s) or BoB (XEP-0231).
> > But with resolutions we can have todays even on small screens, size of
> &
Le samedi 24 février 2018, 18:25:26 CET Kim Alvefur a écrit :
> On Sat, Feb 24, 2018 at 09:12:30AM +0100, Goffi wrote:
> > currently thumbnails are transmitted using http(s) or BoB (XEP-0231).
> > But with resolutions we can have todays even on small screens, size of
> &
ssion, so http is
not an option here. As XEP-0234 is able to transmit several files in the
same session, it would be a good candidate for that.
Doesn anybody see an issue with using XEP-0234 for that? If no I'll propose
the change on the X
Le vendredi 23 février 2018, 10:16:49 CET Goffi a écrit :
> Le vendredi 23 février 2018, 10:02:15 CET Jonas Wielicki a écrit :
> > On Freitag, 23. Februar 2018 09:47:00 CET Goffi wrote:
> > > 1) XEP-0234 is in Last Call which is supposed to be finished, what
> > >
Le vendredi 23 février 2018, 10:02:15 CET Jonas Wielicki a écrit :
> On Freitag, 23. Februar 2018 09:47:00 CET Goffi wrote:
> > 1) XEP-0234 is in Last Call which is supposed to be finished, what the
> > status about that?
>
> The Council vote isn’t over yet (but fr
types)
Beside that this XEP is really usable.
Thanks
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
I also think it is
very unlikely that it is changed, so your proposition seems a reasonable
fix.
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
most adventurous ones). If other people are
willing to work on this field, please contact me.
Goffi
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
1 - 100 of 278 matches
Mail list logo
