FOSS server implementation

61

38

11

0

0

22

Must-have

Ability to host our own server

31

33

29

0

0

39

Must-have

FOSS clients available for desktop (at least Linux/BSD + Windows) as well as mobile

54

54

10

0

0

14

Must-have

Full-featured, patent-free and stable specification or API for writing clients (e.g. for Plasma Mobile)

41

46

20

0

0

25

Must-have

Open governance (user/dev community is setting direction of software, spec, and/or service), not tightly controlled by a single company

26

33

30

0

0

43

Must-have

Free of charge (clients and server)

52

51

12

0

0

17

Must-have

Defined protocol specification (i.e. not implementation-defined)

27

29

23

0

1

52

Must-have

Anonymity: When using an account, all details (names, e-mail addresses ...) are optional and hideable, no SIM requirement

40

29

23

0

2

38

Must-have

Modest bandwidth usage both for server and client

21

21

33

0

0

57

Must-have

Legal to use in all countries with KDE contributors or users

36

32

19

0

1

44

Must-have

Easy ability to temporarily set yourself to unavailable, muting notifications and making the unavailability visible to others

27

19

27

1

0

58

Must-have

Ability to mute notifications from specific channels

39

31

20

0

0

42

Must-have

Listing of all public channels in a namespace, with search function

23

22

35

0

1

51

Must-have

Good bridge to IRC exists (stable and reliable, no individual setup per channel, as close to the un-bridged experience as possible)

19

20

27

0

1

65

Must-have

Easy way to share files

23

19

29

0

11

50

Must-have

Possibility to create channels / groups that are accessible only upon invitation (also restricting access to that channel's logs and, if available, shared files).

32

13

28

0

10

49

Must-have

Ability to define admins/moderators/roles for channels with ability to ban users

55

25

13

0

1

38

Must-have

Ability to set a channel topic

20

19

29

0

1

63

Must-have

Channels can continue to exist if their creator leaves them or deletes his/her account

48

28

21

0

1

34

Must-have

Encrypted communication possible

29

45

25

1

0

32

Must-have

Client is well integrated with Plasma (uses standard notifications, no x-embed tray icon, uses native file dialogs, etc)

21

27

39

0

0

45

Must-have

Client has good accessibility

25

20

26

0

1

60

Must-have

Client has good performance and usability in large (500 users) and very active (>60 messages per minute) channels

42

32

19

1

0

38

Must-have

Client has good performance and usability for users that are active in lots of channels (30+)

43

21

21

1

0

46

Must-have

Client has low resource usage (so most likely no web or electron apps)

37

35

26

0

0

34

Must-have

Federated (i.e. if KDE hosts our own server, we can still communicate with people on other servers)

14

24

37

1

4

52

Must-have

Permanent history across mobile and desktop clients out of the box, including messages sent while offline

15

19

35

0

8

55

Attractor

Uses a port that is usually open even on public networks (e.g. in universities)

15

19

39

0

0

59

Attractor

IRC-like GUI available (high information density, fully tabular layout)

20

16

18

0

8

70

Inclusion

Support for multiple accounts within the same client, being able to log in with multiple accounts at the same time

17

11

25

0

1

78

Inclusion

Can be used without having to sign up for an account

15

13

30

0

8

66

Inclusion

Migration path from current solution 

22

7

16

0

2

85

Inclusion

Usable from Tor or similar anonymization networks

18

10

20

1

2

81

Inclusion

Ability to automatically push Phabricator / Bugzilla notifications for a specific topic into a specific channel

6

18

36

1

0

71

Inclusion

Web client available

9

18

35

0

1

69

Inclusion

Reply to (quote) messages with reference to the original message

8

12

38

0

5

69

Inclusion

CLI client that can be ran on a X/Wayland-less server and used via ssh and similar available

15

5

35

0

2

75

Inclusion

Only limited impact on KDE server and sysadmin resources

11

8

30

0

0

83

Nice-to-have

Ability to open a channel at the oldest unread message instead of just the newest message

8

5

39

0

5

75

Nice-to-have

Bridges to other solutions which are popular within KDE (Telegram, Matrix, Rocket) exist

9

16

37

1

1

68

Nice-to-have

Ability to enter and use full name and email address (all optional) and be searchable by them

1

5

33

1

15

77

Nice-to-have

Search for shared files

4

7

27

0

13

81

Nice-to-have

User avatars

5

6

23

1

19

78

Nice-to-have

Ability to notify a whole channel and/or highlight / pin a specific message for the whole channel

5

8

28

0

11

80

Nice-to-have

Ability to open tickets on Phabricator or Bugzilla from within the chat

1

9

25

0

9

88

Nice-to-have

Telegram- or Slack-like GUI available (e.g. user avatars next to messages, whitespace between messages)

3

12

20

0

15

82

Nice-to-have

Easy way (GUI) to insert Unicode emoji into a message

5

4

27

0

10

86

Nice-to-have

Ability to broadcast messages across many channels, for example, to announce a meeting starting now

5

7

31

0

6

83

Nice-to-have

Ability to annotate images within the client, such as doodle on them, highlight or add messages to images (So that there is prompt and easy feedback on mockups for example)

0

8

28

0

8

88

Nice-to-have

Ability to explicitly highlight / notify individual users (even) if they have muted a channel

8

9

25

1

21

68

Problematic

Ability to react to a message with an emoticon (and multiple reactions with the same emoticon are simply counted)

1

3

20

0

22

86

Problematic

Ability to edit messages to e.g. correct typos (with clear indication that a message has been edited)

5

11

33

0

21

62

Problematic

Stickers

1

2

13

1

39

76

Avoid