Bug 32815 - Improve fallback behaviour when user's server has no conference component.
Summary: Improve fallback behaviour when user's server has no conference component.
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: git master
Hardware: Other All
: medium minor
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-04 03:26 UTC by Will Thompson
Modified: 2011-01-28 09:20 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Use conference.telepathy.im as the default MUC server (1.34 KB, patch)
2011-01-28 08:55 UTC, Will Thompson 		Details | Splinter Review
View All

Description Will Thompson 2011-01-04 03:26:17 UTC 
Today I tried to create an ad-hoc conference containing two fellow fruit fans. Unfortunately my Jabber server doesn't have a MUC component. (That sysadmin should pull his socks up.)

Gabble doesn't have any fallback MUC servers configured by default. This seems a bit upsetting. The Illustrious Rob removed the conference.jabber.org default back at the dawn of time. I'm not sure what the rationale is. I don't know who exactly would configure fallback-conference-server, ever.

One option would be to re-add a hard-coded conference server. (conference.telepathy.im?) Another option might be to try discoing the contacts we're trying to invite to see if their servers have MUC components if ours does not. (This would actually not have helped because neither of these people have MUC components either.)
Comment 1 Will Thompson 2011-01-28 08:55:59 UTC 
Created attachment 42660 [details] [review]
Use conference.telepathy.im as the default MUC server

Fixes: <https://bugs.freedesktop.org//show_bug.cgi?id=32815>
Comment 2 Will Thompson 2011-01-28 09:20:54 UTC 
Pushed this to master. It'll be in 0.11.7. http://git.collabora.co.uk/?p=telepathy-gabble.git;a=commitdiff;h=0841b15aaaef2295b6860206d2656cfd32a8a2fa

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.