Google聊天服务器存档(XEP-0136) [英] Google chat server archive (XEP-0136)

查看:110
本文介绍了Google聊天服务器存档(XEP-0136)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在寻找一种方法,该方法如何使用XEP-0136标准从Google服务器检索聊天消息的存档,但我只是在尝试使用该功能时才得到这些结果.

I am looking for a way how to retrieve archive of chat messages from google server via using XEP-0136 standard, but I got these results just trying to ask for the feature.

请求:

<iq type="get"><pref xmlns="urn:xmpp:archive"/></iq>

响应:

<iq xmlns="jabber:client" type="error" to="myEmail@gmail.com/9FF72CA7">
    <pref xmlns="urn:xmpp:archive"/>
        <error code="501" type="cancel">
            <feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
        </error>
</iq>

因此,看起来Google并未实现此功能,但这是真的吗?我不这么认为.

So it looks like google does not implement this feature, but is it true? I don't think so.

尝试设置隐身性时也发生了同样的情况,这确实受到Google服务器的支持.

The same happened with trying to set invisibility which is definitely supported by Google server.

请求:

<iq type="set" id="invisible1" from="myEmail@gmail.com/00230F07">
    <query xmlns="jabber:iq:privacy">
        <active name="invisible"/>
    </query>
</iq>

响应:

<iq xmlns="jabber:client" type="error" id="invisible1" to="myEmail@gmail.com/00230F07">
    <query xmlns="jabber:iq:privacy">
        <active name="invisible"/>
    </query>
    <error code="501" type="cancel">
        <feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
    </error>
</iq>

所以我可能做错了什么.任何帮助将不胜感激.

So probably I am doing something wrong. Any help will be appreciated.

推荐答案

我也已经研究了很长时间了.如JoSo已经指出的那样,似乎无法通过任何XMPP标准访问聊天记录.可以通过XMPP与聊天记录进行的唯一交互是通过非标准

I've also been looking into this for quite some time now. It appears, as JoSo already pointed out, that there is no way to access the chat history through any XMPP standard. The only interaction with the chat history that is possible via XMPP is enabling or disabling Off-the-Record through a non-standard XMPP extension.

话虽这么说,例如 Chrome扩展程序之类的Google官方聊天客户端,它们被废弃的 Windows客户端和Android应用程序能够同步聊天.因此,必须至少有某种方式可以从外部访问聊天记录.但是,在任何地方都没有关于此功能的文档,并且Google论坛中的所有问题都无法得到解答.不少人猜想它可能会通过XEP-0136实施,但没有任何官方用语,它也可能是完全专有的XMPP扩展.

That being said, the official Google Chat clients such as the Chrome extension, their kind of abandoned Windows client and the Android application are able to sync chats. Thus, there must be at least some way to access the chat history from the outside. However, there is no documentation on this feature anywhere and all questions in the Google forums go unanswered. Quite a few people guess that it might be implemented through XEP-0136 as it would make sense, but without any official word it might also be a completely proprietary XMPP extension.

出于隐身目的,它受到支持,但Google再次使用其使用自己的方式,而不是使用XEP-0016扩展名.在这种情况下,至少在此处中记录了它们的方式.因此,只需使用其google:shared-status命名空间将自己设置为不可见.

For invisibility, it is supported but Google again goes their own way instead of using the XEP-0016 extension. At least their way is documented here in this case. Thus, just use their google:shared-status namespace to set yourself invisible.

总而言之,尝试使用Google聊天服务器的任何XMPP扩展确实是一个痛苦,因为许多功能是专有的,使用其自身笨拙的扩展而不是标准,或者根本没有实现.至少有关公共扩展的完整文档非常不错.

That all being said, trying out any XMPP extensions with Google's chat servers is a real pain as many features are proprietary, use their own awkward extensions instead of the standard or simply are not implemented. At least the documentation for the hand-full of public extensions is quite good.

如果您正在寻找Google的官方答案,那么您也很幸运.第三方客户的大多数Google Talk功能(例如Pidgin)已由开发人员进行反向工程.在您询问之前,它们的音频/视频和文件传输扩展名也与当前标准相距几英里.

In case you're looking for official answers from Google, you're also quite of luck. Most of the Google Talk features of third party clients such as Pidgin have been reverse engineered by the developers. Before you ask, their audio/video and filetransfer extensions are also quite some miles off the current standard.

这篇关于Google聊天服务器存档(XEP-0136)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