On 04/26/2018 10:35 AM, Jonas Wielicki wrote:
> As it turns out, several implementations are making it not trivial for
> operators to be GDPR compliant. One of the things definitely necessary (as
> far
> as our understanding goes) is that users must be able to have their data
> deleted in a
Dear all,
Today I have received new announcements about 4 XEPs (0363/0223/0122/0373):
- https://xmpp.org/extensions/xep-0363.html -> Version: 0.6.0 / Last
Updated: 2018-04-21
- https://xmpp.org/extensions/xep-0223.html -> Version: 1.1 / Last
Updated: 2018-03-28
-
Hi Ivan,
On Donnerstag, 26. April 2018 14:03:15 CEST Ivan Vučica wrote:
> Today I learned about XEP-0068 which seems to specify an IDL-like XML
> for data forms. It also defines a registry for FORM_TYPEs maintained
> by the XMPP Registrar. I feel this could be very useful to client
> libraries,
Version 0.6.0 of XEP-0363 (HTTP File Upload) has been released.
Abstract:
This specification defines a protocol to request permissions from
another entity to upload a file to a specific path on an HTTP server
and at the same time receive a URL from which that file can later be
downloaded again.
Version 1.1 of XEP-0223 (Persistent Storage of Private Data via
PubSub) has been released.
Abstract:
This specification defines best practices for using the XMPP publish-
subscribe extension to persistently store private information such as
bookmarks and client configuration options.
Changelog:
Version 0.3.0 of XEP-0373 (OpenPGP for XMPP) has been released.
Abstract:
Specifies end-to-end encryption and authentication of data with the
help of OpenPGP, announcement, discovery and retrieval of public keys
and a mechanism to synchronize secret keys over multiple devices.
Changelog:
Version 1.0.2 of XEP-0122 (Data Forms Validation) has been released.
Abstract:
This specification defines a backwards-compatible extension to the
XMPP Data Forms protocol that enables applications to specify
additional validation guidelines related to a form, such as validation
of standard XML
Hi all,
During the last "XSF & GDPR" meeting (minutes pending), we were discussing
HTTP Upload.
As it turns out, several implementations are making it not trivial for
operators to be GDPR compliant. One of the things definitely necessary (as far
as our understanding goes) is that users must
I have reviewed channel ownership with my co-author, and we believe that the
best plan is to make channel Owner mandatory. I will make the edits,
unless there is list discussion to the contrary.
While I can see sensible use case for "no Owner" channels, the current
choice to make it
Hi,
Today I learned about XEP-0068 which seems to specify an IDL-like XML
for data forms. It also defines a registry for FORM_TYPEs maintained
by the XMPP Registrar. I feel this could be very useful to client
libraries, which can generate code with structs for predefined types
a-la protocol
>
> Okay, I’m not sure if what I’m going to write even makes sense, but I prefer
> to
> have it stated instead of hindsight later on. I think this feature might be
> problematic, because:
>
> - Ownership implies responsibility. Adding third parties as owners without
> their
> consent and a
Manuel,
> -Original Message-
> From: Manuel Rubio
> Sent: 25 April 2018 20:39
> To: XMPP Standards
> Cc: Steve Kille
> Subject: Re: [Standards] XEP-0369: MIX - About create a room/channel
>
> Hi,
>
> I'm not sure if
Ralph,
> -Original Message-
> From: Ralph Meijer
> Sent: 25 April 2018 08:26
> To: XMPP Standards ; Steve Kille
>
> Subject: Re: [Standards] XEP-0369: MIX - About create a room/channel
>
>
> Section 3.9.1 says two things:
>
>
13 matches
Mail list logo