<![CDATA[We should rethink how the communitcation channels for piefed devs work]]>So currently, we have two different closed-off 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.

The other issue with this is the closed-off nature of these real-time chat applications. Shure, anyone can join, but answers to technical questions will inevitably get burried in unstructured long chatlogs, which no new develloper will read through. That will lead to a lot of questions being asked, that were already answered previously.

If we abandoned these channels in favor of one unified piefed community (like piefed-devellopment@piefed.social) or something, we could build a good knowledge base of answered questions, that are easy to search through and look around in and will also get indexed by search engines. This will make it easier and easier for new developers to join over time, as they will be able to look through an increasingly extensive knowledge base if they have any questions and also easily find the people, that are willing to help them.

Funnily enough, Rimou has already talked about the advantages of a forum-like communication channel for open source devellopers, so i think it's time for us to apply this to our own project.

]]>https://citiverse.it/topic/879ac366-80b7-4f19-9d55-5b871c9844c8/we-should-rethink-how-the-communitcation-channels-for-piefed-devs-workRSS for NodeSat, 11 Apr 2026 13:29:52 GMTWed, 08 Apr 2026 17:56:45 GMT60<![CDATA[Reply to We should rethink how the communitcation channels for piefed devs work on Wed, 08 Apr 2026 20:41:22 GMT]]>> @sibbo@sopuli.xyz said:
>
> I think the modern way of handling support for open source software is discourse.

I'm also going to go out on a limb and say that this seems to be the case because Jeff Atwood put his name behind Discourse. He's a big name (he's also an outspoken blogger who rubs some people the wrong way, but I digress...) Lots of open-source projects just happen to find Discourse first instead of other good forums like NodeBB and Flarum.

To each their own.

]]>https://citiverse.it/post/https://activitypub.space/post/1749https://citiverse.it/post/https://activitypub.space/post/1749Wed, 08 Apr 2026 20:41:22 GMT<![CDATA[Reply to We should rethink how the communitcation channels for piefed devs work on Wed, 08 Apr 2026 20:38:31 GMT]]>Personally, if you're going to pick a forum, I would recommend NodeBB

(caveat; I work on NodeBB)

It federates well with Piefed out of the box (Discourse federation is lagging well behind), has private forums and real-time chat. Robust plugin system, themes, PWA, open API for whatever functionality you want to build 🙂

However, if we're splitting hairs, I agree with @deckpacker@piefed.social in that you might as well just use Piefed directly. I am a big fan of dog fooding.

But if @rimu@piefed.social prefers the forum approach, I am here to help.

]]>https://citiverse.it/post/https://activitypub.space/post/1748https://citiverse.it/post/https://activitypub.space/post/1748Wed, 08 Apr 2026 20:38:31 GMT<![CDATA[Reply to We should rethink how the communitcation channels for piefed devs work on Wed, 08 Apr 2026 19:46:57 GMT]]>Like skavau mentioned elsewhere, the realtime chatrooms do serve a useful purpose. It is more freeflowing and responsive. So, it's nice to do things like realtime debugging or issue resolution (a lot of other piefed admins are there to provide expertise). Also, we have gone there in the past to brainstorm different feature ideas or ways to solve an issue, just to kind of get a temperature check from some power users there.

]]>https://citiverse.it/post/https://crust.piefed.social/comment/328770https://citiverse.it/post/https://crust.piefed.social/comment/328770Wed, 08 Apr 2026 19:46:57 GMT<![CDATA[Reply to We should rethink how the communitcation channels for piefed devs work on Wed, 08 Apr 2026 19:36:14 GMT]]>Having back and forth chat on a bunch of issues in Matrix or Zulip has been very useful. It's just a different format than the Reddit/forum-esque experience of here.

]]>https://citiverse.it/post/https://piefed.social/comment/10879975https://citiverse.it/post/https://piefed.social/comment/10879975Wed, 08 Apr 2026 19:36:14 GMT<![CDATA[Reply to We should rethink how the communitcation channels for piefed devs work on Wed, 08 Apr 2026 19:34:47 GMT]]>What's wrong with a simple piefed community?

]]>https://citiverse.it/post/https://piefed.social/comment/10879957https://citiverse.it/post/https://piefed.social/comment/10879957Wed, 08 Apr 2026 19:34:47 GMT<![CDATA[Reply to We should rethink how the communitcation channels for piefed devs work on Wed, 08 Apr 2026 19:30:21 GMT]]>All I can say here is: Come on Fluxer. Do something.

]]>https://citiverse.it/post/https://piefed.social/comment/10879906https://citiverse.it/post/https://piefed.social/comment/10879906Wed, 08 Apr 2026 19:30:21 GMT<![CDATA[Reply to We should rethink how the communitcation channels for piefed devs work on Wed, 08 Apr 2026 19:29:16 GMT]]>I think I know the solution. Retrofit PieFed with live group chat channels alike Discord text channels(?) (done with ActivityPub of course). Make the Wiki pages federate. And then eat our own dogfood.

