papamike writes:  

I made an error when I posted about my blog. I thought I had the blog theme set as the default, but I had a different theme which destroyed the blog effect. I just now discovered the error and corrected it. Take a look at it now and you'll see the blog as I designed it.

Go Here to see it and leave your mark on my calender.
papamike

matteoiamma writes:  

I report you the most advanced and customizable phpbb3tonuke block! It's compatible with phpbb3tonuke by nukekorea and with the standard bb3 bridge. Last posts from bb3(Title, Authors, Replies, Readings, , Last reply, forum icon/title), good graphic, multi-language, administration panel and settings..etc...

Try a demo here
For download it go here

SECUNIA ADVISORY ID: SA44678

VERIFY ADVISORY: http://secunia.com/advisories/44678/78

CRITICALITY: Highly Critical

RELEASE DATE: 2011-05-26

DESCRIPTION: Some vulnerabilities have been reported in Google Chrome, which can be exploited by malicious people to bypass certain security restrictions and compromise a user's system. The vulnerabilities are reported in versions prior to 11.0.696.71. Read More...

montego writes:  

A new version of ShortLinks (1.3.0) has been release over at Montego Scripts. This release includes a significant core engine change (hence the major release bump). Come see the full article regarding this new release as well as links to the download, documentation and forums. This is our first product release since announcing our RavenNuke™ ONLY support policy.

Southern writes:  

1. Use an SQL Injection Cheat Sheet

This particular tip is just a link to a useful resource with no discussion on how to use it. Studying various permutations of one specific attack can be useful, but your time is better spent learning how to safeguard against it. Additionally, there is much more to Web app security than SQL injection. XSS (Cross-Site Scripting) and CSRF (Cross-Site Request Forgeries), for example, are at least as common and at least as dangerous.

We can provide some much-needed context, but because we don’t want to focus too much on one attack, we’ll first take a step back. Every developer should be familiar with good security practices, and apps should be designed with these practices in mind. A fundamental rule is to never trust data you receive from somewhere else. Another rule is to escape data before you send it somewhere else. Combined, these rules can be simplified to make up a basic tenet of security: filter input, escape output (FIEO). Read More...

Southern writes:  

Enjoy!

1. echo is faster than print.
2. Wrap your string in single quotes (') instead of double quotes (") is faster because PHP searches for variables inside "" and not in '', use this when you're not using variables you need evaluating in your string.
3. Use sprintf instead of variables contained in double quotes, it's about 10x faster.
4. Use echo's multiple parameters (or stacked) instead of string concatenation.
5. Use pre-calculations, set the maximum value for your for-loops before and not in the loop. ie: for ($x=0; $x 6. Unset or null your variables to free memory, especially large arrays.
7. Avoid magic like __get, __set, __autoload.
8. Use require() instead of require_once() where possible.
9. Use full paths in includes and requires, less time spent on resolving the OS paths.
10. require() and include() are identical in every way except require halts if the file is missing. Performance wise there is very little difference.


more with citations: hm2k Internet Engineering