Submitted by: bakank
Posted at: 2012-10-24 13:29:54
See full post and comment: http://9gag.com/gag/5678727

“O que? Já é 8 horas?”

What if we lived in a world where the only available typeface was Comic-Sans? That’s the idea, or at least must have been what the Russian Belgorod-based designer Oleg Tarasov was thinking when he decided to re-design some of the most well know brands of our time using the usually frowned upon Comic-Sans type.

Oleg posted his designs over on his Behance profile. The comments there ranged from the very common “this looks funny” — well, what would we all expect from a font with the word comic in its name, right? — to the surprising positive response praising some of his versions over the originals.

What!? Ouch, I don’t know if I can agree with that, read on to get my views on them, but hey, you be the judge!

Here’s a selection with the best, well, I mean least worst of them. Check them out:

 

Adidas

The global sports Adidas logo and more friendly-looking mark. The type? Well, you know.

 

Android

Surprisingly the tiny little green robot, err, I mean android, looks quite cute.

 

Coca-Cola

Improving Coca-Cola’s logo is a huge challenge in itself, who dares? A quick tip, using Comic-Sans to get there is not the right way of doing it.

 

EA Games

I wouldn’t be surprised if the guys from EA end up using this logo on a real game made for children. Or perhaps they already did, anyone can confirm that?

 

eBay

Here’s something funny, as if the above is not a joke already, but I bet some designers are going to say this version looks better than the official new eBay logo.

 

HTML5

I recall the launch of the HTML5 logo and how people said it didn’t make much sense at all. So, a big red shield with the number 5 in it, guess what? It makes even less sense now.

 

Lacoste

I can’t stop seeing a little green arm and a slighted elevated biceps, perhaps an alligator ate the arm of a fairly strong man.

 

Microsoft

If Microsoft was to launch a tablet made with children in mind, guess how the logo would look? I would go with the logo below; spot on.

 

Harley-Davidson Motorcycles

Tiny little motorcycles made for those rebel toddlers who don’t want to eat their meals on time.

 

Nestle

This comic-sans logo almost got me. Nestle is such an organic brand that this logo doesn’t actually look bad. Ok, I’m not making a case for it, obviously I prefer the original!

 

Nike

Remove the sharp edges and Nike is now an Australian boomerang manufacturer.

 

YouTube

Ahh, this one is easy, a YouTube made for kids, with safe and sound, quality educational videos.

 

Should we all be in favor of this change and live in a world made of happy-looking brands? If you ask me, certainly not, but many have already pursued the comic-sanstification of world renown brands before, such as the French design studio Cephalization — yes, I know, what a name — who are behind the Comics Sans Project, where they receive submissions of comic-sans-based logos from all over the world. Oh God, the agony!

If you haven’t pulled your eyes out yet and want to see a bit more comic-gore, be sure to check more logos over Oleg’s page on Behance and the Comics Sans Project. Good luck!

 

What do you think of multi-billion dollar multinationals adopting Comic-Sans in their logos? Have you ever successfully used Comic-Sans for branding? Let us know in the comments.

10 Cartoon Characters in 400+ poses – only $24!

Source

Aproveitando, se você precisa de uma comparação entre os navegadores…

real historia;
string sender;
sender = "Kennedy Alves";
Cliente: Oi, eu não estou conseguindo acessar o site da empresa…
Programador: O site está normal. Tente usar outro navegador…
Cliente: Tá. Deixa eu ver se eu trouxe…
Programador: PLOFT!
–
Camiseta: The name is Sparrow, Jack Sparrow

Minha vontade é de:

Submitted by: tobovzcrd
Posted at: 2012-10-19 03:32:02
See full post and comment: http://9gag.com/gag/5637315

Submitted by: alsiii
Posted at: 2012-10-18 17:24:55
See full post and comment: http://9gag.com/gag/5633139

Submitted by: aminationeition
Posted at: 2012-10-18 12:00:35
See full post and comment: http://9gag.com/gag/5630940

Submitted by: frankysea
Posted at: 2012-10-17 15:58:21
See full post and comment: http://9gag.com/gag/5628958

Since the advent of the first web search engines, designers and developers have struggled with issues of how to increase their placement on a search engine results page.

With the major search engines (Google, Bing, etc.) unwilling to reveal their ranking algorithms — protecting them from “black hat” search engine optimizers attempting to game the system — “white hat” search engine experts must play a constant guessing game to determine which tactics will be most effective.

The continuing development of technologies, from HTML and XML to JavaScript and Flash, has made the pursuit of prime search engine real estate a massive industry in its own right.

The introduction of HTML5 has simplified many tasks, but adds another layer of complexity in this area.

HTML5 and multimedia

