Post · bonfire.mavnn.eu

Post

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)

#XMPP #WhatNeedsDone

monal-im.org :xmpp:

@Monal@fosstodon.org replied · 6 days ago

@maikel monal is looking like shrek doing yoga? How's that?

Maikel 🇪🇺 🇪🇸

@maikel@vmst.io replied · 6 days ago

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.

#XMPP #WhatNeedsDone

Debacle

@debacle@framapiaf.org replied · 6 days ago

@maikel

Maybe it's just me, but:

#XMPP is the protocol, like "HTTP" or "SMTP" etc.

#Jabber is open, federated, standard chat. Similar to "web" or "email".

CiscoJabber™ is that thingy nobody cares about, not even Cisco.

Maikel 🇪🇺 🇪🇸

@maikel@vmst.io replied · 6 days ago

@debacle To me XMPP is the specification while Jabber the most common consensus implementation of the FOSS version of it. But I guess it's just matter of opinion really.

Even Wikipedia disagrees with us.

https://en.wikipedia.org/wiki/XMPP

Whatever it needs, it should change the logo to somehitng more arsehole-ish, it seems to work better.

XMPP - Wikipedia

Daniel Gultsch

@daniel@gultsch.social replied · 6 days ago

@maikel Since you mentioned that before: what are NIPs?

Maikel 🇪🇺 🇪🇸

@maikel@vmst.io replied · 6 days ago

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

#XMPP #WhatNeedsDoing

Maikel 🇪🇺 🇪🇸

@maikel@vmst.io replied · 6 days ago

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.

#XMPP #WhatNeedsDoing