Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Read Me Code of Conduct

Modified February 21, 2020

Code of Conduct

Any information within this post is subject to change at any time. Welcome to Code Forum! We are truly honoured to have you with us as a member of the Code Forum community and look forward to the many great things ahead. Before you start indulging in our community, we kindly ask for you to take a few moments to look over the CC of Code Forum to ensure you and other members have fun and are safe while using our website.

Help out the community by:

  1. Try to greet new members in the introduction forum! We want to show newcomers that we are a friendly community.
  2. You may reply to an old post if related.
  3. If your question gets resolved, please mark the reply as the thread "solution". This will help others who are having similar issues.
    1. Please note: It is at the Guardians Team's discretion on whether or not to give a warning on this.
  4. Share us!
Inappropriate Content:
  1. When posting you need to be sure to add some value to your post. Add lots of information, explain yourself, make your posts enjoyable to read.
    1. This shall include thread titles, or titles or resources, media items.
  2. Make yourself understood. Use proper grammar to the best of your ability. We understand that English may not be everyone’s main language, but make an attempt. You won’t get in trouble for a misplaced comma or typos, but it would help everyone if you could make sure everyone understands your message.
  3. Using people's content is okay with their consent if you were not permitted by the author of the original post/content will be removed and you shall be given a warning.
  4. Posting illegal/null and or hacking scripts is prohibited (Hacking scripts will result in a permanent ban).
  5. Any discussions regarding illegal hacking are prohibited. E.g. to take control and or access data without the permission of the owner.
  6. No sharing inappropriate pictures.
  7. Before posting a thread asking for help please review (Before asking your question), (Q&A system has changed) and (How to ask a good question).
  8. Any posts that contain pornography and child pornography will be removed and your account will be permanently banned. Local authorities will be contacted.
  9. When sharing or placing code in a thread/post please format the code using our BBCode to make it easier to read and understand by whoever is looking at your code. Check out the thread that was created about BBCode and examples on how to use it properly. Read Me - How to post your code into threads
  10. Avoid posting threads and posts that contain a wall of text
    1. this is defined as posting a large paragraph or more)
    2. Suggestion: Instead format your post in such a way that it makes it interesting and understandable. It should be straight to the point and easy to read. Perhaps add some photos, bullet points, coloured font, code examples etc.
  11. Avoid posting screenshots and or pictures of code. It makes it harder to come up with a solution to your question if we cannot copy and paste the code into our personal IDE's.
  12. Do not post threads asking for coders to code and or build a program for you. You can request guidance, or team members to assist you but do NOT ask others to do the work for you.
  13. Do not edit your original thread content and replace it with one-liners like "Solved" or "Nevermind" leave it as is, please reply to your thread stating that you have solved it and provide the solution.
  14. Do not post any sensitive data on Code Forum that may either harm or put others in danger. Including but limited to sharing emails, passwords, sensitive government information such as SSN/SIN numbers, credit cards, addresses, phone numbers.
    1. If you are needing help with managing data with code or other methods then please use a tool such as Mockaroo - Random Data Generator and API Mocking Tool | JSON / CSV / SQL / Excel or something similar to generate this data for you, do NOT use production data. When you use randomly generated data, please specify in your thread where you got the data from.
  15. No posting minified code. It makes it very difficult to read, please format your code. If using VS Code, you can use an extension called Pretty Formatter.
Inappropriate Behaviour/Language:
  1. Be respectful towards members' opinions and ideas they may have. It's fair to disagree and to have a different perspective, but present your case on why you disagree thoroughly.
  2. When replying to other member's post try to stay on topic, although we will not penalize you, we strongly encourage you to not divert from the topic. E.g. the post is about HTML, but you decide to start talking about cats.
  3. Use common sense. This includes but is not limited to avoiding spamming, being excessively rude or arguing against the staff members. If you have a conflict with a member or a staff member, contact the administration through a private message rather than having heated debates in the forum discussions. Avoid using Vulgar, offensive or otherwise obscene names towards staff or another member.
  4. Unwelcoming behaviour is not tolerated at Code Forum; this is in regards to posts or replies where statements such as "Google it, search google" and or "that's a stupid question" will result in a warning. We are a community, we help each other, encourage each other.
  5. Please provide more than just a simple answer to a question. It would be helpful to include an explanation, facts, and examples to better illustrate your point.
    1. It's important to remember that the author or member may not have coding experience and is only looking to make minor adjustments to their website. In these cases, providing a solution with a brief explanation may be the easiest option.
  6. Do not use 'bump' within 24 hours of thread creation, and or if the post has not had any activity for 24 hours.
    1. Modifying and or changing a topic and posting a reply with information DOES NOT count toward a bump.
    2. Example: You posted about needing help with C++ but figured out part of your problem before anyone could help you, then you may post a reply.
      1. Use 'bump' when you have nothing further to add but wish to bring your or another thread back to the top for more information and or an answer to the thread.
  7. If you have more than one account and one of them is banned - then all accounts under your IP address will be banned as it will be taken as you are evading a ban. However, in special circumstances, you may be given an exemption which must be approved by an Administrator.
  8. We kindly ask for your patience while awaiting a response to your thread. It may take a few days for someone to answer your post. Please refrain from repeatedly PM'ing or replying to your thread (this refers to someone replying without supplying additional context), as it can be perceived as disrespectful and may result in a warning.
    1. Staff members may not know every answer and are not expected to provide answers;
    2. Members (including you) are not expected to provide answers if you chose not to.
