I think I’ve found a relatively nice solution for #FediLinks in #Conversations_im.
You can put web+ap URIs into a message (or room description) and ideally a click on those will open your Mastodon client. However if no installed app supports those (the only app that I’m aware of is Fedilab) Conversations will open a browser instead.
Currently no app will create web+ap links but it is fairly easy to handcraft them.
cc @SoniEx2
@josephcox
> He changed his profile picture to a photo of himself so it was much easier to see which Jason Signal contact corresponded to that Jason.
This still leaves the risk of people deliberately changing their username+profile picture to match that of Jason to trick you to invite the wrong Jason to the group chat
In #Conversations_im we try to show the Jabber ID (not just the username) in relevant places (during invites, for new chats)
For #Signal that would be the phone number, I guess
For the next #Conversations_im release I’m refactoring how URIs are linked / made clickable. I’m adding a bunch of URI schemes like tel and mailto on top of the existing xmpp, http(s) and geo but removing support for "things that look like web URLs but aren’t actually URIs" (like 'example.com') to avoid some false positives.
Once the 2.18.0-beta comes out tomorrow or so let me know if you see things that isn’t matched and should be matched or vice versa.
@wiktor I understand the concern about bad fallback on the web. I just wish people would be a bit more pragmatic about it and at least add support for reading / opening such URIs. Nobody suggested replace all Follow buttons with web+activitypub: links.
Can we have support for FEP-07d7 in #Tusky and #Fedilab? (cc @Tusky @apps)
It shouldn’t be that hard to implement at least one of the possible URI schemes in #Conversations_im, #Lttrs, #Tusky and #Fedilab. Maybe get @delta on board too?
Is there any #ActivityPub / #Mastodon URI scheme used in the wild that would allow me to open an ActivityPub account directly in my Android app?
I've seen 'acct' and 'web+ap' mentioned but none seem to be implemented.
The goal is that given a text of "Here is my Mastodon profile acct:daniel@gultsch.social" #Conversations_im can link that directly into #Tusky. (Just like mailto and xmpp URIs open my E-Mail or IM app respectively)
@alienghic the short answer is yes. The longer answer is: it depends and 'military' isn’t a homogeneous use-case. There are certainly armed forces and intelligence agencies that use a fairly vanilla #Conversations_im.
If you're still recommending #Signal, you may have missed the tech oligarchs' takeover of the US government. The best time to recommend European alternatives was 8 years ago; the second best is now.
Absolutely nobody knows what an XMPP address is, so just go ahead and call it a:
I don’t usually do this kind of evangelism, but if you’re looking for a reason to try #XMPP on #GlobalSwitchDay, now’s the perfect time: #Conversations_im is currently free on Google Play!
https://play.google.com/store/apps/details?id=eu.siacs.conversations
I love open source, and I want young people to know there’s a career path outside of #FAANG. Open source can be financially sustainable—it just gets super hard if one of your key goals is making your investors even richer. #Conversations_im is about the same age as #Matrix. I never took VC funding, and I’m doing fine.
#Conversations_im and #BlabberIm traditionally had compatible backup formats. However the backup format has changed in the two years since Blabber has been abandoned. To migrate to Conversations and keep your history do the following:
· Create Backup on Blabber
· Install version 2.12.7 of Conversations from F-Droid and restore backup. Do not activate the account!
· Upgrade to latest Conversations.
· Optionally: Create another backup and migrate to the Play Store version.
It’s time to stop using Blabber.im
The abandoned fork of #Conversations_im has a critical security issue: attackers can bypass STARTTLS negotiation, resulting in an unencrypted connection to a fake server. This vulnerability is similar to the STARTLS attack discovered in various email clients¹
Fixed in Conversations 2.13.1 (Feb 2024)
Please migrate to Conversations immediately! It's free on Google Play until the end of the year and always free on #fdroid
Continuing a decade-long tradition #Conversations_im is currently available for free on Google Play.
https://play.google.com/store/apps/details?id=eu.siacs.conversations
Merry Christmas 
Happy Holidays 
and have fun at #38C3
Did you know that you can configure custom notification sounds per contact or group chat in #Conversations_im?
Apparently not many people knew that so the next version will make, what essentially is a native Android feature, easier to access via the overflow menu of contact or group chat details.
It is pretty cool that #Conversations_im sales have been paying my rent for the last 10 years.
Not everything needs to be a subscription.
Constantly begging for donations or ratings is not something you will see #Conversations_im do. An instant messaging app should benefit its users not its developers.
At the #XMPP Summit − after a topic is well-discussed and a rough consensus reached − someone needs to volunteer to write the XEP.
Last year, I volunteered to write the XEP for synchronizing read states across devices.
It's called Message Displayed Synchronization and is now in Last Call, where community feedback is gathered before a XEP becomes 'stable.'
https://xmpp.org/extensions/xep-0490.html
Prototype implementations are in @Monal and #Conversations_im.
Good news and bad news.
#Conversations_im 2.17.0 has support for emoji reactions 
Since @Codeberg appears to be under constant DDoS attacks they have added pretty strict rate limits that the @fdroidorg build server keeps running into. 
Another build cycle just failed and it's unclear when 2.17.0 will be available on F-Droid.
Maybe Codeberg and F-Droid can back channel an allow list or something? 
Continuing a tradition #Conversations_im is available for free on the Google Play Store for the next 7 days.
https://play.google.com/store/apps/details?id=eu.siacs.conversations
@christian @larma We (The XSF / People who write and implement XEPs) have a tendency to wait with advancing a XEP to stable until we have sufficient implementation experience.
Your question (which matters more for end users) should be: Why hasn't this been implemented?
Implementing reactions is not as straight as it might seem. Both #Conversations_im and #Gajim wanted to rewrite the database layer to accommodate this feature. On the Conversations side we also wanted to rework the UI before this.
