Pidgin 3 MVP requirements

Applications Pidgin
1

This post is mainly geared towards pidgin and protocol developers, but as I keep getting reminded, Pidgin 2’s days on Wayland are getting shorter and shorter and we need to get Pidgin 3 usable.

So I would like to know, what are you’re absolute required features to start using Pidgin 3 as soon as possible. I know I’ve been heads down and in the weeds a bit about making things work long term, but I’m certain I’m overlooking some simple stuff that would be easy wins.

This list will help me decide what to focus on, but please be reasonable. We’re trying to find a way to an MVP, so if you’re like Voice and Video with NAT traversal, realize that that’s not what I’m asking for here :wink:

So here’s a quick list for me personally

  • Account re-connection
  • Zulip channels
  • Image attachments
  • Reactions but not super high importance
1 Like
2

The biggest issue for me right now is that accounts disconnect after a while. But I think that’s already point number one on your list. Also Zulip channels would be number two for me.

1 Like
3

I think my list will be not be helpful. I think I have already seen every single point somewhere – I just did not come around to try them in my plug-ins, yet.

  • message persisting mechanism – I use Pidgin not only for the conversation, but conservation of the chat history is actually more important to me (I do not care whether that is plain files or an unencrypted database)
  • file transfers – receiving and sending attachments in channels and DMs (whether images are embedded into the conversation view or not is secondary to me)
  • signal for "this message has (probably) been displayed and read (the user interacted with the conversation in some way) – requested by an early user
2 Likes
4

Thanks for your input.

message persisting mechanism – I use Pidgin not only for the conversation, but conservation of the chat history is actually more important to me (I do not care whether that is plain files or an unencrypted database)

Working on it, but that’s still a beta or rc feature, not an mvp one.

file transfers – receiving and sending attachments in channels and DMs (whether images are embedded into the conversation view or not is secondary to me)

We call these attachments in purple 3. Everything is there for them except persistence and the ui doesn’t display or give you an option to add them yet.

File transfers are peer 2 peer file transfers like DCC in IRC for example.

signal for "this message has (probably) been displayed and read (the user interacted with the conversation in some way) – requested by an early user

This will most likely be a beta or rc feature.