Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T telepathy-gabble
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 289
    • Issues 289
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TelepathyTelepathy
  • telepathy-gabble
  • Issues
  • #208
Closed
Open
Issue created Feb 09, 2012 by Bugzilla Migration User@bugzilla-migration

telepathy-gabble does not persist OLPC pubsub data

Submitted by Daniel Drake

Assigned to Telepathy bugs list

Link to original bug (#45853)

Description

The src/conn-olpc.c code in telepathy-gabble uses pubsub to share data between roster users about the users icon colour, public ssh key, activity information, etc.

However, by default, pubsub is a "broadcast-and-forget" system, i.e. the server will broadcast the data to any existing clients, but not save it to be queried later.

Old ejabberd versions were not exactly specs-compliant here and stored the data anyway, but new ejabberd versions do not store the data by default, and this isn't configurable.

This means that OLPC presence is broken - when connecting to a network, Sugar/telepathy attempts to retrieve the public keys and icon colors of all existing users on the network (via pubsub query). This fails (the server didn't store it) so the presence is broken.

The pubsub messages generated by telepath-gabble/wocky should be modified to mark the data as persistent, to be stored to the server, according to http://xmpp.org/extensions/xep-0223.html.

Reproduced with telepathy-gabble-0.15.3.

Assignee
Assign to
Time tracking