1. Rivaling clients to Whatsapp. 2.
Uncategorized
7
Posts
3
Posters
0
Views
-
RE: https://gultsch.social/@daniel/115751087451745641
1. Rivaling clients to Whatsapp.
2. Incredible simplification, people don't want, cannot afford to learn what OMEMO is, "this message has been encoded for another device" is a humongous UX failure.
3. Consistency among clients.
4. Consistent "send voice message" button, consisten "send short video" button, consistent "send live location" button. Go to reason 1.
5. Less FOSS now, paid later projects. Why are most free on F-droid and paid-for in Google Playstore?
6. An iOS client that doesn't look as ugly as Shrek doing yoga.
7. Clip button should only be for attachments, not for everything (Conversations) -
RE: https://gultsch.social/@daniel/115751087451745641
1. Rivaling clients to Whatsapp.
2. Incredible simplification, people don't want, cannot afford to learn what OMEMO is, "this message has been encoded for another device" is a humongous UX failure.
3. Consistency among clients.
4. Consistent "send voice message" button, consisten "send short video" button, consistent "send live location" button. Go to reason 1.
5. Less FOSS now, paid later projects. Why are most free on F-droid and paid-for in Google Playstore?
6. An iOS client that doesn't look as ugly as Shrek doing yoga.
7. Clip button should only be for attachments, not for everything (Conversations)8. Stick to a name either Jabber or XMPP, not both. It's confusing.
9. Make people aware of how many things are Jabber in disguise (Whatsapp, Grindr, Google Hangouts, etc) with a corporation behind monetising it using the people as the product.
10. Incentives for running servers. In Mastondon we're really good at justifying donating to our admins when they run a decent service.
11. RFCs or XEPs written as easy to read an implement as NIPs.
12. Attached directories. XMPP is directoryless same as email, what about searching people by their Mastodon handle, by their email handle, use WebFinger. -
8. Stick to a name either Jabber or XMPP, not both. It's confusing.
9. Make people aware of how many things are Jabber in disguise (Whatsapp, Grindr, Google Hangouts, etc) with a corporation behind monetising it using the people as the product.
10. Incentives for running servers. In Mastondon we're really good at justifying donating to our admins when they run a decent service.
11. RFCs or XEPs written as easy to read an implement as NIPs.
12. Attached directories. XMPP is directoryless same as email, what about searching people by their Mastodon handle, by their email handle, use WebFinger.Right now IMHO the client that needs desperately the most investment in time and COMMUNITY engineering effort is Conversations.im .
Monocles for example, need someone to implement OMEMO to WebXDC which is the uniquely interesting feature of DeltaChat. Pixelsocial is incredible for in-group private rolls (could literally take the power away from neighbourhood/thematic facebook groups).
Give her a hand! https://codeberg.org/monocles/monocles_chat/issues/353
I'd be happy as fuck to help any of this projects if they were using Kotlin Multiplatform or the RFCs of XMPP were as understandable as NIPs, but they arent
-
Right now IMHO the client that needs desperately the most investment in time and COMMUNITY engineering effort is Conversations.im .
Monocles for example, need someone to implement OMEMO to WebXDC which is the uniquely interesting feature of DeltaChat. Pixelsocial is incredible for in-group private rolls (could literally take the power away from neighbourhood/thematic facebook groups).
Give her a hand! https://codeberg.org/monocles/monocles_chat/issues/353
I'd be happy as fuck to help any of this projects if they were using Kotlin Multiplatform or the RFCs of XMPP were as understandable as NIPs, but they arent
My partner (du-jour) struggles to configure Conversations because there's no Spanish translations of it. He can't disable its nofications on his watch because of this.
And I would be happy using Monocles if WebXDC worked without cumbersome steps in between (read the issue before this toot). I can follow those steps with @surfhosting because we're tech saavy, but most of humanity isn't. Hence they need Whatsapp simplicity.
UX rule number 1 = if users need a manual you've failed. This is pretty much the reason Apple refries tech better. They are a UX-centred company. It's also why it bores power-users.
-
8. Stick to a name either Jabber or XMPP, not both. It's confusing.
9. Make people aware of how many things are Jabber in disguise (Whatsapp, Grindr, Google Hangouts, etc) with a corporation behind monetising it using the people as the product.
10. Incentives for running servers. In Mastondon we're really good at justifying donating to our admins when they run a decent service.
11. RFCs or XEPs written as easy to read an implement as NIPs.
12. Attached directories. XMPP is directoryless same as email, what about searching people by their Mastodon handle, by their email handle, use WebFinger.@maikel Since you mentioned that before: what are NIPs?
-
My partner (du-jour) struggles to configure Conversations because there's no Spanish translations of it. He can't disable its nofications on his watch because of this.
And I would be happy using Monocles if WebXDC worked without cumbersome steps in between (read the issue before this toot). I can follow those steps with @surfhosting because we're tech saavy, but most of humanity isn't. Hence they need Whatsapp simplicity.
UX rule number 1 = if users need a manual you've failed. This is pretty much the reason Apple refries tech better. They are a UX-centred company. It's also why it bores power-users.
#Spanish is the most-spoken EU language worldwide, so #Conversations_im should have a translation.
@daniel, is there e.g. a #weblate instance or similar, where the #freeSoftware and #Jabber community could help?
-
#Spanish is the most-spoken EU language worldwide, so #Conversations_im should have a translation.
@daniel, is there e.g. a #weblate instance or similar, where the #freeSoftware and #Jabber community could help?
@debacle @maikel @surfhosting According to https://translate.codeberg.org/projects/conversations/-/es/ the Spanish translation is complete.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
- A quanto le vende le aragoste?
- Vive 80 euro al kilo, morte 40 euro
- Ok, me ne ammazzi due, allora
-
La #Cina è (sempre più) vicina. Il "progetto Manhattan" di Pechino | Il Foglio https://www.ilfoglio.it/tecnologia/2025/12/19/news/il-progetto-manhattan-cinese-8453648/
-
@mariusor@metalhead.club Fair point! To clarify: FediChatBot is just a tech demo for @botkit@hollo.social, the ActivityPub bot framework I've been building. BotKit itself has nothing to do with LLMs—it's for creating any kind of fediverse bot (weather bots, notification bots, RSS feeds, etc.). I just happened to use an LLM for the demo since it makes for an interactive example. Not advocating for AI integration in the fediverse, just showcasing what the framework can do.
-
@_elena It is deeply sad and chilling in equal measure that there is this lazy reliance because mental faculties are atrophying. Attention, patience, critical thinking, questioning things ... and all the while writing can be wonderfully cathartic.
-
@misantropo70 colpito a morte mentre stavi facendo del bene.
Maledetti!
-
@francina1909 io morto ieri (credo) durante la donazione sangue. Stavano passando tutte le canzoni di Natale quindi direi anche quella.
-
@_elena At your daughter's age, it is also an ideal time to start learning a second language. A smart teacher once told us that each parent should pick a different language and only speak to our daughters in that language. As teens and adults they are now as fluent in both English and French as native speakers. It has given them the ability to attend schools in multiple countries without any language barriers.
-
The "UNIX v4 tape" running in simh PDP11 emu on IRIX:
