Language:
switch to room list switch to menu My folders
Go to page: First ... 36 37 38 39 [40]
[#] Tue Feb 24 2015 01:00:32 EST from ax25 @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

I am getting authentication failed when trying to connect with mcabber, but it might just be a simple matter of it being late at night :-)  I will give it another go tomorrow.  Thanks IG.



[#] Tue Feb 24 2015 09:38:09 EST from bainwave @ Uncensored

Subject: Re: Multiple domains support

[Reply] [ReplyQuoted] [Headers] [Print]

Thanks for your reply.

But how users will login into the server?

and if you have any doc please publish it

--

Bain

Mon Feb 23 2015 06:35:12 EST from dothebart @ Uncensored Subject: Re: Multiple domains support

you can configure them in Aministration -> Domain names and Internet mail configuration

Your users can then choose to receive mails on those domains.

If you need strict separation there are two options:

 - don't allow users to edit their personal vcards (and do it for them)

 - run two separate citadel instances with each one domain configured.



 



[#] Tue Feb 24 2015 10:01:35 EST from dothebart @ Uncensored

Subject: Re: Multiple domains support

[Reply] [ReplyQuoted] [Headers] [Print]

Users will login with their username or their email address.

-> if you have two users with the same name, you need to give them different usernames.

Tue Feb 24 2015 09:38:09 EST from bainwave @ Uncensored Subject: Re: Multiple domains support

Thanks for your reply.

But how users will login into the server?

and if you have any doc please publish it

--

Bain

Mon Feb 23 2015 06:35:12 EST from dothebart @ Uncensored Subject: Re: Multiple domains support

you can configure them in Aministration -> Domain names and Internet mail configuration

Your users can then choose to receive mails on those domains.

If you need strict separation there are two options:

 - don't allow users to edit their personal vcards (and do it for them)

 - run two separate citadel instances with each one domain configured.



 



 



[#] Tue Feb 24 2015 23:37:34 EST from ax25 @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

I am giving up on mcabber.  Seems broken.



[#] Thu Feb 26 2015 08:17:37 EST from "Stefan Jakobs" <stefan@localside.net> to room_Citadel_Support <room_citadel_support@uncensored.citadel.org>

Subject: XMPP: psi+, kopete

[Reply] [ReplyQuoted] [Headers] [Print]

Hi,

I tried to use uncensored's XMPP feature with psi+ and kopete. It failed with
both. They never finished the connection process.

Sniffing the connection with wireshark tells me, that the login was
successful. The server even announced the PRESENCE of some other users. But
the client still seams to wait for something.

Regards
Stefan

[#] Thu Feb 26 2015 08:31:42 EST from "Stefan Jakobs" <stefan@localside.net> to citadel_support@citadel.org

Subject: Re: [Citadel Support] install OpenSuse 13.2 x64 fail

[Reply] [ReplyQuoted] [Headers] [Print]

You wrote:
can you try to install the 13.1 berkeley db rpm on the 13.2?

I installed libcares, libcitadel, citadel and libdb from 13.1 on a 13.2
system, but it didn't help. Still the same error.

I even recompiled the citadel suite to use libdb 4.5: citserver reports the
same error.

Regards
Stefan

[#] Thu Feb 26 2015 15:28:18 EST from jefft88 @ Uncensored

Subject: secure authentication with Citadel.

[Reply] [ReplyQuoted] [Headers] [Print]

Hello,

Does anyone know how to set up secure authentication with Citadel.

Thanks,

Jeff



[#] Thu Feb 26 2015 17:06:35 EST from IGnatius T Foobar @ Uncensored

Subject: Re: secure authentication with Citadel.

[Reply] [ReplyQuoted] [Headers] [Print]

Does anyone know how to set up secure authentication with Citadel.

Yes, many people do.

[#] Sat Feb 28 2015 03:59:54 EST from mo @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

 

 

Sun Feb 15 2015 20:44:18 EST from IGnatius T Foobar @ Uncensored

Hi everyone.

This morning I made some small but *very* effective bugfixes to the XMPP service in Citadel. These changes are *live* here on Uncensored. So far, I have tested the following clients:

* Pidgin (of course)
* jwchat.org (a web-based client ... not sure why you'd use this in production since WebCit has a chat client built in, but it tested clean and that's good)
* Xabber (a client for Android)

All three are working great now. So here's where you come in, folks ... if you have any other favorite clients, now's the time to test them. Again, test them here on Uncensored, not on a released version of Citadel, as we haven't published this code yet. I suppose you could also test against git master if you really insist on your own server.

Here are the tests that need to be run:

1. When you log in, the roster should populate with all other users who are logged in.
2. Send and receive instant messages (of course).
3. When users log in and out, they appear and disappear from the roster.
4. The roster of a Citadel account should *never* show any "offline buddies."
This is because Citadel's XMPP implementation assumes that the user community should always consist of the people currently logged in to the server, and sends roster pushes to reflect this.

If you test a client and the above four tests pass, please post your results so we can include that client in the next release announcement.

I just logged in to uncensored xmpp/jabber with the "bitlbee"  (IRC to xmpp gateway) client. This is for users of the "irssi" IRC client, which i know at least one of you here uses, and means you can access all xmpp chat rooms while using IRC (on colsole).

Here is how i set it up:

 

1) Install bitlbee:        I used my linux distros package manager 

2) connect  to bitlbee deamon:     start the  IRC client, irssi;-  

  •  issue:  /connect bitlbee  (or /connect localhost  even:   you should now be in the bitlbee control channel)

3) setup/register an account password for your new bitlbee account** on your machine:

  •   issue: register
  •  issue: /oper
  •  issue: <your-new-bitlbee-account_password>

4) add a xmpp/jabber account:-  

  • issue:   account add  jabber  <username>@uncensored.citadel.org
  • issue: /oper <return>
  • issue: <your-uncensored-account_password>

to check the account has been added successfully:

  • issue: account list

you can add further accounts; twitter, gtalk, facebook etc...

 ** When you come to start up the irssi client next, you will be prompted for your bitlbee password; when you login you will automatically login to 'all' your xmpp/jabber accounts

5) login and chat:  use either the numeric or name ID of the account (you can see the numeric ID when you 'list' the accounts):-

  • issue: account <ID> on     (logout is: account <ID> off, if needed)

You should now see the names of,all your account's, contacts in the bitlbee control channel

to chat with someone in the bitlbee control channel:

  • issue: <contact_name>: <message>    (don't forget the colon after contact's name ;) )

or, which i find 'much' easier if there are alot of people from various xmpp accounts added and 'lot' of contacts in the bitlbee controlo channel:

  • issue: /msg <contact_name> <message>      (and a separate channel will be opened for you and your contact - much easier)

 

 

Now that was to test. To set up so you auto login each time see irssi docs and use same setup for bitlbee as they use for facebook.

 

 

 

 

    

 



[#] Sat Feb 28 2015 04:36:24 EST from mo @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Bitlbee and irssi, more info:

1)

Here is a link to the bitlbee facebook howto.

https://wiki.bitlbee.org/HowtoFacebook

I used the old way to login, with a password, you might want to use OAuth.

 

2)

and also here is the docs i used, which might be better. I posted them up on my blog on uncensored. See the comments for the docs.

http://uncensored.citadel.org/readfwd?go=trinkets%20and%20oddities?p=1883055487



[#] Sat Feb 28 2015 04:49:08 EST from mo @ Uncensored

Subject: xmpp bitlbee-irssi

[Reply] [ReplyQuoted] [Headers] [Print]

On first impressions, it all works great! I logged in to uncensored with my console iorc client irssi. I saw all 'most' of the logged in users on uncensored - but not all?

I left a message for someone and had a chat with them. Great!

I was logged on to webcit at the same time as using my console irc client and the webcit chat/xmpp window opened up as soon as my chat was responded to (via my friends android client - pidgin i believe(?)).

I could see all the messages typed from my friend on both my webcit and irc client. However the two clients i used do not sync ( i typed some messages in my irc client, some on webcit and they were both seen by my friend (on his android client) but i could not see what i typed from webcit on my irc client and the also the other way ) - so you need use one or the other clients to see 'all' your messages in one window.

Still it works like a charm.

 

See my previous post here (no Subject) for a few links to Docs.

Sat Feb 28 2015 03:59:54 EST from mo @ Uncensored

 

 

Sun Feb 15 2015 20:44:18 EST from IGnatius T Foobar @ Uncensored

Hi everyone.

This morning I made some small but *very* effective bugfixes to the XMPP service in Citadel. These changes are *live* here on Uncensored. So far, I have tested the following clients:

* Pidgin (of course)
* jwchat.org (a web-based client ... not sure why you'd use this in production since WebCit has a chat client built in, but it tested clean and that's good)
* Xabber (a client for Android)

All three are working great now. So here's where you come in, folks ... if you have any other favorite clients, now's the time to test them. Again, test them here on Uncensored, not on a released version of Citadel, as we haven't published this code yet. I suppose you could also test against git master if you really insist on your own server.

Here are the tests that need to be run:

1. When you log in, the roster should populate with all other users who are logged in.
2. Send and receive instant messages (of course).
3. When users log in and out, they appear and disappear from the roster.
4. The roster of a Citadel account should *never* show any "offline buddies."
This is because Citadel's XMPP implementation assumes that the user community should always consist of the people currently logged in to the server, and sends roster pushes to reflect this.

If you test a client and the above four tests pass, please post your results so we can include that client in the next release announcement.

I just logged in to uncensored xmpp/jabber with the "bitlbee"  (IRC to xmpp gateway) client. This is for users of the "irssi" IRC client, which i know at least one of you here uses, and means you can access all xmpp chat rooms while using IRC (on colsole).

Here is how i set it up:

 

1) Install bitlbee:        I used my linux distros package manager 

2) connect  to bitlbee deamon:     start the  IRC client, irssi;-  

  •  issue:  /connect bitlbee  (or /connect localhost  even:   you should now be in the bitlbee control channel)

