-
Anything ‘published’ on the web is viewed as intellectual property and, regardless of whether it displays a copyright symbol or not, is therefore copyrighted by the originator. The only exception to this is if there is a “free and unrestricted reuse” statement associated with the work.
In order to protect our members and TFL from possible litigation, all members must abide by the following new rules:
1. Copying and pasting entire articles from another site to TFL is strictly prohibited. The same applies to articles from print or other media, and to posting photographs taken of copyrighted pages or other media.
2. Copyright law provides for “fair use” of portions of a copyrighted work. You can copy no more than a SINGLE paragraph from the article to your post (3 or 4 sentences at most).
3. You must provide a link to the article along with the name of website. For example: ww.xxx.yyy/zzz (The Lower Thumbsuck Daily News).
4. You must provide, in your own words, a brief summary of the article AND your reasons for believing it will be of interest to TFL members. Failure to do so may result in the thread being closed or your post being deleted as a “cut and paste drive by.”
5. Photographs and other images are also copyrighted. "Hotlinking" of images (so that it appears in your message) from other sites is also prohibited unless you own rights to the image. If you wish to share an image, provide a clickable link to it.
Posts that do not follow these new guidelines will be altered or deleted by staff. Members who continue to violate this policy may lose their posting privileges at TFL.
Thank you for your cooperation and your participation in TFL, the leading online forum for firearms enthusiasts.
Loggin in over and over
- Thread starter Sleuth
- Start date
kingabby:
That's because you are not checking "remember me" when you login.
Failure to check that box means your session expires after 20 minutes (or whatever the timeout on a particular forum is configured to), so when you try to post your reply after that 20 minutes, your session has expired and the forum does not consider you logged in. Since guests can't post, it makes you log in again.
TBH, we should default that "remember me" box to checked.
That's because you are not checking "remember me" when you login.
Failure to check that box means your session expires after 20 minutes (or whatever the timeout on a particular forum is configured to), so when you try to post your reply after that 20 minutes, your session has expired and the forum does not consider you logged in. Since guests can't post, it makes you log in again.
TBH, we should default that "remember me" box to checked.
Assuming you do allow TFL to place a cookie in your system, that is a new one on us. I don't know of any reason other than the ones given here for you to be logged out, or to appear to be logged out, that is. In reality, if you checked off "Remember me", you are still autologged off after 20 minutes of idle time, but you are also autologged in when you return. It should have been transparent to you. Maybe there is a security setting somewhere in your system that is causing it.
re-logging in manually isn't what I'd call dealing with it.
Firefox 4:
Tools menu, pick Options
Privacy tab, pick "remove individual cookies"
search for thefiringline
Chrome:
From the main menu (wrench icon top right to the right of the url bar), pick Options (windows) or Preferences (linux).
On the left pane, pick "Under the Hood"
At the top, pick "Content Settings ..."
Near the top, pick "All cookies and site data"
search for thefiringline
Look at all cookies starting with "bb". The domain for each bb* cookie should be ".thefiringline.com"
If you see any cookies with domain* thefiringline.com (without a leading dot), remove them.
*Do not confuse the "Site" column in Firefox's and Chrome's listings with the domain. In FF the domain is shown near the bottom when you highlight a particular cookie -- you should see "Name:", "Content:", "Domain:" series of values on sequential lines. In Chrome, when you click on a cookie to view, you should see a similar "Name:", "Content:", "Domain:" list of values pop up below the cookie list.
Obviously, if you don't care about having to log in again, you can delete all cookies from thefiringline.com and then the cookie problem should be sorted.
A similar exercise can be applied to any forum site you're having trouble with. You only need to know what domain they set cookies for, and delete any possibly conflicting cookies with different domains. If you visit a site foo.com, the cookies that get sent are foo.com and .foo.com. If you visit a site www.foo.com, the cookies that get sent are www.foo.com and .foo.com
Firefox 4:
Tools menu, pick Options
Privacy tab, pick "remove individual cookies"
search for thefiringline
Chrome:
From the main menu (wrench icon top right to the right of the url bar), pick Options (windows) or Preferences (linux).
On the left pane, pick "Under the Hood"
At the top, pick "Content Settings ..."
Near the top, pick "All cookies and site data"
search for thefiringline
Look at all cookies starting with "bb". The domain for each bb* cookie should be ".thefiringline.com"
If you see any cookies with domain* thefiringline.com (without a leading dot), remove them.
*Do not confuse the "Site" column in Firefox's and Chrome's listings with the domain. In FF the domain is shown near the bottom when you highlight a particular cookie -- you should see "Name:", "Content:", "Domain:" series of values on sequential lines. In Chrome, when you click on a cookie to view, you should see a similar "Name:", "Content:", "Domain:" list of values pop up below the cookie list.
Obviously, if you don't care about having to log in again, you can delete all cookies from thefiringline.com and then the cookie problem should be sorted.
A similar exercise can be applied to any forum site you're having trouble with. You only need to know what domain they set cookies for, and delete any possibly conflicting cookies with different domains. If you visit a site foo.com, the cookies that get sent are foo.com and .foo.com. If you visit a site www.foo.com, the cookies that get sent are www.foo.com and .foo.com
mrgoodwrench76
New member
Using any anit-virus stuff? Sometimes AV software will override windows security settings automatically even after you tell windows to change it. Unless you have requested to be prompted by windows before any such change then you would not be aware.
Evan Thomas
New member
Turning off javascript disables much of the web. If you're worried about rogue js compromising data on important sites like banks or trading sites or even ecommerce sites like amazon, use a separate VM [1], or a separate FF profile [2], or simply use one browser (e.g. Chrome) for "safer" stuff like finances, and another VM/profile/browser (e.g. Firefox) for casual browsing. The safer browser can be loaded up with extensions, for instance -- and most of these are for Firefox -- Disconnect (chrome), Ghostery, Adblock, Noscript, Betterprivacy, HTTPS-Everywhere, Perspectives, and Leechblock (invert the rules, block everything with "*" and allow "+*.bankingsite.com" "+*.tradingsite.com" to prevent accidentally visiting less-safe sites in your "safer" firefox profile, if you don't trust noscript to do the job).
I know you think you're being prudent by disabling javascript globally, but that's a lost cause. If you're that worried about javascript, use VMs so you can use modern sites they way they're designed to be used, while isolating that from your more sensitive browsing.
Also, to echo Vanya, Noscript is great. It also does good things beyond simply blocking scripts, so it's nice to have in any FF profile even if you don't want to block javascript.
[1] Guide to setting up ubuntu inside of virtualbox: http://www.psychocats.net/ubuntu/virtualbox
[2] Guide to using Firefox profiles: http://support.mozilla.com/en-US/kb/Managing profiles (then modify your Firefox start menu or taskbar link or desktop link/shortcut and after the final double quote, add -no-remote -profilemanager ...that will let you easily start a new instance of firefox running a different profile even if another firefox instance is already running.