I think that'd be a good long term goal. Unfortunately it's a lot of work. I don't think group (live) chat is specified in AP. We probably want encryption and that's a hassle. And there's some hurdles in implementing Wiki federation as well. (And we do like 5 bazillion other things in PieFed so I'm not sure about the prioritization of something like this.)

]]>https://citiverse.it/post/https://palaver.p3x.de/comment/3813359https://citiverse.it/post/https://palaver.p3x.de/comment/3813359Wed, 08 Apr 2026 19:29:16 GMT<![CDATA[Reply to We should rethink how the communitcation channels for piefed devs work on Wed, 08 Apr 2026 19:27:03 GMT]]>I think, that the vast majority of pieced developers is actively using piefed (or some piefed-compatible software) though, because otherwise, how would you even think of contributing to a project like that?
Is not breaking some peoples habits really worth all the negative aspects of realtime chat platforms like Zulip or Matrix?
I think there would be some huge upsides, if we explicitly told people on the codeberg page to post their questions to our forum instead of asking it on matrix/zulip.

]]>https://citiverse.it/post/https://piefed.social/comment/10879862https://citiverse.it/post/https://piefed.social/comment/10879862Wed, 08 Apr 2026 19:27:03 GMT<![CDATA[Reply to We should rethink how the communitcation channels for piefed devs work on Wed, 08 Apr 2026 19:17:27 GMT]]>A development focused community isn't a bad idea, really. rimu has mentioned in the past that we need to dogfood our own platform more. We have some specific ones already:

  • for css customization - !piefed_css@piefed.social
  • for api questions/updates - !piefed_api@piefed.social
  • for plugins - !piefed_plugins@piefed.social

But, having a catch-all everything else might be useful. The closest thing we have to this currently is the codeberg repo. There is lots of info to be found in codeberg issues and PR's and I find myself linking those quite often in matrix discussions. However, it isn't something that casual users usually know how to navigate or search.

The different chat platform options are there mainly to help meet people where they are. Lots of the fediverse uses matrix, so many people only really reach out to us on there. We made a zulip instance to help address some of the shortcomings of the matrix chatroom since Zulip allows for topic-based organization in a kind of hybrid between a chatroom and a forum. However, the number of people using zulip is far smaller than matrix.

]]>https://citiverse.it/post/https://crust.piefed.social/comment/328661https://citiverse.it/post/https://crust.piefed.social/comment/328661Wed, 08 Apr 2026 19:17:27 GMT<![CDATA[Reply to We should rethink how the communitcation channels for piefed devs work on Wed, 08 Apr 2026 18:48:17 GMT]]>Maybe a Loomio instance linked to the chat would be best?

]]>https://citiverse.it/post/https://slrpnk.net/comment/21692247https://citiverse.it/post/https://slrpnk.net/comment/21692247Wed, 08 Apr 2026 18:48:17 GMT<![CDATA[Reply to We should rethink how the communitcation channels for piefed devs work on Wed, 08 Apr 2026 18:24:46 GMT]]>Yeah, I've seen some projects use that, but I see no reason to, considering it's not FOSS and piefed is really well suited for this exact purpose.

]]>https://citiverse.it/post/https://piefed.social/comment/10879148https://citiverse.it/post/https://piefed.social/comment/10879148Wed, 08 Apr 2026 18:24:46 GMT<![CDATA[Reply to We should rethink how the communitcation channels for piefed devs work on Wed, 08 Apr 2026 18:21:43 GMT]]>I think the modern way of handling support for open source software is discourse.

]]>https://citiverse.it/post/https://sopuli.xyz/comment/22889219https://citiverse.it/post/https://sopuli.xyz/comment/22889219Wed, 08 Apr 2026 18:21:43 GMT