Custom Query (1098 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (22 - 24 of 1098)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Ticket Resolution Summary Owner Reporter
#317 obsolete Auto-deletion of Off-line Meebo Contacts, preferably Chascon
Description

Okay, I'm, throwing this in as a Meebo bug (enhancement?), even though Bitlbee does not support Meebo. I assume that I am the first?? that has gotten Bitlbee and Meebo working or the first to report it as I cannot find info on google or your web-page. I assume it needs just a little fine tuning on the dev end, referring to auto-deletion of off-line Meebo contacts.

Here's a run down from my article on Meebo working with Bitlbee, among other "clones".

"Bitlbee Instructions I got Meebo working with Bitlbee too but deleting the continuous stream of contacts --as they log-off-- might be frustrating. Of course, this depends on the amount of traffic your site receives, but if you're getting that much congestion you need another service such as email. I added Meebo to Bitlbee the following way, in a one line command,

  • account add jabber username@…/Home yourPassword meebo.org:5222

It was also accepted without the "/Home" bit. ... Suffixing ":ssl" disables Bitlbee's ability to log on; Bitlbee reports "Login error: Unable to connect" and signs off --so don't request "ssl". Bitlbee needs a script to automize off-line Meebo contact deletion in real time. The other option would be selectively allow off-line Meebo contacts show presence on the roster. Thus, one could manually delete them as they take off-line status (assuming that Meebo contact names are not recycled in which case rendering deletion unnecessary). This might be manageable if "only Meebo contacts" show as off-line, as enabling off-line visibility for all IM accounts would become unmanageable; This, due to the sheer number of off-line contacts at any given time and the needle in the haystack scenario contact deletion involves. To lighten this quandary, perhaps unix commands could be enabled, such as

"blist all | grep @hotmail.com" or the more native feeling "blist xaccount" to list all xaccount contacts (ie., "blist msn" or "blist accountCode" as in "blist 0")."

http://mauroandres.wordpress.com/2007/09/03/access-meebo-via-bitlbee-or-a-jabber-client/

Chascon

#318 duplicate grep domain name, alias, and real name searches Chascon
Description

"blist all | grep @hotmail.com" or the more native feeling "blist all xaccount" to list all xaccount contacts (ie., "blist msn" or "blist accountCode" as in "blist 0")."

Expanding this beyond domain names to aliases would be useful.

Furthermore, meta-data searches through real names would be useful when one can't associated a contact name with a real person ('s name). These real names searches could work locally if remote Bitlbee, Jabber, or other non-Bitlbee servers do not posses info.

Chascon

#321 invalid Stipulating a Nick Name with the add Command Creates Duplicity Chascon
Description

Problem: "add usename@… NickName" creates the contact on the roster but the contact is also accepted under Bitlbee's own automatically generated username. Thus, two contacts are created and are really duplicates.

Expected Result: get the gmail contact registered with the nick name without duplication

Solution: Short term solution is to use the "rename" command posthumously

Chascon

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Note: See TracQuery for help on using queries.