For many years, web designers and developers have used plug-ins such as Adobe Flash and Microsoft Silverlight to add audio, video and graphics content to their projects. These plug-ins have enabled professionals to create glossy, eye-catching designs that have attracted visitors and won numerous awards.

However, these sites have traditionally suffered from poor search engine ranking due to webcrawler’s inability to index this type of content. Great strides were being made in this area just prior to the death of Flash, but to a large degree, investment in the area of plugin indexing has now ceased altogether.

HTML5 allows for indexing multimedia content, such as menus, audio and video, with new markup tags. The content within these tags can improve a site’s search engine ranking. Indeed an HTML5 site consistently ranks higher than the equivalent site built with a plugin; however there is some question as to HTML5′s suitability for all tasks.

Google frequently tells us to build a site for the user, with ‘natural’ content. We may need to wait for HTML6 for that to be possible.

Chess image via Shutterstock

 

HTML5 and link types

In previous years, developers would use the “rel” attribute on their link tags to specify which links that a web crawler should not follow:

<a href="no-follow.htm" rel="nofollow">Don't Follow This Link</a>

In HTML5, new values for the “rel” attribute of the link tag allow us to create a context for a document that, moving forward, should provide greatly improved search results for users:

Alternate allows us to specify alternate content, the same text in PDF format for example, or the same content in a different language.

<link rel="alternate" hreflang="es" href="espanol.html">

Author enables us to link to an author’s profile. This is of great benefit on Google if the author is signed up to Google+.

<link rel="author" href="https://plus.google.com/0123456789">

Bookmark lets blogs link to an article’s permanent URL, helpful if your articles are usually published on a home page.

<a rel="bookmark" href="http://mysite.com/article.html">Permalink</a>

Help is designed to be used by third party apps to provide access to help files. Not much use on a blog page, but invaluable for web-based apps.

<link rel="help" href="helpfiles.html">

License provides a link to licensing information.

<a rel="license" href="licensing.html">License information</a>

Next and Prev are used when a document is part of a series, giving context to the current page.

<a rel="next" href="page-2.html">Next</a>
<a rel="prev" href="page-0.html">Previous</a>

Search provides a link to a resource that can be used to search through the current document and its related pages.

<link rel="search" href="http://www.mysite.com/mysearch.xml">

The full specification for these attribute values can be found on the W3C site.

 

HTML5 and ranking

In late 2010, John Mueller of Google remarked that HTML5 is “still very much a work in progress” and that the company is still working on ways to index HTML5 content. However, the company is making a sincere effort to incorporate the indexing of HTML5 content into its newest generation of web crawlers.

Chimp chess image via Shutterstock

While Google’s relationship with HTML5 standards remains in flux, and while Google remains the focus of most SEO efforts, HTML5′s introduction of new content and ways of describing that content is unlikely to offer any real SERP benefits.

However, the merits of allowing more content to be indexed with less effort is not in dispute, and with HTML5 rapidly becoming the new standard for web design it is just a matter of time before HTML5 sites outrank xHTML sites. Webdesigners should be planning for that future today.

 

Do you take full advantage of HTML5′s extra markup? Have you seen any SEO benefit of coding in HTML5 over xHTML? Let us know in the comments.

Create a Simple Mobile Homepage – only $23!

Source

The Urban Ninja Strikes Again

[via]

nobody

Tweet

One of the main problems with technology is the frequent lapses in security we experience; a lot of information is stolen daily and used to steal more information, send spam messages, open backdoors to systems and sometimes even do damage to our computers.

None of these issues unknown to WordPress, a staggering number of sites have become victims of unpleasant criminals exploiting the community for their own personal gain.

In order for you to beat this threat we’ve put together a roundup of some good tools and tips on how to avoid being the next victim. Or if you’re unlucky enough to already be a victim, how to fight back and fix your installation.

Exploit attacks

You may have heard about it, you may even know the details, but for those who haven’t here’s the problem: an exploit is a piece of malicious code distributed to exploit a weakness in existing code.

TimThumb was susceptible to an attack of this kind; one its functions, which allows users to upload images from different sites and access them freely, stored images in a cache directory so that Timthumb doesn’t have to reprocess them again. This function could be exploited by a hacker uploading files to the server, allowing them access to as many resources from the WordPress installation as they wish.

Exactly the same problem affected Uploadify, a plugin allowing users to upload files. When not properly controlled the plugin allowed hackers free access to the site by uploading PHP scripts to grant access permissions.

 

Maintenance image via Shutterstock.

The problem in these cases, as with the majority of exploit attacks, was not WordPress but rather the plugins themselves. The solution is simple, keep your plugins up to date and report any bugs that you encounter to the developers to help them to patch potential issues.

 

SQL injections

