I have continued working with Kiwi IRC's lead developer. I brought up
the topic of KDE and showed him their Etherpad, which listed all sorts
of requirements and nice-to-haves for a messaging solution. In response,
he said he is willing to work with KDE and LibreOffice to build a
platform that we can be happy with.
I posted my proposal to KDE community list:
https://mail.kde.org/pipermail/kde-community/2017q3/003857.html
For convenience, I will include below the text that the Kiwi dev wrote
after reading KDE's requirement list:
Kiwi Next is the next generation of the Kiwi IRC client, specifically
aiming to bring modern interfaces and ease of use from platforms such as
Slack to IRC.
Many communities have established environments built up around IRC so
any features or additions that Kiwi IRC brings will be 100% IRC
compliant throughout and put to the IRCv3 working group so that other
clients and servers may also make use of the functions.
The UI for Kiwi Next is getting tested on all major browsers including
mobile, with translations being made available for 28 languages to make
sure that anybody trying to be part of a community can do so.
Keeping people connected to IRC so that they may receive notifications
on their desktop and/or mobile is a huge feature currently missing from
IRC. This is currently being developed directly into Kiwi IRC so it is
available out of the box with minimal fuss. Once connected and logged
into your existing network services, a user can then simply resume their
session with complete message history and searching. This is a feature
that will be introduced on kiwiirc.com very soon but also entirely open
source to be used anywhere. Works very similar to ZNC in that Kiwi acts
as a normal IRC client which means any IRC client can make use of the
same server.
A lot of the points mentioned are very much inline with the aims for
Kiwi Next, most likely due to the same mindset: Slack + IRC merged
together with some IRCv3 features thrown in.
Some quick overview points:
* 100% standards compliant
* Part of the IRCv3 working group to improve IRC itself
* Open source with an available hosted solution
* Use existing infrastructure and tools
* Multilingual and accessible
* Web based while still allowing desktop clients to be used
* Has already been tested with thousands of users in a single channel
flood fest
* Built in media preview (images, videos, PDFs, anything that can be
embedded)
Soon to be released:
* Team based channels that supports @everybody highlighting
* Switchable message views such as traditional IRC view and a more
relaxed avatar + relaxed view
* Message reactions (Using IRCv3 standards so they work with other
clients too)
In development at the moment:
* Built in BNC with desktop/mobile notifications
* Use Kiwi IRC and a desktop client on the same account at the same time
(similar to ZNC)
* Message history + searching + exporting
* File sharing by uploading files through the UI, with optional file
history
Not in development but can easily be added into Kiwi Next if required:
* Replying to a message with a reference/quote
* Editing messages
* Annotate images linked/shared through the client
* Stickers between Kiwi clients or between all IRC clients
--
To unsubscribe e-mail to: projects+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-projects] On the communication channels we use (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.