You can subscribe to this list here.
2012 |
Jan
|
Feb
|
Mar
|
Apr
(24) |
May
(35) |
Jun
(5) |
Jul
(8) |
Aug
|
Sep
|
Oct
(7) |
Nov
(3) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
(7) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
(1) |
Feb
(3) |
Mar
(7) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(4) |
Oct
(4) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <dus...@us...> - 2012-06-03 01:35:46
|
Revision: 320 http://responsibility.svn.sourceforge.net/responsibility/?rev=320&view=rev Author: dustsource Date: 2012-06-03 01:35:39 +0000 (Sun, 03 Jun 2012) Log Message: ----------- Made the following edits to the documentation related to rating improvement data: --Added the "Rating Improvement Data" guide. --In the "Configuration Explained" guide: --'Configuration Parts' section, 'Tweaks', 'Provide improvement data': Clarified relationship between this setting and rating warnings in reports. --In the "Understanding the Reports" guide: --'Improving the reports' section: --In the last paragraph (item), clarified relationship between the 'Provide improvement data' setting and rating warnings in reports. --Added a final item linking to new "Rating Improvement Data" guide. --In the "Troubleshooting the Reports" guide: --'Why are there so many false positives?' section: --Adjusted the text to help clarify relationship between the 'Provide improvement data' setting and rating warnings in reports. --Added brief comment about and link to the new "Rating Improvement Data" guide. --In the "Privacy Policy" document: --'What about the improvement data?' section: Clarified relationship between the 'Provide improvement data' setting and rating warnings in reports. Modified Paths: -------------- documentation/pages/0301-ConfigurationExplained.page documentation/pages/0705-UnderstandingReports.page documentation/pages/0709-TroubleshootingReports.page documentation/pages/0910-PrivacyPolicy.page Added Paths: ----------- documentation/pages/5050-RateImprovData.page Modified: documentation/pages/0301-ConfigurationExplained.page =================================================================== --- documentation/pages/0301-ConfigurationExplained.page 2012-05-27 00:52:27 UTC (rev 319) +++ documentation/pages/0301-ConfigurationExplained.page 2012-06-03 01:35:39 UTC (rev 320) @@ -27,7 +27,7 @@ - <*Instant threshold*>: Here you can enable instant reports, which means your accountability partner will get a report instantly when NR thinks you're looking at inappropriate content. You can also set the sensitivity. Entering zero means this feature is disabled. Otherwise, lower numbers mean higher sensitivity. (0 = Disabled; 1-5 = Very sensitive; 6-20 = Medium; 21+ = Low sensitivity) - <*Report strength threshold*>: Only matches with a strength higher than this number will be included in the <*Warnings*> section of the reports. That way you're able to set some sort of sensitivity for what to display. This number ranking system for these items is a fairly new feature that still needs to be tested and tweaked in order to make it accurate and useful. To find out more about this ranking system, including how you can help in making it more accurate, see [[0705-UnderstandingReports.html#4 this section]] of the "Understanding the Reports" guide. - <*Always perform tokenmatch*>: Using tokenmatch increases the report creation time because it's more complicated, but it results in much more accurate reports. If you're having problems with reports taking too long to create you might want to exclude it. - - <*Provide improvement data*>: Use this option if you'd like to help us with the development of NR. The program will <*anonymously*> send your warnings to our server and store them there. This will help us see how to improve the blacklists. + - <*Provide improvement data*>: Use this option if you'd like to help with the development of NR. The program will <*anonymously*> send your warnings to our server and store them there. This will help the developers see how to improve the blacklists. (Note that if you or your accountability partners choose to [[0705-UnderstandingReports.html#9 help improve the accuracy of reports]], the improvement data related to any rated warnings will be sent to and stored on the NR server, even if this option is not selected in your settings.) - <*Send me newsletters*>: Choose this if you want the latest information about new versions, how to help, and other things that might be of interest. These emails are not sent on a regular basis, but rather whenever there's a need to update users with fresh information. !!Blacklist categories Modified: documentation/pages/0705-UnderstandingReports.page =================================================================== --- documentation/pages/0705-UnderstandingReports.page 2012-05-27 00:52:27 UTC (rev 319) +++ documentation/pages/0705-UnderstandingReports.page 2012-06-03 01:35:39 UTC (rev 320) @@ -80,4 +80,5 @@ %> In the drop-down menu, the first number is simply the current ranking that NR has given this item. The numbers after that (0, 25, 50, 75, 100) represent various points or markers along the 0-100 continuum that represent levels of the likelihood of an URL being a cause for concern or not. See the [[#4 Warnings]] section on this page to see a description of what each of these levels is meant to represent. - - So the way to help out is to look at each item, evaluate which of the levels it best fits into (according to the above-mentioned description), and then choose the corresponding number from the dropdown menu. When you do this, your rating of the URL will be sent to the NR server, which will then help the developers know how to make any necessary adjustments to NR's filtering methods. (Once you have rated an URL, the number you chose will show up on a white background and the drop-down menu will no longer be available for that item. However, if you close and re-open the report, it will appear as it did at first.) Note that it is helpful to assign a rating to an URL regardless of whether it's current ranking is accurate or whether it is way off. Also, the more people that are regularly reporting ratings of URLs in this way, the more accurate the reports will become. So your help would definitely be appreciated! + - So the way to help out is to look at each item, evaluate which of the levels it best fits into (according to the above-mentioned description), and then choose the corresponding number from the dropdown menu. When you do this, the URL and its related information, along with your rating of it, will be sent to the NR server. (Note that this information is then stored on the NR server even if the user has not selected 'Provide improvement data' in their online settings.) This will then help the developers know how to make any necessary adjustments to NR's filtering methods. (Once you have rated an URL, the number you chose will show up on a white background and the drop-down menu will no longer be available for that item. However, if you close and re-open the report, it will appear as it did at first.) Note that it is helpful to assign a rating to an URL regardless of whether it's current ranking is accurate or whether it is way off. Also, the more people that are regularly reporting ratings of URLs in this way, the more accurate the reports will become. So your help would definitely be appreciated! + - If you would like to help improve the accuracy of reports by rating improvement data provided by other users as well, see the [[5050-RateImprovData.html "Rating Improvement Data" guide]] for more information. Modified: documentation/pages/0709-TroubleshootingReports.page =================================================================== --- documentation/pages/0709-TroubleshootingReports.page 2012-05-27 00:52:27 UTC (rev 319) +++ documentation/pages/0709-TroubleshootingReports.page 2012-06-03 01:35:39 UTC (rev 320) @@ -18,6 +18,7 @@ - The attached report may be 'broken' because of some problems in its code (such as the appearance of unwanted newlines and single quotes). If this is the case, the usual symptom is that JavaScript will not work at all, meaning that neither the JavaScript tree nor the text message about JavaScript being disabled will be displayed. Improvements to the software are the best long-term solution, but until that happens a temporary workaround is to try to 'repair' the broken report by clicking on [[http://netresponsibility.com/repair.php this link]] and following the instructions there. This is not guaranteed to work in every case, but it is worth trying. Also, note that the report you are trying to repair needs to be smaller than 12 MB. !!!Why are there so many false positives? -There may be a lot of false positives (i.e. a warning that is not really a problem) in the <*Warnings*> section of the reports you receive, causing you to wonder why there are so many, and if there isn't anything we can do to lessen or completely avoid them. The reason there are so many is because we are still working at testing and tweaking our filtering method in order to catch what needs to be caught, and ignore the rest. The developers of NR can do a certain amount of improvement on their own, but it would be tremendously helpful to us if NR users and accountability partners also helped out with this process. Here are the two main ways that help can be given: - - Make sure the NR user has selected the option 'Provide improvement data' in the 'Tweaks' section of their online settings. When this is selected, the program will <*anonymously*> send the warnings from each report to our server and store them there. This will help us see how to improve the blacklists. - - A relatively new feature we are using in the <*Warnings*> section of reports is a color-coded number ranking system for each item listed. Because it has not been extensively tested, you should not completely rely on it at the current time. However, we are working on improving its accuracy and the good news is, since we're including it in the reports that are sent out, you are also able to help out with this. For more information about how you can give valuable help by giving a bit of your time whenever you receive a report, see the [[0705-UnderstandingReports.html#9 Improving the Reports]] section of the "Understanding the Reports" guide. Thanks in advance for whatever help you can give in making the reports more accurate and useful! +There may be a lot of false positives (i.e. a warning that is not really a problem) in the <*Warnings*> section of the reports you receive, causing you to wonder why there are so many, and if there isn't anything that can be done to lessen or completely avoid them. The reason there are so many is because efforts are still being made to test and tweak the filtering method in order to catch what needs to be caught, and ignore the rest. The developers of NR can do a certain amount of improvement on their own, but it would be tremendously helpful if NR users and accountability partners also helped out with this process. Here are three different ways that help can be given: + - NR users can make sure the option 'Provide improvement data' is selected in the 'Tweaks' section of their online settings. When this is selected, the program will <*anonymously*> send the warnings from each report to our server and store them there. This will help developers understand how to improve the blacklists and filtering methods. + - A relatively new feature we are using in the <*Warnings*> section of reports is a color-coded number ranking system for each item listed. Because it has not been extensively tested, you should not completely rely on it at the current time. However, efforts are being made to improve its accuracy and the good news is, since it is included in the reports that are sent out, you are also able to help out with this. For more information about how you can give valuable help by giving a bit of your time whenever you receive a report, see the [[0705-UnderstandingReports.html#9 'Improving the Reports' section of the "Understanding the Reports" guide]]. Thanks in advance for whatever help you can give in making the reports more accurate and useful! + - You may also help improve the accuracy of reports by rating improvement data provided by other users as well. See the [[5050-RateImprovData.html "Rating Improvement Data" guide]] for more information about how you can do this. Modified: documentation/pages/0910-PrivacyPolicy.page =================================================================== --- documentation/pages/0910-PrivacyPolicy.page 2012-05-27 00:52:27 UTC (rev 319) +++ documentation/pages/0910-PrivacyPolicy.page 2012-06-03 01:35:39 UTC (rev 320) @@ -13,7 +13,7 @@ !!!What about the improvement data? -If you choose to send improvement data, it means all visited sites that are flagged as inappropriate are sent to our server. We do not store any information about who visited these sites, such as username, IP number, MAC address etc. This anonymous data helps us develop better filtering algorithms that in return will produce better reports. +If you choose to send improvement data, it means all visited sites that are flagged as inappropriate are sent to our server. If users or their accountability partners choose to [[0705-UnderstandingReports.html#9 help improve the accuracy of reports]] by rating URLs NR has flagged, the data related to these URLs will be sent to the NR server, even if the user did not select the 'Provide improvement data' option in their settings. We do not store any information about who visited these sites, such as username, IP number, MAC address etc. This anonymous data helps us develop better filtering algorithms that in return will produce better reports. !!!What information do we collect? Added: documentation/pages/5050-RateImprovData.page =================================================================== --- documentation/pages/5050-RateImprovData.page (rev 0) +++ documentation/pages/5050-RateImprovData.page 2012-06-03 01:35:39 UTC (rev 320) @@ -0,0 +1,110 @@ +Rating improvement data +A50NR_DevIntro + +!!!Introduction +There are currently three ways that Net Responsibility (NR) users and their accountability partners (APs) can help improve the accuracy of the <*Warnings*> section of the reports. One way is for the user to make sure they have selected the option 'Provide improvement data' in the <*Tweaks*> section of their [[0301-ConfigurationExplained.html online configuration settings]], which automatically and <*anonymously*> sends all <*Warnings*> items to the NR server where they can then be rated, analyzed, etc. in order to improve NR's filtering methods. A second way is for users and APs to [[0705-UnderstandingReports.html#9 rate individual items]] from the <*Warnings*> section of the reports they receive. This guide describes the third way you can help out, which is by rating the improvement data that has been received from multiple NR users. Please note that, while this is a great way to help out, you also need to be careful in how you go about it, since it is possible that while you are doing this you will see keywords and URLs that will tempt your mind to go in directions you don't want it to. In a later section of this guide, you will find some ideas and tips for protecting yourself as needed. + +All of the improvement data can be viewed and rated by using an online interface hosted on the NR server. [[http://www.netresponsibility.com/dev/improvement_data.php Click here to see what it looks like or begin using it.]] You may find it helpful to have it open in your browser as you read through the rest of this guide, which explains how it works, along with the various options that can be used with it. + + +!!!Online interface options +This section explains the various options available for you to customize your approach to rating the improvement data. + +!!The 'Where' field +The warnings are loaded in a MySQL string, and if you are familiar with that syntax it will be easy to load specific types of warnings you're looking for. A percentage sign (%) will match anything or nothing. You may leave this field empty to load all warnings. Here are some examples of how to use SQL syntax in the 'Where' field to load warnings selectively: + - category LIKE 'porn' + - category LIKE 'personal blacklist' + - keyword LIKE 'sex%' + - strength < 50 + - rating = 0 + - category LIKE 'porn' AND strength < 50 + +!!'Order by' +Here you can choose the order in which you want the warnings to be shown. The options may be self-explanatory, especially if you've used a similar sort of sorting or ordering function before. This option can be combined with the options 'Ascending' or 'Descending' in order to reverse the order. Here is a list (same as in the drop-down menu) of the ways that the warnings can be sorted/ordered: + - Date: This is the default option, and refers to the date the warning was flagged. Combined with 'Ascending' it will show the earliest warnings first. This is helpful if you want to focus on the newest or oldest warnings. + - Amount: This refers to the number of times that this identical URL and a particular keyword match was sent to the NR server. Combined with 'Ascending' it will show URLs with the least amount first. This is helpful if you want to focus on rating URLs that are more frequent or less frequent. + - Rating: This refers to a number from 0 to 5, which represents the average of how a warning has been rated by users and/or accountability partners. If the number is 0, it means the warning has not yet been rated. The numbers 1, 2, 3, 4, and 5 represent points along a continuum from something that was definitely a false positive (lower number) to something that was definitely an inappropriate site (higher number). Because these are based on an average, you may see numbers with decimals like 1.23 or 3.45, etc., but they will all be within the 1-5 range if they have been rated before. This is helpful if you want to focus on warnings that are currently unrated or warnings that other users have considered to be more or less likely to be inappropriate sites. + - Votes: This refers to the number of times that this warning has been rated. This is helpful if you want to focus on warnings that have been rated less or more times by other people. + - Blacklist: This allows you to order the warnings according to the particular blacklist (i.e. 'Models' or 'Porn' or 'Celebrities') they are associated with. This is helpful if you want to focus in on one particular type of warning at a time. + - Keyword: This allows you to order the warnings according to the keywords they are associated with. This is helpful if you want to focus in on warnings for one particular keyword at a time. + - Strength: This refers to a number from 0 to 100+, and is the initial value assigned to the warning when NR filtered it the first time, with higher numbers indicating that NR is reporting a greater likelihood of that site being inappropriate. This is helpful if you want to focus on warnings to which NR has assigned either a low strength or a high strength. + +!!'Ascending' or 'Descending' +This option is basically just a way to switch the order of the various 'Order by' options listed above. For options that are based on values or numbers, choosing 'Ascending' will start with the lowest value and move higher. For options that are based on words, 'Ascending' will start with the letter 'A' (or whatever is closest to it) and move through the alphabet to the letter 'Z'. Choosing 'Descending' will do just the opposite of 'Ascending'. + +!!'Limit' +This option allows you to choose how many warnings you want to have loaded at one time. The default is 100 but you may increase it if you want, or decrease it if it's taking too long to load. + +!!'Reload' +If you click on this button, it will reload all warnings. So, if you have simply had warnings appended (either automatically or manually) and you want to start fresh with a new set of warnings, this can be helpful. Or if you have changed any of the options in regards to what types of warnings you want to view and rate, or how you want them sorted, you will need to press this button in order to apply those changes. + +!!'Append' +You can press this button if you want to load more warnings, and have them added to the end of those already displayed. This will happen automatically when you are rating the last few warnings shown. + +!!'Show/hide details' +You can click on this link (or press the key 'd' on your keyboard) to show/hide more details about selected warning(s). + +!!'Vote once' +It is recommended to use this option. If you have it selected, the interface will recognize if you've already rated a warning and avoid displaying it to +you again in the current or any subsequent rating session. You will need to log in with your NR account in order to choose this option, and also for it to work properly. + + +!!!Warnings display +You can think of the warnings as being displayed in a table of rows and columns. Each row deals with only one warning, and the various columns give different information about the warning. The following is a short description (from left to right) of the type of information contained in each column. + +!!Strength +In the same way as in the NR reports, the first column contains a color-coded number from 0 to 100+, and is the initial value assigned to the warning when NR filtered it the first time, with higher numbers indicating that NR is reporting a greater likelihood of that site being inappropriate. This value will never be affected by your rating of the warning. + +!!Current rating +The second column contains a number from 0 to 5, representing the current rating of that warning, based on how it has been rated by other users and/or accountability partners. If the number is 0, it means the warning has not yet been rated by anyone. The numbers 1, 2, 3, 4, and 5, represent points along a continuum from something that was definitely a false positive (lower number) to something that was definitely an inappropriate site (higher number). Once a warning has been rated more than once, this number is based on the average rating, so you may see numbers with decimals like 1.23 or 3.45, etc., but they will all be within the 1-5 range if they have been rated before. The rating that you give will be included in calculating a new average rating that will appear in this column. If you choose the 'Show details' option, the number of "votes" will also be displayed within parentheses in this column. + +!!Rate +In the third column, for a warning you have not yet rated, you will see the numbers 1, 2, 3, 4, and 5. You can click on any of these numbers to rate the warning. This can also be done with the keyboard by first [[#17 selecting the warning(s)]] you want to rate and then pressing the number on the keyboard of the rating you want to give. If you choose the 'Show details' option, the blacklist category and keyword for the warning will be displayed in this column +as well. Once you have rated a warning, only the number you gave it will show up in this column. + +!!Abbreviated URL +The fourth column contains the abbreviated URL with emphasized matches. This is what you will use to determine what rating to give the warning. Hovering over the URL will show the blacklist category and keyword. If you choose the 'Show details' option, the complete URL will display, also with the matches emphasized. Clicking on the URL will not take you to the associated site. + + +!!!How to rate the warnings +So far, we have looked at the various details and options found on the online interface page for interacting with the improvement data. In this section we will look at how you actually rate the warnings. + +!!How do I know what number to rate a warning as? +We want to see each warning rated according to the following points or markers on a 1-5 continuum: + - <!1:!> This is definitely a false positive. The keyword might be present, but it's obvious it wasn't any harm. Example string from URL: + +<*cas.be.eu.criteo.com/..._SIMBHNUZBLkvp90fZwLE<!SeX!>vVkp5MPrZms71bFwm8o...*> + + - <!2:!> This was a match, but is unlikely a really dangerous site. Example string from URL: + +<*a.tribalfusion.com/...50&addBlockingCategories=<!Adult!>,Political,Flashing...*> + + - <!3:!> You should probably look at the URL to ensure this isn't something to be concerned about. It's a match, but not necessarily dangerous. Example string from URL: + +<*upload.wikimedia.org/...150px-<!MariahCarey!>13EdwardsDec1998.jpg*> + + - <!4:!> This is most probably something to worry about. If several of these URLs are listed you should get in touch with the user to check if everything is okay. Example string from URL: + +<*www.google.com/...&geo&q="<!sunny!>+<!leone!>+<!sex!>"&gprop&date=today+3-m&...*> + + - <!5:!> This is not only a match, it's <*definitely*> a bad site; you don't even have to think twice, it's really that obvious. Most often a combination of several keywords are found in the same URL. We'd rather not give an example for this level. + +<!Note:!> If you have also rated warnings from within an NR report, you will notice that the 1-2-3-4-5 rating continuum detailed above is identical to the 0-25-50-75-100 rating continuum used in the reports, but just using different numbers. The reason for the difference in numbers is because this online interface was developed before the 0-25-50-75-100 levels of strength were set, which are used in the reports. So, even though the numbers are different, the rating is done in the same way. See the [[0705-UnderstandingReports.html#4 'Warnings' section of the "Understanding the Reports" guide]] for more information about the levels of strength used in the reports and how you can rate warnings within a report. + +!!Selecting and deselecting warnings +You can select a warning by clicking on it anywhere except on the numbered links in the third column. When a warning is selected, it will have a grey background. If you want to select multiple warnings that are consecutive, select the first one and then hold down the 'Shift' key while clicking on the last one. If you want to select multiple warnings that are not consecutive, select one of them and then hold down the 'Ctrl' key while clicking on the others. The advantage of selecting multiple warnings is that you can then rate them all at the same time with the same number. If you have multiple warnings selected, you can also deselect any one of them by holding down the 'Ctrl' key while clicking on the one you don't want selected. If you want to deselect all warnings, you can simply click on any warning (without holding any keys down), which will result in only that one being selected. + +!!Rating the warnings +As mentioned above, you can click on the numbered links in the third column in order to rate a warning, but you can also use the numbers on your keyboard to give ratings to whatever warnings are selected at the time. When you press 1, 2, 3, 4, or 5 on the keyboard, all the selected warnings will be given that number rating. Once you do this, the next unrated warning will then be automatically selected. This makes it easier to go through a lot of warnings, simply by selecting one and pressing the keys 1-5 accordingly, or selecting a lot of warnings at the same time and giving them all the same rating. You may also use the up and down arrows on your keyboard to select the next or previous warning. + + +!!!Ideas and tips for avoiding and resisting temptations +Obviously, if you help with rating this improvement data, you'll likely find a lot of warnings and matches that may pull your thoughts in directions you don't want to go. Because of this, you will want to make sure you do whatever you need to in order to avoid and resist temptation. Here are a couple ideas that might help with this: + - Only rate the improvement data when someone else is around. Even better is to tell them explicitly what you're about to do, and ask them to keep an eye on you. + - Never do it when you're too tired or are feeling sick. When you're weak physically, it will be easier to fall than at other times. + - If you sense that your thoughts are wandering inappropriately, shut down the computer/internet access immediately. It's simply not worth it. + - Only rate warnings with a low strength, since these are probably not as harmful. This can be set in the 'Where' field. + - When you face warnings that have an obvious rating of 5, don't stop and look at them, just rate and proceed. Refuse to let yourself think about what the image, website, movie etc. looked like in reality. The same thing goes for other rating levels as well. If the level is more or less obvious, then don't take time to investigate it further, just rate and proceed. + - Set a time limit on how long you're going to sit down and do this. It might be better to do it in a few shorter intervals than for an extended period of time. + - If you for any reason realize that you shouldn't be doing this, then you may blacklist the site by adding it to your personal blacklist. + This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <mpn...@us...> - 2012-05-27 00:52:33
|
Revision: 319 http://responsibility.svn.sourceforge.net/responsibility/?rev=319&view=rev Author: mpnordland Date: 2012-05-27 00:52:27 +0000 (Sun, 27 May 2012) Log Message: ----------- Readding HTTPHit files, seems they didn't make it, access to the internal request and response objects is now added, along with the url being stored as a object attribute Modified Paths: -------------- branches/multiuser/projectFiles/linux/net-responsibility.layout Added Paths: ----------- branches/multiuser/include/HTTPHit.h branches/multiuser/src/HTTPHit.cpp Added: branches/multiuser/include/HTTPHit.h =================================================================== --- branches/multiuser/include/HTTPHit.h (rev 0) +++ branches/multiuser/include/HTTPHit.h 2012-05-27 00:52:27 UTC (rev 319) @@ -0,0 +1,49 @@ +// This file is part of Net Responsibility. +// +// Net Responsibility is free software: you can redistribute it and/or modify +// it under the terms of the GNU General Public License as published by +// the Free Software Foundation, either version 2 of the License, or +// (at your option) any later version. +// +// Net Responsibility is distributed in the hope that it will be useful, +// but WITHOUT ANY WARRANTY; without even the implied warranty of +// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +// GNU General Public License for more details. +// +// You should have received a copy of the GNU General Public License +// along with Net Responsibility. If not, see <http://www.gnu.org/licenses/>. +// +//HTTPHit can store all the information about a url. + + + +#ifndef HTTPHIT_H +#define HTTPHIT_H +#include <iostream> +#include <string> +#include <sstream> +#include "/Poco/Net/HTTPRequest.h" +#include "/Poco/Net/HTTPResponse.h" +#include "/Poco/Net/HTTPMessage.h" + +using Poco::Net::HTTPMessage; +using Poco::Net::HTTPRequest; +using Poco::Net::HTTPResponse; +using namespace std; + +class HTTPHit +{ + + public: + HTTPHit(); + virtual void read(string); + HTTPRequest* getRequest(); + HTTPResponse* getResponse(); + protected: + HTTPRequest _request; + HTTPResponse _response; + string _url; +} + + +#endif //HTTPHIT_H Modified: branches/multiuser/projectFiles/linux/net-responsibility.layout =================================================================== --- branches/multiuser/projectFiles/linux/net-responsibility.layout 2012-05-26 17:15:14 UTC (rev 318) +++ branches/multiuser/projectFiles/linux/net-responsibility.layout 2012-05-27 00:52:27 UTC (rev 319) @@ -19,8 +19,8 @@ <File name="../../include/Filter.h" open="1" top="0" tabpos="18"> <Cursor position="1342" topLine="30" /> </File> - <File name="../../include/HTTPHit.h" open="1" top="1" tabpos="31"> - <Cursor position="309" topLine="0" /> + <File name="../../include/HTTPHit.h" open="1" top="0" tabpos="31"> + <Cursor position="1350" topLine="8" /> </File> <File name="../../include/History.h" open="1" top="0" tabpos="30"> <Cursor position="0" topLine="60" /> @@ -74,10 +74,10 @@ <Cursor position="4017" topLine="113" /> </File> <File name="../../src/Filter.cpp" open="1" top="0" tabpos="7"> - <Cursor position="1528" topLine="184" /> + <Cursor position="1528" topLine="127" /> </File> - <File name="../../src/HTTPHit.cpp" open="1" top="0" tabpos="32"> - <Cursor position="0" topLine="0" /> + <File name="../../src/HTTPHit.cpp" open="1" top="1" tabpos="32"> + <Cursor position="306" topLine="0" /> </File> <File name="../../src/History.cpp" open="1" top="0" tabpos="6"> <Cursor position="723" topLine="113" /> Added: branches/multiuser/src/HTTPHit.cpp =================================================================== --- branches/multiuser/src/HTTPHit.cpp (rev 0) +++ branches/multiuser/src/HTTPHit.cpp 2012-05-27 00:52:27 UTC (rev 319) @@ -0,0 +1,32 @@ +#include "HTTPHit.h" + +HTTPHit::HTTPHit() +{ +} + +HTTPHit::read(string message) +{ + istringstream inStream(message); + if (message.find("HTTP") != message.npos) + { + //this is a request + this->_request.read(inStream); + this->_url = this->_request.getHost() + this->_request.getURI(); + } + + else: + { + //this is a response + this->_response.read(inStream); + } +} + +HTTPHit::getRequest() +{ + return *_request; +} + +HTTPHit::getResponse() +{ + return *_response; +} This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <mpn...@us...> - 2012-05-26 17:15:20
|
Revision: 318 http://responsibility.svn.sourceforge.net/responsibility/?rev=318&view=rev Author: mpnordland Date: 2012-05-26 17:15:14 +0000 (Sat, 26 May 2012) Log Message: ----------- Adding HTTPHit class with basic functionality Modified Paths: -------------- branches/C++_Rewrite/proxy/net-responsibility-proxy/net-responsibility-proxy.layout branches/multiuser/Socket_fun/Socket_fun/Socket_fun.layout branches/multiuser/projectFiles/linux/net-responsibility.cbp branches/multiuser/projectFiles/linux/net-responsibility.layout Modified: branches/C++_Rewrite/proxy/net-responsibility-proxy/net-responsibility-proxy.layout =================================================================== --- branches/C++_Rewrite/proxy/net-responsibility-proxy/net-responsibility-proxy.layout 2012-05-26 15:31:50 UTC (rev 317) +++ branches/C++_Rewrite/proxy/net-responsibility-proxy/net-responsibility-proxy.layout 2012-05-26 17:15:14 UTC (rev 318) @@ -1,8 +1,8 @@ <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <CodeBlocks_layout_file> <ActiveTarget name="Debug" /> - <File name="include/ProxyServer.h" open="1" top="0" tabpos="2"> - <Cursor position="1406" topLine="26" /> + <File name="include/ProxyServer.h" open="1" top="0" tabpos="3"> + <Cursor position="1406" topLine="28" /> </File> <File name="include/ProxyServerConnection.h" open="1" top="0" tabpos="4"> <Cursor position="0" topLine="0" /> @@ -10,8 +10,8 @@ <File name="include/ProxyServerConnectionFactory.h" open="1" top="0" tabpos="6"> <Cursor position="455" topLine="0" /> </File> - <File name="src/ProxyServer.cpp" open="1" top="0" tabpos="3"> - <Cursor position="1435" topLine="19" /> + <File name="src/ProxyServer.cpp" open="1" top="0" tabpos="4"> + <Cursor position="1435" topLine="21" /> </File> <File name="src/ProxyServerConnection.cpp" open="1" top="0" tabpos="5"> <Cursor position="151" topLine="0" /> @@ -19,7 +19,7 @@ <File name="src/ProxyServerConnectionFactory.cpp" open="1" top="1" tabpos="7"> <Cursor position="164" topLine="0" /> </File> - <File name="src/main.cpp" open="1" top="0" tabpos="1"> + <File name="src/main.cpp" open="1" top="0" tabpos="2"> <Cursor position="21" topLine="0" /> </File> </CodeBlocks_layout_file> Modified: branches/multiuser/Socket_fun/Socket_fun/Socket_fun.layout =================================================================== (Binary files differ) Modified: branches/multiuser/projectFiles/linux/net-responsibility.cbp =================================================================== --- branches/multiuser/projectFiles/linux/net-responsibility.cbp 2012-05-26 15:31:50 UTC (rev 317) +++ branches/multiuser/projectFiles/linux/net-responsibility.cbp 2012-05-26 17:15:14 UTC (rev 318) @@ -147,6 +147,7 @@ <Unit filename="../../include/ConfigSubsystem.h" /> <Unit filename="../../include/Database.h" /> <Unit filename="../../include/Filter.h" /> + <Unit filename="../../include/HTTPHit.h" /> <Unit filename="../../include/History.h" /> <Unit filename="../../include/MainApplication.h" /> <Unit filename="../../include/MyXml.h" /> @@ -160,11 +161,13 @@ <Unit filename="../../include/Sniffer.h" /> <Unit filename="../../include/SnifferSubsystem.h" /> <Unit filename="../../include/SnifferThread.h" /> + <Unit filename="../../include/UID.h" /> <Unit filename="../../include/Warnings.h" /> <Unit filename="../../src/Bypasses.cpp" /> <Unit filename="../../src/ConfigSubsystem.cpp" /> <Unit filename="../../src/Database.cpp" /> <Unit filename="../../src/Filter.cpp" /> + <Unit filename="../../src/HTTPHit.cpp" /> <Unit filename="../../src/History.cpp" /> <Unit filename="../../src/MainApplication.cpp" /> <Unit filename="../../src/MyXml.cpp" /> @@ -178,12 +181,14 @@ <Unit filename="../../src/Sniffer.cpp" /> <Unit filename="../../src/SnifferSubsystem.cpp" /> <Unit filename="../../src/SnifferThread.cpp" /> + <Unit filename="../../src/UID.cpp" /> <Unit filename="../../src/Warnings.cpp" /> <Unit filename="../../src/main.cpp" /> <Extensions> <code_completion /> <debugger /> <lib_finder disable_auto="1" /> + <envvars /> </Extensions> </Project> </CodeBlocks_project_file> Modified: branches/multiuser/projectFiles/linux/net-responsibility.layout =================================================================== --- branches/multiuser/projectFiles/linux/net-responsibility.layout 2012-05-26 15:31:50 UTC (rev 317) +++ branches/multiuser/projectFiles/linux/net-responsibility.layout 2012-05-26 17:15:14 UTC (rev 318) @@ -7,26 +7,29 @@ <File name="../../include/Blacklist.h" open="1" top="0" tabpos="22"> <Cursor position="2485" topLine="136" /> </File> - <File name="../../include/Bypasses.h" open="1" top="0" tabpos="25"> + <File name="../../include/Bypasses.h" open="1" top="0" tabpos="24"> <Cursor position="2114" topLine="34" /> </File> <File name="../../include/ConfigSubsystem.h" open="1" top="0" tabpos="22"> <Cursor position="0" topLine="20" /> </File> - <File name="../../include/Database.h" open="1" top="0" tabpos="22"> - <Cursor position="1596" topLine="42" /> + <File name="../../include/Database.h" open="1" top="0" tabpos="28"> + <Cursor position="2738" topLine="56" /> </File> <File name="../../include/Filter.h" open="1" top="0" tabpos="18"> - <Cursor position="1342" topLine="37" /> + <Cursor position="1342" topLine="30" /> </File> - <File name="../../include/History.h" open="1" top="0" tabpos="22"> - <Cursor position="2025" topLine="66" /> + <File name="../../include/HTTPHit.h" open="1" top="1" tabpos="31"> + <Cursor position="309" topLine="0" /> </File> + <File name="../../include/History.h" open="1" top="0" tabpos="30"> + <Cursor position="0" topLine="60" /> + </File> <File name="../../include/MainApplication.h" open="1" top="0" tabpos="21"> - <Cursor position="2876" topLine="81" /> + <Cursor position="2876" topLine="74" /> </File> <File name="../../include/MyXml.h" open="1" top="0" tabpos="26"> - <Cursor position="1051" topLine="21" /> + <Cursor position="1051" topLine="14" /> </File> <File name="../../include/Options.h" open="1" top="0" tabpos="22"> <Cursor position="2965" topLine="93" /> @@ -37,50 +40,53 @@ <File name="../../include/PluginBase.h" open="1" top="0" tabpos="33"> <Cursor position="67" topLine="0" /> </File> - <File name="../../include/Report.h" open="1" top="0" tabpos="24"> - <Cursor position="1318" topLine="54" /> + <File name="../../include/Report.h" open="1" top="0" tabpos="23"> + <Cursor position="1318" topLine="47" /> </File> <File name="../../include/ReportBase.h" open="1" top="0" tabpos="22"> <Cursor position="1817" topLine="28" /> </File> - <File name="../../include/ReportSubsystem.h" open="1" top="0" tabpos="27"> - <Cursor position="1141" topLine="35" /> + <File name="../../include/ReportSubsystem.h" open="1" top="0" tabpos="25"> + <Cursor position="1141" topLine="28" /> </File> <File name="../../include/Request.h" open="1" top="0" tabpos="20"> - <Cursor position="1635" topLine="41" /> + <Cursor position="1635" topLine="35" /> </File> <File name="../../include/Sniffer.h" open="1" top="0" tabpos="19"> - <Cursor position="1386" topLine="27" /> + <Cursor position="2423" topLine="57" /> </File> <File name="../../include/SnifferSubsystem.h" open="1" top="0" tabpos="22"> <Cursor position="1364" topLine="22" /> </File> - <File name="../../include/SnifferThread.h" open="1" top="0" tabpos="22"> - <Cursor position="4248" topLine="132" /> + <File name="../../include/SnifferThread.h" open="1" top="0" tabpos="27"> + <Cursor position="4886" topLine="91" /> </File> - <File name="../../include/Warnings.h" open="1" top="0" tabpos="22"> - <Cursor position="428" topLine="12" /> + <File name="../../include/Warnings.h" open="1" top="0" tabpos="29"> + <Cursor position="428" topLine="5" /> </File> <File name="../../src/Bypasses.cpp" open="1" top="0" tabpos="14"> - <Cursor position="3150" topLine="156" /> + <Cursor position="3150" topLine="149" /> </File> <File name="../../src/ConfigSubsystem.cpp" open="1" top="0" tabpos="11"> - <Cursor position="1586" topLine="36" /> + <Cursor position="1586" topLine="29" /> </File> <File name="../../src/Database.cpp" open="1" top="0" tabpos="2"> - <Cursor position="2826" topLine="67" /> + <Cursor position="4017" topLine="113" /> </File> <File name="../../src/Filter.cpp" open="1" top="0" tabpos="7"> <Cursor position="1528" topLine="184" /> </File> + <File name="../../src/HTTPHit.cpp" open="1" top="0" tabpos="32"> + <Cursor position="0" topLine="0" /> + </File> <File name="../../src/History.cpp" open="1" top="0" tabpos="6"> - <Cursor position="723" topLine="120" /> + <Cursor position="723" topLine="113" /> </File> <File name="../../src/MainApplication.cpp" open="1" top="0" tabpos="12"> - <Cursor position="6939" topLine="244" /> + <Cursor position="6939" topLine="3" /> </File> <File name="../../src/MyXml.cpp" open="1" top="0" tabpos="17"> - <Cursor position="3782" topLine="115" /> + <Cursor position="3782" topLine="108" /> </File> <File name="../../src/Options.cpp" open="1" top="0" tabpos="9"> <Cursor position="1994" topLine="85" /> @@ -92,25 +98,25 @@ <Cursor position="0" topLine="0" /> </File> <File name="../../src/Report.cpp" open="1" top="0" tabpos="3"> - <Cursor position="8934" topLine="278" /> + <Cursor position="8934" topLine="197" /> </File> - <File name="../../src/ReportBase.cpp" open="1" top="1" tabpos="16"> - <Cursor position="1689" topLine="181" /> + <File name="../../src/ReportBase.cpp" open="1" top="0" tabpos="16"> + <Cursor position="1689" topLine="172" /> </File> <File name="../../src/ReportSubsystem.cpp" open="1" top="0" tabpos="10"> <Cursor position="1078" topLine="28" /> </File> <File name="../../src/Request.cpp" open="1" top="0" tabpos="5"> - <Cursor position="1830" topLine="18" /> + <Cursor position="1830" topLine="9" /> </File> <File name="../../src/Sniffer.cpp" open="1" top="0" tabpos="4"> - <Cursor position="2391" topLine="18" /> + <Cursor position="1956" topLine="35" /> </File> <File name="../../src/SnifferSubsystem.cpp" open="1" top="0" tabpos="13"> - <Cursor position="1886" topLine="37" /> + <Cursor position="1886" topLine="24" /> </File> - <File name="../../src/SnifferThread.cpp" open="1" top="0" tabpos="23"> - <Cursor position="4443" topLine="131" /> + <File name="../../src/SnifferThread.cpp" open="1" top="0" tabpos="22"> + <Cursor position="2793" topLine="53" /> </File> <File name="../../src/Warnings.cpp" open="1" top="0" tabpos="8"> <Cursor position="627" topLine="54" /> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-26 15:31:56
|
Revision: 317 http://responsibility.svn.sourceforge.net/responsibility/?rev=317&view=rev Author: dustsource Date: 2012-05-26 15:31:50 +0000 (Sat, 26 May 2012) Log Message: ----------- Made the following edits to the documentation: --In the "Compile from Source" guide: --'Testing the installation' section: replaced previous instructions with a link to the relevant section in the "Troubleshooting Installation and Configuration" guide. --'Introduction' section: --Edited 'older versions' link to point to SourceForge collection of .deb and tar.gz packages. --Noted the need for the installation of whatever packages are needed for compiling. --In the "Install from Packages" guide: --Added a 'Testing the installation' section at the end. --'Introduction' section: --Edited 'older versions' link to point to SourceForge collection of .deb and tar.gz packages. --edited the 'source code' links in the 'About binary packages' and 'Mac OS X' sections to point to the "Compile from Source" guide. --'Ubuntu' section: clarified that the PPA is only for users who are using Ubuntu versions currently supported by Canonical. --In the "Troubleshooting Reports" guide: --'Why am I not receiving a report?' section: added a link to the "Troubleshooting Installation and Configuration" guide. --In the "FAQ" guide: --'Installing...' section: added question regarding testing NR. Modified Paths: -------------- documentation/doc/net-responsibility-3.0.2-doc.zip Modified: documentation/doc/net-responsibility-3.0.2-doc.zip =================================================================== (Binary files differ) This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-26 15:30:13
|
Revision: 316 http://responsibility.svn.sourceforge.net/responsibility/?rev=316&view=rev Author: dustsource Date: 2012-05-26 15:30:06 +0000 (Sat, 26 May 2012) Log Message: ----------- Made the following edits to the documentation: --In the "Compile from Source" guide: --'Testing the installation' section: replaced previous instructions with a link to the relevant section in the "Troubleshooting Installation and Configuration" guide. --'Introduction' section: --Edited 'older versions' link to point to SourceForge collection of .deb and tar.gz packages. --Noted the need for the installation of whatever packages are needed for compiling. --In the "Install from Packages" guide: --Added a 'Testing the installation' section at the end. --'Introduction' section: --Edited 'older versions' link to point to SourceForge collection of .deb and tar.gz packages. --edited the 'source code' links in the 'About binary packages' and 'Mac OS X' sections to point to the "Compile from Source" guide. --'Ubuntu' section: clarified that the PPA is only for users who are using Ubuntu versions currently supported by Canonical. --In the "Troubleshooting Reports" guide: --'Why am I not receiving a report?' section: added a link to the "Troubleshooting Installation and Configuration" guide. --In the "FAQ" guide: --'Installing...' section: added question regarding testing NR. Modified Paths: -------------- documentation/pages/0304-InstallFromPackages.page documentation/pages/0305-CompileFromSource.page documentation/pages/0709-TroubleshootingReports.page documentation/pages/0901-FAQ.page Modified: documentation/pages/0304-InstallFromPackages.page =================================================================== --- documentation/pages/0304-InstallFromPackages.page 2012-05-21 11:52:26 UTC (rev 315) +++ documentation/pages/0304-InstallFromPackages.page 2012-05-26 15:30:06 UTC (rev 316) @@ -8,15 +8,15 @@ 1. Before installing Net Responsibility (NR), you'll need to [[http://netresponsibility.com/register.php register an account]] if you haven't already. -2. Older versions are provided but not recommended. [[http://netresponsibility.com/download.php#Older You may find them here]]. +2. Older versions are provided but not recommended. [[https://sourceforge.net/projects/responsibility/files/net-responsibility/ You may find them here]]. !!!About binary packages -We hope to supply binary packages (installation files) for as many platforms (operating systems) as possible. If there is none for your platform, you'll need to download and compile the [[http://netresponsibility.com/download.php#Source source code]]. If you would be interested in creating such packages for any platform, please [[mailto:res...@li... let us know]]. +We hope to supply binary packages (installation files) for as many platforms (operating systems) as possible. If there is none for your platform, you'll need to download and compile the [[0305-CompileFromSource.html source code]]. If you would be interested in creating such packages for any platform, please [[mailto:res...@li... let us know]]. !!!Ubuntu <!Note:!> If you have version 2.0.2 or earlier installed, you will need to uninstall it before installing a later version. The older versions are named <*netresponsibility*> (without a dash), whereas the newer ones are named <*net-responsibility*> (with a dash). -There is a PPA (Personal Package Archive) for Ubuntu users. To add the PPA to your system and install the latest version of NR, simply run these commands in a terminal: +There is a PPA (Personal Package Archive) for users of Ubuntu versions that are currently supported by Canonical. To add the PPA to your system and install the latest version of NR, simply run these commands in a terminal: sudo add-apt-repository ppa:roggan87/nr sudo apt-get update @@ -30,7 +30,7 @@ Alternative manual installation method: Download the [[https://sourceforge.net/projects/responsibility/files/net-responsibility/ DEB (.deb) package]] of the latest version, double-click on it, and follow the on-screen prompts. !!!Mac OS X -We're working on creating packages for Mac users. It is technically possible to download the [[http://netresponsibility.com/download.php#Source source code]] and compile it. More information about compiling it on Mac can be [[http://netresponsibility.com/forum/index.php?topic=63.0 found here]]. However, the easiest thing would be to wait (or help us out with creating the package). +We're working on creating packages for Mac users. It is technically possible to download the [[0305-CompileFromSource.html source code]] and compile it. More information about compiling it on Mac can be [[http://netresponsibility.com/forum/index.php?topic=63.0 found here]]. However, the easiest thing would be to wait (or help us out with creating the package). !!!Windows Our goal is to supply NR for all major platforms, including Windows. There are some important features that are not yet implemented in the Windows version. Therefore we've decided to wait before we release it. Once those things are fixed, we'll create an installation file and post it here. @@ -72,3 +72,5 @@ During the last step, you need to enter a username and password. Simply use the same as you did when registering your NR account. +!!!Testing the installation +If you've successfully worked through the steps above, NR should now be installed. If you want to test to see if it is running as it should, see the [[0309-TroubleshootingInstallation.html#0 Troubleshooting Installation and Configuration]] guide for instructions on the best way to do this. Modified: documentation/pages/0305-CompileFromSource.page =================================================================== --- documentation/pages/0305-CompileFromSource.page 2012-05-21 11:52:26 UTC (rev 315) +++ documentation/pages/0305-CompileFromSource.page 2012-05-26 15:30:06 UTC (rev 316) @@ -10,8 +10,10 @@ 1. Before installing Net Responsibility (NR), you'll need to [[http://netresponsibility.com/register.php register an account]] if you haven't already. -2. Older versions are provided but not recommended. [[http://netresponsibility.com/download.php#Older You may find them here]]. +2. Older versions are provided but not recommended. [[https://sourceforge.net/projects/responsibility/files/net-responsibility/ You may find them here]]. +3. Necessary packages that are needed for compiling will need to be installed (if they are not already) before you can successfully complete the following steps. On an Ubuntu system, you should be able to do this by making sure the <*build-essential*> package is installed, since this results in the installation of a group of compiling-related packages that are needed for doing any Debian package building. This package might not be installed by default in your version of Ubuntu. + !!!POCO libraries You will first need to install the POCO libraries. Note that the version needs to be 1.4 or later. Some platforms have these libraries precompiled and packaged. Otherwise you need to compile them yourself. Start by [[http://pocoproject.org/download/index.html downloading the complete edition]] (i.e. not the <*basic edition*>). Unpack (extract) it (on a platform like Ubuntu, this can often be done by right-clicking on the file and choosing the unpack/extract option from the menu), which will result in the creation of a directory (folder) with the same name as the file you downloaded, and which contains other folders and files. If you want, you can unpack the file to one directory and then copy the extracted contents to another directory where you will work with it. Once you have the POCO folders and files in the directory you want them, you then need to open a terminal window and use the <*cd*> command to move yourself to that directory. While there you then need to do three things: configure, compile and install. For a user who has chosen to use the <*/home/name/poco*> directory, the procedure should look like this: @@ -38,9 +40,4 @@ During the last step, you need to enter a username and password. Simply use the same as you did when registering your NR account. !!!Testing the installation -If you've successfully worked through the steps above, NR should now be installed. If you want to test to see if it is running as it should, you can run the following command in the terminal: - - ps -ef|grep net-responsibility ----- - -If the only line you see contains <*grep*>, then it's not running as it should. However, if you see an additional line that contains <*net-responsibility --daemon*> then you know it is running as it should. +If you've successfully worked through the steps above, NR should now be installed. If you want to test to see if it is running as it should, see the [[0309-TroubleshootingInstallation.html#0 Troubleshooting Installation and Configuration]] guide for instructions on the best way to do this. Modified: documentation/pages/0709-TroubleshootingReports.page =================================================================== --- documentation/pages/0709-TroubleshootingReports.page 2012-05-21 11:52:26 UTC (rev 315) +++ documentation/pages/0709-TroubleshootingReports.page 2012-05-26 15:30:06 UTC (rev 316) @@ -3,7 +3,7 @@ !!!Why am I not receiving a report? Assuming that any necessary internet connections are working, the following are possible reasons why someone did not receive a Net Responsibility (NR) report that they were expecting: - - The user has not successfully registered, installed, and/or configured the NR program. + - The user has not successfully registered, installed, and/or configured the NR program. In this case, the [[0309-TroubleshootingInstallation.html Troubleshooting Installation and Configuration guide]] may be helpful. - There is a bug in the NR program. - The user did not enter the expected email address during the registration process, or did not save their settings. - The email containing the report was considered spam by the email server or email client, and was automatically quarantined, or directed to a Spam/Junk/Trash folder. Modified: documentation/pages/0901-FAQ.page =================================================================== --- documentation/pages/0901-FAQ.page 2012-05-21 11:52:26 UTC (rev 315) +++ documentation/pages/0901-FAQ.page 2012-05-26 15:30:06 UTC (rev 316) @@ -64,6 +64,9 @@ !!How do I download and/or install a copy of the NR software? If you are interested in a precompiled package (installation file), see [[0304-InstallFromPackages.html these instructions]]. If you are interested in compiling from the source code, see [[0305-CompileFromSource.html these instructions]]. +!!How can I test whether NR is running properly or not? +See the [[0309-TroubleshootingInstallation.html#0 Troubleshooting Installation and Configuration guide]] for instructions on the best way to do this. + !!How do I check what version of NR is installed? One way this can be done is by opening a terminal window and running the following command as root (for Ubuntu users, this means adding <*sudo*> and a space before the command): net-responsibility --debug This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <rog...@us...> - 2012-05-21 11:52:37
|
Revision: 315 http://responsibility.svn.sourceforge.net/responsibility/?rev=315&view=rev Author: roggan87 Date: 2012-05-21 11:52:26 +0000 (Mon, 21 May 2012) Log Message: ----------- Changed the forgot_login_info text. Modified Paths: -------------- documentation/web.txt Modified: documentation/web.txt =================================================================== --- documentation/web.txt 2012-05-19 16:10:27 UTC (rev 314) +++ documentation/web.txt 2012-05-21 11:52:26 UTC (rev 315) @@ -349,10 +349,10 @@ -#forgot_password# +#forgot_login_info# Simply type your username or email address in the field below, and you'll -receive an email with your password. +receive an email with your username and password. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-19 16:10:33
|
Revision: 314 http://responsibility.svn.sourceforge.net/responsibility/?rev=314&view=rev Author: dustsource Date: 2012-05-19 16:10:27 +0000 (Sat, 19 May 2012) Log Message: ----------- Made the following edits to the documentation: --In the "Understanding the Reports" guide: --Added information about the NR report's number ranking feature for 'Warnings' items, in relation to the likelihood of an URL being a cause for concern or not. --Added information about how accountability partners and/or users can help improve the accuracy of the above number ranking feature. --Made a few minor edits to text. --Edited links to enable ease of use both online and offline. --In the "Configuration Explained" guide: --Under (Configuration parts / Tweaks / Report strength threshold), expanded explanation of the number ranking system of the 'Warnings' section in reports, and provided a link to the ("Understanding the Reports" guide / Sections of the report / Warnings) section for those who want to find out more details and/or would like to help with improving the accuracy of the ranking system. --Under (Configuration parts / Report parts), included a brief note that the attached report is required for those who want to help improve the accuracy of reports, with a corresponding link to the 'Improving the Reports' section of the "Understanding the Reports" guide. --Under (Configuration parts / Report parts / Warnings), added explanation of the number ranking system, and provided a link to the ("Understanding the Reports" guide / Sections of the report / Warnings) section for those who want to find out more details and/or would like to help with improving the accuracy of the ranking system. --Made minor edits to text. --In the "Being a Good Accountability Partner" guide: --Under 'How Does it Work?', included a link to the 'Improving the Reports' section of the "Understanding the Reports" guide for APs who might want to help with this. --Edited links to enable ease of use both online and offline. --In the "Troubleshooting the Reports" guide: --Added section titled 'Why are there so many false positives?', which briefly refers to the 'Warnings' section, the number ranking system, and the opportunity to help improve the accuracy of the reports, including a link to the 'Improving the Reports' section of the "Understanding the Reports" guide for anyone who might want to help with this. --Edited links to enable ease of use both online and offline. --In the "FAQ" guide: --Added item in the 'Reports -- Problems' section, titled 'Why are there so many false positives?'. --Edited links to enable ease of use both online and offline. --In the "Contribute to NR" guide: --Added 'Improve the Reports' section. --In the "Troubleshooting Installation and Configuration" guide: --Edited links to enable ease of use both online and offline. --In the "Mission Statement" document: --Made some minor text edits and added a link to the 'Improving the Reports' section of the "Understanding the Reports" guide for anyone who might want to help with this. --In the "Privacy Policy" document: --Made some minor text and link edits. Modified Paths: -------------- documentation/doc/net-responsibility-3.0.2-doc.zip Modified: documentation/doc/net-responsibility-3.0.2-doc.zip =================================================================== (Binary files differ) This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-19 16:06:18
|
Revision: 313 http://responsibility.svn.sourceforge.net/responsibility/?rev=313&view=rev Author: dustsource Date: 2012-05-19 16:06:10 +0000 (Sat, 19 May 2012) Log Message: ----------- Made the following edits to the documentation: --In the "Understanding the Reports" guide: --Added information about the NR report's number ranking feature for 'Warnings' items, in relation to the likelihood of an URL being a cause for concern or not. --Added information about how accountability partners and/or users can help improve the accuracy of the above number ranking feature. --Made a few minor edits to text. --Edited links to enable ease of use both online and offline. --In the "Configuration Explained" guide: --Under (Configuration parts / Tweaks / Report strength threshold), expanded explanation of the number ranking system of the 'Warnings' section in reports, and provided a link to the ("Understanding the Reports" guide / Sections of the report / Warnings) section for those who want to find out more details and/or would like to help with improving the accuracy of the ranking system. --Under (Configuration parts / Report parts), included a brief note that the attached report is required for those who want to help improve the accuracy of reports, with a corresponding link to the 'Improving the Reports' section of the "Understanding the Reports" guide. --Under (Configuration parts / Report parts / Warnings), added explanation of the number ranking system, and provided a link to the ("Understanding the Reports" guide / Sections of the report / Warnings) section for those who want to find out more details and/or would like to help with improving the accuracy of the ranking system. --Made minor edits to text. --In the "Being a Good Accountability Partner" guide: --Under 'How Does it Work?', included a link to the 'Improving the Reports' section of the "Understanding the Reports" guide for APs who might want to help with this. --Edited links to enable ease of use both online and offline. --In the "Troubleshooting the Reports" guide: --Added section titled 'Why are there so many false positives?', which briefly refers to the 'Warnings' section, the number ranking system, and the opportunity to help improve the accuracy of the reports, including a link to the 'Improving the Reports' section of the "Understanding the Reports" guide for anyone who might want to help with this. --Edited links to enable ease of use both online and offline. --In the "FAQ" guide: --Added item in the 'Reports -- Problems' section, titled 'Why are there so many false positives?'. --Edited links to enable ease of use both online and offline. --In the "Contribute to NR" guide: --Added 'Improve the Reports' section. --In the "Troubleshooting Installation and Configuration" guide: --Edited links to enable ease of use both online and offline. --In the "Mission Statement" document: --Made some minor text edits and added a link to the 'Improving the Reports' section of the "Understanding the Reports" guide for anyone who might want to help with this. --In the "Privacy Policy" document: --Made some minor text and link edits. Modified Paths: -------------- documentation/pages/0301-ConfigurationExplained.page documentation/pages/0309-TroubleshootingInstallation.page documentation/pages/0701-BeingAGoodAP.page documentation/pages/0705-UnderstandingReports.page documentation/pages/0709-TroubleshootingReports.page documentation/pages/0901-FAQ.page documentation/pages/0903-ContributeToNR.page documentation/pages/0905-MissionStatement.page documentation/pages/0910-PrivacyPolicy.page Modified: documentation/pages/0301-ConfigurationExplained.page =================================================================== --- documentation/pages/0301-ConfigurationExplained.page 2012-05-17 12:32:42 UTC (rev 312) +++ documentation/pages/0301-ConfigurationExplained.page 2012-05-19 16:06:10 UTC (rev 313) @@ -25,18 +25,18 @@ - <*Pidfile*>: The location of the pidfile must be specified; otherwise, NR will refuse to start. <!WARNING:!> Don't change this unless you know what you're doing! - <*Report frequency*>: Here you will enter the number of days you want between the emailed reports. If set to zero, the automatic reports will be disabled and you'll have to send reports manually, or by using the task-scheduling package <*cron*>. - <*Instant threshold*>: Here you can enable instant reports, which means your accountability partner will get a report instantly when NR thinks you're looking at inappropriate content. You can also set the sensitivity. Entering zero means this feature is disabled. Otherwise, lower numbers mean higher sensitivity. (0 = Disabled; 1-5 = Very sensitive; 6-20 = Medium; 21+ = Low sensitivity) - - <*Report strength threshold*>: Only matches with a strength higher than this number will be included in the reports. That way you're able to set some sort of sensitivity for what to display. + - <*Report strength threshold*>: Only matches with a strength higher than this number will be included in the <*Warnings*> section of the reports. That way you're able to set some sort of sensitivity for what to display. This number ranking system for these items is a fairly new feature that still needs to be tested and tweaked in order to make it accurate and useful. To find out more about this ranking system, including how you can help in making it more accurate, see [[0705-UnderstandingReports.html#4 this section]] of the "Understanding the Reports" guide. - <*Always perform tokenmatch*>: Using tokenmatch increases the report creation time because it's more complicated, but it results in much more accurate reports. If you're having problems with reports taking too long to create you might want to exclude it. - - <*Provide improvement data*>: Use this option if you'd like to help us with the development of NR. They program will <*anonymously*> send your warnings to our server and store them there. This will help us see how to improve the blacklists. + - <*Provide improvement data*>: Use this option if you'd like to help us with the development of NR. The program will <*anonymously*> send your warnings to our server and store them there. This will help us see how to improve the blacklists. - <*Send me newsletters*>: Choose this if you want the latest information about new versions, how to help, and other things that might be of interest. These emails are not sent on a regular basis, but rather whenever there's a need to update users with fresh information. !!Blacklist categories In this part, you can choose one or more <*blacklists*> that you want NR to use when creating your reports. Each of these blacklists is full of keywords. If any of the words are found in the websites you've visited, it will show up as a warning in the report. !!Report parts -Here you can choose what parts you want included in your NR reports. You can also choose to include a more detailed attached report, which is strongly recommended. Following are the various report parts and related options, along with a brief description of each: +Here you can choose what parts you want included in your NR reports. You can also choose to include a more detailed attached report, which is strongly recommended. (Also note that if you or your accountability partners want to [[0705-UnderstandingReports.html#9 help improve the accuracy of reports]], you will need to have an attached report sent.) Following are the various report parts and related options, along with a brief description of each: - <*Shutdowns*>: NR records if it's shutdown manually or interrupted. Choose this to list these shutdowns, if any, in the report. This can be chosen for the regular and/or attached reports. - - <*Warnings*>: The <*warnings*> part of the report lists any visited websites that contain one or more words from the blacklists. They could be inappropriate websites, but that is not always the case. Therefore, your accountability partner(s) should always double-check them, either by clicking the link or by reading the match in its context. It is strongly recommended to choose this option! This can be chosen for the regular and/or attached reports. + - <*Warnings*>: The <*warnings*> part of the report lists any visited websites that contain one or more words from the blacklists. They could be inappropriate websites, but that is not always the case. Therefore, your accountability partner(s) should always double-check them, either by clicking the link or by reading the match in its context. It is strongly recommended to choose this option! This can be chosen for the regular and/or attached reports. A new feature that is being developed and tested for this section is a number ranking system to indicate the likelihood of an item in this section being a cause for concern rather than a false positive. To find out more about this ranking system, including how you can help in making it more accurate, see [[0705-UnderstandingReports.html#4 this section]] of the "Understanding the Reports" guide. - <*Whitelist*>: If a website contains a blacklisted word, but <*also*> a whitelisted word, it will be found in this part of the report. This way you will be able to tell NR that some websites are okay. This can be chosen for the regular and/or attached reports. - <*No history*>: Choose this if you do not want any of your browsing history to be included in the attached report (this option is not available for regular reports). Note that all websites visited will be searched for a blacklist match independent of what you choose here. - <*Complete history*>: Choose this if you want your complete browsing history (i.e. every webpage accessed) to be included in the attached report (this option is not available for regular reports). Modified: documentation/pages/0309-TroubleshootingInstallation.page =================================================================== --- documentation/pages/0309-TroubleshootingInstallation.page 2012-05-17 12:32:42 UTC (rev 312) +++ documentation/pages/0309-TroubleshootingInstallation.page 2012-05-19 16:06:10 UTC (rev 313) @@ -59,11 +59,11 @@ If this command executes successfully and you are connected to the internet, then a manual report (i.e. a report of your internet activity) should be sent. -If you think test emails/reports and/or manual (or automatic) reports are being sent but are not being received by the email recipients, see [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports this guide]] for further troubleshooting ideas. +If you think test emails/reports and/or manual (or automatic) reports are being sent but are not being received by the email recipients, see [[0709-TroubleshootingReports.html this guide]] for further troubleshooting ideas. !!!Configuration changes are not implemented -If you have made changes to your configuration settings online, but NR does not seem to have implemented them, see [[http://netresponsibility.com/documentation.php?id=0301-ConfigurationsExplained this guide]] to make sure you are using the right procedure for making these changes. +If you have made changes to your configuration settings online, but NR does not seem to have implemented them, see [[0301-ConfigurationExplained.html this guide]] to make sure you are using the right procedure for making these changes. !!!Further help If you are having problems with installation and/or configuration that you are still not able to solve, [[http://www.netresponsibility.com/forum/ visit our forum]]. You can browse through the various threads in the "Installation and Configuration" category to see if anyone else has encountered the same problem and if you can find any solutions there. If that still doesn't help, you can start a new topic describing your problem, and we will do our best to assist you in resolving it. Note that you will need to be logged in to post to the forum. Modified: documentation/pages/0701-BeingAGoodAP.page =================================================================== --- documentation/pages/0701-BeingAGoodAP.page 2012-05-17 12:32:42 UTC (rev 312) +++ documentation/pages/0701-BeingAGoodAP.page 2012-05-19 16:06:10 UTC (rev 313) @@ -11,7 +11,7 @@ - A willingness to contact the user if there are concerns about possible inappropriate internet use. !!!How does it work? -Once an AP has given their email address to the user and the user has successfully completed registration, installation, and configuration of NR, then reports will be periodically emailed to the AP. To better understand the content of these reports, see [[http://netresponsibility.com/documentation.php?id=0705-UnderstandingReports Understanding the reports]]. For other problems with reports, see [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports Troubleshooting the reports]]. +Once an AP has given their email address to the user and the user has successfully completed registration, installation, and configuration of NR, then reports will be periodically emailed to the AP. To better understand the content of these reports, see [[0705-UnderstandingReports.html Understanding the reports]]. For other problems with reports, see [[0709-TroubleshootingReports.html Troubleshooting the reports]]. If you'd be willing to give a little bit of your time to helping improve the accuracy of the reports, see [[0705-UnderstandingReports.html#9 Improving the Reports]] for details on how you can do this. !!!Follow up on reports It is important that you as an AP follow up on anything that you have a question about in a report that you receive. It may turn out that there was actually no inappropriate internet use by the NR user, but they need to know that you are monitoring these reports as they come to you and will approach them if there is anything that raises a question. Modified: documentation/pages/0705-UnderstandingReports.page =================================================================== --- documentation/pages/0705-UnderstandingReports.page 2012-05-17 12:32:42 UTC (rev 312) +++ documentation/pages/0705-UnderstandingReports.page 2012-05-19 16:06:10 UTC (rev 313) @@ -8,14 +8,37 @@ Depending on the NR user's settings, their report will include one or more of the following sections. !!Introductory material -At the beginning of the email report, the NR user is identified by the name they used when they registered online, and there is a link to the NR website, where you can find more information or help as needed. There is also a list of any 'suspicious' words or phrases that NR found as it monitored the website addresses (URLs) the user visited. These are set up as internal links, so clicking on them will take you to the 'Warnings' section, where you can see a list of the URLs visited that contained that particular word or phrase. This section is included in the email report only. +At the beginning of the email report, the NR user is identified by the name they used when they registered online, and there is a link to the NR website, where you can find more information or help as needed. There is also a list of any 'suspicious' words or phrases that NR found as it monitored the website addresses (URLs) the user visited. These are set up as internal links, so clicking on them will take you to the <*Warnings*> section, where you can see a list of the URLs visited that contained that particular word or phrase. This section is included in the email report only. !!Bypasses This section shows any activity that might indicate an attempt to bypass the NR software, such as manually shutting down the program, changing certain files on the user's computer, etc. If there are any items in this section, it could mean that the user was attempting to bypass the NR software in order to use the internet inappropriately, but it is also possible that it was caused by a problem on their computer, or by them doing some testing of the software. It is best for the AP to check with the user any time there are items listed in this section. This section may be included in both the email report and the attached report. !!Warnings -It is strongly recommended that this section be included in the report, since it shows any URLs the user's computer accessed that NR flags as inappropriate. Each item includes a clickable link that can be used to confirm what the web page is, but it is good to be aware that some of these web pages may contain inappropriate content and/or malware that can be harmful to a computer. Each item also includes a color-coded number. The higher this number is, the more likely this item is an actual instance of inappropriate internet use; likewise, the lower this number is, the more likely this item is a false positive. It is possible that false positives will show up in this section, but there are ongoing efforts to improve its accuracy. If an AP sees links here that they think are not false positives, it is best for them to check with the user about them. This section may be included in both the email report and the attached report. +It is strongly recommended that this section be included in the report, since it shows any URLs the user's computer accessed that NR flags as inappropriate. If an AP sees links here that they think are not false positives, it is best for them to check with the user about them. This section may be included in both the email report and the attached report. Here is an example from a regular email report: +<% +<img src="images/erwarn.png" alt="Warning item from email report" border="0"> +%> + +Each item includes a clickable link that can be used to confirm what the web page is, but it is good to be aware that some of these web pages may contain inappropriate content and/or malware that can be harmful to a computer. Each item also includes a color-coded number, which is NR's attempt at indicating the likelihood of it being an inappropriate site (with the higher number intended to mean a greater likelihood). Because this is a fairly new report feature that hasn't been tested extensively, it's likely that some of the number rankings given are not accurate, so an AP should not rely that heavily on these numbers at the current time. However, there are ongoing efforts to improve its accuracy. In fact, if you would be willing to give just a little bit of your time to help us improve this feature, we would be grateful! For more information about how you can help, see the [[#9 Improving the reports]] section of this page. Eventually we hope that these number rankings will accurately rate URLs according to the following points or markers on a 0-100 continuum: + - <!0 (zero):!> This is definitely a false positive. The keyword might be present, but it's obvious it wasn't any harm. Example string from URL: + +<*cas.be.eu.criteo.com/..._SIMBHNUZBLkvp90fZwLE<!SeX!>vVkp5MPrZms71bFwm8o...*> + + - <!25:!> This was a match, but is unlikely a really dangerous site. Example string from URL: + +<*a.tribalfusion.com/...50&addBlockingCategories=<!Adult!>,Political,Flashing...*> + + - <!50:!> You should probably look at the URL to ensure this isn't something to be concerned about. It's a match, but not necessarily dangerous. Example string from URL: + +<*upload.wikimedia.org/...150px-<!MariahCarey!>13EdwardsDec1998.jpg*> + + - <!75:!> This is most probably something to worry about. If several of these URLs are listed you should get in touch with the user to check if everything is okay. Example string from URL: + +<*www.google.com/...&geo&q="<!sunny!>+<!leone!>+<!sex!>"&gprop&date=today+3-m&...*> + + - <!100:!> This is not only a match, it's <*definitely*> a bad site; you don't even have to think twice, it's really that obvious. Most often a combination of several keywords are found in the same URL. We'd rather not give an example for this level. + Note that in this section you may see terms such as 'Porn', 'Pornstars', 'Models', 'Celebrities', 'Pornstars extended', 'Models extended', Celebrities extended', etc. These are just the names of the particular 'blacklist' that contained the word(s) that triggered the warning. Also note that some website addresses in the report may not have actually been visited by the user. For instance, when some websites load, they access other websites in order to load icons or images, possibly for advertisements or for a person's avatar on a forum, etc. A common example is that a user's history of all websites visited might show that they visited the Facebook website multiple times when they actually never did; they simply visited other websites that had loaded one or more images from the Facebook domain. As a result, some items might show up as warnings that might be confusing for both the AP and the user as to why they are there. Normally a closer examination of the URL and its domain will help you and the user determine whether or not the item was generated by a visited website rather than by the user themselves. !!Whitelist @@ -38,4 +61,23 @@ Here are a few things for an AP to remember when they are looking at a NR report: - Things that look suspicious may actually be okay. Everything should be looked at in context and the NR user should be contacted about anything that is not understood. - When some links in the report are clicked, they will lead to another web page. These links are listed because they are suspicious, so the AP will want to be especially cautious if clicking them. - - For problems related to reports, see the [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports Troubleshooting the Reports]] guide. + - For problems related to reports, see the [[0709-TroubleshootingReports.html Troubleshooting the Reports]] guide. + +!!!Improving the reports +Even though a lot of work has already gone into improving NR's reports, we recognize that much more can be done to make them as helpful to the user and as convenient for the AP as possible. One of the ways that an AP and/or a user can assist with this is by giving a little bit of their time to evaluate and rate URLs in the <*Warnings*> section in regards to the likelihood that they are an accurate report of possible inappropriate internet use, or whether they are false positives. If you are interested in doing this, here is what you need to do: + - First make sure that you are receiving an attached report, rather than only the regular email report. If you are an AP and are not receiving an attached report, you will need to request the NR user to change his online settings so you will start receiving it. (The size of the attached file can sometimes be somewhat large, so if that is an issue, you may want to request the user to adjust their settings so you get a zipped (compressed) copy of the attached report.) If you are a NR user and are not receiving a report at all, you can start receiving your own reports by simply adding your email address as an AP in your online settings. + - When you get an attached report, open it. See [[#7 The attached report]] section of this page for the best way to do this. If you are running into problems, you can also check out the [[0709-TroubleshootingReports.html Troubleshooting the reports]] guide. + - If there is a <*Warnings*> section, expand it by clicking on the plus sign beside it. There may be one or more keywords listed in this section; if there are any, expand one or more of them. Here is an example of what this might look like: + +<% +<img src="images/arwarn.png" alt="Warning item in attached report" border="0"> +%> + +You'll see that each item in the <*Warnings*> section has the same color-coded numbers as are shown in the regular email report, but here there is also a drop-down menu for each of the numbers that can be opened by clicking on the number or the arrow to the right of it. Here's how it looks with this menu open for the first item in the above image: + +<% +<img src="images/arwarnm.png" alt="Warning item menu in attached report" border="0"> +%> + +In the drop-down menu, the first number is simply the current ranking that NR has given this item. The numbers after that (0, 25, 50, 75, 100) represent various points or markers along the 0-100 continuum that represent levels of the likelihood of an URL being a cause for concern or not. See the [[#4 Warnings]] section on this page to see a description of what each of these levels is meant to represent. + - So the way to help out is to look at each item, evaluate which of the levels it best fits into (according to the above-mentioned description), and then choose the corresponding number from the dropdown menu. When you do this, your rating of the URL will be sent to the NR server, which will then help the developers know how to make any necessary adjustments to NR's filtering methods. (Once you have rated an URL, the number you chose will show up on a white background and the drop-down menu will no longer be available for that item. However, if you close and re-open the report, it will appear as it did at first.) Note that it is helpful to assign a rating to an URL regardless of whether it's current ranking is accurate or whether it is way off. Also, the more people that are regularly reporting ratings of URLs in this way, the more accurate the reports will become. So your help would definitely be appreciated! Modified: documentation/pages/0709-TroubleshootingReports.page =================================================================== --- documentation/pages/0709-TroubleshootingReports.page 2012-05-17 12:32:42 UTC (rev 312) +++ documentation/pages/0709-TroubleshootingReports.page 2012-05-19 16:06:10 UTC (rev 313) @@ -11,8 +11,13 @@ For the first three reasons, the user will need to make sure any problems are resolved. The first and third reasons can be looked at by testing the NR program, checking online settings, and making sure NR has been configured after any changes to online settings. The second reason can be looked at by examining any errors generated by the NR program and/or contacting the developers or other users via the NR website or the forum mentioned on the main page. For the third reason it would also be good to check that the intended email address is correct. For the fourth reason, the person receiving the email will need to figure out a solution. If an accountability partner (AP) is not receiving a report they were expecting, they should first try to make sure it is not for the fourth reason, and then they should contact the user and request them to check out the first three reasons. Please note that, even if reports have been coming through without a problem before, it is still possible that they may begin to be treated as spam. However, most email servers and email clients have a way to 'train' their spam filters or 'whitelist' certain 'From' addresses, which should keep this from becoming a problem. !!!Why doesn't the attached report work right? -For an introduction to the attached report, see the [[http://netresponsibility.com/documentation.php?id=0705-UnderstandingReports Understanding the Reports]] guide. Following are some reasons why an attached report might not be functioning as it should: +For an introduction to the attached report, see the [[0705-UnderstandingReports.html Understanding the Reports]] guide. Following are some reasons why an attached report might not be functioning as it should: - If the attached file is a ZIP file, the computer may not have software installed to 'unzip' or extract it. Try downloading it to a location outside of your web browser and email client. If you have the necessary software installed, you may be able to right-click on the ZIP file and choose 'Extract', 'Extract here', or something similar, which should result in an HTML file being created that you can then view with your web browser. If you don't see this option when you right-click, you may need to download and install 'archive manager' software in order to extract it. - If the attached file is an HTML file (these usually have an .htm or .html extension), the most likely problem is that your web browser or email client does not have JavaScript enabled. If this is the case, then you will see a message informing you of this. It is recommended that you save the attached file somewhere outside of your web browser or email client, and then try to open it with your web browser. If you get the same message, then JavaScript is not working correctly in your browser. Make sure that JavaScript is both installed AND enabled in your browser, remembering that with some browsers it is possible that the settings may have JavaScript 'enabled' even if it's not actually installed. Also note that Java and JavaScript are two different things, even though they share the same name. To check if JavaScript is currently enabled in the browser you're using, you can try this [[http://www.isjavascriptenabled.com/ JavaScript Test]] website. - If you are able to open the attached file in your web browser and see the report, but certain parts of the tree structure are missing or not working properly, then JavaScript is working correctly in your browser, but you have probably opened it from within your webmail account (in your web browser) or your email client. For security purposes some email servers and email clients will 'strip' certain parts of an attachment (like parts of a JavaScript script) when it is opened. In order for the report to work properly, the attached file should be saved somewhere outside of the web browser or email client, and then opened from that location. - The attached report may be 'broken' because of some problems in its code (such as the appearance of unwanted newlines and single quotes). If this is the case, the usual symptom is that JavaScript will not work at all, meaning that neither the JavaScript tree nor the text message about JavaScript being disabled will be displayed. Improvements to the software are the best long-term solution, but until that happens a temporary workaround is to try to 'repair' the broken report by clicking on [[http://netresponsibility.com/repair.php this link]] and following the instructions there. This is not guaranteed to work in every case, but it is worth trying. Also, note that the report you are trying to repair needs to be smaller than 12 MB. + +!!!Why are there so many false positives? +There may be a lot of false positives (i.e. a warning that is not really a problem) in the <*Warnings*> section of the reports you receive, causing you to wonder why there are so many, and if there isn't anything we can do to lessen or completely avoid them. The reason there are so many is because we are still working at testing and tweaking our filtering method in order to catch what needs to be caught, and ignore the rest. The developers of NR can do a certain amount of improvement on their own, but it would be tremendously helpful to us if NR users and accountability partners also helped out with this process. Here are the two main ways that help can be given: + - Make sure the NR user has selected the option 'Provide improvement data' in the 'Tweaks' section of their online settings. When this is selected, the program will <*anonymously*> send the warnings from each report to our server and store them there. This will help us see how to improve the blacklists. + - A relatively new feature we are using in the <*Warnings*> section of reports is a color-coded number ranking system for each item listed. Because it has not been extensively tested, you should not completely rely on it at the current time. However, we are working on improving its accuracy and the good news is, since we're including it in the reports that are sent out, you are also able to help out with this. For more information about how you can give valuable help by giving a bit of your time whenever you receive a report, see the [[0705-UnderstandingReports.html#9 Improving the Reports]] section of the "Understanding the Reports" guide. Thanks in advance for whatever help you can give in making the reports more accurate and useful! Modified: documentation/pages/0901-FAQ.page =================================================================== --- documentation/pages/0901-FAQ.page 2012-05-17 12:32:42 UTC (rev 312) +++ documentation/pages/0901-FAQ.page 2012-05-19 16:06:10 UTC (rev 313) @@ -2,7 +2,7 @@ A09NR_FurtherReading !!!About the FAQ -This part of the documentation is meant to be a useful guide when you have a common question about Net Responsibility (NR) for which you need an answer. These are sorted by category and the categories are arranged alphabetically. Many of the answers may be short, but often links will be provided in case more information is needed. If you have a question or problem that is not addressed here, see [[http://netresponsibility.com/documentation.php?id=0902-HowToGetHelp this guide]] to find out other ways of finding answers and solving problems. +This part of the documentation is meant to be a useful guide when you have a common question about Net Responsibility (NR) for which you need an answer. These are sorted by category and the categories are arranged alphabetically. Many of the answers may be short, but often links will be provided in case more information is needed. If you have a question or problem that is not addressed here, see [[0902-HowToGetHelp.html this guide]] to find out other ways of finding answers and solving problems. !!!Configuration, Registration, and Account-Related Questions @@ -10,7 +10,7 @@ Go to the [[http://www.netresponsibility.com NR website]], click on the 'Login' tab, click on 'Forgot password?,' enter your username or email address (the one you used to register) in the box provided, click on 'Send password,' and you should soon get an email containing your username and password. !!How do I change my configuration settings? -[[http://netresponsibility.com/documentation.php?id=0301-ConfigurationsExplained#9 Click here]] for instructions on how to make changes to your online configuration settings. +[[0301-ConfigurationExplained.html#9 Click here]] for instructions on how to make changes to your online configuration settings. !!Can I use the same NR account for more than one computer? Yes, but that means you will also be using the same configuration settings for each computer, so it won't work to use the same account if you want different report frequencies or other differences in settings. @@ -24,15 +24,15 @@ Log in to the [[http://www.netresponsibility.com NR website]], click on the tab with your username on it, click on 'Log out', and then click on 'Delete account'. If this doesn't work [[mailto:res...@li... let us know]] and we'll try to help you out as soon as possible. In your email, please mention the username of the account you are trying to delete, as well as the details of what happened when you tried to delete the account. !!Why are my accountability partners not being notified of configuration changes? -This could be because of improper online configuration settings, a bug in the NR program, or simply because the notification emails are being caught in a spam filter. See [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports this guide]] for more information. +This could be because of improper online configuration settings, a bug in the NR program, or simply because the notification emails are being caught in a spam filter. See [[0709-TroubleshootingReports.html this guide]] for more information. !!Is there any way for accountablility partners to be informed if the NR program is uninstalled? -Yes, they are automatically informed by email when Net Responsibility is uninstalled. If they have not received the expected email, see [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports this guide]] for more information on possible reasons for this. +Yes, they are automatically informed by email when Net Responsibility is uninstalled. If they have not received the expected email, see [[0709-TroubleshootingReports.html this guide]] for more information on possible reasons for this. !!!Development !!How can I help with the Net Responsibility project? -Now this is a question we love to hear! :-) See the [[http://netresponsibility.com/documentation.php?id=0903-ContributeToNR Contribute to Net Responsibility]] guide for some ideas of how you can help (even in small ways) make NR a better program for a wider group of grateful users. +Now this is a question we love to hear! :-) See the [[0903-ContributeToNR.html Contribute to Net Responsibility]] guide for some ideas of how you can help (even in small ways) make NR a better program for a wider group of grateful users. !!Is there a repository set up somewhere that can be 'checked out,' if I'm interested in helping with NR coding (programming)? The SVN trunk for NR can be <*checked out*> from this URL: [[https://responsibility.svn.sourceforge.net/svnroot/responsibility/trunk/ https://responsibility.svn.sourceforge.net/svnroot/responsibility/trunk/]]. For more information on how best to get started with NR coding, [[5001-GettingStarted.html read this guide]]. @@ -43,7 +43,7 @@ If you're interested in following the Windows development process, you can stay updated through [[http://netresponsibility.com/forum/index.php?topic=55.0 this forum thread]]. When logged in, you can click "Notify" for this topic in order to automatically receive email notifications about any new posts. !! What is the current status of Net Responsibility for Mac? -We're working on creating packages for Mac users. It is technically possible to download the [[http://netresponsibility.com/documentation.php?id=0305-CompileFromSource source code]] and compile it. More information about compiling it on Mac can be [[http://netresponsibility.com/forum/index.php?topic=63.0 found here]]. However, the easiest thing would be to wait (or help us out with creating the package). +We're working on creating packages for Mac users. It is technically possible to download the [[0305-CompileFromSource.html source code]] and compile it. More information about compiling it on Mac can be [[http://netresponsibility.com/forum/index.php?topic=63.0 found here]]. However, the easiest thing would be to wait (or help us out with creating the package). !!!General @@ -57,12 +57,12 @@ No, all they need is to have any system that is able to receive email, since this is how NR's reports are sent. !!What is NR's privacy policy? -[[http://netresponsibility.com/documentation.php?id=0910-PrivacyPolicy Click here]] to view our privacy policy. +[[0910-PrivacyPolicy.html Click here]] to view our privacy policy. !!!Installing, Uninstalling, and Upgrading !!How do I download and/or install a copy of the NR software? -If you are interested in a precompiled package (installation file), see [[http://netresponsibility.com/documentation.php?id=0304-InstallFromPackages these instructions]]. If you are interested in compiling from the source code, see [[http://netresponsibility.com/documentation.php?id=0305-CompileFromSource these instructions]]. +If you are interested in a precompiled package (installation file), see [[0304-InstallFromPackages.html these instructions]]. If you are interested in compiling from the source code, see [[0305-CompileFromSource.html these instructions]]. !!How do I check what version of NR is installed? One way this can be done is by opening a terminal window and running the following command as root (for Ubuntu users, this means adding <*sudo*> and a space before the command): @@ -100,10 +100,10 @@ !!!Reports -- Problems !!Why aren't my reports being sent? -This could be for a variety of reasons. See the [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports Troubleshooting the Reports]] guide. +This could be for a variety of reasons. See the [[0709-TroubleshootingReports.html Troubleshooting the Reports]] guide. !!Why am I not receiving reports? -This could be for a variety of reasons. See the [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports Troubleshooting the Reports]] guide. +This could be for a variety of reasons. See the [[0709-TroubleshootingReports.html Troubleshooting the Reports]] guide. !!How do I send a test report/email? This can be done by opening a terminal window and running the following command as root (for Ubuntu users, this means adding <*sudo*> and a space before the command): @@ -111,18 +111,21 @@ Note that a test report is simply a brief email that is sent out to test NR's ability to send out email reports and to see whether they will get caught in a spam filter; it is not meant to contain a report of your internet activity. !!Why are my reports empty (i.e. only showing titles)? -This could happen if you have not done any internet browsing since the last time a report was sent. Otherwise, it's possible that the internet monitoring part of the NR program is not working properly. See [[http://netresponsibility.com/documentation.php?id=0309-TroubleshootingInstallation this guide]] for instructions on how to test whether NR is running properly. +This could happen if you have not done any internet browsing since the last time a report was sent. Otherwise, it's possible that the internet monitoring part of the NR program is not working properly. See [[0309-TroubleshootingInstallation.html this guide]] for instructions on how to test whether NR is running properly. !!Why don't my reports work right? -If you are a NR user or accountability partner who is having trouble with NR's reports, you may find a solution in the [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports Troubleshooting the Reports]] guide. +If you are a NR user or accountability partner who is having trouble with NR's reports, you may find a solution in the [[0709-TroubleshootingReports.html Troubleshooting the Reports]] guide. +!!Why are there so many false positives? +See [[0709-TroubleshootingReports.html#2 this link]] for a brief explanation of what we are doing to improve the accuracy of reports, as well as information on how you, with only a minimal amount of time given, can provide valuable help with that. + !!!Reports -- Timing, Characteristics, Etc. !!How often are reports sent out? The default is every 7th day, but this can be changed by the user in their online settings at the time of registration. It can also be changed anytime after that by the user logging in to the website to edit his configuration settings. !!Is there a way to set up NR so that my reports will include a complete list of website addresses (URLs) visited? -Yes. To do this, go to the [[http://www.netresponsibility.com NR website]], log in, click on the tab with your username on it, click on 'Report parts', and select 'Complete history' in the 'Attached report' section. Then click on 'Log out,' enter the security code, and click on 'Save and log out' in order to save the changes to your settings. The next time a report is sent out, it should include an attached file that contains a complete list of URLs visited. You may also find it helpful to read through the [[http://netresponsibility.com/documentation.php?id=0705-UnderstandingReports Understanding the Reports]] guide and the [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports Troubleshooting the Reports]] guide. +Yes. To do this, go to the [[http://www.netresponsibility.com NR website]], log in, click on the tab with your username on it, click on 'Report parts', and select 'Complete history' in the 'Attached report' section. Then click on 'Log out,' enter the security code, and click on 'Save and log out' in order to save the changes to your settings. The next time a report is sent out, it should include an attached file that contains a complete list of URLs visited. You may also find it helpful to read through the [[0705-UnderstandingReports.html Understanding the Reports]] guide and the [[0709-TroubleshootingReports.html Troubleshooting the Reports]] guide. !!Can I specify what time of the day reports are sent out? No, not in your online configuration settings. However, you can use a task-scheduling package like [[https://help.ubuntu.com/community/CronHowto cron]] to do it. The command to use in <*cron*> to send reports is <*net-responsibility --report*> and you need to make sure <*cron*> has root privileges. You will also need to set the report frequency to '0' in your online configuration settings to prevent Net Responsibility from sending out reports automatically. Modified: documentation/pages/0903-ContributeToNR.page =================================================================== --- documentation/pages/0903-ContributeToNR.page 2012-05-17 12:32:42 UTC (rev 312) +++ documentation/pages/0903-ContributeToNR.page 2012-05-19 16:06:10 UTC (rev 313) @@ -92,6 +92,11 @@ needed. More information can be [[5004-Documentation.html found here]]. +!!!Improve the reports + +You can provide valuable help in improving the accuracy of items listed in the <*Warnings*> section of the reports. More information can be [[0705-UnderstandingReports.html#9 found here]]. + + !!!Code contributions Since Net Responsibility is free and open source, anyone can Modified: documentation/pages/0905-MissionStatement.page =================================================================== --- documentation/pages/0905-MissionStatement.page 2012-05-17 12:32:42 UTC (rev 312) +++ documentation/pages/0905-MissionStatement.page 2012-05-19 16:06:10 UTC (rev 313) @@ -17,8 +17,7 @@ !!Accurate and Effective Net Responsibility will always strive towards being more accurate in its -reports. The users can help us out a lot here by sending anonymous improvement data. -Yet we don't want Net Responsibility to slow down the surfing experience, at +reports. The users can help us out a lot here by having anonymous report improvement data sent (an option in the online settings) to the NR server. Both users and accountability partners can also give valuable help by [[0705-UnderstandingReports.html#9 rating URLs]] in the <*Warnings*> section of the reports. At the same time, we don't want Net Responsibility to slow down the surfing experience, at least not too much. @@ -26,7 +25,7 @@ In order to be a good accountability software, Net Responsibility has to be hard to bypass. We may not be able to prevent the user from shutting down the -program, but as long as possible we have to log and report when that's done. +program, but as far as possible we have to log and report when that's done. There will always be a tension between being open and being secure here. With too much customization there is a risk to be unsecure. Therefore all changes that affect the security have to be reported to the accountability partner. @@ -37,16 +36,16 @@ It should be as easy as possible for anyone who wants to be held accountable to setup and install Net Responsibility. -We also want to make it easy to be an accountability partner, by making as easy -and accurate reports as possible. +We also want to make it easy to be an accountability partner, by making the reports as easy +and accurate as possible. !!Almost invisible Net Responsibility should run in the background and do its job automatically. It should also use as little memory and processor power as possible. -The user won't have to worry about if Net Responsibility is running or not, and -shouldn't be able to control it too much. +The user shouldn't have to worry about whether Net Responsibility is running or not, and also +shouldn't be able to have too much control over it. !!Cross-platform Modified: documentation/pages/0910-PrivacyPolicy.page =================================================================== --- documentation/pages/0910-PrivacyPolicy.page 2012-05-17 12:32:42 UTC (rev 312) +++ documentation/pages/0910-PrivacyPolicy.page 2012-05-19 16:06:10 UTC (rev 313) @@ -8,22 +8,22 @@ !!!How are the reports stored? -The reports are only sent to your accountability partners, and are not stored online. There may be other report plugins than the default, that stores the reports differently, but this policy applies to the regular settings. +The reports are only sent to your accountability partners, and are not stored online. There may be other report plugins than the default, that store the reports differently, but this policy applies to the regular settings. !!!What about the improvement data? -If you choose to send improvement data, it means all visited sites that are flagged as inappropriate, are sent to our server. We do not store any information about who that visited the specific sites, such as username, IP number, MAC address etc. This data is helping us developing better filtering algorithms that in return will produce cleaner reports. +If you choose to send improvement data, it means all visited sites that are flagged as inappropriate are sent to our server. We do not store any information about who visited these sites, such as username, IP number, MAC address etc. This anonymous data helps us develop better filtering algorithms that in return will produce better reports. !!!What information do we collect? -We collect information from you when you register an account. You may visit our site anonymously, but in order to install Net Responsibility, you'll need to register. During the registration you will be prompted to enter your name (or nickname), email address and your accountability partner's email addresses. There is also several options that affects the way Net Responsibility will behave. All these settings are stored on our server. +We collect information from you when you register an account. You may visit our site anonymously, but in order to install Net Responsibility, you'll need to register. During the registration you will be prompted to enter your name (or nickname), email address and your accountability partners' email addresses. There are also several options that affect the way Net Responsibility will behave. All these settings are stored on our server. !!!What do we use your information for? -The information will be used by your own Net Responsibility installation to set up properly. We may as well contact you at your email address. This is primarily done for newsletters, which is optional for all users, or if we need to contact you for any other reason. +The information will be used by your own Net Responsibility installation to set up properly. We may also use your email address to contact you. This is primarily done for newsletters, which is optional for all users, or if we need to contact you for any other reason. !!!How do we protect your information? @@ -33,29 +33,29 @@ !!!What about deleting an account? -You may at any time delete your Net Responsibility account. This is done by logging in and clicking the tab with your username. At the very end of that page, under <*Log out*>, you may choose <*Delete account*>. When doing so, all the information you've entered will be deleted from our server. +You may at any time delete your Net Responsibility account. This is done by logging in to the NR website and clicking the link with your username. At the very end of that page, under <*Log out*>, you may choose <*Delete account*>. When doing so, all the information you've entered will be deleted from our server. !!!Do we use cookies? -We do not use cookies. +No, we do not use cookies. !!!Do we disclose any information to outside parties? -We do not sell, trade, or otherwise transfer to outside parties your personally identifiable information. We may release your information when we believe release is appropriate to comply with the law, enforce our site policies, or protect ours or others rights, property, or safety. +We do not sell, trade, or otherwise transfer to outside parties your personally identifiable information. We may release your information when we believe release is appropriate to comply with the law, enforce our site policies, or protect our own or others rights, property, or safety. !!!California Online Privacy Protection Act Compliance Because we value your privacy we have taken the necessary precautions to be in compliance with the California Online Privacy Protection Act. We therefore will not distribute your personal information to outside parties without your consent. -As part of the California Online Privacy Protection Act, all users of our site may make any changes to their information at anytime by logging in and clicking the tab containing your username. +As part of the California Online Privacy Protection Act, all users of our site may make any changes to their information at anytime by logging in and clicking the link containing your username. !!!Childrens Online Privacy Protection Act Compliance -We are in compliance with the requirements of COPPA (Childrens Online Privacy Protection Act), we do not collect any information from anyone under 13 years of age. Our website, products and services are all directed to people who are at least 13 years old or older. +We are in compliance with the requirements of COPPA (Childrens Online Privacy Protection Act). We do not collect any information from anyone under 13 years of age. Our website, products and services are all directed to people who are at least 13 years old or older. !!!Your Consent @@ -71,7 +71,7 @@ If there are any questions regarding this privacy policy you may contact us using the information below. -http://www.netresponsibility.com/forum -co...@ne... + - http://www.netresponsibility.com/forum + - [[mailto:co...@ne... co...@ne...]] This policy is partially powered by Free Privacy Policy and Rhino Support [[http://www.rhinosupport.com/ helpdesk software]]. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <rog...@us...> - 2012-05-17 12:32:53
|
Revision: 312 http://responsibility.svn.sourceforge.net/responsibility/?rev=312&view=rev Author: roggan87 Date: 2012-05-17 12:32:42 +0000 (Thu, 17 May 2012) Log Message: ----------- Updated some texts to make it fit for the new template and website structure. Modified Paths: -------------- documentation/web.txt Modified: documentation/web.txt =================================================================== --- documentation/web.txt 2012-05-17 09:59:31 UTC (rev 311) +++ documentation/web.txt 2012-05-17 12:32:42 UTC (rev 312) @@ -9,7 +9,9 @@ - The header names are used to locate the different texts, do not change them! - Partial links starts with a slash for the root folder - Full links starting with http:// or similiar are opened in new windows - - You may use the reference links for simplicity + - You may use the reference links for simplicity. These are also available + in the forum and blog posts, so in any of these places, you may write a + reference link like [this][Forum], or [like this][Search]. ---> @@ -454,7 +456,7 @@ -#start# +#about# **Net Responsibility is an accountability software** for Linux and Mac OS X. It monitors the sites you visit on the internet, and sends e-mail reports to This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <rog...@us...> - 2012-05-17 09:59:40
|
Revision: 311 http://responsibility.svn.sourceforge.net/responsibility/?rev=311&view=rev Author: roggan87 Date: 2012-05-17 09:59:31 +0000 (Thu, 17 May 2012) Log Message: ----------- Updated some texts to make it fit for the new template and website structure. Modified Paths: -------------- documentation/web.txt Modified: documentation/web.txt =================================================================== --- documentation/web.txt 2012-05-16 12:59:34 UTC (rev 310) +++ documentation/web.txt 2012-05-17 09:59:31 UTC (rev 311) @@ -19,14 +19,18 @@ [Download]: /download.php [Forum]: /forum/ [Register]: /register.php + [Search]: /search.php [Documentation]: /documentation.php [Compile from source]: /documentation.php?id=0305-CompileFromSource [Privacy Policy]: /documentation.php?id=0910-PrivacyPolicy [Dev Docs]: http://www.netresponsibility.com/dev/docs - [Bug tracker]: http://sourceforge.net/p/responsibility/bugs/ - [Feature request]: http://sourceforge.net/p/responsibility/feature-requests/ + [SourceForge page]: http://sourceforge.net/p/responsibility/ + [Bug tracker]: http://sourceforge.net/p/responsibility/bugs/ + [Feature request]: http://sourceforge.net/p/responsibility/feature-requests/ + [Files]: http://sourceforge.net/projects/responsibility/files/net-responsibility/ + [Latest version]: https://sourceforge.net/projects/responsibility/files/latest/download [NR-devel]: <mailto:res...@li...> @@ -277,13 +281,33 @@ #contact# -Make sure you've checked out our <a href="help.php">help section</a> first. - -**Note:** If you want us to get back to you personally, please include your -email address. +There are several different ways to get in contact with us depending on what +issue you're facing. You may want to read [this good complete +guide](/documentation.php?id=0902-HowToGetHelp) on how to get help. For a +short summary, please read on. + - *Help with installation etc.* If you're having problems registering, + installing Net Responsibility etc. you would probably first want to read + all relevant [documentation][] about it. If you still have questions, + please consult the [forum][], or [mailing list][NR-devel]. + - *Bugs.* If you think you've encountered a bug in Net Responsibility or + the website, please first make sure (at least as sure as you can) that it's + not related to your specific operating system. Then search through the [Bug + tracker][] to see if it's already reported, otherwise write a ticket. We + will deal with it as soon as possible. + - *Feature requests.* Do you have an excellent idea of how to improve Net + Responsibility? Please let us know by submitting a [feature request][]! + - *Other questions.* Questions not covered in the sections above will + probably be best to ask in the [forum][]. Please [search][] for an answer + in relevant places first. + - *Feedback.* Just want to drop a line about pros or cons you've found in + Net Responsibility? Feel free to do so in the [forum][]. + - *Contributions.* If you're interested in getting involved with any area + of Net Responsibility, please read [this + guide](/documentation.php?id=0903-ContributeToNR). + #delete_account# Your account is now deleted. Your accountability partners have been informed @@ -292,146 +316,18 @@ -#download_Arch_Linux# +#download# -If <a href="http://archlinux.fr/yaourt-en" target="_blank">yaourt</a> is -installed you can download and install Net Responsibility by running the following command: +For some operating systems there are binary packages (installation files) to +use. Read more about them +[here](/documentation.php?id=0304-InstallFromPackages). Our ambition is to +supply binary packages for as many platforms as possible. If there is none +for your platform, you'll need to download and [compile the source +code][Compile from source]. If you would be interested in creating such +packages for any platform, please [let us know][NR-devel]. - yaourt -S net-responsibility -Otherwise, simply follow [these instructions](http://netresponsibility.com/documentation.php?id=0304-InstallFromPackages#5). - - -#download_Debian# - -**Note:** If you have version 2.0.2 or earlier installed, you will need to uninstall it before installing a later version. The older versions are named *netresponsibility* (without a dash), whereas the newer ones are named *net-responsibility* (with a dash). - -If your Debian-based distribution supports downloading and installing from the Ubuntu PPA, see the 'Ubuntu' section for instructions on how to add the NR PPA to your system. Otherwise, follow [these instructions](http://netresponsibility.com/documentation.php?id=0304-InstallFromPackages#6). - - - -#download_Mac_OSX# - -We're working on creating packages for Mac users. It is technically -possible to download the <a href="#Source" target="_self">source code</a> -and compile it. More information about compiling on Mac can be <a -href="forum/index.php?topic=63.0" target="_self">found here</a>. However, -the easiest thing would be to wait (or help us out with creating the package). - - - -#download_Older# - -**NOTE: These packages are not officially supported, and we recommend -installing version 3.0 or later. However, these packages are provided in -case anyone is interested in using them.** - -Stable (Beta) Version: - - - <a href="files/netresponsibility-2.0.deb" target="_blank">netresponsibility-2.0.deb</a> (213 KB) - - <a href="files/netresponsibility-2.0.amd64.deb" target="_blank">netresponsibility-2.0.amd64.deb</a> (213 KB) - - <a href="files/net-responsibility-2.0.tar.gz" target="_blank">net-responsibility-2.0.tar.gz</a> (Source code) (131 KB) - -Unstable (Alpha) Version: - - - <a href="files/netresponsibility-2.0.2.deb" target="_blank">netresponsibility-2.0.2.deb</a> (221 KB) - - <a href="files/netresponsibility-2.0.2.amd64.deb" target="_blank">netresponsibility-2.0.2.amd64.deb</a> (221 KB) - - <a href="files/net-responsibility-2.0.2.tar.gz" target="_blank">net-responsibility-2.0.2.tar.gz</a> (Source code) (138 KB) - -Which file you download depends on your distribution. If you are running a -Debian or <a -href="http://en.wikipedia.org/wiki/List_of_Linux_distributions#Debian-based" -target="_blank">Debian-based</a> Linux distribution (such as Ubuntu), then -you need the .deb file. If you're using another Linux distribution, then you -can download the source code and follow the instructions below. - -New to Linux/Ubuntu? Start <a href="help.php#29">here</a>. - -**Net Responsibility Installation** - -To install versions 2.0 or later, you have to register an account <a -href="register.php">here</a> first. Once you've done that, simply follow the -instructions below. - - - If you downloaded the .deb file, follow the respective installation procedures for your distribution. - - If you downloaded the source tarball (archived file ending in '.tar.gz'), extract it and follow the directions in the README file. - - <a href="help.php#28">Click here</a> for more detailed installation instructions. - -**Net Responsibility 2.0 Configuration** - -To configure the program's settings so it will begin monitoring and -reporting internet usage, you can do either of the following: - - - Click on the menu item Applications > Internet > Configure - Net Responsibility. - - Enter `net-responsibility-config-gui` in the terminal. - - <a href="help.php#114" target="_self">Click here</a> for - more detailed configuration instructions. - - - -#download_Source# - -To download and install Net Responsibility from the source code, see [these instructions][Compile from source]. - - - -#download_Start# - -Before downloading and installing, you'll need to -[register an account][Register]. Once that's done, simply choose the -OS (operating system) you want to download Net Responsibility for. - -Our ambition is to supply binary packages (installation files) for as -many platforms as possible. If there is none for your platform, you'll need -to download and compile the <a href="#Source" target="_self">source -code</a>. If you would be interested in creating such packages for any -platform, please [let us know][NR-devel]. - -Older versions are provided but not recommended. <a href="download.php#Older" target="_blank">You may find them here</a>. - - - -#download_Ubuntu# - -**Note:** If you have version 2.0.2 or earlier installed, you will need -to uninstall it before installing a later version. The older versions are -named *netresponsibility* (without a dash), whereas the newer ones are named -*net-responsibility* (with a dash). - -There is a PPA (Personal Package Archive) for Ubuntu users. To add the PPA -and install the latest version, simply type these commands in a terminal: - - sudo add-apt-repository ppa:roggan87/nr - sudo apt-get update - sudo apt-get install net-responsibility - -During the last step, you need to enter username and password. Simply -use the same as you did when registering your account. - -This could also be done through your favorite package manager, such as -Synaptic. If you dare, you could change *roggan87/nr* to *roggan87/nrdev*. -Then you will also get notified of new beta versions that are not tested by -a wider range of people. - - - -#download_Windows# - -Our goal is to supply Net Responsibility for all major platforms, including -Windows. At the moment there are still some important features that are not -implemented in the Windows version. Therefore we've decided to wait before -we release it. Once those things are fixed, we'll create an installation -file and post it here. - -If you're interested in following the Windows development process, you can -stay updated through <a href="forum/index.php?topic=55.0">this thread</a>. -If you want to receive email notifications when a new post is made to this -thread, first log in, go to the thread, and then click the "Notify" button. - - - #edit_config# You can make changes in your configuration here. The changes will be @@ -460,10 +356,13 @@ #forum_contact# -This forum is the place to look for help and discuss Net Responsibility. +Here in the forum you may interact with other users and the developer team. +Before posting new threads, make sure to [search][] through the forum, +documentation and other relevant places for the information you're looking +for. -If, for some reason, you want to get in contact with us another way, you may -also send an email to <co...@ne...>. +Anyone is able to browse through the forum, but only users are able to post +new topics, reply to old ones etc. To do so, please log in first. @@ -562,16 +461,8 @@ one or more accountability partners that you choose. It is [open source][] and released under the GNU GPL license. -**Version 3.0 is released.** We encourage all users to use this version instead -of the older ones based on Ruby and Python. Simply go to the -[download page][Download] for instructions on download and installation on -various platforms. Release notes are -[found here](http://downloads.sourceforge.net/project/responsibility/net-responsibility/3.0/readme). -**Further help** and documentation is found in the [forum][]. - - #testmail# Hi! This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <rog...@us...> - 2012-05-16 12:59:46
|
Revision: 310 http://responsibility.svn.sourceforge.net/responsibility/?rev=310&view=rev Author: roggan87 Date: 2012-05-16 12:59:34 +0000 (Wed, 16 May 2012) Log Message: ----------- Made some minor edits in documentation, mostly making some links work. Also implemented the new CSS stylesheet. Modified Paths: -------------- documentation/doc/net-responsibility-3.0.2-doc.zip documentation/pages/0305-CompileFromSource.page documentation/pages/0307-WorkingWithBlacklists.page documentation/pages/0910-PrivacyPolicy.page documentation/resources/css/styles.css Added Paths: ----------- documentation/pages/0301-ConfigurationExplained.page Removed Paths: ------------- documentation/pages/0301-ConfigurationsExplained.page Modified: documentation/doc/net-responsibility-3.0.2-doc.zip =================================================================== (Binary files differ) Copied: documentation/pages/0301-ConfigurationExplained.page (from rev 309, documentation/pages/0301-ConfigurationsExplained.page) =================================================================== --- documentation/pages/0301-ConfigurationExplained.page (rev 0) +++ documentation/pages/0301-ConfigurationExplained.page 2012-05-16 12:59:34 UTC (rev 310) @@ -0,0 +1,61 @@ +Configuration explained +A03NR_Install + +!!!Overview +The configuration of Net Responsibility (NR) refers to user-specific settings that enable the program to run on a particular computer system. Before you install NR you need to [[http://netresponsibility.com/register.php register an account]] on the website, if you haven't done so already. The information you enter during registration will be used during the NR install process to do the initial configuration on your computer system in order for it to work properly. + +The configuration information is stored on the website and is periodically downloaded by NR as needed. To manually configure NR by downloading the configuration information you can run the following command in a terminal window: + + sudo net-responsibility -c +---- +<!Note:!> If you are not an Ubuntu/Debian user, you may need to change <*sudo*> to <*su*>. The main thing to know is that the <*net-responsibility*> command needs to be run as 'root', however your particular platform handles that. + +!!!Configuration parts +During and/or after the NR registration process (which is all done online at the NR website), you will have the opportunity to specify certain settings for the following parts of the program's configuration. + +!!Name, password, etc. +Here you will choose a username and password, which you will use to log in on the website (i.e. to change your settings, write forum posts, etc.), and which you may also need to use on your computer (i.e., when you first install NR, or when you manually configure NR). Your password is only saved on the NR website, where it is used to verify your user identity. You will need to enter your password a second time, just to doublecheck that you've created the password you intended. You will also need to enter your name or you can enter an alias, as long as your accountability partners know what it is, since NR uses this name when sending reports. + +!!Email addresses +One of the things you'll enter here is your email address, which will be the email used to activate your NR account. Note that when NR sends reports it sends them from the email address re...@ne... rather than your email address. In this part you will also enter the email addresses of those you wish to receive reports. These will normally be one or more accountability partners, but you may also want to enter your own email address as well, either to make sure everything is working okay or in case you want to get a copy of the reports. It may appear that you can only enter a limited amount of email addresses, but as you fill in the last visible field, an additional blank field will appear. This will continue until you've entered all the email addresses you need. + +!!Tweaks +In this part, the following options can be set: + - <*Logfile*>: The location of the logfile must be specified; otherwise, NR will refuse to start. <!WARNING:!> Don't change this unless you know what you're doing! + - <*Pidfile*>: The location of the pidfile must be specified; otherwise, NR will refuse to start. <!WARNING:!> Don't change this unless you know what you're doing! + - <*Report frequency*>: Here you will enter the number of days you want between the emailed reports. If set to zero, the automatic reports will be disabled and you'll have to send reports manually, or by using the task-scheduling package <*cron*>. + - <*Instant threshold*>: Here you can enable instant reports, which means your accountability partner will get a report instantly when NR thinks you're looking at inappropriate content. You can also set the sensitivity. Entering zero means this feature is disabled. Otherwise, lower numbers mean higher sensitivity. (0 = Disabled; 1-5 = Very sensitive; 6-20 = Medium; 21+ = Low sensitivity) + - <*Report strength threshold*>: Only matches with a strength higher than this number will be included in the reports. That way you're able to set some sort of sensitivity for what to display. + - <*Always perform tokenmatch*>: Using tokenmatch increases the report creation time because it's more complicated, but it results in much more accurate reports. If you're having problems with reports taking too long to create you might want to exclude it. + - <*Provide improvement data*>: Use this option if you'd like to help us with the development of NR. They program will <*anonymously*> send your warnings to our server and store them there. This will help us see how to improve the blacklists. + - <*Send me newsletters*>: Choose this if you want the latest information about new versions, how to help, and other things that might be of interest. These emails are not sent on a regular basis, but rather whenever there's a need to update users with fresh information. + +!!Blacklist categories +In this part, you can choose one or more <*blacklists*> that you want NR to use when creating your reports. Each of these blacklists is full of keywords. If any of the words are found in the websites you've visited, it will show up as a warning in the report. + +!!Report parts +Here you can choose what parts you want included in your NR reports. You can also choose to include a more detailed attached report, which is strongly recommended. Following are the various report parts and related options, along with a brief description of each: + - <*Shutdowns*>: NR records if it's shutdown manually or interrupted. Choose this to list these shutdowns, if any, in the report. This can be chosen for the regular and/or attached reports. + - <*Warnings*>: The <*warnings*> part of the report lists any visited websites that contain one or more words from the blacklists. They could be inappropriate websites, but that is not always the case. Therefore, your accountability partner(s) should always double-check them, either by clicking the link or by reading the match in its context. It is strongly recommended to choose this option! This can be chosen for the regular and/or attached reports. + - <*Whitelist*>: If a website contains a blacklisted word, but <*also*> a whitelisted word, it will be found in this part of the report. This way you will be able to tell NR that some websites are okay. This can be chosen for the regular and/or attached reports. + - <*No history*>: Choose this if you do not want any of your browsing history to be included in the attached report (this option is not available for regular reports). Note that all websites visited will be searched for a blacklist match independent of what you choose here. + - <*Complete history*>: Choose this if you want your complete browsing history (i.e. every webpage accessed) to be included in the attached report (this option is not available for regular reports). + - <*Only hostnames*>: Choose this if you want just the hostnames (i.e. main website names, like www.yahoo.com, but not every page associated with that website) of your browsing history to be included in the attached report (this option is not available for regular reports). + - <*Zipped*>: Depending on your internet activity and how often your reports are sent, the attached reports might become quite large. If you choose this option NR will zip (compress) the file before sending it. This means the receiver will have to unzip (decompress) the report every time, but it also saves space in his/her email account. The file usually decreases to 10-20% of the original size when zipped. If the report is larger than 10MB it will be zipped automatically. + +You may find it helpful for yourself and your accountability partners to have NR send reports using various combinations of the above options. This will give you a chance to see some sample reports and decide together what will work best for you. + +!!Personal blacklist +Here you can enter keywords to make your personal blacklist. If you click on the blank field for this option, some basic instructions with some helpful links will show up on the right-hand side. If you already have a list you want to add, you can copy and paste it in the field. It will be split at every line break. + +!!Personal whitelist +Here you can enter keywords to make your personal whitelist. If you click on the blank field for this option, some basic instructions with some helpful links will show up on the right-hand side. Note that only the hostname will be matched against the whitelist. If you already have a list you want to add, you can copy and paste it in the field. It will be split at every line break. + +!!!Configuration changes +If you want to make any changes to the configuration of NR, here are the steps to follow: + - Go to the NR website, log in with your username and password, and click on the tab that shows your username. This will take you to the page where your current configuration options can be viewed. + - Click on the various sections to open them and make the desired changes. + - Once you are done making changes, click on the 'Log out' section, enter the security code and click on 'Save and log out'. + - Run the NR configuration manually (see instructions in the 'Overview' section above), which will download the new configuration information to your computer. +Once you have completed the above steps successfully, NR should now be running according to the new configuration options you chose. Also note that whoever normally receives your reports (i.e. your accountability partner) will also be notified when you change NR's configuration. + Deleted: documentation/pages/0301-ConfigurationsExplained.page =================================================================== --- documentation/pages/0301-ConfigurationsExplained.page 2012-05-15 01:40:17 UTC (rev 309) +++ documentation/pages/0301-ConfigurationsExplained.page 2012-05-16 12:59:34 UTC (rev 310) @@ -1,61 +0,0 @@ -Configuration explained -A03NR_Install - -!!!Overview -The configuration of Net Responsibility (NR) refers to user-specific settings that enable the program to run on a particular computer system. Before you install NR you need to [[http://netresponsibility.com/register.php register an account]] on the website, if you haven't done so already. The information you enter during registration will be used during the NR install process to do the initial configuration on your computer system in order for it to work properly. - -The configuration information is stored on the website and is periodically downloaded by NR as needed. To manually configure NR by downloading the configuration information you can run the following command in a terminal window: - - sudo net-responsibility -c ----- -<!Note:!> If you are not an Ubuntu/Debian user, you may need to change <*sudo*> to <*su*>. The main thing to know is that the <*net-responsibility*> command needs to be run as 'root', however your particular platform handles that. - -!!!Configuration parts -During and/or after the NR registration process (which is all done online at the NR website), you will have the opportunity to specify certain settings for the following parts of the program's configuration. - -!!Name, password, etc. -Here you will choose a username and password, which you will use to log in on the website (i.e. to change your settings, write forum posts, etc.), and which you may also need to use on your computer (i.e., when you first install NR, or when you manually configure NR). Your password is only saved on the NR website, where it is used to verify your user identity. You will need to enter your password a second time, just to doublecheck that you've created the password you intended. You will also need to enter your name or you can enter an alias, as long as your accountability partners know what it is, since NR uses this name when sending reports. - -!!Email addresses -One of the things you'll enter here is your email address, which will be the email used to activate your NR account. Note that when NR sends reports it sends them from the email address re...@ne... rather than your email address. In this part you will also enter the email addresses of those you wish to receive reports. These will normally be one or more accountability partners, but you may also want to enter your own email address as well, either to make sure everything is working okay or in case you want to get a copy of the reports. It may appear that you can only enter a limited amount of email addresses, but as you fill in the last visible field, an additional blank field will appear. This will continue until you've entered all the email addresses you need. - -!!Tweaks -In this part, the following options can be set: - - <*Logfile*>: The location of the logfile must be specified; otherwise, NR will refuse to start. <!WARNING:!> Don't change this unless you know what you're doing! - - <*Pidfile*>: The location of the pidfile must be specified; otherwise, NR will refuse to start. <!WARNING:!> Don't change this unless you know what you're doing! - - <*Report frequency*>: Here you will enter the number of days you want between the emailed reports. If set to zero, the automatic reports will be disabled and you'll have to send reports manually, or by using the task-scheduling package <*cron*>. - - <*Instant threshold*>: Here you can enable instant reports, which means your accountability partner will get a report instantly when NR thinks you're looking at inappropriate content. You can also set the sensitivity. Entering zero means this feature is disabled. Otherwise, lower numbers mean higher sensitivity. (0 = Disabled; 1-5 = Very sensitive; 6-20 = Medium; 21+ = Low sensitivity) - - <*Report strength threshold*>: Only matches with a strength higher than this number will be included in the reports. That way you're able to set some sort of sensitivity for what to display. - - <*Always perform tokenmatch*>: Using tokenmatch increases the report creation time because it's more complicated, but it results in much more accurate reports. If you're having problems with reports taking too long to create you might want to exclude it. - - <*Provide improvement data*>: Use this option if you'd like to help us with the development of NR. They program will <*anonymously*> send your warnings to our server and store them there. This will help us see how to improve the blacklists. - - <*Send me newsletters*>: Choose this if you want the latest information about new versions, how to help, and other things that might be of interest. These emails are not sent on a regular basis, but rather whenever there's a need to update users with fresh information. - -!!Blacklist categories -In this part, you can choose one or more <*blacklists*> that you want NR to use when creating your reports. Each of these blacklists is full of keywords. If any of the words are found in the websites you've visited, it will show up as a warning in the report. - -!!Report parts -Here you can choose what parts you want included in your NR reports. You can also choose to include a more detailed attached report, which is strongly recommended. Following are the various report parts and related options, along with a brief description of each: - - <*Shutdowns*>: NR records if it's shutdown manually or interrupted. Choose this to list these shutdowns, if any, in the report. This can be chosen for the regular and/or attached reports. - - <*Warnings*>: The <*warnings*> part of the report lists any visited websites that contain one or more words from the blacklists. They could be inappropriate websites, but that is not always the case. Therefore, your accountability partner(s) should always double-check them, either by clicking the link or by reading the match in its context. It is strongly recommended to choose this option! This can be chosen for the regular and/or attached reports. - - <*Whitelist*>: If a website contains a blacklisted word, but <*also*> a whitelisted word, it will be found in this part of the report. This way you will be able to tell NR that some websites are okay. This can be chosen for the regular and/or attached reports. - - <*No history*>: Choose this if you do not want any of your browsing history to be included in the attached report (this option is not available for regular reports). Note that all websites visited will be searched for a blacklist match independent of what you choose here. - - <*Complete history*>: Choose this if you want your complete browsing history (i.e. every webpage accessed) to be included in the attached report (this option is not available for regular reports). - - <*Only hostnames*>: Choose this if you want just the hostnames (i.e. main website names, like www.yahoo.com, but not every page associated with that website) of your browsing history to be included in the attached report (this option is not available for regular reports). - - <*Zipped*>: Depending on your internet activity and how often your reports are sent, the attached reports might become quite large. If you choose this option NR will zip (compress) the file before sending it. This means the receiver will have to unzip (decompress) the report every time, but it also saves space in his/her email account. The file usually decreases to 10-20% of the original size when zipped. If the report is larger than 10MB it will be zipped automatically. - -You may find it helpful for yourself and your accountability partners to have NR send reports using various combinations of the above options. This will give you a chance to see some sample reports and decide together what will work best for you. - -!!Personal blacklist -Here you can enter keywords to make your personal blacklist. If you click on the blank field for this option, some basic instructions with some helpful links will show up on the right-hand side. If you already have a list you want to add, you can copy and paste it in the field. It will be split at every line break. - -!!Personal whitelist -Here you can enter keywords to make your personal whitelist. If you click on the blank field for this option, some basic instructions with some helpful links will show up on the right-hand side. Note that only the hostname will be matched against the whitelist. If you already have a list you want to add, you can copy and paste it in the field. It will be split at every line break. - -!!!Configuration changes -If you want to make any changes to the configuration of NR, here are the steps to follow: - - Go to the NR website, log in with your username and password, and click on the tab that shows your username. This will take you to the page where your current configuration options can be viewed. - - Click on the various sections to open them and make the desired changes. - - Once you are done making changes, click on the 'Log out' section, enter the security code and click on 'Save and log out'. - - Run the NR configuration manually (see instructions in the 'Overview' section above), which will download the new configuration information to your computer. -Once you have completed the above steps successfully, NR should now be running according to the new configuration options you chose. Also note that whoever normally receives your reports (i.e. your accountability partner) will also be notified when you change NR's configuration. - Modified: documentation/pages/0305-CompileFromSource.page =================================================================== --- documentation/pages/0305-CompileFromSource.page 2012-05-15 01:40:17 UTC (rev 309) +++ documentation/pages/0305-CompileFromSource.page 2012-05-16 12:59:34 UTC (rev 310) @@ -13,7 +13,7 @@ 2. Older versions are provided but not recommended. [[http://netresponsibility.com/download.php#Older You may find them here]]. !!!POCO libraries -You will first need to install the POCO libraries. Note that the version needs to be 1.4 or later. Some platforms have these libraries precompiled and packaged. Otherwise you need to compile them yourself. Start by [[http://sourceforge.net/projects/poco/files/sources/poco-1.4.2/poco-1.4.2p1-all.tar.gz/download downloading the complete edition]] (i.e. not the <*basic edition*>). Unpack (extract) it (on a platform like Ubuntu, this can often be done by right-clicking on the file and choosing the unpack/extract option from the menu), which will result in the creation of a directory (folder) with the same name as the file you downloaded, and which contains other folders and files. If you want, you can unpack the file to one directory and then copy the extracted contents to another directory where you will work with it. Once you have the POCO folders and files in the directory you want them, you then need to open a terminal window and use the <*cd*> command to move yourself to that directory. While there you then need to do three things: configure, compile and install. For a user who has chosen to use the <*/home/name/poco*> directory, the procedure should look like this: +You will first need to install the POCO libraries. Note that the version needs to be 1.4 or later. Some platforms have these libraries precompiled and packaged. Otherwise you need to compile them yourself. Start by [[http://pocoproject.org/download/index.html downloading the complete edition]] (i.e. not the <*basic edition*>). Unpack (extract) it (on a platform like Ubuntu, this can often be done by right-clicking on the file and choosing the unpack/extract option from the menu), which will result in the creation of a directory (folder) with the same name as the file you downloaded, and which contains other folders and files. If you want, you can unpack the file to one directory and then copy the extracted contents to another directory where you will work with it. Once you have the POCO folders and files in the directory you want them, you then need to open a terminal window and use the <*cd*> command to move yourself to that directory. While there you then need to do three things: configure, compile and install. For a user who has chosen to use the <*/home/name/poco*> directory, the procedure should look like this: cd /home/name/poco ./configure --shared --no-tests --no-samples Modified: documentation/pages/0307-WorkingWithBlacklists.page =================================================================== --- documentation/pages/0307-WorkingWithBlacklists.page 2012-05-15 01:40:17 UTC (rev 309) +++ documentation/pages/0307-WorkingWithBlacklists.page 2012-05-16 12:59:34 UTC (rev 310) @@ -4,9 +4,9 @@ !!!Suggested Regexp syntax If you're working with blacklists and whitelists you need to know something about regular expressions (regexp). There is plenty of information on the internet, but here are some basics. -Please try these simple examples in the [[javascript:regexp_editor(); Regexp Editor]], and it shouldn't take too long before you become familiar with it. You can read [[http://netresponsibility.com/documentation.php?id=0307-WorkingWithBlacklists#1 this section]] (below) to get started. +Please try these simple examples in the <{<a href="http://netresponsibility.com/lib/regexp_editor.php" target="_blank">Regexp Editor</a>}>, and it shouldn't take too long before you become familiar with it. You can read [[#11 this section]] (below) to get started. -First of all, it's good to have a little understanding of how Net Responsibility (NR) works. The program takes each blacklist entry to match it against a given string. If you're using the default <*urlmatch*> method the string is each URL you've visited. The <*tokenmatch*> method tries to divide the URLs into natural groups of words. Then each group is tested against the blacklist. This makes the <*tokenmatch*> method more accurate, but logically slower. +First of all, it's good to have a little understanding of how Net Responsibility (NR) works. The program takes each blacklist entry to match it against a given string. It tries to divide the URLs into natural groups of words. Then each group is tested against the blacklist. !!Multiple words If the blacklist entry contains more than one word, NR will try to find each word in the string. If any of the words doesn't exist, there will be no warning. The words don't need to be found in the correct order. For example, <!Jenna Jameson!> will match against (matches in bold): @@ -62,14 +62,14 @@ - <!porn(star|ography)?!> will be displayed as <!porn!> - <!masturbat(e|ing|ion)!> will be displayed as <!masturbate!> -That's it. Feel free to try out your own keywords in the [[javascript:regexp_editor(); Regexp Editor]]. +That's it. Feel free to try out your own keywords in the <{<a href="http://netresponsibility.com/lib/regexp_editor.php" target="_blank">Regexp Editor</a>}>. !!!Using the Regexp editor When you're editing your personal blacklist or whitelist it's strongly recommended that you use the Regexp Editor. The main reason is because it will validate your regular expressions (regexp), so you can be sure they'll work as expected. -You might want to open the [[javascript:regexp_editor(); Regexp Editor]] and try it out while you're reading this guide. +You might want to open the <{<a href="http://netresponsibility.com/lib/regexp_editor.php" target="_blank">Regexp Editor</a>}> and try it out while you're reading this guide. -Make sure you've read [[http://netresponsibility.com/documentation.php?id=0307-WorkingWithBlacklists#0 Suggested Regexp Syntax]] (above) before you proceed. It's useful to know the guidelines mentioned there. +Make sure you've read [[#0 Suggested Regexp Syntax]] (above) before you proceed. It's useful to know the guidelines mentioned there. !!Matching text Here you can type any text you'd like to match. It could be a forbidden URL, or it could be some ugly words. Let's say you want to create a regexp that finds the words <!jenna!> and <!jameson!>, then you simply type these words in this box. Note that you can insert a lot of words here, and later see which ones of these will get matched. Every new line (created by [Enter], not automatic) is independent from the others. That means you can have several groups of words and see which ones are matched. For example, you could insert the following words: @@ -84,7 +84,7 @@ - jenna jamesson!> !!Regexp -Here you type the regular expression (regexp) made using the syntax mentioned [[http://netresponsibility.com/documentation.php?id=0307-WorkingWithBlacklists#0 here]]. +Here you type the regular expression (regexp) made using the syntax mentioned [[#0 here]]. !!Match This shows the result of the text you entered in the 'Matching text' section, filtered with the regexp you typed in the 'Regexp' section. If there's a match, it'll be in <!bold!>. It's updated instantly when you edit the matching text or the regexp. With the matching text we suggested before, the regexp <!jenna jameson!> would match lines 1, 2, 6 and 7. If you only have <!jenna!> as a regexp, the third line will be a match as well. To also match the last line you can change the regexp to the following: <!jenna jamess?on!>. @@ -92,13 +92,13 @@ You can experiment like this until you're happy with the output. !!Displayed as -This shows how the regexp will be shown in the report. We try to make it more readable. You can look [[http://netresponsibility.com/documentation.php?id=0307-WorkingWithBlacklists#0 here]] to see more details on how it works. +This shows how the regexp will be shown in the report. We try to make it more readable. You can look [[#0 here]] to see more details on how it works. !!Method Here you choose which method to use in the filtering. If you're using the Tokenmatch (Advanced) method, you want to choose this. Actually, the difference is only shown if you've inserted an URL (or several divided by [Enter]) in the 'Matching' textbox. !!Add to -When you're done and happy with your brand new regexp, simply hit 'Blacklist' or 'Whitelist' to add it. Note that you'll have to save and logout in order to really save the new entries. +When you're done and happy with your brand new regexp, simply hit 'Black<{}>list' or 'Whitelist' to add it. Note that you'll have to save and logout in order to really save the new entries. !!!Conclusion That's it! Feel free to play around with it, and try to develop the best regexp ever seen. ;-) If you want to share your regexps, please do. Just send us an email at [[mailto:res...@li... res...@li...]]. Modified: documentation/pages/0910-PrivacyPolicy.page =================================================================== --- documentation/pages/0910-PrivacyPolicy.page 2012-05-15 01:40:17 UTC (rev 309) +++ documentation/pages/0910-PrivacyPolicy.page 2012-05-16 12:59:34 UTC (rev 310) @@ -33,7 +33,7 @@ !!!What about deleting an account? -You may at any time delete your Net Responsibility account. This is done by logging in and clicking the tab with your username. At the very end of that page, under “Log out”, you may choose “Delete account”. When doing so, all the information you've entered will be deleted from our server. +You may at any time delete your Net Responsibility account. This is done by logging in and clicking the tab with your username. At the very end of that page, under <*Log out*>, you may choose <*Delete account*>. When doing so, all the information you've entered will be deleted from our server. !!!Do we use cookies? Modified: documentation/resources/css/styles.css =================================================================== --- documentation/resources/css/styles.css 2012-05-15 01:40:17 UTC (rev 309) +++ documentation/resources/css/styles.css 2012-05-16 12:59:34 UTC (rev 310) @@ -1,446 +1,388 @@ -/* - * styles.css - * - * Style Sheet for Applied Informatics Documentation. - * - * Copyright (c) 2004-2007, Applied Informatics - * - */ +/* General settings */ -body -{ - margin-top: 0; - margin-bottom: 0; - margin-left: 0; - margin-right: 0; - color: #000000; - background-color: #ffffff; +h1, h2, h3, h4 { + font-family: serif, Garamond, Times New Roman; + color: black; + margin: 20px 0px 7px 0px; } -p, h1, h2, h3, h4, h5, h6, ul, ol, li, td, th, address, blockquote, strong, b, emph, i -{ - font-family: "Trebuchet MS", Geneva, Arial, Helvetica, SunSans-Regular, sans-serif; +h1 { + font-size: 32px; + text-align: center; + color: #333333; + margin: 5px 0 10px 0; + } -p, ul, ol, address, blockquote, h6 -{ - color: black; - font-size: 9pt; - line-height: 12pt; - margin-top: 6px; - margin-bottom: 4px; +h2 { + margin-top: 25px; + font-size: 18px; } -h1 -{ - color: black; - font-size: 18pt; - font-weight: normal; - line-height: 22pt; - margin-top: 12px; - margin-right: 0; - margin-bottom: 12px; + +h3 { + font-size: 15px; + margin: 20px 0 0 0; + padding-left: 6px; + background: #CCC; + border-bottom: 1px solid #AAA; } -h1.category, h1.namespace -{ - font-size: 10pt; + +h4 { font-weight: bold; - margin-top: 0px; - margin-bottom: 8px; - margin-left: 16px; - margin-right: 16px; - line-height: 10pt; - background: #0076B8; - color: white; + font-size: 12px; } -h1.template -{ - font-size: 11pt; - margin-top: 0px; - margin-bottom: 0px; - margin-left: 16px; - margin-right: 16px; - line-height: 12pt; - background: #0076B8; - color: white; +h2 a, h3 a, h4 a +{ + color: black; + text-decoration: none; } -h1.title, h1.symbol -{ - font-size: 16pt; - margin-top: 0px; - margin-bottom: 0px; - margin-left: 16px; - margin-right: 16px; - line-height: 18pt; - background: #0076B8; - color: white; -} -div.header -{ - margin-top: 0; - margin-left: 0; - margin-right: 0; - margin-bottom: 0; - background: #0076B8; - color: white; - padding-top: 8px; - padding-bottom: 8px; - border-bottom-width: 1px; - border-bottom-color: #012F50; - border-bottom-style: solid; -} -div.body -{ - margin-top: 16px; - margin-left: 16px; - margin-right: 16px; +td { + font-size: 12px; } -pre -{ - color: #111; - background: #F4F4F4; - font-size: 8pt; - border-bottom-width: 1px; - border-bottom-color: #CCCCCC; - border-bottom-style: solid; - padding-top: 4px; - padding-bottom: 4px; - padding-left: 4px; - padding-right: 4px; +hr { + border: solid 1px #CCCCCC; + height: 1px; } -h2 -{ - color: black; - font-size: 16px; - margin-top: 14px; - margin-bottom: 0; +.help { + border: solid #999999; + border-width: 0 0 0 1; + margin: 0 0 25 10; + padding: 0 0 0 5; } -h3 -{ - color: black; - font-size: 10pt; - margin-top: 10px; - margin-right: 0; - margin-bottom: 0px; - background: #CCC; - border-bottom-width: 1px; - border-bottom-color: #AAA; - border-bottom-style: solid; - padding-left: 4px; - padding-right: 4px; - padding-top: 2px; - padding-bottom: 2px; +.adminHelp { + border: solid #FF6666; + border-width: 0 0 0 1; + margin: 0 0 25 10; + padding: 0 0 0 5; } -h3.overview -{ - color: black; - font-size: 12pt; - margin-top: 0; - margin-right: 0; - margin-bottom: 0px; - background: white; - border-bottom-width: 0px; - padding-left: 0px; - padding-right: 0px; - padding-top: 0px; - padding-bottom: 0px; +body { + overflow-y: scroll; + font-family: sans-serif, verdana; + font-size: 12px; + margin: 0px; + padding: 0px; + background: white top url('../img/bg.png') repeat-x; + height: 100%; + line-height: 140%; } -h4 -{ - color: black; - font-size: 10pt; - margin-top: 10px; - margin-bottom: 0; +html { + height: 100%; } -p.decl -{ - color: black; - font-size: 8pt; - line-height: 10pt; - margin-top: 0; - margin-right: 0; - margin-bottom: 0; - background: #DDD; - border-bottom-width: 1px; - border-bottom-color: #BBB; - border-bottom-style: solid; - padding-left: 4px; - padding-right: 4px; - padding-top: 3px; - padding-bottom: 3px; +p { + display: block; + padding: 0px; + margin: 6px 0 12px 0; + font-size: 12px; } -p.index -{ - font-size: 8pt; - line-height: 10pt; +img { + margin: 0px; + border: 0px; } -li -{ - font-size: 9pt; - color: #000000; - margin-left: 0px; - margin-bottom: 2px; - margin-top: 4px; +div { + text-align: left; } -ul -{ +ul { padding-left: 0px; margin-left: 2em; - list-style-type: disc; - list-style-position: outside; - list-style-image: url(../images/bullet.gif); - margin-top: 4px; + list-style-type: disc; + list-style-position: outside; + list-style-image: url('../images/bullet.gif'); + margin-top: 4px; } -div.toc ul +li { - padding-left: 0px; - margin-left: 2em; - list-style-type: disc; - list-style-position: outside; - list-style-image: url(../images/bullet.gif); - margin-top: 4px; + font-size: 9pt; + color: #000000; + margin: 2px 0px; } li.level1 { - font-size: 9pt; - color: #000000; - margin-left: 0px; - margin-bottom: 2px; - margin-top: 2px; - font-weight: bold; + /* Currently a normal link */ } -li.level2 -{ - font-size: 9pt; - color: #000000; - margin-left: 16px; - margin-bottom: 2px; - margin-top: 2px; +li.level2 { + margin: 2px 0 0 16px; + font-style: italic; } li.level3 { - font-size: 9pt; - color: #000000; - margin-left: 32px; - margin-bottom: 2px; - margin-top: 2px; + margin: 2px 0 0 32px; + font-style: italic; } -strong, b -{ - font-weight: bold; +pre { + background: #f4f4f4; + overflow: auto; + border-bottom: 1px solid #CCCCCC; + padding: 4px; } -emph, i -{ - font-style: italic; +/* General template styling */ + +#top-logo { + background: url('../img/logo.png'); + width: 561px; + height: 116px; + position: absolute; + top: -116px; + left: 0px; } -.address -{ - line-height: 11pt; - margin-bottom: 4px; +#start-link { + position: absolute; + background: transparent; + top: 16px; + left: 33px; + width: 491px; + height: 49px; + cursor: pointer; + cursor: hand; } -.footer -{ - font-size: 7pt; - font-family: Verdana, Arial, Helvetica, sans-serif; - text-align: left; - line-height: 9pt; - margin-top: 16px; - margin-left: 0; - margin-right: 0; - margin-bottom: 10px; +#main { + background: transparent url('../img/shadow_repeat.png') repeat-y; + width: 561px; + min-height: 370px; + position: relative; + top: 116px; } -a:link -{ - color: #069; - text-decoration: underline; +#dogear { + background: white top right url('../img/dogear.png') no-repeat; + width: 530px; + height: 366px; + position: absolute; + top: 0px; + left: 0px; + z-index: -1; } -a:visited -{ - color: #069; - text-decoration: underline; +#dogear-padding { + float: right; + width: 50px; + height: 50px; } -a:active -{ - color: #069; - text-decoration: underline; +#IEbugfixer { + height: 370px; + width: 1px; + float: right; } -a:hover -{ - color: #069; - text-decoration: underline; +#content { + position: relative; + width: 510px; + padding: 10px; + left: 15px; } -a.namespace:link -{ - color: white; - text-decoration: none; +#shadow-left { + background: #ffffff url('../img/shadow_left.png') no-repeat; + width: 15px; + height: 366px; + position: absolute; + left: 0px; + top: 0px; } -a.namespace:visited -{ - color: white; - text-decoration: none; +#shadow-right { + background: #ffffff url('../img/shadow_right.png') no-repeat; + width: 17px; + height: 366px; + position: absolute; + right: 0px; + top: 0px; } -a.namespace:active -{ - color: white; - text-decoration: underline; +#bottom { + background: url('../img/soap.png'); + width: 622px; + height: 140px; + position: absolute; + bottom: -140px; + left: 0px; } -a.namespace:hover -{ - color: white; - text-decoration: underline; +/* The tabs */ + +#nav { + position: absolute; + bottom: 0px; + left: 25px; + height: 24px; + font-size: 0px; + min-width: 50px; } -a.class:link -{ - color: black; - text-decoration: none; +#nav span a { + position: relative; + bottom: 7px; + color: #e3ddff; } -a.class:visited -{ - color: black; - text-decoration: none; +#nav span.active-tab a { + position: relative; + bottom: 7px; + color: #100d20; } -a.class:active -{ - color: #069; - text-decoration: underline; +#nav span span.before { + width: 11px; + height: 100%; + background-image: inherit; + background-repeat: no-repeat; + background-position: 0px -24px; } -a.class:hover -{ - color: #069; - text-decoration: underline; +#nav span { + position: relative; + height: 24px; + min-width: 10px; + background-image: url('../img/tabs.png'); + background-repeat: repeat-x; + background-position: 0px -48px; + display: inline-block; + list-style-type: none; + font-size: 10px; } -a.footer:link -{ - color: #069; - text-decoration: underline; +#nav span span.after { + width: 11px; + height: 100%; + background-image: inherit; + background-position: 0px -72px; } -a.footer:visited -{ - color: #069; - text-decoration: underline; + +#nav span.active-tab span.before { + background-position: 0px -96px; } -a.footer:active -{ - color: #069; - text-decoration: underline; +#nav span.active-tab { + background-position: 0px -120px; } -a.footer:hover -{ - color: #069; - text-decoration: underline; +#nav span.active-tab span.after { + background-position: 0px -144px; } -h3.overview a:link, h3.overview a:visited -{ - color: black; - text-decoration: none; +#loginDiv { + background: white; + border: 1px solid #999999; + width: 210px; + position: absolute; + top: 0px; + left: 150px; + z-index: 10; + box-shadow: 0 2px 10px #999999; } -h3.overview a:active, h3.overview a:hover -{ - color: #069; - text-decoration: none; +#loginError { + color: red; + font-weight: bold; } -h2 a:link, h3 a:link, h4 a:link -{ - color: black; - text-decoration: none; +/* Styling for the links */ + +a { + color: #416373; + /*font-weight: bold;*/ + text-decoration: underline; } -h2 a:visited, h3 a:visited, h4 a:visited -{ - color: black; - text-decoration: none; +a:link { + color: #416373; } -h2 a:active, h3 a:active, h4 a:active -{ - color: black; - text-decoration: none; +a:hover { + color: black; } -h2 a:hover, h3 a:hover, h4 a:hover -{ - color: black; - text-decoration: none; +a:active { + color: black; } -li.level1 a:link, li.level2 a:link, li.level3 a:link -{ - color: #069; - text-decoration: underline; +/* Specific styling for the documentation */ + +div.description img { + display: block; + margin: 15px auto; + max-width: 100%; + box-shadow: 0 2px 10px #999999; } -li.level1 a:visited, li.level2 a:visited, li.level3 a:visited -{ - color: #069; - text-decoration: underline; + +div.header { + background: #416373; + color: white; + padding: 10px 0px; } -li.level1 a:active, li.level2 a:active, li.level3 a:active -{ - color: #069; - text-decoration: underline; +div.header a, div.header a:link { + color: white; } -li.level1 a:hover, li.level2 a:hover, li.level3 a:hover -{ - color: #069; - text-decoration: underline; +div.header a:hover, div.header a:active { + color: white; + text-decoration: none; } -.image -{ - margin-top: 10px; - margin-bottom: 10px; +div.header h1 { + color: white; + margin: 0px 16px; + text-align: left; } -.imagecaption +div.header h1.namespace, div.header h1.category, div.header h1.template { + font-size: 14px; +} + +div.header h1.symbol, div.header h1.title { + font-size: 22px; +} + +div.body { - font-family: "Trebuchet MS", Geneva, Arial, Helvetica, SunSans-Regular, sans-serif; - color: black; - font-size: 9pt; - line-height: 12pt; + margin: 16px; +} + +div.description h3, h3.overview { font-style: italic; - margin-top: 4px; - margin-bottom: 0px; + margin-top: 10px; + padding: 0px; + background: transparent; + border: 0px; } + +p.footer { + font-size: 7pt; + text-align: left; + line-height: 9pt; + margin: 16px 0px; +} + +p.decl { + margin-top: 0px; + background: #DDD; + overflow: auto; + border-bottom: 1px solid #BBB; + padding: 4px; +} This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-15 01:40:23
|
Revision: 309 http://responsibility.svn.sourceforge.net/responsibility/?rev=309&view=rev Author: dustsource Date: 2012-05-15 01:40:17 +0000 (Tue, 15 May 2012) Log Message: ----------- An updated set of documentation for uploading to website. Modified Paths: -------------- documentation/doc/net-responsibility-3.0.2-doc.zip Modified: documentation/doc/net-responsibility-3.0.2-doc.zip =================================================================== (Binary files differ) This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-15 01:37:36
|
Revision: 308 http://responsibility.svn.sourceforge.net/responsibility/?rev=308&view=rev Author: dustsource Date: 2012-05-15 01:37:29 +0000 (Tue, 15 May 2012) Log Message: ----------- Expanded the following documentation: --"Why Net Resposibility?" --"Showcase with Screenshots" --"Working with the Blacklists" --"Troubleshooting Installation and Configuration" --"FAQ" --"How to Get Help" Modified Paths: -------------- documentation/pages/0101-WhyNR.page documentation/pages/0102-Showcase.page documentation/pages/0307-WorkingWithBlacklists.page documentation/pages/0309-TroubleshootingInstallation.page documentation/pages/0901-FAQ.page documentation/pages/0902-HowToGetHelp.page Modified: documentation/pages/0101-WhyNR.page =================================================================== --- documentation/pages/0101-WhyNR.page 2012-05-15 01:34:40 UTC (rev 307) +++ documentation/pages/0101-WhyNR.page 2012-05-15 01:37:29 UTC (rev 308) @@ -1,8 +1,11 @@ Why Net Responsibility? A01NR_Appetizer -!!!Why accountability software? +!!!Why internet accountability software? +Some people have come to the belief that some of the ways they have been using the internet are unhealthy and potentially harmful and destructive to themselves and others they relate to. The two most popular examples of this are pornography and gambling. If they act on this belief and decide to make a change in the way they use the internet, this can often be difficult because of trying to break old habits and/or addictive behaviors. One thing that is helpful for them is to have one or more accountability partners that they communicate with regularly and honestly about how they are using the internet and whether they are staying faithful to the changes they wish to make. They also find that choosing to use internet accountability software can be a helpful tool in this process because it automatically monitors their internet usage and reports it to their accountability partner(s). The presence of accountability software will give extra incentive to resist the urge to go back to one's old ways of internet use, and also avoids a situation where a person might consider using deception and denial when asked about whether they have slipped into old habits. In short, they choose to use this type of software to help them live better lives. -!!!What about the others? +!!!What about other internet accountability software? +Both [[http://www.covenanteyes.com/ Covenant Eyes]] and [[http://www.x3watch.com/ X3watch]] are popular internet accountability programs, but neither one of their main products is currently compatible with Linux-based computer systems, and neither one is open-source. The Net Responsibility project was started to fill the need for a good open-source internet accountability software for Linux. Since then, our vision has expanded to also eventually make it available on other platforms like Windows and Mac OS X, in order to provide a good open-source alternative to the software currently available. !!!Conclusion +We believe that Net Responsibility fills an important need for those who are looking for a good internet accountability program for Linux. Beyond this, we believe that it can become a good open-source alternative on other platforms as well. Modified: documentation/pages/0102-Showcase.page =================================================================== --- documentation/pages/0102-Showcase.page 2012-05-15 01:34:40 UTC (rev 307) +++ documentation/pages/0102-Showcase.page 2012-05-15 01:37:29 UTC (rev 308) @@ -2,7 +2,75 @@ A01NR_Appetizer !!!Features +Net Responsibility (NR) is a good open-source internet accountability software for Linux-based systems, and we are working towards making it available for all major platforms, including Windows and Mac OS X. Its purpose is to help people change their surfing habits by giving them a useful tool for holding themselves accountable to others. Following are its main features: + - <!Internet monitoring.!> Whenever the user's computer is on, NR is keeping track of all web browsing activity. + - <!Regular reports emailed to accountability partners.!> Automatic reports can be sent daily, every other day, or with any number of days in-between. + - <!Inappropriate content flagged in reports.!> Any activity NR finds suspicious will be displayed prominently so accountability partners will see it. + - <!Instant email reports.!> Users can choose to have a report emailed to their accountability partners as soon as NR senses any suspicious activity. + - <!Reports include an overview as well as details.!> The overview is often all that needs to be looked at, but accountability partners can also view a list of every website visited if they wish. + - <!Suspicious websites are ranked.!> Each of these is assigned a number to indicate the probability that it is inappropriate. + - <!Unlimited number of accountability partners.!> Users can choose to have reports sent to as many people as they want. + - <!Discourages tampering or 'cheating' by users.!> Any attempts to bypass NR will be detected and reported to accountability partners. + - <!Highly configurable.!> Users are able to choose from a wide variety of built-in settings to suit their specific needs. Third-party tools and access to the source code gives even greater flexibility if needed. + - <!User forum.!> The user forum can be browsed for information, and can also be used as a place to discuss any questions or problems users may be facing. !!!Reports +Here is a two-part example of an email report: +<% +<img src="images/EmlRpt1.png" alt="Email Report, Part 1" border="1"> +%> + +<% +<img src="images/EmlRpt2.png" alt="Email Report, Part 2" border="1"> +%> + +Here is an example of the more detailed attached report: + +<% +<img src="images/AttRpt.png" alt="Attached Report" border="1"> +%> + !!!Installation +Before NR can be installed, a user needs to go to the NR website and register... + +<% +<img src="images/WebReg.png" alt="Registration" border="0"> +%> + +During the registration process, users enter their configuration settings, which are then stored on the NR server. + +After registration, a terminal window can be opened... + +<% +<img src="images/MenuTerm.png" alt="Menu for Terminal" border="0"> +%> + +which might look something like this: + +<% +<img src="images/Term.png" alt="Terminal" border="0"> +%> + +After entering a few commands in the terminal, Net Responsibility is installed and running. + +Users can also use a package manager with a GUI to install NR... + +<% +<img src="images/PkgMngr.png" alt="Package Manager" border="0"> +%> + +!!!Forum +Users also have access to a forum where they can browse for information or discuss any questions or problems they are facing with other users or the NR developers... + +<% +<img src="images/Forum.png" alt="Forum" border="0"> +%> + + +!!!Mailing list +If users prefer to use email, they can also contact the NR developers with questions or problems they are facing... + +<% +<img src="images/Email.png" alt="Email to Mailing List" border="0"> +%> Modified: documentation/pages/0307-WorkingWithBlacklists.page =================================================================== --- documentation/pages/0307-WorkingWithBlacklists.page 2012-05-15 01:34:40 UTC (rev 307) +++ documentation/pages/0307-WorkingWithBlacklists.page 2012-05-15 01:37:29 UTC (rev 308) @@ -2,5 +2,103 @@ A03NR_Install !!!Suggested Regexp syntax +If you're working with blacklists and whitelists you need to know something about regular expressions (regexp). There is plenty of information on the internet, but here are some basics. +Please try these simple examples in the [[javascript:regexp_editor(); Regexp Editor]], and it shouldn't take too long before you become familiar with it. You can read [[http://netresponsibility.com/documentation.php?id=0307-WorkingWithBlacklists#1 this section]] (below) to get started. + +First of all, it's good to have a little understanding of how Net Responsibility (NR) works. The program takes each blacklist entry to match it against a given string. If you're using the default <*urlmatch*> method the string is each URL you've visited. The <*tokenmatch*> method tries to divide the URLs into natural groups of words. Then each group is tested against the blacklist. This makes the <*tokenmatch*> method more accurate, but logically slower. + +!!Multiple words +If the blacklist entry contains more than one word, NR will try to find each word in the string. If any of the words doesn't exist, there will be no warning. The words don't need to be found in the correct order. For example, <!Jenna Jameson!> will match against (matches in bold): + - www.google.com/q=<!jenna!>+<!jameson!> + - www.google.com/q=<!jameson!>+mrs+<!jenna!> + - www.google.com/q=james+jameson + - www.google.com/q=jenna + +!!Case doesn't matter +The matches are always case-insensitive. For example: + - <!porn!> will match against <!porn!>, <!Porn!>, <!PORN!>, <!pOrn!>, etc. + +!!Alphabetic characters +You might want to think of regular expressions as patterns. The simplest ones are only made of alphabetic characters. For example: + - <!porn + - pornstar + - jenna jameson!> + +!!Question mark (?) with one character +Some characters have certain functions. For instance, a question mark (?) is used to tell the filter to match one or zero of the preceding character. For example: + - <!boobs?!> will match <!boob!> or <!boobs!> because the <*s*> is optional. + +!!Question mark (?) with multiple characters +You can also use the question mark for more than one character, but then you need to group them together with parentheses. For example: + - <!porn(star)?!> will match <!porn!> or <!pornstar!> because <*star*> is optional. + - <!porn(stars?)?!> will match <!porn!>, <!pornstar!> or <!pornstars!>, but not <*porns*>. + +!!Vertical bar (|) +Another useful character is the vertical bar (|). It is used as the word <*or*>. Match this <*or*> that. It's best to use it inside parentheses. For example: + - <!porn(star|ography)!> will match <!pornstar!> <*or*> <!pornography!>, but not <*porn*>. + - <!masturbat(e|ing|ion)!> will match <!masturbate!>, <!masturbating!> and <!masturbation!>. + +!!Question mark (?) with vertical bar (|) +Of course, you can also use the question mark together with the vertical bar. For example: + - <!porn(star|ography)?!> will match <!porn!>, <!pornstar!> <*or*> <!pornography!>. + +!!Conditional word matches +Sometimes it might be useful to match one word, and if existing, a second one. The following example is valid: + - <!sex (anal|oral|group)?!> will match <!sex!>, and if <!anal!>, <!oral!> or <!group!> also exists, it will be included in the match. + +!!Other characters (*) (+) (.) +Similar to (?) we have (*) and (+). While (?) means one or zero of the preceding, (*) means zero or more of the preceding, and (+) means one or more. It is recommended to avoid these characters with Net Responsibility because they may cause many false positives, but you might use them at your own risk. For example: + - <!xxx+!> will match <!xxx!>, <!xxxxxxx!>, <!xxxxxxxxxxxxxxxxxx!> and so on. + - <!po+rn!> will match <!porn!>, <!pooorn!>, <!poooooooorn!> and so on. + +One character that is often used inside regular expressions is the dot (.). A dot means one of any character. It is often used together with the asterisk (.*) to create a pattern that matches anything or nothing. It is strongly suggested to avoid this pattern since it will produce many false positives, and the reports will be harder to understand. Since Net Responsibility doesn't care about what comes before or after a match, the following patterns would be totally unnecessary: + - <!.*porn.* + - porn.*star!> + +!!Making the reports easier to read +In the reports, every match is categorized according to the blacklist keyword it matched against. So both <*porn*> and <*pornstar*> would fall into the category <*porn(star|ography)?*>, but to make the reports a little easier to understand, Net Responsibility tries to strip out irrelevant information. Therefore, all question marks are removed along with the preceding character, or characters in parentheses. The example above would simply be displayed as <*porn*>. Also, for other parentheses only the first word will be displayed, so you should put the easiest to understand first. For example: + - <!boobs?!> will be displayed as <!boob!> + - <!porn(star|ography)?!> will be displayed as <!porn!> + - <!masturbat(e|ing|ion)!> will be displayed as <!masturbate!> + +That's it. Feel free to try out your own keywords in the [[javascript:regexp_editor(); Regexp Editor]]. + !!!Using the Regexp editor +When you're editing your personal blacklist or whitelist it's strongly recommended that you use the Regexp Editor. The main reason is because it will validate your regular expressions (regexp), so you can be sure they'll work as expected. + +You might want to open the [[javascript:regexp_editor(); Regexp Editor]] and try it out while you're reading this guide. + +Make sure you've read [[http://netresponsibility.com/documentation.php?id=0307-WorkingWithBlacklists#0 Suggested Regexp Syntax]] (above) before you proceed. It's useful to know the guidelines mentioned there. + +!!Matching text +Here you can type any text you'd like to match. It could be a forbidden URL, or it could be some ugly words. Let's say you want to create a regexp that finds the words <!jenna!> and <!jameson!>, then you simply type these words in this box. Note that you can insert a lot of words here, and later see which ones of these will get matched. Every new line (created by [Enter], not automatic) is independent from the others. That means you can have several groups of words and see which ones are matched. For example, you could insert the following words: + - <!jenna jameson + - jameson jenna + - jenna + - jameson + - jen jameson + - jennas jameson + - www.google.com/search?q=jenna+jameson + - www.jenna.com/jameson + - jenna jamesson!> + +!!Regexp +Here you type the regular expression (regexp) made using the syntax mentioned [[http://netresponsibility.com/documentation.php?id=0307-WorkingWithBlacklists#0 here]]. + +!!Match +This shows the result of the text you entered in the 'Matching text' section, filtered with the regexp you typed in the 'Regexp' section. If there's a match, it'll be in <!bold!>. It's updated instantly when you edit the matching text or the regexp. With the matching text we suggested before, the regexp <!jenna jameson!> would match lines 1, 2, 6 and 7. If you only have <!jenna!> as a regexp, the third line will be a match as well. To also match the last line you can change the regexp to the following: <!jenna jamess?on!>. + +You can experiment like this until you're happy with the output. + +!!Displayed as +This shows how the regexp will be shown in the report. We try to make it more readable. You can look [[http://netresponsibility.com/documentation.php?id=0307-WorkingWithBlacklists#0 here]] to see more details on how it works. + +!!Method +Here you choose which method to use in the filtering. If you're using the Tokenmatch (Advanced) method, you want to choose this. Actually, the difference is only shown if you've inserted an URL (or several divided by [Enter]) in the 'Matching' textbox. + +!!Add to +When you're done and happy with your brand new regexp, simply hit 'Blacklist' or 'Whitelist' to add it. Note that you'll have to save and logout in order to really save the new entries. + +!!!Conclusion +That's it! Feel free to play around with it, and try to develop the best regexp ever seen. ;-) If you want to share your regexps, please do. Just send us an email at [[mailto:res...@li... res...@li...]]. Modified: documentation/pages/0309-TroubleshootingInstallation.page =================================================================== --- documentation/pages/0309-TroubleshootingInstallation.page 2012-05-15 01:34:40 UTC (rev 307) +++ documentation/pages/0309-TroubleshootingInstallation.page 2012-05-15 01:37:29 UTC (rev 308) @@ -1,3 +1,69 @@ -Troubleshooting +Troubleshooting installation and configuration A03NR_Install +!!!Testing Net Responsibility +After you install or update Net Responsibility (NR) or if you suspect a problem, you may want to test whether it is working properly. Here are a few ways to to do that. + +!!Is the NR program running properly? +Since Net Responsibility is designed to run in the background, it is often useful to have a way to confirm whether it is running properly or not. Following is a guide to the best way to do this, using a script file we've developed for this purpose. It is best to wait for several minutes after your system starts or NR is started before running this test. + +<!Step 1:!> Download the tarball (archived file) from [[https://responsibility.svn.sourceforge.net/svnroot/responsibility/utils/check-nr/check-nr.tar.gz this link]] and extract/unpack it to the directory/folder of your choice. The contents should include the script file <*check-nr.sh*> and a README file with instructions on how to use it. + +<!Step 2:!> Next you'll need to use the <*cd*> command in a terminal window to go to the folder where you put the script file. So, if I put it in <*/my/big/folder*> I would enter the following command: + + cd /my/big/folder + +<!Step 3:!> Once you're in the folder where the script file is, then you want to run the script by entering the following command: + + sudo ./check-nr.sh + +(Note: <*sudo*> is the way Ubuntu gives a command root permission. If you are using a different system, you just need to know that the command <*./check-nr*> needs to be run with root permission, however that is handled.) + +If the above command runs successfully, and NR is running properly, then you should see this output: + + Net Responsibility seems to be up and running + +If NR is not running properly, then you should see this output: + + Net Responsibility is NOT running! + +<!Troubleshooting:!> +It's possible that when you try to run the script, you'll get an error message like this: + + sudo: ./check-nr: command not found + +If this happens, it's likely that the script file doesn't have 'execute' permission, and so the system doesn't allow it to run. To give it 'execute' permission, you can run the following command: + + chmod +x check-nr.sh + +Then you can try the previous command again to see if it's working. If you get the error again in the future, you'll just need to run the above command again before running the script. + +An alternative, but less reliable, test to see if NR is running properly can be done by running the following command in the terminal: + + ps -ef|grep net-responsibility + +If the only line of output you see contains <*grep*>, then NR is not running as it should. However, if you see an additional line that contains <*net-responsibility --daemon*> then it is probably running as it should. Note that it is best to wait for several minutes after your system starts or NR is started before running this test. + +!!Is NR sending reports? +The following tests send emails to whatever email addresses you entered to receive reports (such as your accountability partners) when you registered on the website. So for testing purposes, you will want to first make sure that your own email is included in that section of the settings. Note that it may take some time for these emails to show up, and they may end up in the Spam/Junk/Trash folder of the email server, or be quarantined by a spam filtering system. + +You can test NR's email delivery by running the following command in a terminal: + + sudo net-responsibility -tr + +If this command executes successfully and you are connected to the internet, then a test report (i.e. an email with a brief message, not a report of your internet activity) should be sent. + +After doing a bit of internet browsing (so there is some activity to report), you can test NR's creation and sending of reports by running the following command in a terminal: + + sudo net-responsibility -r + +If this command executes successfully and you are connected to the internet, then a manual report (i.e. a report of your internet activity) should be sent. + +If you think test emails/reports and/or manual (or automatic) reports are being sent but are not being received by the email recipients, see [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports this guide]] for further troubleshooting ideas. + + +!!!Configuration changes are not implemented +If you have made changes to your configuration settings online, but NR does not seem to have implemented them, see [[http://netresponsibility.com/documentation.php?id=0301-ConfigurationsExplained this guide]] to make sure you are using the right procedure for making these changes. + +!!!Further help +If you are having problems with installation and/or configuration that you are still not able to solve, [[http://www.netresponsibility.com/forum/ visit our forum]]. You can browse through the various threads in the "Installation and Configuration" category to see if anyone else has encountered the same problem and if you can find any solutions there. If that still doesn't help, you can start a new topic describing your problem, and we will do our best to assist you in resolving it. Note that you will need to be logged in to post to the forum. Modified: documentation/pages/0901-FAQ.page =================================================================== --- documentation/pages/0901-FAQ.page 2012-05-15 01:34:40 UTC (rev 307) +++ documentation/pages/0901-FAQ.page 2012-05-15 01:37:29 UTC (rev 308) @@ -1,6 +1,155 @@ -FAQ +FAQ (Frequently Asked Questions) A09NR_FurtherReading !!!About the FAQ +This part of the documentation is meant to be a useful guide when you have a common question about Net Responsibility (NR) for which you need an answer. These are sorted by category and the categories are arranged alphabetically. Many of the answers may be short, but often links will be provided in case more information is needed. If you have a question or problem that is not addressed here, see [[http://netresponsibility.com/documentation.php?id=0902-HowToGetHelp this guide]] to find out other ways of finding answers and solving problems. -!!!Questions and Answers +!!!Configuration, Registration, and Account-Related Questions + +!!How can I find out my username and/or password, if I've lost or forgotten them? +Go to the [[http://www.netresponsibility.com NR website]], click on the 'Login' tab, click on 'Forgot password?,' enter your username or email address (the one you used to register) in the box provided, click on 'Send password,' and you should soon get an email containing your username and password. + +!!How do I change my configuration settings? +[[http://netresponsibility.com/documentation.php?id=0301-ConfigurationsExplained#9 Click here]] for instructions on how to make changes to your online configuration settings. + +!!Can I use the same NR account for more than one computer? +Yes, but that means you will also be using the same configuration settings for each computer, so it won't work to use the same account if you want different report frequencies or other differences in settings. + +Also, each computer will send out reports independent of the others. So if you've set up NR to send one report a week, and use the same account for two computers, your accountability partners will end up receiving two reports a week, without knowing which one is from which computer. + +!!Can I configure NR for different users of the same computer, so that each user has their own NR account? +Currently this is not possible, as far as we know, but this is a feature that might be implemented in the future. + +!!How do I delete my NR account? +Log in to the [[http://www.netresponsibility.com NR website]], click on the tab with your username on it, click on 'Log out', and then click on 'Delete account'. If this doesn't work [[mailto:res...@li... let us know]] and we'll try to help you out as soon as possible. In your email, please mention the username of the account you are trying to delete, as well as the details of what happened when you tried to delete the account. + +!!Why are my accountability partners not being notified of configuration changes? +This could be because of improper online configuration settings, a bug in the NR program, or simply because the notification emails are being caught in a spam filter. See [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports this guide]] for more information. + +!!Is there any way for accountablility partners to be informed if the NR program is uninstalled? +Yes, they are automatically informed by email when Net Responsibility is uninstalled. If they have not received the expected email, see [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports this guide]] for more information on possible reasons for this. + +!!!Development + +!!How can I help with the Net Responsibility project? +Now this is a question we love to hear! :-) See the [[http://netresponsibility.com/documentation.php?id=0903-ContributeToNR Contribute to Net Responsibility]] guide for some ideas of how you can help (even in small ways) make NR a better program for a wider group of grateful users. + +!!Is there a repository set up somewhere that can be 'checked out,' if I'm interested in helping with NR coding (programming)? +The SVN trunk for NR can be <*checked out*> from this URL: [[https://responsibility.svn.sourceforge.net/svnroot/responsibility/trunk/ https://responsibility.svn.sourceforge.net/svnroot/responsibility/trunk/]]. For more information on how best to get started with NR coding, [[5001-GettingStarted.html read this guide]]. + +!! What is the current status of Net Responsibility for Windows? +There are some important features that are not yet implemented in the Windows version of NR. Therefore we've decided to wait before we release it. Once those things are fixed, we will create an installation file and make it available on our website. + +If you're interested in following the Windows development process, you can stay updated through [[http://netresponsibility.com/forum/index.php?topic=55.0 this forum thread]]. When logged in, you can click "Notify" for this topic in order to automatically receive email notifications about any new posts. + +!! What is the current status of Net Responsibility for Mac? +We're working on creating packages for Mac users. It is technically possible to download the [[http://netresponsibility.com/documentation.php?id=0305-CompileFromSource source code]] and compile it. More information about compiling it on Mac can be [[http://netresponsibility.com/forum/index.php?topic=63.0 found here]]. However, the easiest thing would be to wait (or help us out with creating the package). + +!!!General + +!!Is Net Responsibility like X3Watch, but for Linux? +The short answer is yes, NR is like X3Watch for Linux. It is developed by a different team, but it has the same intentions. While there is a definite focus on providing internet accountability for Linux systems, our goal is to eventually make it available on a variety of platforms, including Mac OS X and Windows. + +!!Why is NR being developed for Windows, a platform for which there is already internet accountability software? +After version 2.0.2, we decided to rewrite NR using a different programming language that would have less limitations and give us more flexibility. While the focus of the rewrite remained on developing a good internet accountability program for Linux systems, we decided it was also a good opportunity to begin working towards making it compatible with other platforms as well. While there is other accountability software available for Windows, there are currently no good open source alternatives. Also, if we make NR available for more platforms, the chance of finding more developers also increases, thus improving the overall program. + +!!Do my accountability partners need to be running a Linux system? +No, all they need is to have any system that is able to receive email, since this is how NR's reports are sent. + +!!What is NR's privacy policy? +[[http://netresponsibility.com/documentation.php?id=0910-PrivacyPolicy Click here]] to view our privacy policy. + +!!!Installing, Uninstalling, and Upgrading + +!!How do I download and/or install a copy of the NR software? +If you are interested in a precompiled package (installation file), see [[http://netresponsibility.com/documentation.php?id=0304-InstallFromPackages these instructions]]. If you are interested in compiling from the source code, see [[http://netresponsibility.com/documentation.php?id=0305-CompileFromSource these instructions]]. + +!!How do I check what version of NR is installed? +One way this can be done is by opening a terminal window and running the following command as root (for Ubuntu users, this means adding <*sudo*> and a space before the command): + net-responsibility --debug +One of the lines of output should mention what version of NR is installed. + +!!Why does it say I have a later version of NR when I am trying to upgrade? +Depending on the software that is handling the upgrade (e.g. a package manager), this can happen when the current version and new version use different version numbering systems. Usually the problem can be resolved by first uninstalling the current version and then installing the new version. If using a package manager, you may need to refresh/update it after uninstalling the current version so it will recognize the new version as available to install. + +!!I just upgraded to NR 3.x and I can't find the GUI that used to be one of my menu items. +The GUI that was used in versions 2.x for configuration, sending test reports/emails, and sending manual reports is not currently available in NR 3.x. See the second post in [[http://www.netresponsibility.com/forum/index.php?topic=80.0 this thread]] for instructions on how you can do these same things using terminal commands. + +!!!Internet Monitoring + +!!Which browsers are compatible with NR? +All HTTP traffic on your computer is monitored, logged, and reported, so NR will work with any browser. + +!!Does NR monitor internet use with Google Chrome's 'incognito' mode, Firefox's 'private' surfing, etc.? +Yes, it will monitor and log all HTTP traffic on your computer, regardless of the browser, browser mode, or browser settings you use. + +!!Does NR monitor all internet connections, whether or not they are made through a browser? +Any HTTP traffic on your computer is monitored, logged, and reported, so if a program other than a browser makes a connection over HTTP, that will be monitored and logged as well. NR does not currently monitor internet connections using protocols other than HTTP. + +!!How does NR handle proxy forwarding websites? +Net Responsibility will probably not be able to catch anything viewed through a proxy site, but you may add keywords to your personal blacklist (found in your online configuration settings) that will report if you've visited a proxy site. Here are some examples: + proxy + proxies + glype + atproxy.net + proxy.org +You may extend this list as you find more sites you want to flag. Note however that all the domains containing the word <*proxy*> should get caught automatically if the keyword <*proxy*> is added. + +You will probably have to inform your accountability partner(s) what the related warnings mean and why it matters that proxy sites are reported. + +!!!Reports -- Problems + +!!Why aren't my reports being sent? +This could be for a variety of reasons. See the [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports Troubleshooting the Reports]] guide. + +!!Why am I not receiving reports? +This could be for a variety of reasons. See the [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports Troubleshooting the Reports]] guide. + +!!How do I send a test report/email? +This can be done by opening a terminal window and running the following command as root (for Ubuntu users, this means adding <*sudo*> and a space before the command): + net-responsibility -tr +Note that a test report is simply a brief email that is sent out to test NR's ability to send out email reports and to see whether they will get caught in a spam filter; it is not meant to contain a report of your internet activity. + +!!Why are my reports empty (i.e. only showing titles)? +This could happen if you have not done any internet browsing since the last time a report was sent. Otherwise, it's possible that the internet monitoring part of the NR program is not working properly. See [[http://netresponsibility.com/documentation.php?id=0309-TroubleshootingInstallation this guide]] for instructions on how to test whether NR is running properly. + +!!Why don't my reports work right? +If you are a NR user or accountability partner who is having trouble with NR's reports, you may find a solution in the [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports Troubleshooting the Reports]] guide. + +!!!Reports -- Timing, Characteristics, Etc. + +!!How often are reports sent out? +The default is every 7th day, but this can be changed by the user in their online settings at the time of registration. It can also be changed anytime after that by the user logging in to the website to edit his configuration settings. + +!!Is there a way to set up NR so that my reports will include a complete list of website addresses (URLs) visited? +Yes. To do this, go to the [[http://www.netresponsibility.com NR website]], log in, click on the tab with your username on it, click on 'Report parts', and select 'Complete history' in the 'Attached report' section. Then click on 'Log out,' enter the security code, and click on 'Save and log out' in order to save the changes to your settings. The next time a report is sent out, it should include an attached file that contains a complete list of URLs visited. You may also find it helpful to read through the [[http://netresponsibility.com/documentation.php?id=0705-UnderstandingReports Understanding the Reports]] guide and the [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports Troubleshooting the Reports]] guide. + +!!Can I specify what time of the day reports are sent out? +No, not in your online configuration settings. However, you can use a task-scheduling package like [[https://help.ubuntu.com/community/CronHowto cron]] to do it. The command to use in <*cron*> to send reports is <*net-responsibility --report*> and you need to make sure <*cron*> has root privileges. You will also need to set the report frequency to '0' in your online configuration settings to prevent Net Responsibility from sending out reports automatically. + +!!Is it possible to send out more than one report a day? +No, not with your regular online configuration settings. However, you can use a task-scheduling package like [[https://help.ubuntu.com/community/CronHowto cron]] to do it. The command to use in <*cron*> to send reports is <*net-responsibility --report*> and you need to make sure <*cron*> has root privileges. You will also need to set the report frequency to '0' in your online configuration settings to prevent Net Responsibility from sending out reports automatically. + +!!If I use the 'tokenmatch' option, what is the expected time that it should take to generate a report, and what should it be without using it? +There is no definite answer to this, as it depends on your internet activity, your report frequency settings, and other variables. Versions of NR later than 2.0.2 are definitely faster in generating reports. If you use the internet at a fairly steady pace, you could try one setting for one report and then try another setting for the next report (for the same amount of days), and see if there was any notable difference. + +!!!Terminal Window, Commands, and Output + +!!When I see the line "Other instance found" followed by the line "Shutting net-responsibility down" in the output, does this mean there is a problem with NR? +Even though this output sounds negative, this is what it means: "There is an instance of Net Responsibility that is already up and running, so this instance can safely quit, letting the running instance do its job." This normally means that NR is working as it should. + +!!What does the output line "Downloading configuration file" mean? +Each NR user's specific configuration settings are stored online based on the settings they chose when they registered and any changes they made since then. This output line means that NR is downloading your configuration settings from the server, in case there were any changes made since the last time it downloaded it. These settings will then inform NR how it should run on your computer. + +!!How do I use the terminal to move into a specific directory/folder? +Once you know the path of the folder you want to move to, you can use the <*cd*> command to go there. So, if you want to move to the folder <*/my/big/folder*> you can use the following command: + cd /my/big/folder +Assuming you are now in <*/my/big/folder*> but you want to move up one folder to <*/my/big*> you can use the following command: + cd .. +Whatever folder you are in, if you want to go back to your 'root' folder (i.e. where you are when you first open the terminal), you can use the following command: + cd ~ + +!!How do I run a command with 'root' privileges in Ubuntu? +To run a command with 'root' privileges in Ubuntu, you need to add <*sudo*> and a space to the front of the command. So if you wanted to run the command <*net-responsibility -c*> in order to manually download your NR configuration file, then the full command would look like this: + sudo net-responsibility -c +When you do this, it will normally require you to enter your Ubuntu username and password, unless you did that fairly recently with another command using <*sudo*>. Modified: documentation/pages/0902-HowToGetHelp.page =================================================================== --- documentation/pages/0902-HowToGetHelp.page 2012-05-15 01:34:40 UTC (rev 307) +++ documentation/pages/0902-HowToGetHelp.page 2012-05-15 01:37:29 UTC (rev 308) @@ -2,11 +2,42 @@ A09NR_FurtherReading !!!What kind of problem is it? +Whether you are trying to solve a problem yourself, or whether you are asking for someone else's help, it is best to first collect as many relevant details as possible. These will include the following: + - The operating system and version you are using (i.e. Ubuntu 10.10). + - The version of Net Responsibility (NR) you are using. + - Any error messages you think may be related to your problem, even if they don't make sense to you. + - Specific details of any problems you had in trying to follow instructions (i.e. from the forum, documentation, etc.). For instance, where in the process did you run into the problem? What were you trying to do? What happened as a result? Save a copy of any text output or error message you received. Or if something doesn't make sense, note exactly what it was that you didn't understand and any related questions that would help to clarify things for you. + - Any other information that you feel might be relevant. +Depending on the kind of problem you're facing, it may be able to be solved by: + - You! :-) (via Google or another search engine, or the NR documentation) + - Other end-users (via the forum or mailing lists). + - NR developers (via the forum, mailing lists, bug tracker, or feature requests). + - Nobody, at present. (Developing the software takes a lot of time and energy, and there are limitations in regards to what NR can do and what platforms it can run on. However, knowing about these types of problems people are facing helps us to know how we can improve NR in the future.) + +!!!Self help +Even if you think you don't know much about computers, or programming, or the particular problem you are facing, you would be surprised at the number of problems that you will be able to solve yourself. Take the time to make a reasonable effort to find information on your own before asking for help. A good place to start is the [[http://netresponsibility.com/documentation.php NR documentation]] (where you're at now), and the [[http://www.netresponsibility.com/forum/ NR forum]] is also a good place to browse for ideas. If you are new to the computer system you are using, there are often helpful guides and tutorials online that can be accessed by a simple search with Google, Bing, or your favorite search engine. Using part or all of an error message to do an online search can also bring up some potential solutions. + +If you have tried figuring things out yourself and are coming up short, then it is time to ask others for help. If you do ask us or other users for help, please be patient and respectful. We know it can be frustrating to have unresolved problems with software you are counting on, but remember that anyone who is helping you is volunteering their time and may not be able to reply as quickly as you would like. We will do our best to help you, and also appreciate any help you can give towards improving NR. + !!!Documentation +We have made an attempt to include basic information for both NR users and their accountability partners in our [[http://netresponsibility.com/documentation.php documentation]] (where you're at now). This includes an introduction to the program for those who are considering it, instructions on installing and configuring NR, understanding NR's reports, a FAQ section, and other useful information. When you have a question or problem, you should always check here first. If there's information you feel would be helpful to include in the documentation, or parts of it you feel are incorrect or confusing, please [[mailto:res...@li... let us know]]. +!!!Forum +The [[http://www.netresponsibility.com/forum/ NR forum]] contains various categories, including "General Discussion," "Installation and Configuration," "Accountability Partners," and "Development". You can browse through the threads in each of these categories to see if anyone has had a similar question or problem, whether it is an ongoing issue, or whether a solution was discovered. If you log in to the website (with the username and password you created when you registered as an NR user), you can post a reply to an existing topic or start a new topic in order to ask others for help. If you do request help, make sure you include all the relevant details about your problem. <!Note:!> If you have a definite bug to report or want to submit a feature request, please see the "Bug tracker and Feature requests" section below for the best way to handle these. + +!!!Mailing lists +If you prefer to use email to ask for help, you can contact the NR developers at their mailing list address: [[mailto:res...@li... res...@li...]]. If you do request help in this way, make sure you include all the relevant details about your problem. Also, when replying to an email on this list, please observe the following guidelines: + - All your replies should be sent to res...@li.... + - Remove everything from the email you're replying to, except for parts that you're answering or responding to in particular. + - Your response should be placed right after the part you're referring to. + - Don't change the subject. (This helps keep all related messages in the same 'thread' for later reference.) + !!!Bug tracker and Feature requests +If your problem turns out to be a problem with the NR software itself (the NR developers can help you to identify this), then this is considered a <*bug*>. The best way to work towards getting this bug fixed is to enter it in the [[http://sourceforge.net/p/responsibility/bugs/ NR bug tracker]]. Please try to be as specific as possible, and include <*the version of your NR installation*> and <*what platform/system and version (i.e. Ubuntu 10.10) you're running*>. If you manage to install the software, but not to get it running properly, please try to run it with this command, and paste the output in your bug report (Ubuntu users need to add <*sudo*> before the command) : -!!!Forum + net-responsibility --debug -!!!Mailing lists +If there are features you'd like to see in Net Responsibility, please let us know. We're constantly working toward implementing and stabilizing more features and your requests are valuable. Some of you might have experience with other accountability software, or simply have some stunning ideas that we could've never come up with on our own. Think outside the box. + +Please remember that it may take time for us to implement a requested feature, and if you want it more quickly, you may be interested in working on it yourself. Even then, please [[http://sourceforge.net/p/responsibility/feature-requests/ add it as a feature request]]. Try to be as specific as possible: What do you want to see implemented? What is the difference from what you're seeing now and what you would like to see? Are you able to illustrate the end product? Do you have a proposal of how to get there? This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-15 01:34:46
|
Revision: 307 http://responsibility.svn.sourceforge.net/responsibility/?rev=307&view=rev Author: dustsource Date: 2012-05-15 01:34:40 +0000 (Tue, 15 May 2012) Log Message: ----------- Added the following images for 'Showcase' documentation: --Attached report (AttRpt.png) --Email to mailing list (Email.png) --Email report, part 2 (part 1 committed earlier) (EmlRpt2.png) --Forum page (Forum.png) --Menu path for terminal (MenuTerm.png) --Package manager window (PkgMngr.png) --Terminal (Term.png) --Registration page (WebReg.png) Added Paths: ----------- documentation/resources/images/AttRpt.png documentation/resources/images/Email.png documentation/resources/images/EmlRpt2.png documentation/resources/images/Forum.png documentation/resources/images/MenuTerm.png documentation/resources/images/PkgMngr.png documentation/resources/images/Term.png documentation/resources/images/WebReg.png Added: documentation/resources/images/AttRpt.png =================================================================== (Binary files differ) Property changes on: documentation/resources/images/AttRpt.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: documentation/resources/images/Email.png =================================================================== (Binary files differ) Property changes on: documentation/resources/images/Email.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: documentation/resources/images/EmlRpt2.png =================================================================== (Binary files differ) Property changes on: documentation/resources/images/EmlRpt2.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: documentation/resources/images/Forum.png =================================================================== (Binary files differ) Property changes on: documentation/resources/images/Forum.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: documentation/resources/images/MenuTerm.png =================================================================== (Binary files differ) Property changes on: documentation/resources/images/MenuTerm.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: documentation/resources/images/PkgMngr.png =================================================================== (Binary files differ) Property changes on: documentation/resources/images/PkgMngr.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: documentation/resources/images/Term.png =================================================================== (Binary files differ) Property changes on: documentation/resources/images/Term.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: documentation/resources/images/WebReg.png =================================================================== (Binary files differ) Property changes on: documentation/resources/images/WebReg.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-14 16:11:42
|
Revision: 306 http://responsibility.svn.sourceforge.net/responsibility/?rev=306&view=rev Author: dustsource Date: 2012-05-14 16:11:31 +0000 (Mon, 14 May 2012) Log Message: ----------- EmlRpt1.png image for 'Showcase' documentation; testing document generation. Added Paths: ----------- documentation/resources/images/EmlRpt1.png Added: documentation/resources/images/EmlRpt1.png =================================================================== (Binary files differ) Property changes on: documentation/resources/images/EmlRpt1.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <rog...@us...> - 2012-05-13 22:28:13
|
Revision: 305 http://responsibility.svn.sourceforge.net/responsibility/?rev=305&view=rev Author: roggan87 Date: 2012-05-13 22:28:06 +0000 (Sun, 13 May 2012) Log Message: ----------- Edited some links in web.txt to markdown syntax. Also note the reference link style to make use of the same links more than once. I left some links in HTML, but they'll probably be removed soon enough. Modified Paths: -------------- documentation/web.txt Modified: documentation/web.txt =================================================================== --- documentation/web.txt 2012-05-13 14:21:50 UTC (rev 304) +++ documentation/web.txt 2012-05-13 22:28:06 UTC (rev 305) @@ -2,13 +2,41 @@ This file is parsed by www.netresponsibility.com to extract information to display on various pages. Everything here is written with Markdown syntax and -will be parsed accordingly. Note that the header names are used to locate the -different texts, do not change them! +will be parsed accordingly. +*Please note:* + + - The header names are used to locate the different texts, do not change them! + - Partial links starts with a slash for the root folder + - Full links starting with http:// or similiar are opened in new windows + - You may use the reference links for simplicity + ---> +#reference_links# + [Download]: /download.php + [Forum]: /forum/ + [Register]: /register.php + + [Documentation]: /documentation.php + [Compile from source]: /documentation.php?id=0305-CompileFromSource + [Privacy Policy]: /documentation.php?id=0910-PrivacyPolicy + [Dev Docs]: http://www.netresponsibility.com/dev/docs + + [Bug tracker]: http://sourceforge.net/p/responsibility/bugs/ + [Feature request]: http://sourceforge.net/p/responsibility/feature-requests/ + + [NR-devel]: <mailto:res...@li...> + + [RegExp Editor]: javascript:regexp_editor(); + + [Open Source]: http://en.wikipedia.org/wiki/Open_source + + + + #activate# Hi {name}! @@ -19,7 +47,9 @@ #config_attached_report_parts# -The attached report is new since 2.0a2; read more about it <a href="http://netresponsibility.com/documentation.php?id=0705-UnderstandingReports#7" target="_blank">here</a>. Including it is strongly recommended. +The attached report is new since 2.0a2; read more about it +[here](http://netresponsibility.com/documentation.php?id=0705-UnderstandingReports#7). +Including it is strongly recommended. The different parts are the same as in the usual report, except for the history. @@ -136,8 +166,7 @@ These keywords are used as regular expressions. You can read more about this <a href="article.php?id=105" target="_blank">here</a>. It is highly -recommended to use the <a href="javascript:regexp_editor();">Regexp -Editor</a>. Read more about how to use it <a href="article.php?id=109" +recommended to use the [Regexp Editor][]. Read more about how to use it <a href="article.php?id=109" target="_blank">here</a>. If you already have a list you want to add, you can copy and paste it in the @@ -236,8 +265,7 @@ These keywords are used as regular expressions. You can read more about this <a href="article.php?id=105" target="_blank">here</a>. It is highly -recommended to use the <a href="javascript:regexp_editor();">Regexp -Editor</a>. Read more about how to use it +recommended to use the [Regexp Editor][]. Read more about how to use it <a href="article.php?id=109" target="_blank">here</a>. Note that only the hostname will be matched against the whitelist. @@ -271,7 +299,7 @@ yaourt -S net-responsibility -Otherwise, simply follow <a href="http://netresponsibility.com/documentation.php?id=0304-InstallFromPackages#5" target="_blank">these instructions</a>. +Otherwise, simply follow [these instructions](http://netresponsibility.com/documentation.php?id=0304-InstallFromPackages#5). @@ -279,7 +307,7 @@ **Note:** If you have version 2.0.2 or earlier installed, you will need to uninstall it before installing a later version. The older versions are named *netresponsibility* (without a dash), whereas the newer ones are named *net-responsibility* (with a dash). -If your Debian-based distribution supports downloading and installing from the Ubuntu PPA, see the 'Ubuntu' section for instructions on how to add the NR PPA to your system. Otherwise, follow <a href="http://netresponsibility.com/documentation.php?id=0304-InstallFromPackages#6" target="_blank">these instructions</a>. +If your Debian-based distribution supports downloading and installing from the Ubuntu PPA, see the 'Ubuntu' section for instructions on how to add the NR PPA to your system. Otherwise, follow [these instructions](http://netresponsibility.com/documentation.php?id=0304-InstallFromPackages#6). @@ -345,22 +373,21 @@ #download_Source# -To download and install Net Responsibility from the source code, see <a href="http://netresponsibility.com/documentation.php?id=0305-CompileFromSource" target="_blank">these instructions</a>. +To download and install Net Responsibility from the source code, see [these instructions][Compile from source]. #download_Start# -Before downloading and installing, you'll need to <a href="register.php" -target="_self">register an account</a>. Once that's done, simply choose the +Before downloading and installing, you'll need to +[register an account][Register]. Once that's done, simply choose the OS (operating system) you want to download Net Responsibility for. Our ambition is to supply binary packages (installation files) for as many platforms as possible. If there is none for your platform, you'll need to download and compile the <a href="#Source" target="_self">source code</a>. If you would be interested in creating such packages for any -platform, please <a href="mailto:res...@li..." -target="_blank">let us know</a>. +platform, please [let us know][NR-devel]. Older versions are provided but not recommended. <a href="download.php#Older" target="_blank">You may find them here</a>. @@ -410,7 +437,7 @@ You can make changes in your configuration here. The changes will be reported to your accountability partner(s). -Before using the <a href="javascript:regexp_editor();">Regexp Editor</a>, or +Before using the [Regexp Editor][], or editing the personal black/whitelist, please read <a href="article.php?id=105" target="_blank">Suggested Regexp Syntax</a>. You also might want to read <a href="article.php?id=109" target="_blank">this @@ -436,8 +463,7 @@ This forum is the place to look for help and discuss Net Responsibility. If, for some reason, you want to get in contact with us another way, you may -also send an email to <a -href="mailto:co...@ne...">co...@ne...</a>. +also send an email to <co...@ne...>. @@ -451,9 +477,7 @@ #login# In order to change your configuration or post anything in the forum you'll -have to log in. Do so here. Please report any bugs at the Net Responsibility -Launchpad page <a href="https://bugs.launchpad.net/netresponsibility" -target="_blank">here</a>. +have to log in. Do so here. <a href="forgot_password.php">Forgot your password?</a> @@ -485,8 +509,7 @@ #mail_info# This report was generated by Net Responsibility. -For more information visit -<a href="http://www.netresponsibility.com/">www.netresponsibility.com</a>. +For more information visit <http://www.netresponsibility.com>. Please do not reply to this address (re...@ne...). @@ -505,16 +528,17 @@ ------------------- -If you don't want these newsletters you can simply <a href="login.php">log -in</a> as usual and uncheck the box called "Send me newsletters" in the -"Tweaks" section of your configuration settings. +If you don't want these newsletters you can simply +[log in](http://www.netresponsibility.com/login.php) as usual and uncheck the +box called "Send me newsletters" in the "Tweaks" section of your configuration +settings. #privacy_policy# -The Privacy Policy has been moved to our main documentation. You can <a -href="http://netresponsibility.com/documentation.php?id=0910-PrivacyPolicy" target="_blank">find it here</a>. +The Privacy Policy has been moved to our main documentation. You can find it +[here][Privacy Policy]. #repair_reports# @@ -535,19 +559,16 @@ **Net Responsibility is an accountability software** for Linux and Mac OS X. It monitors the sites you visit on the internet, and sends e-mail reports to -one or more accountability partners that you choose. It is <a -href="http://en.wikipedia.org/wiki/Open_source" target="_blank">open -source</a> and released under the GNU GPL license. +one or more accountability partners that you choose. It is [open +source][] and released under the GNU GPL license. **Version 3.0 is released.** We encourage all users to use this version instead -of the older ones based on Ruby and Python. Simply go to the <a -href="download.php" target="_self">download page</a> for instructions on download and installation on various platforms. Release notes are <a -href="http://downloads.sourceforge.net/project/responsibility/net-responsibili -ty/3.0/readme?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fresponsibility%2Ffil -es%2Fnet-responsibility%2F3.0%2F&ts=1328442933&use_mirror=garr" -target="_blank">found here</a>. +of the older ones based on Ruby and Python. Simply go to the +[download page][Download] for instructions on download and installation on +various platforms. Release notes are +[found here](http://downloads.sourceforge.net/project/responsibility/net-responsibility/3.0/readme). -**Further help** and documentation is found in <a href="forum/" target="_self">the forum</a>. +**Further help** and documentation is found in the [forum][]. @@ -556,4 +577,4 @@ Hi! This is a testmail from Net Responsibility. For more information please -visit <a href='http://www.netresponsibility.com'>www.netresponsibility.com</a>. +visit <http://www.netresponsibility.com>. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-13 14:21:56
|
Revision: 304 http://responsibility.svn.sourceforge.net/responsibility/?rev=304&view=rev Author: dustsource Date: 2012-05-13 14:21:50 +0000 (Sun, 13 May 2012) Log Message: ----------- Fixed 'feature request' link and made various minor edits in "Contribute to Net Responsibility" guide. Modified Paths: -------------- documentation/pages/0903-ContributeToNR.page Modified: documentation/pages/0903-ContributeToNR.page =================================================================== --- documentation/pages/0903-ContributeToNR.page 2012-05-13 02:53:45 UTC (rev 303) +++ documentation/pages/0903-ContributeToNR.page 2012-05-13 14:21:50 UTC (rev 304) @@ -28,7 +28,7 @@ Please try to be as specific as possible, and include <*the version of your installation*> and <*what platform you're running*>. If you manage to install the software, but not to get it running properly, please try to run it with this -command, and paste the output in your bug report (Ubuntu users need to add sudo +command, and paste the output in your bug report (Ubuntu users need to add <*sudo*> before the command) : net-responsibility --debug @@ -37,19 +37,9 @@ !!Feature requests -If there's features you're missing in Net Responsibility, please let us know. -We're constantly working toward implementing and stabilizing more features and -your requests are valuable. Some of you might have experience of other -accountability software, or simply have some stunning ideas that we could've -never come up with. Think outside the box. +If there are features you'd like to see in Net Responsibility, please let us know. We're constantly working toward implementing and stabilizing more features and your requests are valuable. Some of you might have experience with other accountability software, or simply have some stunning ideas that we could've never come up with on our own. Think outside the box. -Please remember that it may take time for us to implement your feature, and if -you want it quick, you may be interested in looking at it yourself. Even then, -please [[http://sourceforge.net/p/responsibility/feature-requests/ -add it as a feature request]]. Try to be as specific as possible, what do you -want to see implemented, and what's the difference from the result you're -seeing now? Are you able to illustrate the goal? Do you have any proposal of -how to get there? +Please remember that it may take time for us to implement a requested feature, and if you want it more quickly, you may be interested in working on it yourself. Even then, please [[http://sourceforge.net/p/responsibility/feature-requests/ add it as a feature request]]. Try to be as specific as possible: What do you want to see implemented? What is the difference from what you're seeing now and what you would like to see? Are you able to illustrate the end product? Do you have a proposal of how to get there? !!Forum @@ -58,62 +48,60 @@ [[http://www.netresponsibility.com/forum/ the forum]]. -!!!Keep updated +!!!Stay updated -Whether you're actively involved in developing Net Responsibility or not, you -would do much by being kept updated. This way you'll more easily be able to -come with relevant suggestions, patches, bug reports etc. +Whether you're actively involved in developing Net Responsibility or not, it would help a lot for you +to stay updated. This way you'll more easily be able to +give relevant suggestions, patches, bug reports, etc. !!Mailing lists <*res...@li...*>. This list will be used for all major discussion about Net Responsibility development. Before making definite decisions, we'll post them to the -mailing list so everyone can have their word about it. Note that you don't +mailing list so everyone can have their say about it. Note that you don't have to be an active contributor to the project to be a subscriber of this -mailing list. By subscribing, you will be able to follow the process anyway, -and maybe come with other opinions from time to time. +mailing list. By subscribing, you will be able to follow the process, +and possibly express your opinions and ideas from time to time. [[https://lists.sourceforge.net/lists/listinfo/responsibility-devel Subscribe here]]. <*res...@li...*>. -Whenever someone is making a commit to our SVN repository, a "commit mail" -will be sent to this list. It'll include the log message and the diff. This -is also an excellent way to keep updated and see what changes are made to -the code. It's also helping us spot bugs or come with alternative -suggestions faster. Even if you don't understand the diffs, you'll be able +Whenever someone makes a <*commit*> to our SVN repository, a "commit email" +will be sent to this list. It'll include the log message and the <*diff*>. This +is also an excellent way to stay updated and see what changes are made to +the code. It can also help us to spot bugs or come up with alternative +suggestions faster. Even if you don't understand the <*diffs*>, you'll be able to follow the log messages, and by doing so understand what changes/bug -fixes are implemented in the code. +fixes have been implemented in the code. [[https://lists.sourceforge.net/lists/listinfo/responsibility-commit Subscribe here]]. !!Running the latest versions By using the latest versions of Net Responsibility, you'll be more in sync -with the developers, and therefore have more relevant information to come -with. Also, you'll help us spot bugs that may slip into new versions. Ubuntu +with the developers, and therefore have more relevant information to provide. Also, you'll be able to help us spot bugs that may slip into new versions. Ubuntu users with the PPA added will automatically run the latest stable release. -Before releasing versions we're trying to test them in a beta stage. -Whenever it's time for beta testing, will announce it on the devel mailing -list. The more people that's willing to bug test the beta releases, the more +Before releasing new versions we try to test them in a beta stage. +Whenever we're ready for beta testing, we'll announce it on the devel mailing +list. The more people that are willing to bug test the beta releases, the more stable software we'll be able to produce. !!!Improve documentation You can help us a lot by improving the documentation. No coding skills are -needed. More information are to be [[5004-Documentation.html found here]]. +needed. More information can be [[5004-Documentation.html found here]]. !!!Code contributions -Since Net Responsibility is free and open source, anyone is able to +Since Net Responsibility is free and open source, anyone can contribute with their programming skills. Read the -[[5001-GettingStarted.html getting started guide]] to get going with the +[[5001-GettingStarted.html getting started guide]] to find out how to begin coding. !!!Create packages -For many users the existence of precompiled packages are the difference -between staying with or leaving the project. Struggling through compilation -without any knowledge about it may frustrate anyone. Therefore there is a -huge need to have working packages/install files. You may engage in creating -such, please read more details in [[5006-CreatingPackages.html this guide]]. +For many users the availability of precompiled packages means the difference +between staying with Net Responsibility or moving on to another solution. Struggling through compilation +without any knowledge about it can frustrate anyone. Thus there is a +huge need to have user-friendly and working packages/install files. If you're interested in helping with this, you can find out more details in [[5006-CreatingPackages.html this guide]]. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-13 02:53:51
|
Revision: 303 http://responsibility.svn.sourceforge.net/responsibility/?rev=303&view=rev Author: dustsource Date: 2012-05-13 02:53:45 +0000 (Sun, 13 May 2012) Log Message: ----------- Minor cosmetic edits to website texts. Modified Paths: -------------- documentation/web.txt Modified: documentation/web.txt =================================================================== --- documentation/web.txt 2012-05-11 23:28:18 UTC (rev 302) +++ documentation/web.txt 2012-05-13 02:53:45 UTC (rev 303) @@ -368,8 +368,8 @@ #download_Ubuntu# -***Note:** *If you have version 2.0.2 or earlier installed, you will need -to uninstall it before installing a later version. The older versions are +**Note:** If you have version 2.0.2 or earlier installed, you will need +to uninstall it before installing a later version. The older versions are named *netresponsibility* (without a dash), whereas the newer ones are named *net-responsibility* (with a dash). This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-11 23:28:24
|
Revision: 302 http://responsibility.svn.sourceforge.net/responsibility/?rev=302&view=rev Author: dustsource Date: 2012-05-11 23:28:18 +0000 (Fri, 11 May 2012) Log Message: ----------- Updated and edited some web texts. Modified Paths: -------------- documentation/web.txt Modified: documentation/web.txt =================================================================== --- documentation/web.txt 2012-05-11 09:53:27 UTC (rev 301) +++ documentation/web.txt 2012-05-11 23:28:18 UTC (rev 302) @@ -19,9 +19,7 @@ #config_attached_report_parts# -The attached report is new since 2.0a2; read more about it <a -href="help.php#118" target="_blank">here</a>. Including it is strongly -recommended. +The attached report is new since 2.0a2; read more about it <a href="http://netresponsibility.com/documentation.php?id=0705-UnderstandingReports#7" target="_blank">here</a>. Including it is strongly recommended. The different parts are the same as in the usual report, except for the history. @@ -38,7 +36,7 @@ #config_blacklist_categories# These blacklists are full of keywords. If any of these words are found in -your visited sites, it will show up as a warning in the report. Choose which +the website addresses (URLs) your computer has accessed, it will show up as a warning in the report. Choose which categories you want to use. @@ -47,8 +45,8 @@ Depending on your internet activity and how often your reports are sent, the attached reports might become big. If you check this box Net Responsibility -will zip the file before sending it. This means the receiver will have to -unzip the report every time, but it also saves space on his/her email account. +will zip (compress) the file before sending it. This means the receiver will have to +unzip (decompress) the report every time, but it also saves space in their email account. The file usually decreases to 10-20% of the original size when zipped. @@ -65,7 +63,7 @@ #config_email_to# -Enter the email address(es) you want reports sent to here. +Enter the email address(es) to which you want reports sent here. @@ -81,7 +79,7 @@ Since version 2.0.1 you can enable instant reports. That means your accountability partner gets a report instantly when Net Responsibility -thinks you're watching inappropriate content. Here you can set the +thinks you're looking at inappropriate content. Here you can set the sensitivity. 0 means the feature is disabled. Otherwise the lower number means higher sensitivity. @@ -112,8 +110,8 @@ #config_newsletter# Check this box if you want the latest information about new versions, how to -help and other stuff that might be of interest. These letters are not sent -on a regular basis, but rather when there's a need to update our users with +help and other information that might be of interest. These letters are not sent +on a regular basis, but rather whenever there's a need to update our users with fresh information. @@ -151,14 +149,14 @@ Enter the number of days you want between the emailed reports. If set to zero, the automatic reports will be disabled, and you'll have to send -reports manually. (Or by using cron.) +reports manually. (Or by using the task-scheduler package *cron*.) #config_report_parts_hostnames# -This part will show all the visited hostnames, providing an overview of the -websites you've visited. +This part will show all the hostnames, providing an overview of the +websites your computer accessed. @@ -172,20 +170,20 @@ #config_report_parts_paths# By checking this box, you will include a part that displays the full paths -to all visited websites. +to all websites your computer accessed. #config_report_parts_shutdowns# -Net Responsibility records if it's shutdown manually or interrupted. Check +Net Responsibility records if it is shutdown manually or interrupted. Check this box to include the shutdowns in the report. #config_report_parts_warnings# -The *warnings* part of the report lists the visited websites that contain +The *Warnings* part of the report lists the website addresses (URLs) that contain one or more words from the blacklists. They could be inappropriate websites, but that is not always the case. Therefore, your accountability partner(s) should always double-check them, either by clicking the link or by reading @@ -220,7 +218,7 @@ #config_tokenmatch# -Using tokenmatch increases the report creation time because it's more +Using *tokenmatch* increases the report creation time because it's more complicated, but it results in much more accurate reports. If you're having problems with reports taking too long to create you might want to exclude it. @@ -238,7 +236,8 @@ These keywords are used as regular expressions. You can read more about this <a href="article.php?id=105" target="_blank">here</a>. It is highly -recommended to use the <a>Regexp Editor</a>. Read more about how to use it +recommended to use the <a href="javascript:regexp_editor();">Regexp +Editor</a>. Read more about how to use it <a href="article.php?id=109" target="_blank">here</a>. Note that only the hostname will be matched against the whitelist. @@ -267,56 +266,26 @@ #download_Arch_Linux# -**If <a href="http://archlinux.fr/yaourt-en" target="_blank">yaourt</a> is -installed** you just run the following command: +If <a href="http://archlinux.fr/yaourt-en" target="_blank">yaourt</a> is +installed you can download and install Net Responsibility by running the following command: yaourt -S net-responsibility -**Otherwise** simply follow these instructions: +Otherwise, simply follow <a href="http://netresponsibility.com/documentation.php?id=0304-InstallFromPackages#5" target="_blank">these instructions</a>. - - Download the package <a href="https://aur.archlinux.org/packages/ne/net-responsibility/net-responsibility.tar.gz" target="_blank">here</a> - - Extract it - - Open a terminal and cd to the extracted folder - - Run `makepkg -s` - - Run `*"**sudo pacman -U ./net-responsibility-3.0.1-3**-[ i386 or x86_64 ]**.pkg.tar.xz**"` -*(Note that you'll need to replace the [bracketed] portion of the above -command with either i386 or x86_64 in order to specify what your system's -architecture is.)* -**For more information** regarding installation of packages in Arch Linux, -<a href="https://wiki.archlinux.org/index.php/AUR#Installing_packages" -target="_blank">look here</a>. - - - #download_Debian# -**Note:** You'll need to uninstall any installed version prior to 2.0.2. -Those packages are named netresponsibility, without the dash. +**Note:** If you have version 2.0.2 or earlier installed, you will need to uninstall it before installing a later version. The older versions are named *netresponsibility* (without a dash), whereas the newer ones are named *net-responsibility* (with a dash). -**Some Debian-based** distributions do not support installing from the -Ubuntu PPA. In this case, you may try to install <a -href="https://sourceforge.net/projects/responsibility/files/net-responsibility -/" target="_blank">our debian packages</a> manually. Note that you'll need -to install libpoco, version 1.4 or later, first. If your distro does not -have libpoco precompiled, you can download <a -href="https://sourceforge.net/projects/responsibility/files/libpoco/" -target="_blank">all packages here</a>. +If your Debian-based distribution supports downloading and installing from the Ubuntu PPA, see the 'Ubuntu' section for instructions on how to add the NR PPA to your system. Otherwise, follow <a href="http://netresponsibility.com/documentation.php?id=0304-InstallFromPackages#6" target="_blank">these instructions</a>. -**When installing**, you'll have to install the libpoco packages first, in -the correct order. After that is done, you can install net-responsibility. -You should be able to use your favorite package manager, or the command line -tool <a href="http://en.wikipedia.org/wiki/Dpkg" target="_blank">dpkg</a>. -**During the last step**, you need to enter username and password. Simply -use the same as you did when registering your account. - - #download_Mac_OSX# -**We're working on** creating packages for Mac users. It is technically +We're working on creating packages for Mac users. It is technically possible to download the <a href="#Source" target="_self">source code</a> and compile it. More information about compiling on Mac can be <a href="forum/index.php?topic=63.0" target="_self">found here</a>. However, @@ -358,7 +327,7 @@ instructions below. - If you downloaded the .deb file, follow the respective installation procedures for your distribution. - - If you downloaded the source tarball (file ending in '.tar.gz'), extract it and follow the directions in the README file. + - If you downloaded the source tarball (archived file ending in '.tar.gz'), extract it and follow the directions in the README file. - <a href="help.php#28">Click here</a> for more detailed installation instructions. **Net Responsibility 2.0 Configuration** @@ -376,64 +345,24 @@ #download_Source# -First you need to install the **Poco libraries**, version 1.4 or later. -Some platforms have these libraries precompiled and packaged. Otherwise, -you need to compile them yourself. Start by <a -href="http://sourceforge.net/projects/poco/files/sources/poco-1.4.2/poco-1.4.2 -p1-all.tar.gz/download" target="_blank">downloading the complete -edition</a>. Unpack it and open a terminal window. Use the *cd* command to -go to the directory to which you unpacked the Poco files. Once you're there, -you will need to configure, compile and install the Poco libraries. The -procedure should look like this: +To download and install Net Responsibility from the source code, see <a href="http://netresponsibility.com/documentation.php?id=0305-CompileFromSource" target="_blank">these instructions</a>. - cd poco-1.4.2p1-all #Or whatever folder you've used - ./configure --shared --no-tests --no-samples - make - sudo make install #Change sudo to "su;" if not Ubuntu/Debian user -Once you've installed the Poco libs, **you also need libpcap**. Many -systems either have it installed by default, or provide packages for -libpcap. Your system may already have a libpcap package installed, but if -your system also provides a libpcap-dev package, you need to make sure that -is installed as well. -**Now finally**, it's time to compile Net Responsibility itself. Download -and unpack the <a -href="https://sourceforge.net/projects/responsibility/files/latest/download" -target="_blank">tarball</a>. - -In your terminal, configure, compile and install like this: - - tar -xvf net-responsibility-3.0.tar.gz - cd net-responsibility-3.0 - ./configure - make - sudo make install #Change sudo to "su;" if not Ubuntu/Debian user - -In the last step you will also be prompted to type your username and -password, if it's the first time you install. - -**If you got this far** Net Responsibility should be installed. When running -`ps -ef|grep net-responsibility` you should get an output line similar to -`net-responsibility --daemon`. - - - #download_Start# -**Before downloading**, you'll need to <a href="register.php" +Before downloading and installing, you'll need to <a href="register.php" target="_self">register an account</a>. Once that's done, simply choose the OS (operating system) you want to download Net Responsibility for. -**Our ambition** is to supply binary packages (installation files) for as +Our ambition is to supply binary packages (installation files) for as many platforms as possible. If there is none for your platform, you'll need to download and compile the <a href="#Source" target="_self">source code</a>. If you would be interested in creating such packages for any platform, please <a href="mailto:res...@li..." -target="_blank">let us know</a><a href="forum/index.php?topic=51.0" -target="_self"></a>. +target="_blank">let us know</a>. -**Older versions** are provided but not recommended. <a href="download.php#Older" target="_blank">You may find them here</a>. +Older versions are provided but not recommended. <a href="download.php#Older" target="_blank">You may find them here</a>. @@ -451,10 +380,10 @@ sudo apt-get update sudo apt-get install net-responsibility -**During the last step**, you need to enter username and password. Simply +During the last step, you need to enter username and password. Simply use the same as you did when registering your account. -**This could also** be done through your favorite package manager, such as +This could also be done through your favorite package manager, such as Synaptic. If you dare, you could change *roggan87/nr* to *roggan87/nrdev*. Then you will also get notified of new beta versions that are not tested by a wider range of people. @@ -504,7 +433,7 @@ #forum_contact# -**This forum is the place** to look for help and discuss Net Responsibility. +This forum is the place to look for help and discuss Net Responsibility. If, for some reason, you want to get in contact with us another way, you may also send an email to <a @@ -584,8 +513,8 @@ #privacy_policy# -The Privacy Policy have moved to our main documentation. Found here: -<http://netresponsibility.com/documentation.php?id=0910-PrivacyPolicy> +The Privacy Policy has been moved to our main documentation. You can <a +href="http://netresponsibility.com/documentation.php?id=0910-PrivacyPolicy" target="_blank">find it here</a>. #repair_reports# @@ -598,7 +527,7 @@ This is not working for 100% of broken reports, but it might be worth a try. -**Note:** The report has to be smaller than 12mb. +**Note:** The report has to be smaller than 12 MB. @@ -610,17 +539,15 @@ href="http://en.wikipedia.org/wiki/Open_source" target="_blank">open source</a> and released under the GNU GPL license. -**Version 3.0 is released.** We encourage all users to use that one instead +**Version 3.0 is released.** We encourage all users to use this version instead of the older ones based on Ruby and Python. Simply go to the <a -href="download.php" target="_self">download page</a> to find installation -instructions. Release notes are <a +href="download.php" target="_self">download page</a> for instructions on download and installation on various platforms. Release notes are <a href="http://downloads.sourceforge.net/project/responsibility/net-responsibili ty/3.0/readme?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fresponsibility%2Ffil es%2Fnet-responsibility%2F3.0%2F&ts=1328442933&use_mirror=garr" target="_blank">found here</a>. -**Further help** and documentation is found in -<a href="forum/" target="_self">the forum</a>. +**Further help** and documentation is found in <a href="forum/" target="_self">the forum</a>. @@ -629,4 +556,4 @@ Hi! This is a testmail from Net Responsibility. For more information please -visit <a href='http://www.netresponsibility.com'>www.netresponsibility.com</a> +visit <a href='http://www.netresponsibility.com'>www.netresponsibility.com</a>. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <rog...@us...> - 2012-05-11 09:53:37
|
Revision: 301 http://responsibility.svn.sourceforge.net/responsibility/?rev=301&view=rev Author: roggan87 Date: 2012-05-11 09:53:27 +0000 (Fri, 11 May 2012) Log Message: ----------- Added web.txt, which stores all web texts. This file is written in Markdown and parsed by http://www.netresponsibility.com/dev/update_docs.php?web_texts Now updating and commiting patches even for the website will be easier. Added Paths: ----------- documentation/web.txt Added: documentation/web.txt =================================================================== --- documentation/web.txt (rev 0) +++ documentation/web.txt 2012-05-11 09:53:27 UTC (rev 301) @@ -0,0 +1,632 @@ +<!--- + +This file is parsed by www.netresponsibility.com to extract information to +display on various pages. Everything here is written with Markdown syntax and +will be parsed accordingly. Note that the header names are used to locate the +different texts, do not change them! + +---> + + + +#activate# + +Hi {name}! + +Please enter your password to activate your account. + + + +#config_attached_report_parts# + +The attached report is new since 2.0a2; read more about it <a +href="help.php#118" target="_blank">here</a>. Including it is strongly +recommended. + +The different parts are the same as in the usual report, except for the history. + + + +#config_attached_report_parts_history# + +Here you decide how much of the history you want to attach. Either all of +it, or only the hostnames, or nothing. Note that everything will be searched +through for a blacklist match independent of what you choose here. + + + +#config_blacklist_categories# + +These blacklists are full of keywords. If any of these words are found in +your visited sites, it will show up as a warning in the report. Choose which +categories you want to use. + + + +#config_compress_attached_report# + +Depending on your internet activity and how often your reports are sent, the +attached reports might become big. If you check this box Net Responsibility +will zip the file before sending it. This means the receiver will have to +unzip the report every time, but it also saves space on his/her email account. + +The file usually decreases to 10-20% of the original size when zipped. + +If the report is larger than 10MB it will be zipped automatically. + + + +#config_email_from# + +Type your email address here. You will use this email to activate your +account, but the reports will be sent from report@ netresponsibility.com. + + + +#config_email_to# + +Enter the email address(es) you want reports sent to here. + + + +#config_improve_data# + +Use this option if you'd like to help us with the development. Net +Responsibility will **anonymously** send your warnings to our server and +store them there. This will help us see how to improve the blacklists. + + + +#config_instant_threshold# + +Since version 2.0.1 you can enable instant reports. That means your +accountability partner gets a report instantly when Net Responsibility +thinks you're watching inappropriate content. Here you can set the +sensitivity. 0 means the feature is disabled. Otherwise the lower number +means higher sensitivity. + +0 = Disabled +1-5 = Very sensitive +6-20 = Medium +21+ = Low sensitivity + + + +#config_logfile_pidfile# + +The location of the logfile and pidfile must be specified; otherwise, Net +Responsibility will refuse to start. + +**WARNING:** Don't change these unless you know what you're doing! + + + +#config_name# + +What is your name? At a minimum, Net Responsibility uses your name when +sending reports. You can also use an alias, as long as your accountability +partner knows who it is. + + + +#config_newsletter# + +Check this box if you want the latest information about new versions, how to +help and other stuff that might be of interest. These letters are not sent +on a regular basis, but rather when there's a need to update our users with +fresh information. + + + +#config_password# + +This is your password. It is saved on this website only, and is used to +verify your user identity. + + + +#config_password2# + +This has to be the same as the password entered above. It is only to +doublecheck that you've entered the password you intended. + + + +#config_personal_blacklist# + +Here you can add keywords to your personal blacklist. + +These keywords are used as regular expressions. You can read more about this +<a href="article.php?id=105" target="_blank">here</a>. It is highly +recommended to use the <a href="javascript:regexp_editor();">Regexp +Editor</a>. Read more about how to use it <a href="article.php?id=109" +target="_blank">here</a>. + +If you already have a list you want to add, you can copy and paste it in the +field. It will be split at every line break. + + + +#config_report_frequency# + +Enter the number of days you want between the emailed reports. If set to +zero, the automatic reports will be disabled, and you'll have to send +reports manually. (Or by using cron.) + + + +#config_report_parts_hostnames# + +This part will show all the visited hostnames, providing an overview of the +websites you've visited. + + + +#config_report_parts_info# + +Check this box if you want to include a short introductory message at the +beginning of the report. + + + +#config_report_parts_paths# + +By checking this box, you will include a part that displays the full paths +to all visited websites. + + + +#config_report_parts_shutdowns# + +Net Responsibility records if it's shutdown manually or interrupted. Check +this box to include the shutdowns in the report. + + + +#config_report_parts_warnings# + +The *warnings* part of the report lists the visited websites that contain +one or more words from the blacklists. They could be inappropriate websites, +but that is not always the case. Therefore, your accountability partner(s) +should always double-check them, either by clicking the link or by reading +the match in its context. It is strongly recommended to have this box checked! + + + +#config_report_parts_whitelist# + +If a website contains a blacklisted word, but *also* a whitelisted word, it +will be found in this part of the report. This way you will be able to tell +Net Responsibility that some websites are okay. + + + +#config_report_strength_threshold# + +Only matches with a strength higher than this number will be included in the +reports. That way you're able to set some sort of sensitivity for what to +display. This setting only applies to Net Responsibility 3.0 and later. + + + +#config_security_code# + +Please enter the letters shown in the box above this field. The reason is to +confirm that you're a real human person. + +Simply click the box above to generate a new security code. + + + +#config_tokenmatch# + +Using tokenmatch increases the report creation time because it's more +complicated, but it results in much more accurate reports. If you're having +problems with reports taking too long to create you might want to exclude it. + + + +#config_username# + +This is your login name. Choose a name that's easy to remember. + + + +#config_whitelist# + +Here you can add keywords to your whitelist. + +These keywords are used as regular expressions. You can read more about this +<a href="article.php?id=105" target="_blank">here</a>. It is highly +recommended to use the <a>Regexp Editor</a>. Read more about how to use it +<a href="article.php?id=109" target="_blank">here</a>. + +Note that only the hostname will be matched against the whitelist. + +If you already have a list you want to add, you can copy and paste it in the +field. It will be split at every line break. + + + +#contact# + +Make sure you've checked out our <a href="help.php">help section</a> first. + +**Note:** If you want us to get back to you personally, please include your +email address. + + + +#delete_account# + +Your account is now deleted. Your accountability partners have been informed +about this, but you should contact them and tell them the reason why you +deleted your account. + + + +#download_Arch_Linux# + +**If <a href="http://archlinux.fr/yaourt-en" target="_blank">yaourt</a> is +installed** you just run the following command: + + yaourt -S net-responsibility + +**Otherwise** simply follow these instructions: + + - Download the package <a href="https://aur.archlinux.org/packages/ne/net-responsibility/net-responsibility.tar.gz" target="_blank">here</a> + - Extract it + - Open a terminal and cd to the extracted folder + - Run `makepkg -s` + - Run `*"**sudo pacman -U ./net-responsibility-3.0.1-3**-[ i386 or x86_64 ]**.pkg.tar.xz**"` + +*(Note that you'll need to replace the [bracketed] portion of the above +command with either i386 or x86_64 in order to specify what your system's +architecture is.)* + +**For more information** regarding installation of packages in Arch Linux, +<a href="https://wiki.archlinux.org/index.php/AUR#Installing_packages" +target="_blank">look here</a>. + + + +#download_Debian# + +**Note:** You'll need to uninstall any installed version prior to 2.0.2. +Those packages are named netresponsibility, without the dash. + +**Some Debian-based** distributions do not support installing from the +Ubuntu PPA. In this case, you may try to install <a +href="https://sourceforge.net/projects/responsibility/files/net-responsibility +/" target="_blank">our debian packages</a> manually. Note that you'll need +to install libpoco, version 1.4 or later, first. If your distro does not +have libpoco precompiled, you can download <a +href="https://sourceforge.net/projects/responsibility/files/libpoco/" +target="_blank">all packages here</a>. + +**When installing**, you'll have to install the libpoco packages first, in +the correct order. After that is done, you can install net-responsibility. +You should be able to use your favorite package manager, or the command line +tool <a href="http://en.wikipedia.org/wiki/Dpkg" target="_blank">dpkg</a>. + +**During the last step**, you need to enter username and password. Simply +use the same as you did when registering your account. + + + +#download_Mac_OSX# + +**We're working on** creating packages for Mac users. It is technically +possible to download the <a href="#Source" target="_self">source code</a> +and compile it. More information about compiling on Mac can be <a +href="forum/index.php?topic=63.0" target="_self">found here</a>. However, +the easiest thing would be to wait (or help us out with creating the package). + + + +#download_Older# + +**NOTE: These packages are not officially supported, and we recommend +installing version 3.0 or later. However, these packages are provided in +case anyone is interested in using them.** + +Stable (Beta) Version: + + - <a href="files/netresponsibility-2.0.deb" target="_blank">netresponsibility-2.0.deb</a> (213 KB) + - <a href="files/netresponsibility-2.0.amd64.deb" target="_blank">netresponsibility-2.0.amd64.deb</a> (213 KB) + - <a href="files/net-responsibility-2.0.tar.gz" target="_blank">net-responsibility-2.0.tar.gz</a> (Source code) (131 KB) + +Unstable (Alpha) Version: + + - <a href="files/netresponsibility-2.0.2.deb" target="_blank">netresponsibility-2.0.2.deb</a> (221 KB) + - <a href="files/netresponsibility-2.0.2.amd64.deb" target="_blank">netresponsibility-2.0.2.amd64.deb</a> (221 KB) + - <a href="files/net-responsibility-2.0.2.tar.gz" target="_blank">net-responsibility-2.0.2.tar.gz</a> (Source code) (138 KB) + +Which file you download depends on your distribution. If you are running a +Debian or <a +href="http://en.wikipedia.org/wiki/List_of_Linux_distributions#Debian-based" +target="_blank">Debian-based</a> Linux distribution (such as Ubuntu), then +you need the .deb file. If you're using another Linux distribution, then you +can download the source code and follow the instructions below. + +New to Linux/Ubuntu? Start <a href="help.php#29">here</a>. + +**Net Responsibility Installation** + +To install versions 2.0 or later, you have to register an account <a +href="register.php">here</a> first. Once you've done that, simply follow the +instructions below. + + - If you downloaded the .deb file, follow the respective installation procedures for your distribution. + - If you downloaded the source tarball (file ending in '.tar.gz'), extract it and follow the directions in the README file. + - <a href="help.php#28">Click here</a> for more detailed installation instructions. + +**Net Responsibility 2.0 Configuration** + +To configure the program's settings so it will begin monitoring and +reporting internet usage, you can do either of the following: + + - Click on the menu item Applications > Internet > Configure + Net Responsibility. + - Enter `net-responsibility-config-gui` in the terminal. + - <a href="help.php#114" target="_self">Click here</a> for + more detailed configuration instructions. + + + +#download_Source# + +First you need to install the **Poco libraries**, version 1.4 or later. +Some platforms have these libraries precompiled and packaged. Otherwise, +you need to compile them yourself. Start by <a +href="http://sourceforge.net/projects/poco/files/sources/poco-1.4.2/poco-1.4.2 +p1-all.tar.gz/download" target="_blank">downloading the complete +edition</a>. Unpack it and open a terminal window. Use the *cd* command to +go to the directory to which you unpacked the Poco files. Once you're there, +you will need to configure, compile and install the Poco libraries. The +procedure should look like this: + + cd poco-1.4.2p1-all #Or whatever folder you've used + ./configure --shared --no-tests --no-samples + make + sudo make install #Change sudo to "su;" if not Ubuntu/Debian user + +Once you've installed the Poco libs, **you also need libpcap**. Many +systems either have it installed by default, or provide packages for +libpcap. Your system may already have a libpcap package installed, but if +your system also provides a libpcap-dev package, you need to make sure that +is installed as well. + +**Now finally**, it's time to compile Net Responsibility itself. Download +and unpack the <a +href="https://sourceforge.net/projects/responsibility/files/latest/download" +target="_blank">tarball</a>. + +In your terminal, configure, compile and install like this: + + tar -xvf net-responsibility-3.0.tar.gz + cd net-responsibility-3.0 + ./configure + make + sudo make install #Change sudo to "su;" if not Ubuntu/Debian user + +In the last step you will also be prompted to type your username and +password, if it's the first time you install. + +**If you got this far** Net Responsibility should be installed. When running +`ps -ef|grep net-responsibility` you should get an output line similar to +`net-responsibility --daemon`. + + + +#download_Start# + +**Before downloading**, you'll need to <a href="register.php" +target="_self">register an account</a>. Once that's done, simply choose the +OS (operating system) you want to download Net Responsibility for. + +**Our ambition** is to supply binary packages (installation files) for as +many platforms as possible. If there is none for your platform, you'll need +to download and compile the <a href="#Source" target="_self">source +code</a>. If you would be interested in creating such packages for any +platform, please <a href="mailto:res...@li..." +target="_blank">let us know</a><a href="forum/index.php?topic=51.0" +target="_self"></a>. + +**Older versions** are provided but not recommended. <a href="download.php#Older" target="_blank">You may find them here</a>. + + + +#download_Ubuntu# + +***Note:** *If you have version 2.0.2 or earlier installed, you will need +to uninstall it before installing a later version. The older versions are +named *netresponsibility* (without a dash), whereas the newer ones are named +*net-responsibility* (with a dash). + +There is a PPA (Personal Package Archive) for Ubuntu users. To add the PPA +and install the latest version, simply type these commands in a terminal: + + sudo add-apt-repository ppa:roggan87/nr + sudo apt-get update + sudo apt-get install net-responsibility + +**During the last step**, you need to enter username and password. Simply +use the same as you did when registering your account. + +**This could also** be done through your favorite package manager, such as +Synaptic. If you dare, you could change *roggan87/nr* to *roggan87/nrdev*. +Then you will also get notified of new beta versions that are not tested by +a wider range of people. + + + +#download_Windows# + +Our goal is to supply Net Responsibility for all major platforms, including +Windows. At the moment there are still some important features that are not +implemented in the Windows version. Therefore we've decided to wait before +we release it. Once those things are fixed, we'll create an installation +file and post it here. + +If you're interested in following the Windows development process, you can +stay updated through <a href="forum/index.php?topic=55.0">this thread</a>. +If you want to receive email notifications when a new post is made to this +thread, first log in, go to the thread, and then click the "Notify" button. + + + +#edit_config# + +You can make changes in your configuration here. The changes will be +reported to your accountability partner(s). + +Before using the <a href="javascript:regexp_editor();">Regexp Editor</a>, or +editing the personal black/whitelist, please read <a +href="article.php?id=105" target="_blank">Suggested Regexp Syntax</a>. You +also might want to read <a href="article.php?id=109" target="_blank">this +documentation</a> on the Regexp Editor. + + + +#email_notification# + +ro...@ho..., rog...@gm..., du...@gm..., rob...@gm... + + + +#forgot_password# + +Simply type your username or email address in the field below, and you'll +receive an email with your password. + + + +#forum_contact# + +**This forum is the place** to look for help and discuss Net Responsibility. + +If, for some reason, you want to get in contact with us another way, you may +also send an email to <a +href="mailto:co...@ne...">co...@ne...</a>. + + + +#help# + +If you don't find an answer here, or if you want to report a bug or feature +request, please <a href="contact.php">contact us</a>. + + + +#login# + +In order to change your configuration or post anything in the forum you'll +have to log in. Do so here. Please report any bugs at the Net Responsibility +Launchpad page <a href="https://bugs.launchpad.net/netresponsibility" +target="_blank">here</a>. + +<a href="forgot_password.php">Forgot your password?</a> + + + +#mail_activate# + +Hi {name}, and welcome to Net Responsibility! + +You need to activate your account before you can start using the program. +All you need to do is click the following link. (In some email programs you +may have to copy the link and paste it in your browser. It is case-sensitive.) + +http://www.netresponsibility.com/activate.php?username={user}&confirm={activate} + + + +#mail_forgot_password# + +Hi {name}! + +Your Net Responsibility login: + +Username: {user} +Password: {password} + + + +#mail_info# + +This report was generated by Net Responsibility. +For more information visit +<a href="http://www.netresponsibility.com/">www.netresponsibility.com</a>. + +Please do not reply to this address (re...@ne...). + + + +#mail_omitted_partner# + +Your friend, {name}, has configured Net Responsibility to use another +account. That means you will no longer receive reports from him/her. This +may be an attempt to bypass the software. + + + +#newsletter_footer# + + +------------------- + +If you don't want these newsletters you can simply <a href="login.php">log +in</a> as usual and uncheck the box called "Send me newsletters" in the +"Tweaks" section of your configuration settings. + + + +#privacy_policy# + +The Privacy Policy have moved to our main documentation. Found here: +<http://netresponsibility.com/documentation.php?id=0910-PrivacyPolicy> + + +#repair_reports# + +Here you can try to repair 'broken' reports. It is mainly done by removing +unwanted newlines and escaping single quotes. Unless you know what is wrong +with your report, we suggest doing both. Simply upload your broken report +and let us take care of the rest. Both compressed and uncompressed (htm- and +zip-files) can potentially be repaired. + +This is not working for 100% of broken reports, but it might be worth a try. + +**Note:** The report has to be smaller than 12mb. + + + +#start# + +**Net Responsibility is an accountability software** for Linux and Mac OS X. +It monitors the sites you visit on the internet, and sends e-mail reports to +one or more accountability partners that you choose. It is <a +href="http://en.wikipedia.org/wiki/Open_source" target="_blank">open +source</a> and released under the GNU GPL license. + +**Version 3.0 is released.** We encourage all users to use that one instead +of the older ones based on Ruby and Python. Simply go to the <a +href="download.php" target="_self">download page</a> to find installation +instructions. Release notes are <a +href="http://downloads.sourceforge.net/project/responsibility/net-responsibili +ty/3.0/readme?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fresponsibility%2Ffil +es%2Fnet-responsibility%2F3.0%2F&ts=1328442933&use_mirror=garr" +target="_blank">found here</a>. + +**Further help** and documentation is found in +<a href="forum/" target="_self">the forum</a>. + + + +#testmail# + +Hi! + +This is a testmail from Net Responsibility. For more information please +visit <a href='http://www.netresponsibility.com'>www.netresponsibility.com</a> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-11 07:12:40
|
Revision: 300 http://responsibility.svn.sourceforge.net/responsibility/?rev=300&view=rev Author: dustsource Date: 2012-05-11 07:12:29 +0000 (Fri, 11 May 2012) Log Message: ----------- Expanded guides related to accountability partners. Modified Paths: -------------- documentation/doc/net-responsibility-3.0.2-doc.zip Modified: documentation/doc/net-responsibility-3.0.2-doc.zip =================================================================== (Binary files differ) This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-11 06:34:43
|
Revision: 299 http://responsibility.svn.sourceforge.net/responsibility/?rev=299&view=rev Author: dustsource Date: 2012-05-11 06:34:36 +0000 (Fri, 11 May 2012) Log Message: ----------- Expanded guides related to accountability partners. Modified Paths: -------------- documentation/doc/net-responsibility-3.0.2-doc.zip Modified: documentation/doc/net-responsibility-3.0.2-doc.zip =================================================================== (Binary files differ) This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-11 05:05:55
|
Revision: 298 http://responsibility.svn.sourceforge.net/responsibility/?rev=298&view=rev Author: dustsource Date: 2012-05-11 05:05:49 +0000 (Fri, 11 May 2012) Log Message: ----------- Expanded "Troubleshooting the Reports" guide. Modified Paths: -------------- documentation/pages/0709-TroubleshootingReports.page Modified: documentation/pages/0709-TroubleshootingReports.page =================================================================== --- documentation/pages/0709-TroubleshootingReports.page 2012-05-11 03:25:21 UTC (rev 297) +++ documentation/pages/0709-TroubleshootingReports.page 2012-05-11 05:05:49 UTC (rev 298) @@ -1,2 +1,18 @@ Troubleshooting the reports A07NR_ForAP + +!!!Why am I not receiving a report? +Assuming that any necessary internet connections are working, the following are possible reasons why someone did not receive a Net Responsibility (NR) report that they were expecting: + - The user has not successfully registered, installed, and/or configured the NR program. + - There is a bug in the NR program. + - The user did not enter the expected email address during the registration process, or did not save their settings. + - The email containing the report was considered spam by the email server or email client, and was automatically quarantined, or directed to a Spam/Junk/Trash folder. + +For the first three reasons, the user will need to make sure any problems are resolved. The first and third reasons can be looked at by testing the NR program, checking online settings, and making sure NR has been configured after any changes to online settings. The second reason can be looked at by examining any errors generated by the NR program and/or contacting the developers or other users via the NR website or the forum mentioned on the main page. For the third reason it would also be good to check that the intended email address is correct. For the fourth reason, the person receiving the email will need to figure out a solution. If an accountability partner (AP) is not receiving a report they were expecting, they should first try to make sure it is not for the fourth reason, and then they should contact the user and request them to check out the first three reasons. Please note that, even if reports have been coming through without a problem before, it is still possible that they may begin to be treated as spam. However, most email servers and email clients have a way to 'train' their spam filters or 'whitelist' certain 'From' addresses, which should keep this from becoming a problem. + +!!!Why doesn't the attached report work right? +For an introduction to the attached report, see the [[http://netresponsibility.com/documentation.php?id=0705-UnderstandingReports Understanding the Reports]] guide. Following are some reasons why an attached report might not be functioning as it should: + - If the attached file is a ZIP file, the computer may not have software installed to 'unzip' or extract it. Try downloading it to a location outside of your web browser and email client. If you have the necessary software installed, you may be able to right-click on the ZIP file and choose 'Extract', 'Extract here', or something similar, which should result in an HTML file being created that you can then view with your web browser. If you don't see this option when you right-click, you may need to download and install 'archive manager' software in order to extract it. + - If the attached file is an HTML file (these usually have an .htm or .html extension), the most likely problem is that your web browser or email client does not have JavaScript enabled. If this is the case, then you will see a message informing you of this. It is recommended that you save the attached file somewhere outside of your web browser or email client, and then try to open it with your web browser. If you get the same message, then JavaScript is not working correctly in your browser. Make sure that JavaScript is both installed AND enabled in your browser, remembering that with some browsers it is possible that the settings may have JavaScript 'enabled' even if it's not actually installed. Also note that Java and JavaScript are two different things, even though they share the same name. To check if JavaScript is currently enabled in the browser you're using, you can try this [[http://www.isjavascriptenabled.com/ JavaScript Test]] website. + - If you are able to open the attached file in your web browser and see the report, but certain parts of the tree structure are missing or not working properly, then JavaScript is working correctly in your browser, but you have probably opened it from within your webmail account (in your web browser) or your email client. For security purposes some email servers and email clients will 'strip' certain parts of an attachment (like parts of a JavaScript script) when it is opened. In order for the report to work properly, the attached file should be saved somewhere outside of the web browser or email client, and then opened from that location. + - The attached report may be 'broken' because of some problems in its code (such as the appearance of unwanted newlines and single quotes). If this is the case, the usual symptom is that JavaScript will not work at all, meaning that neither the JavaScript tree nor the text message about JavaScript being disabled will be displayed. Improvements to the software are the best long-term solution, but until that happens a temporary workaround is to try to 'repair' the broken report by clicking on [[http://netresponsibility.com/repair.php this link]] and following the instructions there. This is not guaranteed to work in every case, but it is worth trying. Also, note that the report you are trying to repair needs to be smaller than 12 MB. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-11 03:25:27
|
Revision: 297 http://responsibility.svn.sourceforge.net/responsibility/?rev=297&view=rev Author: dustsource Date: 2012-05-11 03:25:21 +0000 (Fri, 11 May 2012) Log Message: ----------- Expanded "Understanding the Reports" guide, and included information about the attached report that had been separate in the old documentation. Modified Paths: -------------- documentation/pages/0705-UnderstandingReports.page Modified: documentation/pages/0705-UnderstandingReports.page =================================================================== --- documentation/pages/0705-UnderstandingReports.page 2012-05-08 12:07:27 UTC (rev 296) +++ documentation/pages/0705-UnderstandingReports.page 2012-05-11 03:25:21 UTC (rev 297) @@ -1,2 +1,41 @@ Understanding the reports A07NR_ForAP + +!!!Introduction +For Net Responsibility (NR) to be as effective as possible, it is important that an accountability partner (AP) understands the reports they receive. When a user registers on the NR website they are able to choose a variety of settings, which will determine how often reports are sent out, as well as their format and content. One format is to have only a basic report included in the email itself, and another is to have an additional more detailed report in a file attached to the email. If there is something you don't understand about a report you received, you should take the time to read this and other relevant guides, ask the NR user, or contact the NR developers, so that you can be an informed and helpful AP. + +!!!Sections of the report +Depending on the NR user's settings, their report will include one or more of the following sections. + +!!Introductory material +At the beginning of the email report, the NR user is identified by the name they used when they registered online, and there is a link to the NR website, where you can find more information or help as needed. There is also a list of any 'suspicious' words or phrases that NR found as it monitored the website addresses (URLs) the user visited. These are set up as internal links, so clicking on them will take you to the 'Warnings' section, where you can see a list of the URLs visited that contained that particular word or phrase. This section is included in the email report only. + +!!Bypasses +This section shows any activity that might indicate an attempt to bypass the NR software, such as manually shutting down the program, changing certain files on the user's computer, etc. If there are any items in this section, it could mean that the user was attempting to bypass the NR software in order to use the internet inappropriately, but it is also possible that it was caused by a problem on their computer, or by them doing some testing of the software. It is best for the AP to check with the user any time there are items listed in this section. This section may be included in both the email report and the attached report. + +!!Warnings +It is strongly recommended that this section be included in the report, since it shows any URLs the user's computer accessed that NR flags as inappropriate. Each item includes a clickable link that can be used to confirm what the web page is, but it is good to be aware that some of these web pages may contain inappropriate content and/or malware that can be harmful to a computer. Each item also includes a color-coded number. The higher this number is, the more likely this item is an actual instance of inappropriate internet use; likewise, the lower this number is, the more likely this item is a false positive. It is possible that false positives will show up in this section, but there are ongoing efforts to improve its accuracy. If an AP sees links here that they think are not false positives, it is best for them to check with the user about them. This section may be included in both the email report and the attached report. + +Note that in this section you may see terms such as 'Porn', 'Pornstars', 'Models', 'Celebrities', 'Pornstars extended', 'Models extended', Celebrities extended', etc. These are just the names of the particular 'blacklist' that contained the word(s) that triggered the warning. Also note that some website addresses in the report may not have actually been visited by the user. For instance, when some websites load, they access other websites in order to load icons or images, possibly for advertisements or for a person's avatar on a forum, etc. A common example is that a user's history of all websites visited might show that they visited the Facebook website multiple times when they actually never did; they simply visited other websites that had loaded one or more images from the Facebook domain. As a result, some items might show up as warnings that might be confusing for both the AP and the user as to why they are there. Normally a closer examination of the URL and its domain will help you and the user determine whether or not the item was generated by a visited website rather than by the user themselves. + +!!Whitelist +This section shows any URLs the user's computer accessed that NR would normally consider inappropriate, but which NR or the user have marked as being okay. Putting something on this list is one way to avoid false positives in the 'Warnings' section. It is best for the AP to at least scan this section to see if there is anything that is actually inappropriate, and to check with the user if necessary. This section may be included in both the email report and the attached report. + +!!History +This section gives a history of the user's internet use by recording the URLs of websites and web pages that their computer has accessed. Hostnames (main website addresses) may be listed, such as 'google.com'. Underneath a hostname other sub-hostnames may be listed, such as 'clients1.google.com' and 'www.google.com'. Under these hostnames and/or sub-hostnames, each individual web page may be listed. This allows the AP to scan just the hostnames, and then look in more detail at the web pages under a particular hostname as desired. If there is no internet history shown or it is not as detailed as the AP desires, they should contact the user so that they can change their configuration settings accordingly. This section is included in the attached report only. + +!!!The attached report +A NR user can choose to have a more detailed version of the report sent with the basic email report as an attached file. This attached report is an HTML file that any JavaScript-enabled web browser should be able to open. This may be an easier way of viewing the report, since it uses a tree structure (similar to some file managers) that enables the AP to easily choose more or less detail as desired. According to its size and/or the NR user's online configuration settings, the report may be compressed and attached as a ZIP file. When the ZIP file is extracted, it will create the HTML file. For best viewing results, an AP should do the following with an attached report: + + - If it is a ZIP file, extract or 'unzip' it, making a note of where the HTML file has been extracted to. (You may first need to save the ZIP file somewhere on your computer outside of the web browser or email client.) + - If it is an HTML file, save it somewhere on the computer outside of the web browser or email client. + - Make sure an installed web browser has JavaScript enabled. + - Go to where the HTML file was extracted or saved, and open it with the JavaScript-enabled web browser. + +If the above steps were successful, the AP should see a web page in their browser that has a few 'Options' links at the top, and the report sections organized as 'branches' in a 'tree' structure under them. An item in the tree that has a '+' sign next to it can be 'expanded' by clicking on the '+' sign. The 'History' section contains the URLs that were accessed by the user's computer. Clicking on the 'Display time' link will cause the time and date to be shown next to each event and each URL that was accessed. Once this link is clicked, the text of the link will change to 'Hide time', which can then be clicked at any time to turn this feature off. Clicking on the 'Expand all nodes' link will completely expand every part of the tree. Depending on how much information is in the report, this may feel somewhat overwhelming, but it is a relatively fast and easy way to show all the information at once. + +!!!Things to remember +Here are a few things for an AP to remember when they are looking at a NR report: + - Things that look suspicious may actually be okay. Everything should be looked at in context and the NR user should be contacted about anything that is not understood. + - When some links in the report are clicked, they will lead to another web page. These links are listed because they are suspicious, so the AP will want to be especially cautious if clicking them. + - For problems related to reports, see the [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports Troubleshooting the Reports]] guide. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <dus...@us...> - 2012-05-08 12:07:38
|
Revision: 296 http://responsibility.svn.sourceforge.net/responsibility/?rev=296&view=rev Author: dustsource Date: 2012-05-08 12:07:27 +0000 (Tue, 08 May 2012) Log Message: ----------- Expanded "Being a Good Accountability Partner" guide. Modified Paths: -------------- documentation/pages/0701-BeingAGoodAP.page Modified: documentation/pages/0701-BeingAGoodAP.page =================================================================== --- documentation/pages/0701-BeingAGoodAP.page 2012-05-05 15:03:50 UTC (rev 295) +++ documentation/pages/0701-BeingAGoodAP.page 2012-05-08 12:07:27 UTC (rev 296) @@ -1,6 +1,19 @@ Being a good Accountability Partner A07NR_ForAP -!!!Get a basic understanding +!!!Introduction +Having one or more good accountability partners (AP) can make the difference between living in defeat or living in victory. The following things are all that is needed for someone to be an effective AP for a Net Responsibility (NR) user: -!!!Follow up reports + - A computer or other device that is able to receive email. An AP can be using any operating system (OS), regardless of the OS of the NR user. + - An email address. When the user registers on the NR website, they will enter this email address so NR knows where to send its report. + - A web browser with JavaScript enabled, (and possibly software to extract ZIP files), if the user chooses to have their report include an attachment. + - Time to briefly look over the reports that are sent. + - A willingness to contact the user if there are concerns about possible inappropriate internet use. + +!!!How does it work? +Once an AP has given their email address to the user and the user has successfully completed registration, installation, and configuration of NR, then reports will be periodically emailed to the AP. To better understand the content of these reports, see [[http://netresponsibility.com/documentation.php?id=0705-UnderstandingReports Understanding the reports]]. For other problems with reports, see [[http://netresponsibility.com/documentation.php?id=0709-TroubleshootingReports Troubleshooting the reports]]. + +!!!Follow up on reports +It is important that you as an AP follow up on anything that you have a question about in a report that you receive. It may turn out that there was actually no inappropriate internet use by the NR user, but they need to know that you are monitoring these reports as they come to you and will approach them if there is anything that raises a question. + +You may also want to check with the NR user to make sure that they are also receiving a copy of their report. They can do this by editing their configuration on the NR website so that their own email address is included as one of the APs that reports are sent to. If they do receive a copy of the report, this will make it easier for you both if you are asking about a particular item, since you will both be able to view the same report. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |