I've been trying to understand how to setup systems from
the ground up on Ubuntu. I just installed redis onto
the box and here's how I did it and some things to look
out for.
To install:
It’s probably a pretty bad idea to have your site go down, when people are supposed to read the blog post explaining the hack.
Notice how another site reporting the hack received more attention than Twitter’s own announcement. Why was that?
| { | |
| {I have|I've} been {surfing|browsing} online more than {three|3|2|4} hours today, yet I never found any interesting article like yours. {It's|It | |
| is} pretty worth enough for me. {In my opinion|Personally|In my view}, if all {webmasters|site owners|website owners|web owners} and bloggers made good content as | |
| you did, the {internet|net|web} will be {much more|a lot more} | |
| useful than ever before.| | |
| I {couldn't|could not} {resist|refrain from} commenting. {Very well|Perfectly|Well|Exceptionally well} written!| | |
| {I will|I'll} {right away|immediately} {take hold of|grab|clutch|grasp|seize|snatch} | |
| your {rss|rss feed} as I {can not|can't} {in finding|find|to find} your {email|e-mail} subscription {link|hyperlink} or {newsletter|e-newsletter} service. Do {you have|you've} any? | |
| {Please|Kindly} {allow|permit|let} me {realize|recognize|understand|recognise|know} {so that|in order that} I {may just|may|could} subscribe. | |
| Thanks.| |
| <?php | |
| ### --- Snip --- ### | |
| App::after(function($request, $response) | |
| { | |
| // HTML Minification | |
| if(App::Environment() != 'local') | |
| { | |
| if($response instanceof Illuminate\Http\Response) |
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
| /** | |
| * Implementation of hook_entity_info_alter(). | |
| * | |
| * Redirect any links to program taxonomy terms to their corresponding node page. | |
| */ | |
| function content_recipe_entity_info_alter(&$entity_info) { | |
| $entity_info['taxonomy_term']['uri callback'] = 'content_recipe_taxonomy_term_uri'; | |
| } | |
| /** |
Prerequisites:
Software components used:
| var d = document.createElement('div'); | |
| d.innerHTML = '\ | |
| <style>\ | |
| *:not(.icon):not(i), *:not(.icon):not(i):after, *:not(.icon):not(i):before {\ | |
| box-shadow: none !important;\ | |
| text-shadow: none !important;\ | |
| background-image: none !important;\ | |
| }\ | |
| *:not(.icon):not(i) {\ | |
| border-color: transparent !important;\ |
The attack detailed below has stopped (for the time being) and almost all network access for almost all customers have been restored. We're keeping this post and the timeline intact for posterity. Unless the attack resumes, we'll post a complete postmortem within 48 hours (so before Wednesday, March 26 at 11:00am central time).
Criminals have laid siege to our networks using what's called a distributed denial-of-service attack (DDoS) starting at 8:46 central time, March 24 2014. The goal is to make Basecamp, and the rest of our services, unavailable by flooding the network with bogus requests, so nothing legitimate can come through. This attack was launched together with a blackmail attempt that sought to have us pay to avoid this assault.
Note that this attack targets the network link between our servers and the internet. All the data is safe and sound, but nobody is able to get to it as long as the attack is being successfully executed. This is like a bunch of people