Inappropriate Advertising / Spam:
  1. Please do not advertise other developing communities on Code Forum (other forums, discord servers, slack and other platforms). You may, however, reference a resource or a tutorial/guide.
    1. This may also include:
      1. Services and or products you (others) provide.​
  2. Do not promote sites on Code Forum; this may include but is not limited to forum threads, profile posts, private messaging and or any other affiliation to Code Forum.
    1. However, if you are seeking help with your website, app or any other development then you can share a link to help you and others solve your issue.
    2. NEW There is an exception to this rule, you may add a link to your website to your signature and or profile about section. However, you cannot add links advertising your paid service or offerings unless you have received prior permission from the administration team.
      1. An example of what's not allowed:
        • example.com new offers available.
        • example.com offering 10% off.
        • example.com hosting available.
      2. An example of what's allowed:
        • example.com Here is my portfolio website.
        • example.com check out my app that I created.
        • example.com check out my open sourced project.
  3. When providing links to solutions or articles; please explain the context of the link. The right way of sharing links would be: "Code Forum - Where your coding journey begins is where you can get help with coding!" NOT "Code Forum - Where your coding journey begins." Visitors and coders should know where the link is going to direct them.
    1. OPTIONAL: Share the solution/content within the thread followed by the source URL. This will help reduce the amount of clicks for coders when trying to find their solution.
Resources & Media Services:
  1. All media and or resources published to resources/media must be approved by an administrator before it can be seen publicly.
  2. Any posts that contain pornography and child pornography will be removed and your account will be permanently banned. Local authorities will be contacted.
  3. Posting illegal/null and or hacking scripts is prohibited (Hacking scripts will result in a permanent ban).
  4. If you plan on buying resources, be sure that the resource exists first and that it meets your expectations.
    1. Report if you get scammed to administration immediately and contact your bank; scamming will result in account restriction.
  5. Posting of 'paid' services and goods is prohibited. We are a free community.
Participating in Events & Contests:
  1. If you have more than 1 account here at Code Forum, you may ONLY use one to participate. If you are caught with multiple accounts participating, all your accounts will be banned for a period of 7 days. And, you will not be able to participate again.
Recommend precautions (OPTIONAL):
  • We advise that you don't share any personal information that could expose your privacy but it is truly up to you on what you share. By this, we mean anything that is publicly displayed via posts or profiles.
    • Name
    • Age
    • Phone Number
    • Email addresses such as [email protected]
    • Address
    • Your IP
    • We advise that you avoid using your real name in your username, post and anywhere else on Code Forum.
      • CodeSkrill Ok username.
      • JohnCode Ok but still try to avoid using any of your names.
      • John Doe Not advisable.
Please review our Moderation Guide to understand how we perform our moderation duties here at Code Forum.
 

Attachments

  • SR&GBanner.webp
    SR&GBanner.webp
    17.3 KB · Views: 161
Last edited:
I think it wouldn't be bad to limit quotes either:
Quote "in moderation." That means: Especially with long contributions it is desirable to quote only that part on which you want to take a stand - please leave out everything else. That way your answers will not be unnecessarily inflated and everyone will know what your answer refers to.
 
Master Yoda said:
Posting illegal/null and or hacking scripts is prohibited (Hacking scripts will result in a permanent ban).
Any discussions regarding hacking are prohibited.
Hey.

