qpixel code apparently bakes in codidact.com network in places

[cellio]

I'm looking at the dev server and I see the network footer on pages, including the list of sites. A suspension message also included a link to Meta, and I think I saw another Meta link. If somebody else were to run an instance from our repo, these connections would be confusing or wrong.

Ultimately we should figure out how to separate instance from platform, which probably involves configuration knobs and "plug in your footer here" and stuff. In the shorter term, can we document what people will need to change? Is searching the code for "codidact.com" enough to find all the connections and change/remove them? I don't want this to become an onerous task, but it'd be nice to be able to give people a heads-up and suggestions about what to do about it until we get around to separating them.

[Trilarion]

Setting up ones own instance and acting as if it would be an independent QPixel instance is one way of finding out. For example additionally to the network footer, there is also a Codidact side panel (the one with the donate button). While for example the help center is completely empty (there should be at least one test page). The Codidact specific content should all go to a "Codidact flavour of QPixel" repository and some (like the logos) must already be there, but there seem to be several possible candidates for that (docs, community-list)

[cellio]

See https://github.com/codidact/qpixel/issues/826#issuecomment-1214395898 for a list of hard-coded Codidact references.

[MoshiKoi]

See https://github.com/codidact/qpixel/issues/826#issuecomment-1214395898 for a list of hard-coded Codidact references.

Should we close this as a duplicate of the other issue?

[cellio]

Good idea. The other issue has a list of where the hard-coded references are, so let's use that one.