Pimalaya "Loose End" c/o Matrix Ecosystem

[blaggacao]

Even if that's not the classical definition (?), a sensible and modern interpretation of PIM would involve chat. If PIM can be seen as a "personal CRM", i.e. a system to organize communications and associated contacts, then I can't come up with a sensible definition that wouldn't involve chat.

In the same space of foundational technologies, as Pimalaya is situatied, we have the Matrix chat protocol. Disregarding any concrete implementation of chat, Pimalaya may choose the Matrix protocol as a de-facto open standard and provide well-defined integration points towards that ecosystem so that third parties can build useful integrations on top.

The intuition behind this idea, rather to implement and maintain something in-tree, is to make it clear that Pimalaya has thought chat alongside the rest of PIM and concretely show third parties how integration points where designed and conceptualized, eventually backed by a minimal library implementation, if that turns out to make sense, at all.

In my opinion, it wouldn't be a bad idea to brainstorm this further.

Examplification: #4

[soywod]

I totally agree with you, and I definitely want (at some point) to propose chat services. But it is not a priority for me, as there is so much more to do before. Domains like mail, contact and calendar (task, event, todo, journal, alarms) really lack of tools, and I find them more important that chat at this point.

[blaggacao]

and I find them more important that chat at this point.

Absolutely! In addition chat is really well covered by the matrix ecosystem. Once you turn your attention to this domain, I'd hope that it would be as easy and maintenance-lightweight as possible by just adding integration points and otherwise offload to Matrix (which can bridge almost all other chats already).