What about white-hat hacking? White-Hat hacking is when the hacking is being done with the knowledge, permission, and assistance of the contractor(So, if a company, let's say Google, hires a white-hat hacker, then that hacker is allowed to hack because they are doing work on behalf of Googe).

White-Hat hacking isn't really illegal, but it isn't stated if it's allowed. Could you perhaps expand the TOS to state what kind of hacking-discussions are allowed(So, are discussions surrounding white-hat, grey-hat, and black-hat hacking, all banned? Or is white-hat the only one allowed)?
 
Hey.

What about white-hat hacking? White-Hat hacking is when the hacking is being done with the knowledge, permission, and assistance of the contractor(So, if a company, let's say Google, hires a white-hat hacker, then that hacker is allowed to hack because they are doing work on behalf of Googe).

White-Hat hacking isn't really illegal, but it isn't stated if it's allowed. Could you perhaps expand the TOS to state what kind of hacking-discussions are allowed(So, are discussions surrounding white-hat, grey-hat, and black-hat hacking, all banned? Or is white-hat the only one allowed)?
Hello,

As of right now, ALL hacking related topics are forbidden.
 
As of right now, ALL hacking related topics are forbidden.
It reminds me somehow of Germany's government and its ban on hacking

Hacker tools are the most important tools for programmers. Without them you could not detect security holes or other problems.
Strictly speaking one must not talk about the Firefox developer console, this also counts under hacker tools
 
Hacker tools are the most important tools for programmers. Without them you could not detect security holes or other problems.
Strictly speaking one must not talk about the Firefox developer console, this also counts under hacker tools
I do agree that tools for hackers(Regardless of hat), do come in handy, even if the person isn't a hacker and is just a regular, old programmer. Although, we do need to remember that there are certain tools who's legality can be questioned.

Also, I never thought of the Firefox developer-tools(Or any web-browser tools for that matter), to be under hacking tools. So if that's the case, then wouldn't CF need to expand it's TOS to explicitly state: "No discussions regarding hacking are allowed. Including the tools used for debugging in a web-browser." To be honest, I'd find such a statement to be extremely silly, hacker tools or not.
 
Hacker tools are the most important tools for programmers. Without them you could not detect security holes or other problems.
Strictly speaking one must not talk about the Firefox developer console, this also counts under hacker tools
Well they are considered “Developer tools”. No one calls it hacking tools.

Rules have been updated.
 
Last edited:
New rule added, as indicated by **New**. Please avoid posting threads/posts that contain a wall of text. It isn’t pleasant to read.
 
When sharing or placing code in a thread/post please format the code using our BBCode to make it easier to read and understand by whoever is looking at your code. Check out the thread that was created about BBCode and examples on how to use it properly. https://codeforum.org/threads/how-to-post-your-code-into-threads.183/
Hello, everyone!

Whenever you are posting any code on Code Forum please use our code input feature </>, it makes it a lot easier to read and copy.
 
Participating in Events & Contests:
  1. **NEW** If you have more than 1 account here at Code Forum, you may ONLY use one to participate. If you are caught with multiple accounts participating, all your accounts will be banned for a period of 7 days. And, you will not be able to participate again.
The Code of Conduct has been updated. Please review the newly added rule.
 
Code of Conduct has been updated.
**NEW** Do not post threads asking for coders to code and or build a program for you. You can request guidance, or team members to assist you but do NOT ask others to do the work for you.
 
The Code of Conduct has been updated:
**NEW** Do not edit your original thread content and replacing it with one-liners like "Solved" or "Nevermind" leave it as is, please reply to your thread stating that you have solved and provide the solution.
 
Ah, well okay then. Fine by me.

My apologies for the ramble, but after seeing that, it triggered an alarm in my head. Yes, I know it is optional, but again, an alarm went off in my head, due to my concerns over security(And privacy too, as IP Addresses can be used to get a close idea of where somebody currently lives).
The only way for your ip to get leaked...
A) you become a dum-dum and actually give it...
B) you become a dum-dum and click on a shortened url.. alias grabify, iplogger, bitly, etc..
C) CF gets compromised... provided of course that CF does indeed ip log on user login... @Malcolm if so.. please keep an eye on that
D) you and I get into an agreement where I pentest your apps... at that point, you may end up clicking my custom honeypot link.. created for strictly pentesting, and custom because well, ip grabbers in (B) are all too well recognizable and oh too predictable (at this point.. all info will not be disclosed and will remain between you and myself)
E) you become a dum-dum and attempt to create your own ip grabber.. and end up pwning yourself...
 
We have updated the Code of Conduct:
**NEW** When providing links to solutions or articles; please explain the context of the link. The right way of sharing links would be: https://codeforum.org is where you can get help with coding! NOT https://codeforum.org. Visitors and coders should know where the link is going to direct them.
  1. OPTIONAL: Share the solution/content within the thread followed by the source URL. This will help reduce the amount of clicks for coders when trying to find their solution.
 

New Threads

Buy us a coffee!

Back
Top Bottom