3) setup/register an account password for your new bitlbee account** on your machine:

  •   issue: register
  •  issue: /oper
  •  issue: <your-new-bitlbee-account_password>

4) add a xmpp/jabber account:-  

  • issue:   account add  jabber  <username>@uncensored.citadel.org
  • issue: /oper <return>
  • issue: <your-uncensored-account_password>

to check the account has been added successfully:

  • issue: account list

you can add further accounts; twitter, gtalk, facebook etc...

 ** When you come to start up the irssi client next, you will be prompted for your bitlbee password; when you login you will automatically login to 'all' your xmpp/jabber accounts

5) login and chat:  use either the numeric or name ID of the account (you can see the numeric ID when you 'list' the accounts):-

  • issue: account <ID> on     (logout is: account <ID> off, if needed)

You should now see the names of,all your account's, contacts in the bitlbee control channel

to chat with someone in the bitlbee control channel:

  • issue: <contact_name>: <message>    (don't forget the colon after contact's name ;) )

or, which i find 'much' easier if there are alot of people from various xmpp accounts added and 'lot' of contacts in the bitlbee controlo channel:

  • issue: /msg <contact_name> <message>      (and a separate channel will be opened for you and your contact - much easier)

 

 

Now that was to test. To set up so you auto login each time see irssi docs and use same setup for bitlbee as they use for facebook.

 

 

 

 

    

 



 



