Hi, Facebook stops Jabber/XMPP support 10 years ago. AFAIK major SN actors never ever supported Jabber/XMPP.

10 years ago, the procedure was :
▪ Install extraplugins (https://openrepos.net/content/ekze/extraplugins) to add support for more accounts, including Jabber
▪ In Accounts, add a Jabber account with the following credentials:
▪ Username: your-facebook-id@chat.facebook.com
▪ Password: your-facebook-password
▪ Server: chat.facebook.com

There was actually a way to make it work back in 2018 based on a post in this forum. It was using jabber server called jabber no sense net which enabled it to work. This is why i am now searching for a jabber server that was working facebook transport.

Here is the link https://talk.maemo.org/showthread.php?t=99872

There are many public jabber servers online. I might go through them one by one and test them out when i have time

Edit : I find out an alternative to the broken CalDAV sync : syncevolution. It works well with my memotoo.com account (in 2025!). I successfully synchronize :
- memo
- todo
- calendar events
- address book.

The steps by step I follow :
1. install syncevolution 1.3.1 (aegis-dpkg -i syncevolution_1.3-1_armel.deb)
2. run: syncevolution --configure --sync-property "username=123456" --sync-property "password=!@#ABcd1234" memotoo
3.check (with nano...) this file : home/user/.config/syncevolution/default/peers/memotoo/config.ini

Example of required entries:
syncURL = http://sync.memotoo.com/syncml
username = 123456
password = !@#ABcd1234

You may check as well with this command:
syncevolution --print-config memotoo

4. first sync (first full sync => with slow mode) :
syncevolution --sync slow memotoo addressbook
syncevolution --sync slow memotoo calendar
syncevolution --sync slow memotoo todo
syncevolution --sync slow memotoo memo
syncevolution --status memotoo addressbook calendar memo todo

5. next sync (incremental) :
syncevolution --quiet memotoo

:-)

Nice find! I'm still curious what makes CalDAV broken. Maybe its packages should be recompiled with new OpenSSL or something...

i also noticed that curl isn't using the new tls

The original curl would need to be rebuilt, but you can use my newer packages repository:
https://wunderwungiel.pl/MeeGo/wundern9
There is custom OpenSSL 1.1.1w (TLS 1.3) and curl. Optified-path will put things in path

oh wow, very nice

Oftopic: Have you tried ubiboot on your n950 and how will you cope with 3g shutoff in europe, does that still work in poland?

Regarding the caldav bug, i try to investigate further but im a complete ignorant of linux. I tried to strace some app on 2 different n9, one with your tls patch , the other without. I ran strace on /usr/bin/organiser and on /usr/lib/AccountSetup/caldavplugin then i compared respective outputs. No significant differences for my ignorant eyes : 99 % same "not file found" errors in both, the only difference is that your libssl.so.1.0.0 and libcrypto.so.1.0.0 are located in /usr/lib/local as original ones (0.9.8) are in /usr/lib.).

how do you access sites with tls 1.3 and javascript? sInce js isn't supported in the stock browser and other browsers don't seem to use new certificates or tls 1.3 there are some sites i cannot open. aLso in the debian wheezy chroot with updated packages from archive.debian.org they're not accessible. aT least with midori or iceweasel