The WordPress installation itself is not immune to problems. Depending on the version, SQL injection can be a major headache. An SQL injection is a process by which an attacker seeks to pass SQL code via a website form or script in the hope that the SQL code will parse ‘correctly’ and retrieve data from the database. That data might be email addresses, but more likely, it would be usernames and passwords that would then give the user more access for other attacks.

The reason SQL attacks can be so irritating is that to combat them you need to frequently backup your database. Preferably at least once per day.

Maintenance image via Shutterstock.

To avoid that, you can try to secure your files using Apache with a code like this in your .htaccess file:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_METHOD} ^(HEAD|TRACE|DELETE|TRACK) [NC]
RewriteRule ^(.*)$ - [F,L]
RewriteCond %{QUERY_STRING} \.\.\/ [NC,OR]
RewriteCond %{QUERY_STRING} boot\.ini [NC,OR]
RewriteCond %{QUERY_STRING} tag\= [NC,OR]
RewriteCond %{QUERY_STRING} ftp\:  [NC,OR]
RewriteCond %{QUERY_STRING} http\:  [NC,OR]
RewriteCond %{QUERY_STRING} https\:  [NC,OR]
RewriteCond %{QUERY_STRING} (\<|%3C).*script.*(\>|%3E) [NC,OR]
RewriteCond %{QUERY_STRING} mosConfig_[a-zA-Z_]{1,21}(=|%3D) [NC,OR]
RewriteCond %{QUERY_STRING} base64_encode.*\(.*\) [NC,OR]
RewriteCond %{QUERY_STRING} ^.*(\[|\]|\(|\)|<|>|ê|"|;|\?|\*|=$).* [NC,OR]
RewriteCond %{QUERY_STRING} ^.*("|'|<|>|\|{||).* [NC,OR]
RewriteCond %{QUERY_STRING} ^.*(%24&x).* [NC,OR]
RewriteCond %{QUERY_STRING} ^.*(%0|%A|%B|%C|%D|%E|%F|127\.0).* [NC,OR]
RewriteCond %{QUERY_STRING} ^.*(globals|encode|localhost|loopback).* [NC,OR]
RewriteCond %{QUERY_STRING} ^.*(request|select|insert|union|declare).* [NC]
RewriteCond %{HTTP_COOKIE} !^.*wordpress_logged_in_.*$
RewriteRule ^(.*)$ - [F,L]
</IfModule>

This will put off an amateur, but a professional hacker will find another security hole to exploit. Fortunately most attacks are perpetrated by newbies or spammers, using scripts like PHP r57 or Shell. Reducing these attacks will greatly reduce the amount of problems you have to deal with.

 

Default user

The biggest security hole in every system is the end user. It doesn’t matter how complex a password you create. In fact the more complex the password, the worse the security risk; because very complex passwords have to be saved somewhere. Users frequently save passwords in .txt or .doc files on their computer and that leaves the system open to phishing attacks using virus files like trojans.

The only safe place to store a password is inside your own head.

However, even if you only ever store your password in your own memory, you’re still not safe from brute-force attacks. A brute force attack will simply attempt to ‘guess’ your password with repeated attempts to log in. It may start with ‘aaaaaa’, proceeding to ‘aaaaab’ and so on until it reaches ’000000′. This process isn’t limited to a single computer, commonly hundreds of machines run through potential passwords looking for access.

One way to handle brute-force attacks is to install a login limiter that will only permit a few login attempts before blocking access for that user for an hour or so. This reduces the number of chances the attacker has to get in. There are several WordPress plugins that can help you with this: Limit Login Attempts, Better WP Security and Login Security Solution.

Finally, pay attention to usernames. The default username for WordPress is ‘Admin’ and if you leave it as such you’re halving the amount of work the hacker needs to do to access your site. If you didn’t change your username while you were installing WordPress do it now. Just log into your account, create a new account with the username you want, give it administrator permissions and then delete the admin account.

Cleanup image via Shutterstock.

 

Direct Access

Another problem our WordPress sites may have is providing direct access to the login page, simplifying the process of hacking your site.

Whilst securing your passwords is the most pressing issue, a malicious user won’t be able to make use of anything they’ve stolen if they can’t find the login page. The simplest solution to this is to use a plugin like Hide Login to obscure the login page’s location.

Certain files in our WordPress installation can also be accessed if not properly secured. We can clear up these loose ends by adding some more rules to our .htaccess file, like so:

Options All -Indexes
<files .htaccess>
Order allow,deny
Deny from all
</files>
<files readme.html>
Order allow,deny
Deny from all
</files>
<files license.txt>
Order allow,deny
Deny from all
</files>
<files install.php>
Order allow,deny
Deny from all
</files>
<files wp-config.php>
Order allow,deny
Deny from all
</files>
<files error_log>
Order allow,deny
Deny from all
</files>
<files fantastico_fileslist.txt>
Order allow,deny
Deny from all
</files>
<files fantversion.php>
Order allow,deny
Deny from all

 

Default prefix

It should be clear that the more information we give our would-be hacker, the easier it is for them to succeed.

The default WordPress table prefix is ‘wp_’. Why would we want to give them that? Let’s change that prefix to something harder to guess, like ‘oijrr58_’ for example, it will make their lives much more difficult, and increase the chances that your site will remain secure.

For new installations, this is a no-brainer because the installation script asks us for a prefix. For older sites you have two options, you can either make the change manually (only attempt this if you have lots of time and are sure you know what you’re doing) or use a plugin like Better WP Security which will take care of it for you.

 

Too late…

It’s never too late. You can always combat hackers, and prevent yourself from becoming a perpetual victim.

If you’re unsure whether your site has been infected there are tools that will tell you. Sucuri SiteCheck for example will scan your site and if you’re infected, will advise you on what steps to take to correct the problem(s).

Hazardous image via Shutterstock.

Basic fixes

Here are some basic steps to take:

• Backup the site and database, hacked or not, you don’t want to lose your content.
• Make copies of items that aren’t in your database, like images.
• Download the latest version of WordPress.
• Ensure all plugins are up to date, check which versions solve known problems.
• Ensure any templates are up to date, check which versions solve known problems.
• Use an FTP client or cPanel to delete everything in the WordPress directory.
• Upload the new files you downloaded.
• Run the database upgrade.
• Change your password, you don’t want to let the hackers straight back in.
• Finally, check every post, correcting any damage that has been done.

Fighting r57 scripts

r57 is a PHP script that gives an attacker a wide range of capabilities, although the attacker has these capabilities, these won’t work until the shell is on our web server, consequently we can prevent it from working using the following commands:

find /var/www/  -name "*".php  -type f -print0  | xargs -0 grep r57 | uniq -c  | sort -u  | cut -d":" -f1  | awk '{print "rm -rf " $2}' | uniq

This command will look for PHP files located on your WWW folder, then within the found files it will look for any mention of r57 in the filename and contents. Then it will delete the infected file(s).

find /var/www/  -name "*".txt  -type f -print0  | xargs -0 grep r57 | uniq -c  | sort -u  | cut -d":" -f1  | awk '{print "rm -rf " $2}' | uniq

This code does the same, except for TXT files instead of .php files.

Note that these codes are for Linux, don’t try them on Windows or MacOS and be aware that they are potentially very destructive as they’ll delete files without asking for permission.

Obscured code

A major cause for concern within themes is obscured code, because malicious code tends to be harder to find within themes. All sorts of damage can be done, from redirecting users to other sites, to sinking your SEO.

A key weapon in fighting this kind of problem is Theme Authenticity Checker. This plugin will not only check code for suspect lines but will detect static links and obscured code like code generated in base64 that is hard to spot by eye.

 

Fool me once, shame on you…

Just because you’ve been caught out in the past, doesn’t mean you have to keep being played.

Consider taking these steps to secure yourself further:

• Only permit PHP where strictly necessary.
• Ensure that your web server does not allow clients to modify the .htacess file.
• Implement a firewall that will restrict the mail outbound in the port 25 to just the root and email server ID.
• Monitor uploads to your site with an application like ConfigServer eXploit Scanner.

Repair image via Shutterstock.

 

Finally

WordPress security is as important as any site security. You must ensure that both you and your users are protected from spam, malware and phishing attacks. But remember that the first line of defence is actually the anti-virus software on your desktop machine.

 

Have you run into problems with WordPress security? How did you solve the issue? Let us know in the comments.

Written exclusively for WDD by The Shock Family: a team of web professionals and creators of  WordPress Themes Shock (Premium wordpress themes), WP Theme Generator (A great wp theme creator), and DesignShock (useful design sets).

19 Premium Facebook Cover Designs – only $15!

Source

 

 

 

Tweet

Como foi produzido antes do final do salto real, o Lego Felix Baumgartner não cai de pé

nope

Submitted by: juventusfan8
Posted at: 2012-10-13 08:59:52
See full post and comment: http://9gag.com/gag/5589989

Submitted by: endorbine
Posted at: 2012-10-12 18:17:19
See full post and comment: http://9gag.com/gag/5588845

Submitted by: ollybird
Posted at: 2012-10-10 17:07:02
See full post and comment: http://9gag.com/gag/5576097

Submitted by: btorun91
Posted at: 2012-10-10 19:39:42
See full post and comment: http://9gag.com/gag/5572354

Submitted by: reneeevanson
Posted at: 2012-10-10 17:51:57
See full post and comment: http://9gag.com/gag/5571513

Submitted by: tinangtang
Posted at: 2012-10-10 03:26:25
See full post and comment: http://9gag.com/gag/5567316