[#] Sat Feb 28 2015 04:51:40 EST from mo @ Uncensored

Subject: Re: xmpp bitlbee-irssi

[Reply] [ReplyQuoted] [Headers] [Print]

Just in case it gets missed, this is how i succesfully tested the irssi with bitlbee xmpp client on console:

 

I just logged in to uncensored xmpp/jabber with the "bitlbee"  (IRC to xmpp gateway) client. This is for users of the "irssi" IRC client, which i know at least one of you here uses, and means you can access all xmpp chat rooms while using IRC (on colsole).

Here is how i set it up:

 

1) Install bitlbee:        I used my linux distros package manager 

2) connect  to bitlbee deamon:     start the  IRC client, irssi;-  

  •  issue:  /connect bitlbee  (or /connect localhost  even:   you should now be in the bitlbee control channel)

3) setup/register an account password for your new bitlbee account** on your machine:

  •   issue: register
  •  issue: /oper
  •  issue: <your-new-bitlbee-account_password>

4) add a xmpp/jabber account:-  

  • issue:   account add  jabber  <username>@uncensored.citadel.org
  • issue: /oper <return>
  • issue: <your-uncensored-account_password>

to check the account has been added successfully:

  • issue: account list

you can add further accounts; twitter, gtalk, facebook etc...

 ** When you come to start up the irssi client next, you will be prompted for your bitlbee password; when you login you will automatically login to 'all' your xmpp/jabber accounts

5) login and chat:  use either the numeric or name ID of the account (you can see the numeric ID when you 'list' the accounts):-

  • issue: account <ID> on     (logout is: account <ID> off, if needed)

You should now see the names of,all your account's, contacts in the bitlbee control channel

to chat with someone in the bitlbee control channel:

  • issue: <contact_name>: <message>    (don't forget the colon after contact's name ;) )

or, which i find 'much' easier if there are alot of people from various xmpp accounts added and 'lot' of contacts in the bitlbee controlo channel:

  • issue: /msg <contact_name> <message>      (and a separate channel will be opened for you and your contact - much easier)

 

 

Now that was to test. To set up so you auto login each time see irssi docs and use same setup for bitlbee as they use for facebook.

 

 

 

 

    

 



 



 



[#] Sat Feb 28 2015 05:07:45 EST from mo @ Uncensored

Subject: Re: xmpp bitlbee-irssi

[Reply] [ReplyQuoted] [Headers] [Print]

To add: although i cannot see 'all' of what i typed when alternating between two clients, i 'can' see the full log/conversation in the "sent/recieved pages" room/page on uncensored, so that's great.

Not a great issue if you only chat on one client at a time ;)

 

Sat Feb 28 2015 04:49:08 EST from mo @ Uncensored Subject: xmpp bitlbee-irssi

On first impressions, it all works great! I logged in to uncensored with my console iorc client irssi. I saw all 'most' of the logged in users on uncensored - but not all?

I left a message for someone and had a chat with them. Great!

I was logged on to webcit at the same time as using my console irc client and the webcit chat/xmpp window opened up as soon as my chat was responded to (via my friends android client - pidgin i believe(?)).

I could see all the messages typed from my friend on both my webcit and irc client. However the two clients i used do not sync ( i typed some messages in my irc client, some on webcit and they were both seen by my friend (on his android client) but i could not see what i typed from webcit on my irc client and the also the other way ) - so you need use one or the other clients to see 'all' your messages in one window.

Still it works like a charm.

 



Go to page: First ... 36 37 38 39 [40]