#Matrix spent a decade turning the problem of worrying about which extensions your server supports into worrying about which room version your server supports.

Meanwhile, the #XMPP community got their act together, reached a rough consensus on which extensions are worth pursuing, and now you can install any of the four major servers without having to worry about what extensions are working behind the scenes.

nostr:npub1qxta2gd8gd3695alyerumymrdyhe3lujqpl2adnvk84hgzswsrzq8nm80t quicksy.im and our UnifiedPush service (up.conversations.im) are hosted separately and will not be impacted.

We are finally going to upgrade our #ejabberd running on conversations.im, tomorrow, Saturday May 25th.

Unfortunately we won’t be able to do this without some down times throughout the day.

You can visit https://status.conversations.im/ for a simple up/down check or follow this thread for the occasional status update / progress report.

nostr:npub1czlgwwr3d7ywl6fj05p7826avmldz7spjxmsrk2un0luvfkkp60s3887qa no there is nothing that would leak any part of the contact list to the server.

nostr:npub1czlgwwr3d7ywl6fj05p7826avmldz7spjxmsrk2un0luvfkkp60s3887qa you are allowed to upload them if you ask for consent.

I tried arguing with Google for a while however their 7 day deadline to admit publicly that I'm uploading the contact list is running out tomorrow so to not risk the app being removed again I was forced to publish a version without address book integration.

It seems like you can only have an app that requests contacts permission on the PlayStore if you boldly declare that you upload them.

Google had accepted a version of Conversations with address book integration that explicitly asks the user for consent to process the contact list locally on their device before promoting for contacts permission. Our privacy policy included explicit wording w.r.t. local processing of the contact list.

However it is unthinkable for Google that someone would request contacts permission and then *not* upload them. A few days later they changed their mind and threatened to remove the app again.

To celebrate Conversations being back on the Play Store and to deny Google their 15% cut I made the app free for the next ~48 hours. 😜

If you are new here: Check out #XMPP. It's federated, provider and vendor independent instant messaging. It’s great!

https://play.google.com/store/apps/details?id=eu.siacs.conversations

Or get it from #fdroid - That version even has address book integration and public channel discovery! 😂

As it is a long, long tradition Conversations is available for free on the Google Play store for the last week of December.

This tradition was originally born so that when I meet people at Chaos Communication Congress and they ask what I do, they have an easy way to install Conversations. In that regard it's a very special year as we are seeing the return of CCC.

However if you are meeting loved ones to celebrate something else these days that’s fine too.🎄

https://play.google.com/store/apps/details?id=eu.siacs.conversations

#37C3 #XMPP

I just finished a refactor of the Jingle File Transfer code in #Conversations_im.

The P2P file transfer code was probably one of the oldest code in Conversations.

The new code should be a lot more resilient and brings support for XEP-0343: Signaling WebRTC datachannels in Jingle¹. This means we should be able to exchange files directly with #XMPP web clients.

Due to the better NAT hole punching of WebRTC vs Socks Bytestreams we now have a higher chance of actual P2P.

¹: https://xmpp.org/extensions/xep-0343.html

nostr:npub14d8wgj4h303ha52ls6fu5wck2k4ak57k732luy92jv5352jdcg2sx0v62e nostr:npub1jvdpz4ph7nqe3c47hcpgtymzd79y3nw49qp85e3ehn5df9em4jqsfdnl3q It’s more complicated then that. In my case - having a paid app on Google Play - Google will publish my billing address which is the same address my bank account is under. In order for that not to be my home address I would have to set up a company; get a virtual address for my company. This requires a lease. Virtual offices where you get a lease do exists but they costs more then "just a couple of bucks in some places".

Plus the overhead of filing taxes for you company

I'm excited to see the Threads / #activitypub experiment play out.

Threads is going to have a much larger user base than Mastodon. If Threads implementing ActivityPub means someone on Threads can follow what I post on my own personal Mastodon instance that's a good thing. It will increase my potential audience w/o me having to sign up to Threads myself.

Likewise if someone I'm interested in posts on Threads I can easily subscribe to them.

It's just RSS. I don't care what RSS reader you use.