Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Caveat: I am not an online IP expert. I believe the main obstacles would be: Copyrights and attribution. Copyrights The safest and always-valid way to circumvent this obstacle is not to copy ans...
#1: Initial revision
by
einpoklum
·
2025-08-11T21:11:41Z (about 1 year ago)
Caveat: I am not an online IP expert. I believe the main obstacles would be: Copyrights and attribution. ### Copyrights The safest and always-valid way to circumvent this obstacle is not to copy answers verbatim. Read the answer elsewhere, absorb the knowledge, then write your own answer along similar lines. Also, write your own code rather than copying it. If that is impracticable for some reason - you need to determine what copyrights the answer on the chat, or wherever, is posted with; and make sure you observe those. In particular, when reproducing the answer here, make sure that you have the right to redistribute/republish the answer under that license. If you aren't sure - ask on meta on this site, or, well, on opensource.stackexchange.com (but maybe there's another network site on codidact which could be used instead? I don't know). ### Attribution If writing your own answer, still give credit to the discussion on the chat you had read. Say that your answer is "based on the approach described at" or something appropriate. If copying an answer from elsewhere - always always say where you copied the answer from: Site name, URL, and page name/title/subject if relevant.