On 18 Apr 2015, at 03:57, Peter Saint-Andre - yet pe...@andyet.net wrote:
The Message Archive Management spec (XEP-0313) seems to assume that a message
archive will live on the server
It was my intention to not have the text require this. I tried to put some
effort into making it very
On 18/04/2015 11:03, Dave Cridland wrote:
Between XEP-0355 and carbons, I think you're covered already, at first
thought.
Indeed the XEP-0355 has a mechanism to delegate MAM (or something else)
to any entity under the control of the user. The issue here is that the
data still go through the
Sounds like a really nice hack. A recombination of presence, disco and MAM
to gain a totally different user experience.
+1 for the idea :)
Not sure where to put this though. How about
XEP-1337 Hacks
:D
2015-04-18 5:24 GMT+02:00 Kurt Zeilenga kurt.zeile...@isode.com:
On Apr 17, 2015, at
Oh, my list is missing the carbons of course.
2015-04-18 10:58 GMT+02:00 Stefan Strigler stefan.strig...@gmail.com:
Sounds like a really nice hack. A recombination of presence, disco and MAM
to gain a totally different user experience.
+1 for the idea :)
Not sure where to put this though.
On 18 Apr 2015 03:58, Peter Saint-Andre - yet pe...@andyet.net wrote:
Ideally, to me, my message archive would be stored on a trusted device
that is under my control (say, a limited-access storage medium that I keep
in my house). This device could authenticate to my account and advertise
its
The Message Archive Management spec (XEP-0313) seems to assume that a
message archive will live on the server where a user has registered an
account. This raises privacy and security concerns, especially if the
messages are not encrypted: as a user I might not want all that message
history on
On Apr 17, 2015, at 7:57 PM, Peter Saint-Andre - yet pe...@andyet.net
wrote:
The Message Archive Management spec (XEP-0313) seems to assume that a message
archive will live on the server where a user has registered an account. This
raises privacy and security concerns, especially if
