Please only vote if you have contributed to PieFed in some capacity (e.g. coding, translation, reporting bugs, discussing bugs) or might in the near future!

Currently, we have two different developer chats on Zulip and Matrix. This means, that new devs will be confused about which channel to join and experienced devs have to actively look around in both channels for questions to answer. This seems like a really inefficient system, so we should at least decide on one official communication channel.

More discussion at https://piefed.social/c/piefed_meta/p/1964543/we-should-rethink-how-the-communitcation-channels-for-piefed-devs-work

Personally I find Matrix to be a pain in the ass and prefer Zulip. But it hasn't managed to attract as many users as Matrix has despite pushing it quite hard for months. Also PieFed development has started to bleed over into PieFed naturally, such as !piefed_css@piefed.social and !piefed_plugins@piefed.social. So we're in an awkward place at the moment.

31% A PieFed community, only
3% chat.piefed.social - Zulip
10% Matrix channel
18% PieFed + Zulip
21% PieFed + Matrix
13% PieFed + Zulip + Matrix
3% Zulip + Matrix (what we have now)
3% Zulip
39 votes - ended 7 months ago
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 7 months ago

software incompatibilities with other Apub software.

You can just make it federate encrypted data. At least for first only PieFed would be able decrypt the private messages, but eventually at least mBin would join for sure. Safe private messaging would be a very useful feature in any case!

Having to create an account in a specific instance is too much asked, IMO. But having to create an account on some instance supporting a specific feature does feel reasonable, at least to me.

  • source
  • parent