Unverified Commit 89872dff authored by Markus Kirsch's avatar Markus Kirsch Committed by gitbook-bot
Browse files

GitBook: [master] 9 pages modified

parent b76a04e5
......@@ -628,4 +628,5 @@
* [Censorship and Harmful Content](legal/censorship-and-harmful-content.md)
* [Guidelines for Law Enforcement](legal/guidelines-for-law-enforcement.md)
* [Server Lookup](legal/server-lookup.md)
* [DMCA Policy](legal/dmca-policy.md)
......@@ -14,7 +14,7 @@ We also do not want to be the judges on what constitutes the “right” way to
Sometimes, our organization receives a request from a law enforcement body with the aim to produce a certain set of user data to aid in a criminal investigation. Or there might be a request to take down content that has been deemed illegal. We treat these requests very carefully and - where we are able and obliged to help - bring this to the attention of the administrator of the instance. Oftentimes, we cannot do anything though.
That is because we have no way to access or control Rocket.Chat servers. Our platform is open source and has no backdoors or whatsoever to allow us to remotely access your installations. In case of instances hoste by us for others, we forward them to the respective administrator. Where the request is about content on a server directly under our control, such as our Open Server, you can contact us directly under legal@rocket.chat.).
That is because we have no way to access or control Rocket.Chat servers. Our platform is open source and has no backdoors or whatsoever to allow us to remotely access your installations. In case of instances hoste by us for others, we forward them to the respective administrator. Where the request is about content on a server directly under our control, such as our Open Server, you can contact us directly under legal@rocket.chat.\).
### Resources for Administrators Be Notified About Harmful Content
......@@ -26,45 +26,41 @@ With this being the current situation, we wanted to share our stance on how we a
**Our policy principles in this matter are:**
- We do not endorse illegal or unethical usage of Rocket.Chat in any way. We understand these terms to be relative and to be interpreted in their local context.
- We want Rocket.Chat to be a platform that allows for free and unrestricted communication. We do not plan or want to build any kind of backdoor, censorship tool or hidden remote control mechanism into Rocket.Chat.
- Administrators are the ones in control over their installation. Administrators are responsible for their decisions on configuration and content moderation within their instance.
- We comply with valid local or international law enforcement requests to produce user data and inform our users affected by these requests.
- On our Open Server run by us, we want to provide users a positive and fun environment to test our platform and get in touch with us.
* We do not endorse illegal or unethical usage of Rocket.Chat in any way. We understand these terms to be relative and to be interpreted in their local context.
* We want Rocket.Chat to be a platform that allows for free and unrestricted communication. We do not plan or want to build any kind of backdoor, censorship tool or hidden remote control mechanism into Rocket.Chat.
* Administrators are the ones in control over their installation. Administrators are responsible for their decisions on configuration and content moderation within their instance.
* We comply with valid local or international law enforcement requests to produce user data and inform our users affected by these requests.
* On our Open Server run by us, we want to provide users a positive and fun environment to test our platform and get in touch with us.
**While none of these principles are absolute, they are guiding our actions.**
## What can you do when dealing with harmful content in Rocket.Chat?
**For users:**
On our [Open Server](https://open.rocket.chat/), you can report harmful content as per our [code of conduct](https://rocket.chat/code-of-conduct) and we will look into removing it. We want you to be able to use our open.server hassle free.
**For users:** On our [Open Server](https://open.rocket.chat/), you can report harmful content as per our [code of conduct](https://rocket.chat/code-of-conduct) and we will look into removing it. We want you to be able to use our open.server hassle free.
If you encounter another Rocket.Chat instance that is not hosted by us and which you think contains illegal or otherwise harmful content, we recommend you reach out to the administrator of that instance to moderate the related content.
If you do not know who is your administrator, you can check the DNS records for contact information. For instances that are hosted by us, we can contact the administrator on behalf of you. We have published a tool where you can find out if a Rocket.Chat instance is hosted by us ([server lookup](https://rocket.chat/server-lookup)). This is not always clear because no one is obliged to use the Rocket.Chat logo or name.
If you do not know who is your administrator, you can check the DNS records for contact information. For instances that are hosted by us, we can contact the administrator on behalf of you. We have published a tool where you can find out if a Rocket.Chat instance is hosted by us \([server lookup](https://rocket.chat/server-lookup)\). This is not always clear because no one is obliged to use the Rocket.Chat logo or name.
As an ultimate resort, you may want to reach out to the law enforcement body in charge of investigating the potential offense in question. They will tell you the legal remedies available and the potential next steps to take.
**For administrators:**
If you are an administrator, you might have an interest in moderating the content in your instance. Notable features that can help you with that are:
**For administrators:** If you are an administrator, you might have an interest in moderating the content in your instance. Notable features that can help you with that are:
- Making use of the “moderator”-permission in channels to appoint individuals to purge or modify inappropriate messages
- Notification feature for the use of specified words of phrases
- Blacklisting certain words or phrases
- Notifying your users of applicable policies via e.g. pinning messages or adding an announcement to the room
- Requiring confirmation of user registration by an administrator, to prevent unvetted users from posting messages
- Enabling end-to-end encryption: with end-to-end encryption enabled, only an encrypted string of the message is stored on the server. This however prevents content auditing via administrators and moves responsibility for content moderation to users.
- Turning on GoogleVision integration for image uploads, which has options to block images containing graphic or adult content
* Making use of the “moderator”-permission in channels to appoint individuals to purge or modify inappropriate messages
* Notification feature for the use of specified words of phrases
* Blacklisting certain words or phrases
* Notifying your users of applicable policies via e.g. pinning messages or adding an announcement to the room
* Requiring confirmation of user registration by an administrator, to prevent unvetted users from posting messages
* Enabling end-to-end encryption: with end-to-end encryption enabled, only an encrypted string of the message is stored on the server. This however prevents content auditing via administrators and moves responsibility for content moderation to users.
* Turning on GoogleVision integration for image uploads, which has options to block images containing graphic or adult content
All of these features are optional to choose, so you have the total flexibility in what to apply in your specific case. Let us know which kind of features you are currently missing - but would find useful - by opening feature requests in our Github repository (link).
All of these features are optional to choose, so you have the total flexibility in what to apply in your specific case. Let us know which kind of features you are currently missing - but would find useful - by opening feature requests in our Github repository \(link\).
**For law enforcement:**
We sometimes receive requests from law enforcement to remove content from certain Rocket.Chat instances. We have published guidelines for law enforcement (link), how we deal with requests and what to consider before submitting a request to us as the legal entity behind Rocket.Chat.
**For law enforcement:** We sometimes receive requests from law enforcement to remove content from certain Rocket.Chat instances. We have published guidelines for law enforcement \(link\), how we deal with requests and what to consider before submitting a request to us as the legal entity behind Rocket.Chat.
**In summary:** In most cases, we cannot remove the majority of content, because it is outside of our control on servers we do not have (and do not want) access to. If the content in question is on our Open Server, we remove it if it is a breach of our code of conduct or if we are compelled by a law enforcement request. For servers hosted by us and under control of our customers, we remove content after notifying and in collaboration with the instance owner. For questions or contact, please use [legal@rocket.chat](mailto:legal@rocket.chat)
**In summary:** In most cases, we cannot remove the majority of content, because it is outside of our control on servers we do not have \(and do not want\) access to. If the content in question is on our Open Server, we remove it if it is a breach of our code of conduct or if we are compelled by a law enforcement request. For servers hosted by us and under control of our customers, we remove content after notifying and in collaboration with the instance owner. For questions or contact, please use [legal@rocket.chat](mailto:legal@rocket.chat)
**For reporters and media requests:**
Are you researching for an article about Rocket.Chat or where Rocket.Chat plays a role?
**For reporters and media requests:** Are you researching for an article about Rocket.Chat or where Rocket.Chat plays a role?
We would love to explain to you our stance in detail or get a chance to comment before you publish your article. Please reach out to [contact@rocket.chat](mailto:contact@rocket.chat) to get a comment from us on the topic in question.
# Code of Conduct for our communities and open server
# Code of Conduct
_Effective date: September 06, 2019_
## Rocket.Chat Code of Conduct
Dear users,
Dear users,
Rocket.Chat provides numerous spaces for our community to interact and experience our product. Among these are:
[Open.rocket.chat](https://open.rocket.chat/), an open chat community for bringing people together and to showcase Rocket.Chat´s community edition. In addition, new features are tested on the server on a regular basis.
[github.com/RocketChat](http://github.com/RocketChat), our source code repositories where we discuss issues and plan new features
[Forums.rocket.chat](https://forums.rocket.chat/), our webforum to announce new features and provide ways for direct interaction with our developers
Rocket.Chat provides numerous spaces for our community to interact and experience our product. Among these are: [Open.rocket.chat](https://open.rocket.chat/), an open chat community for bringing people together and to showcase Rocket.Chat´s community edition. In addition, new features are tested on the server on a regular basis. [github.com/RocketChat](http://github.com/RocketChat), our source code repositories where we discuss issues and plan new features [Forums.rocket.chat](https://forums.rocket.chat/), our webforum to announce new features and provide ways for direct interaction with our developers
## Introduction
......@@ -27,15 +24,15 @@ We're mainly an English speaking community but welcome all nationalities. If you
We do not want the following behavior on open.rocket.chat:
- Soliciting / advertising
- Offensive, rude, disruptive and unwanted
- Posting of pornographic / gore / nude images
- Harassment, name-calling, racist or sexist remarks, profanity towards others and other forms of bullying
- Insensitive behavior - this will be judged by the reaction of others in the channel
- Flirting or adult content - take these conversations elsewhere
- Posting of links (URLs) to offensive material, sites hosting malware, initiating downloads or promoting illegal activities
- Flooding the chat, spamming, multiple repeats of the same or slightly modified messages
- Reregistering under another account after you have been banned and still under a ban period
* Soliciting / advertising
* Offensive, rude, disruptive and unwanted
* Posting of pornographic / gore / nude images
* Harassment, name-calling, racist or sexist remarks, profanity towards others and other forms of bullying
* Insensitive behavior - this will be judged by the reaction of others in the channel
* Flirting or adult content - take these conversations elsewhere
* Posting of links \(URLs\) to offensive material, sites hosting malware, initiating downloads or promoting illegal activities
* Flooding the chat, spamming, multiple repeats of the same or slightly modified messages
* Reregistering under another account after you have been banned and still under a ban period
## Reporting unwanted behavior
......@@ -45,20 +42,21 @@ Users affected by unwanted behavior can mute other users or report them to the a
If you are asked to modify your behavior or given some other form of instruction but fail to comply, you are likely to be removed from the channel, the discussion or the whole server for a discretionary or unlimited period of time depending on the severity of the matter, depending on the administrator's decision.
Depending on the severity of the misbehavior, users can get banned without warning or be issued a warning. Should administrators deem a subject matter to be inappropriate for the channel and / or the current audience, they may at their discretion make contact via Private Message, making clear any requirement to cease discussing the topic, or - as per their permission level - ban the user. A ban may be temporary (in form of a ban period) or permanent. In addition, the server administrator has the right to remove your user account.
Depending on the severity of the misbehavior, users can get banned without warning or be issued a warning. Should administrators deem a subject matter to be inappropriate for the channel and / or the current audience, they may at their discretion make contact via Private Message, making clear any requirement to cease discussing the topic, or - as per their permission level - ban the user. A ban may be temporary \(in form of a ban period\) or permanent. In addition, the server administrator has the right to remove your user account.
When being corrected by an administrator, please do not argue with them in the main chat. You should request a PM session to help avoid conflict and keep the involvement of others to a minimum.
Attacking administrators in a channel will likely result in a ban. Any genuine visitor should respect their decisions - they have nothing to gain from issuing bans / mutes and are doing so to the best of their ability, on behalf of the community.
Administrators may also choose to request users to leave if they're deemed to be a risk to the safety of the general users / guests within the channel. Not adhering to the request will result in manual removal;
Administrators may also choose to request users to leave if they're deemed to be a risk to the safety of the general users / guests within the channel. Not adhering to the request will result in manual removal;
If you believe that an administrator has misused their authority and you have complied 100% with the rules documented on this page, please forward the following details to support@rocket.chat, including the following information:
- administrator's open.rocket.chat nickname;
- What you believe they have done that demonstrates an abuse of power;
- Associated dates and times - required to review log files etc.
* administrator's open.rocket.chat nickname;
* What you believe they have done that demonstrates an abuse of power;
* Associated dates and times - required to review log files etc.
Note that it can take some time to review log files and liaise with the administrator team, so please don't expect an immediate response.
In case of a ban period issued, you are welcome to return to the channel once your ban period expires, but please be mindful of the reason(s) you got banned, abide by the rules and take into account any administrator feedback received.
In case of a ban period issued, you are welcome to return to the channel once your ban period expires, but please be mindful of the reason\(s\) you got banned, abide by the rules and take into account any administrator feedback received.
......@@ -8,7 +8,7 @@ Rocket.Chat has implemented various updates and changes to its codebase in prepa
A summary of Rocket.Chat's overall GDPR readiness strategy for this project can be found below:
[#9769](https://github.com/RocketChat/Rocket.Chat/issues/9769)
[\#9769](https://github.com/RocketChat/Rocket.Chat/issues/9769)
Our public statement can also be found on [GitHub](https://github.com/RocketChat/Rocket.Chat/issues/10823).
......@@ -16,18 +16,15 @@ The following are some of the more recent GDPR updates that are now part of the
## Right of Access
[#9767](https://github.com/RocketChat/Rocket.Chat/issues/9767)
(implemented [#9906](https://github.com/RocketChat/Rocket.Chat/pull/9906))
[\#9767](https://github.com/RocketChat/Rocket.Chat/issues/9767) \(implemented [\#9906](https://github.com/RocketChat/Rocket.Chat/pull/9906)\)
## Right to be forgotten/erased
[#9766](https://github.com/RocketChat/Rocket.Chat/issues/9766)
(implemented [#9947](https://github.com/RocketChat/Rocket.Chat/pull/9947))
[\#9766](https://github.com/RocketChat/Rocket.Chat/issues/9766) \(implemented [\#9947](https://github.com/RocketChat/Rocket.Chat/pull/9947)\)
## Data Portability
[#9768](https://github.com/RocketChat/Rocket.Chat/issues/9768)
(implemented in [#9906](https://github.com/RocketChat/Rocket.Chat/pull/9906))
[\#9768](https://github.com/RocketChat/Rocket.Chat/issues/9768) \(implemented in [\#9906](https://github.com/RocketChat/Rocket.Chat/pull/9906)\)
## Other rights
......@@ -35,16 +32,15 @@ Other rights for the data subjects are either covered by features already built
### Right to Rectification
The codebase can be configured to support user modification/correction/rectification of any data supplied (entered) by the user.
The codebase can be configured to support user modification/correction/rectification of any data supplied \(entered\) by the user.
### Right to restriction of processing
This is outside the scope of the open source software project, and is up to the controller ( administrator / deployer / operator of the the server system) to enforce.
This is outside the scope of the open source software project, and is up to the controller \( administrator / deployer / operator of the the server system\) to enforce.
### Right to Object
This is outside the scope of the open source software project, and is up to the controller ( administrator / deployer / operator of the server system) to enforce.
This is outside the scope of the open source software project, and is up to the controller \( administrator / deployer / operator of the server system\) to enforce.
## Community compliance
......@@ -55,3 +51,4 @@ Meanwhile, we would welcome any advice, input, or questions you may have regardi
Thank you!
The Rocket.Chat Team
......@@ -12,13 +12,13 @@ As such, you need to be aware that any Rocket.Chat server may be operated by arb
In particular:
- Rocket.Chat Technologies Corp. do not have access to these servers.
- Rocket.Chat Technologies Corp. does not and cannot control or regulate how these servers are operated.
- Rocket.Chat Technologies Corp. cannot access, determine or regulate any contents or information flow on these servers.
* Rocket.Chat Technologies Corp. do not have access to these servers.
* Rocket.Chat Technologies Corp. does not and cannot control or regulate how these servers are operated.
* Rocket.Chat Technologies Corp. cannot access, determine or regulate any contents or information flow on these servers.
For total transparency, Rocket.Chat Technologies Corp. owns and operates only one publicly available Rocket.Chat server in the world. The server that Rocket.Chat Technologies Corp. operates can only be accessed at:
<https://open.rocket.chat>
[https://open.rocket.chat](https://open.rocket.chat)
That server is subject to our [Code of Conduct](https://rocket.chat/code-of-conduct).
......@@ -34,7 +34,7 @@ Rocket.Chat does **not** keep a log of IPs used to access either Community Serve
### Community Server
When someone registers an account at our community server, hosted at <https://open.rocket.chat>, we ask for a name, an e-mail and a password, and they have to verify their e-mail address. Rocket.Chat does not monitor any public or private channels activities other than for the company's own use, such as the #general, #support and #dev public channels.
When someone registers an account at our community server, hosted at [https://open.rocket.chat](https://open.rocket.chat), we ask for a name, an e-mail and a password, and they have to verify their e-mail address. Rocket.Chat does not monitor any public or private channels activities other than for the company's own use, such as the \#general, \#support and \#dev public channels.
### Rocket.Chat Cloud
......@@ -42,7 +42,7 @@ When someone signs up for a Rocket.Chat Cloud server, we ask for a name, e-mail,
## Data retention information
Rocket.Chat retains data and backups of data for an undisclosed amount of time. Rocket.Chat makes backups of Cloud servers according to each customer's choice of plan (daily, twice daily or hourly). Some information we store is automatically collected, while other information is provided at the user’s discretion. Though we do store this information, we cannot guarantee its accuracy. For example, the server in use may not require real name use, email verification or identity authentication, hence the user may have created a fake or anonymous profile.
Rocket.Chat retains data and backups of data for an undisclosed amount of time. Rocket.Chat makes backups of Cloud servers according to each customer's choice of plan \(daily, twice daily or hourly\). Some information we store is automatically collected, while other information is provided at the user’s discretion. Though we do store this information, we cannot guarantee its accuracy. For example, the server in use may not require real name use, email verification or identity authentication, hence the user may have created a fake or anonymous profile.
## Preservation requests
......@@ -50,9 +50,9 @@ We accept requests from law enforcement to preserve records, which constitute po
Preservation requests, in accordance with applicable law, should:
- be signed by the requesting official;
- have a valid return official email address; and be sent on law enforcement letterhead;
- include the server URL of the subject offense and any other information that may help us identify the offending server and/or user.
* be signed by the requesting official;
* have a valid return official email address; and be sent on law enforcement letterhead;
* include the server URL of the subject offense and any other information that may help us identify the offending server and/or user.
We may honor requests for extensions of preservation requests, but encourage law enforcement agencies to seek records through the appropriate channels in a timely manner, as we cannot guarantee that requested information will be available.
......@@ -68,25 +68,25 @@ Non-public information about Rocket.Chat users will not be released to law enfor
### Contents of communications requires a search warrant
Requests for the contents of communications (e.g., messages, files) require a valid search warrant or equivalent from an agency with proper jurisdiction over Rocket.Chat.
Requests for the contents of communications \(e.g., messages, files\) require a valid search warrant or equivalent from an agency with proper jurisdiction over Rocket.Chat.
### Will Rocket.Chat notify users of requests for account information?
Yes. Rocket.Chat's policy is to notify users of requests for their Rocket.Chat account information, which includes a copy of the request, as soon as we are able (e.g., prior to or after disclosure of account information) unless we are prohibited from doing so (e.g., an order under [18 U.S.C. § 2705(b)](https://www.law.cornell.edu/uscode/text/18/2705)). We ask that any non-disclosure provisions include a specified duration (e.g., 90 days) during which Rocket.Chat is prohibited from notifying the user. Exceptions to user notice may include exigent or counterproductive circumstances, such as emergencies regarding imminent threat to life, child sexual exploitation, or terrorism.
Yes. Rocket.Chat's policy is to notify users of requests for their Rocket.Chat account information, which includes a copy of the request, as soon as we are able \(e.g., prior to or after disclosure of account information\) unless we are prohibited from doing so \(e.g., an order under [18 U.S.C. § 2705\(b\)](https://www.law.cornell.edu/uscode/text/18/2705)\). We ask that any non-disclosure provisions include a specified duration \(e.g., 90 days\) during which Rocket.Chat is prohibited from notifying the user. Exceptions to user notice may include exigent or counterproductive circumstances, such as emergencies regarding imminent threat to life, child sexual exploitation, or terrorism.
### What details must be included in account information requests?
Requests for user account information in accordance with applicable law, are required to include the following information:
- Include the Rocket.Chat server URL and @username of the subject Rocket.Chat account in question;
- Provide details about what specific information is requested (e.g., messages, files, account information) and its relationship to your investigation;
- Include a valid official email address (e.g., name@agency.gov) so we may get back in touch with you upon receipt of your legal process;
- Be issued on law enforcement letterhead.
- Law enforcement and government requests for user information should be submitted through [legal@rocket.chat](mailto:legal@rocket.chat). You can find further instructions below.
* Include the Rocket.Chat server URL and @username of the subject Rocket.Chat account in question;
* Provide details about what specific information is requested \(e.g., messages, files, account information\) and its relationship to your investigation;
* Include a valid official email address \(e.g., name@agency.gov\) so we may get back in touch with you upon receipt of your legal process;
* Be issued on law enforcement letterhead.
* Law enforcement and government requests for user information should be submitted through [legal@rocket.chat](mailto:legal@rocket.chat). You can find further instructions below.
### Production of records
Unless otherwise agreed upon, we currently provide responsive records in electronic format (i.e., text files that can be opened with any word processing software such as Word or TextEdit).
Unless otherwise agreed upon, we currently provide responsive records in electronic format \(i.e., text files that can be opened with any word processing software such as Word or TextEdit\).
### Records authentication
......@@ -94,13 +94,13 @@ The records that we produce are self-authenticating. Additionally, the records a
### Cost reimbursement
Rocket.Chat may seek reimbursement for costs associated with information produced pursuant to legal process and as permitted by law (e.g. under [18 U.S.C. §2706](https://www.law.cornell.edu/uscode/text/18/2706)).
Rocket.Chat may seek reimbursement for costs associated with information produced pursuant to legal process and as permitted by law \(e.g. under [18 U.S.C. §2706](https://www.law.cornell.edu/uscode/text/18/2706)\).
## Emergency disclosure requests
In line with our [Privacy Policy](https://rocket.chat/privacy), we may disclose account information to law enforcement in response to a valid emergency disclosure request.
Rocket.Chat evaluates emergency disclosure requests on a case-by-case basis in compliance with relevant law (e.g., [18 U.S.C. § 2702(b)(8)](https://www.law.cornell.edu/uscode/text/18/2702)). If we receive information that provides us with a good faith belief that there is an exigent emergency involving the danger of death or serious physical injury to a person, we may provide information necessary to prevent that harm, if we have it.
Rocket.Chat evaluates emergency disclosure requests on a case-by-case basis in compliance with relevant law \(e.g., [18 U.S.C. § 2702\(b\)\(8\)](https://www.law.cornell.edu/uscode/text/18/2702)\). If we receive information that provides us with a good faith belief that there is an exigent emergency involving the danger of death or serious physical injury to a person, we may provide information necessary to prevent that harm, if we have it.
### How to make an emergency disclosure request
......@@ -108,21 +108,20 @@ If there is an exigent emergency that involves the danger of death or serious ph
Please include all of the following information:
- Indication on your cover sheet, which must be on law enforcement letterhead, that you're submitting an Emergency Disclosure Request;
- Identity of the person who is in danger of death or serious physical injury;
- The nature of the emergency (e.g., report of suicide, bomb threat);
- Rocket.Chat server URL and/or @username of the subject account(s) whose information is necessary to prevent the emergency;
- Any specific Rocket.Chat messages you would like us to review;
- The specific information requested and why that information is necessary to prevent the emergency;
- The signature of the submitting law enforcement officer; and
- All other available details or context regarding the particular circumstances.
* Indication on your cover sheet, which must be on law enforcement letterhead, that you're submitting an Emergency Disclosure Request;
* Identity of the person who is in danger of death or serious physical injury;
* The nature of the emergency \(e.g., report of suicide, bomb threat\);
* Rocket.Chat server URL and/or @username of the subject account\(s\) whose information is necessary to prevent the emergency;
* Any specific Rocket.Chat messages you would like us to review;
* The specific information requested and why that information is necessary to prevent the emergency;
* The signature of the submitting law enforcement officer; and
* All other available details or context regarding the particular circumstances.
## Contact information
Our address details are:
Rocket.Chat Technologies Corp.
251 Little Falls Drive,
Wilmington, DE, 19808
Rocket.Chat Technologies Corp. 251 Little Falls Drive, Wilmington, DE, 19808
Receipt of correspondence is for convenience only and does not waive any objections, including the lack of jurisdiction or proper service.
This diff is collapsed.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment