Slashdot links to a rather unexpected prediction for the time when we are all driven by the robot cars:
“At least one expert is anticipating that, as the so-called ‘smart’ cars get smarter, there will eventually be an increase in an unusual form of distracted driving: hanky-panky behind the wheel.”
28 Ways to Secure WordPress Website covers, as the title says, quite a few ways to make your WordPress website more secure. There is no absolute security, and there are always more that you can do, but this is a good start. Apart from all the useful advice, the article also tells you why you should care:
“Why would anyone hack my site?” – you ask
Let’s be clear. Your site is likely not special. Unless your firm’s name is CNN.
The fact is that most – or the great majority, rather – of attacks are automated. This means that various bots (pieces of software) developed by hackers crawl the web and look for vulnerable sites.
Then if they’re successful, the site gets added to the hacker’s portfolio, so to speak, and can be used for various purposes.
In other words, your site by itself is no special, but 10,000 sites just like yours is pure gold for a hacker. Such a network of hacked sites can be used for things like black hat SEO, mass email sending, database scraping (to get your users’ personal info), and so on.
You really shouldn’t feel overly safe just because/if you run a relatively small website.
Hackers don’t discriminate.
If you are one of those dinosaurs, who still prefer to post content to your own web space and then share it on social media (much like yours truly), then here’s the Ultimate Social Media WordPress plugin (you are using WordPress, right?) that helps will those buttons, sharing, animation, and more. You can even choose how your site’s buttons will look like from 16 different designs.
Containers (Docker, et al) have been getting all the hype recently. I’ve played around with these a bit, but I’m not yet convinced this is the next greatest thing for projects that I am involved with currently. However, it helps to look at these from different perspectives. Here’s a blog post that ties containers to a new term that I haven’t heard before – algorithm economy.
The “algorithm economy” is a term established by Gartner to describe the next wave of innovation, where developers can produce, distribute, and commercialize their code. The algorithm economy is not about buying and selling complete apps, but rather functional, easy to integrate algorithms that enable developers to build smarter apps, quicker and cheaper than before.
Here is yet another DNS / WHOIS record lookup tool. It’s quick and simple – just type the website’s URL and submit a form. You’ll get a result with all the DNS records and WHOIS information, all on one page.
The term DNS stands for Domain Name System, the largest digital database which contains all websites information on the internet. Every domain has authoritative DNS server which publishes information about that domain and the name server for the domain.
Our DNS / Whois record lookup tool will grab A, MX, SOA, NS, TXT and Whois records for a domain name.
Slashdot runs these two stories, a day apart:
Nobody is dying (yet), but it’s an interesting change in trends. Read Slashdot comments for more insight.
An API is a user interface for developers. Put the effort in to ensure it’s not just functional but pleasant to use.
Vinay Sahni has a rather lengthy, detailed, and well-rounded post on how to design a good RESTful API. It covers pretty much everything from URL structures and parameters, request methods, to error handling, documentation, and coding style.
Jordi Boggiano looks at some common files in PHP packages, using Packagist as a data source. There are some interesting metrics in there. For example:
- 58% of packages include a src/ directory and 5% a lib/ one. That’s surprisingly low to me, that means a lot have the code simply in the root folder.
- 4% have a bin/ directory, including some sort of CLI executables.
- 55% have a LICENSE file, that’s.. pretty disastrous but hopefully a lot of those that don’t at least indicate in the README and composer.json
- 49% have some file or directory indicating the presence of tests (phpunit.xml & co). I am not sure if this is good or bad news to be honest, that depends on your expectations.
CommitStrip nails one of the ways of getting into a bad project …
I remember reading an interview with Matt Mullenweg (though can’t seem to find a reference now), where he said that this sort of thing happened with Automattic. People were asking them for commercial support, but they didn’t want to do it, so they started with an insane amount of like $5,000 per month and all of a sudden found themselves with a queue of people outside.
And they were not alone, of course.
Jeff Atwood has an excellent blog post, about the increase in computing powers of the modern CPUs and GPUs and the affects of those on things around us. In particular – games such as chess and Go, and password cracking.
Every time you see a new video card release, don’t think “slightly nicer looking games” think “wow, hash cracking and AI just got 2× faster … again!”