![[at-symbol]](at-symbol-transp.png)
gmx·net
How to block comment spammers without using captchas (spam, bot, proxies)
Spammers usually use proxies to hide their real IP address and to prevent IP blocking. However you can specifically block their proxy servers by using Apache rewrite rules.Are you concerned about this method because your legal visitors might be affected? Don't worry, your visitors probably would use anonymous proxies, but those won't be blocked!
Comment spammers almost always submit through transparent (non-anonymous) proxies. So all you need to do is to add the following rules to the .htaccess file of the affected web directory (or your root directory).
.htaccess code to block transparent proxies:
RewriteEngine on
RewriteCond %{HTTP:FORWARDED-FOR-IP} !^$ [NC,OR]
RewriteCond %{HTTP:FORWARDED-FOR} !^$ [NC,OR]
RewriteCond %{HTTP:FORWARDED} !^$ [NC,OR]
RewriteCond %{HTTP:PC-REMOTE-ADDR} !^$ [NC,OR]
RewriteCond %{HTTP:PROXY-CONNECTION} !^$ [NC,OR]
RewriteCond %{HTTP:HTTP_PROXY_CONNECTION} !^$ [NC,OR]
RewriteCond %{HTTP:USERAGENT-VIA} !^$ [NC,OR]
RewriteCond %{HTTP:VIA} !^$ [NC,OR]
RewriteCond %{HTTP:X-FORWARDED-FOR} !^$ [NC,OR]
RewriteCond %{HTTP:X-FORWARDED} !^$ [NC,OR]
RewriteCond %{HTTP:X-PROXY-CONNECTION} !^$ [NC,OR]
RewriteCond %{HTTP:X-PROXY-CLIENT-IP} !^$ [NC,OR]
RewriteCond %{HTTP:X-BLUECOAT-VIA} !^$ [NC,OR]
RewriteCond %{HTTP:CLIENT-IP} !^$ [NC]
RewriteRule .* - [F,L]
If you test your rules, make sure you test against transparent proxies (non-anonymous) because you most likely find a lot anonymous but rarely the transparent type which is used by spammers.
Also do not forget to take the spammer's reward: Add rel='nofollow' to all links pointing to your forum, guestbook or whatever comment page you are hosting. That page will still get indexed but comment links do no more contribute to Google's page-ranking. The spammer will loose interest.
Original article about htaccess rules by Perishable Press:
http://perishablepress.com/press/2008/04/20/how-to-block-proxy-servers-via-htaccess/
No comments - Edit - Delete
Execution sequence of event-listeners in Firefox 3.5
early...1. scripts associated with XML-bindings in an addon
2. head script tag of website
3. body script tag of website
4. window-eventListener 'DOMContentLoaded' in addon
5. document-eventListener 'DOMContentLoaded' in addon
6. document-eventListener 'load' in addon
7. body tag 'onload' instruction of website
8. window-eventListener 'pageshow' in addon
9. document-eventListener 'pageshow' in addon
...late
As shown above website scripts are executed before addon event-listeners are triggered (except XML bindings which run first).
No comments - Edit - Delete
How to correctly measure Firefox memory consumption
Looking at the task manager usually won't alert you, even if something is going wrong. Most users do not take notice of the really important values since they are not shown by default: In it's default configuration a task manager shows the memory that is currently in use by an application - that's fine, but in many cases this is only a little part of the memory that is really allocated. So the shown usage-value has to be regarded with caution.So what is the difference between memory 'in use' and 'allocated memory'?
Memory in use means the part of memory where current computations are done, it is the most recently used memory area of the application.
On the other side there always is memory that once was allocated by the application but neither was freed nor used since a longer period. So the memory usually is moved away to another area. That is done by a third party, the system memory managment. If this happens, the moved memory is labeled as the application's virtual memory. In some cases it will be swapped to a pagefile.
Moving an amount of used memory to the virtual memory area certainly does not free it. The virtual memory is still part of the application. It definately counts for the applications total memory consumption. To get the real amount of memory allocated by an application it is very important to know that both values, memory usage and virtual memory, need to be added.
Allocation of memory means that the memory cannot be be used by another application until it is freed again. Memory management and virtual memory prevent 'out of memory' errors for a long time, even if your real memory (RAM) is completely exhausted. However, virtual memory does not improve system performance: The downside is, that virtual memory is much slower (factor 1000) than real RAM. So while the virtual memory of an application grows, you probably experience an increasing application slowdown.
Also you cannot see the real memory consumption of an application by just viewing the task manager: As soon as the memory usage of an application excesses a defined point (usually between 50 and 100 MB) the system memory manager will move some memory away to the virtual memory area. The moved memory amount will be subtracted from the 'memory in use' and so you will see a much lower (normal) value here. At the same time the virtual memory grows for exactly the moved amount of memory.
This happens for every application that needs a lot of memory, including Firefox. Luckily every taskmanager provides means to also show the amount of virtual memory of any application. Using the Windows taskmanger you need to configure an extra column to be shown: Virtual memory. It will show the real memory value of an application.
2 Comments - Edit - Delete
Usually my jacket's pocket
is like a black hole. However, grabbing for something I just found a Higgs-particle instead. I think that shouldn't be there ;-)Options: To notify the appropriate research center Click here
No comments - Edit - Delete
Kostenpflichtige Abmahnungen gegen private Homepages
"Seit Jahren bekommen unbedarfte kleine Webmaster und Homepagebesitzer aus heiterem Himmel Abmahnungen mit Gebühren von über 500 Euro bis zu (in Einzelfällen) 10 000 Euro. Die Tendenz ist steigend!
Wie ist das überhaupt möglich?
jeder der etwas im Internet veröffentlicht, also jede Homepage (den Ausdruck 'privat' gibt es im Internetrecht überhaupt nicht), unterliegt automatisch dem Wettbewerbsrecht, und dem neuen Urheberrecht sowieso.
an jedem schöpferischen Produkt, Foto, Grafik, Midi, Text, Zitat besteht ein Urheberrecht. Es gibt im deutschen Recht kein 'Public Domain'! Jeder der also mehr als seinen persönlichen Lebenslauf und Privatfotos veröffentlicht, liefert sich automatisch der Willkür von Rechteinhabern und deren (selbsternannten?) Vertretern aus.
das deutsche Recht erlaubt es, Anwaltsgebühren dem Abgemahnten in Rechnung zu stellen. So kommen mit einem einzigen Verwarnbrief erhebliche Gebühren von 500 Euro aufwärts zustande!
Was kann man tun?
Seit Jahrzehnten schon wird die deutsche Politik und Gesetzgebung im wesentlichen durch Interessenverbände und Lobbies bestimmt. Privatpersonen und kleine Unternehmen haben keine Lobbies. So wundert es wenig, dass sich im Laufe der Jahre im Internet eine Gesetzgebung etablieren konnte, die Interessen und Schutzbedürfniss von Privatpersonen mit Füßen tritt.
Es gilt jetzt
ein Problembewußtsein zu schaffen. Zu informieren und auf Mißstände hinzuweisen. Und zwar nicht in einer Internet-Zeitschrift auf Seite 203, sondern in der großen Öffentlichkeit.
ein Gefühl der Solidarität unter den Webmastern herzustellen. Eine Lobby der kleinen nicht- und semiprofessionellen Homepages. Denn noch sind wir in der Mehrheit. WIR sind das Internet!
Besucht Rettet-das-Internet.de und tragt Euch in unsere Liste ein!"
zitiert aus: Promotionmaterial und Info (http://rettet-das-internet.de/aktion.htm)
No comments - Edit - Delete