“You can easily customize the new inbox – select the tabs you want from all five to none, drag-and-drop to move messages between tabs, set certain senders to always appear in a particular tab and star messages so that they also appear in the Primary tab.”
Demonstration video inside.
Gnometer, a skin for Rainmeter, has been out for around 3 years now and it has a few outdated settings. So far, I have noticed that the Windows Media Player settings for the Media Player gnometer does not work at all. A quick search through the links on the skin and google will lead you to this new plugin called NowPlaying.
The changes to make it work are simple but they are not easy to find as they are scattered through a few posts on the rainmeter forums.
Below, the fully working settings.ini file.
About 2 months ago, I wrote about a photography and video class. It was my intention to write about them weekly and turn those posts into some sort of a summary that would form a mini dossier for this class.
But I didn’t had the time.
And it went too fast. Yes.
But it was nice. I learned a few things (a lot less than what I had imagined, but whatever).
Now, I’m only talking about the Photography part of this formation because, the video part was just ridiculous! I wouldn’t recommend those lessons to anyone in all honesty.
After deploying one of my applications a user reported this error. This is the type of error I personally hate because the Exception Message is not clear to what object is it referring to.
Anyways, nothing that a quick search on Google couldn’t help. Turns out, there’s a limit for input objects in forms defined in ASP.NET since December 2011 Microsoft security patch to prevent malicious code through injection. To change this limit you have to edit your web.config file and add the following code inside your <configuration> tag.
<configuration>... <appSettings> <add key="aspnet:MaxHttpCollectionKeys" value="your_value_here" /> </appSettings> </configuration>
Save your file and restart your IIS.
So today I had my very first class. We went through the very basics of taking a picture.
The process of taking a picture is always split in three moments. Visualize, understand and learning the environment, that will be the first. You shouldn’t be trigger happy and shoot a bunch of picture hoping one will come out perfect or as you idealized it. You have to get involved with your surroundings and learn from it. See what happens, how everything moves. The second one is composition, best angle, best framing. Finally, comes the technical part where you work with light and exposure.
We went through a selection of photos the teacher (Duarte Neves, if you’re interested) chose, discussed and analyzed them. How they were taken, light position, composition etc. The concepts of light and contrast were also explained and he gave us some pratical examples for better understanding.
All in all it was a blast! Can’t wait for the next lessons!
The worst part of it all is the fact that its 11.54pm and I’m on the train home writing this.
Because the “a picture is worth a thousand words” cliché sometimes just doesn’t cut it and the dictionary itself is rather incomplete to come up with a faithful description of whatever travels through the axons of the human brain, I leave this space _______ open to enter whatever word best describes one of the most disgusting, aggressive and pissed off moments I have ever had. (it will come up, eventually)
(pun intented, ha ha!)
Recently, while building a logging class to be used on all my php REST/JSON and SOAP webservices, I came across an issue when reading the REMOTE_ADDR server variable.
When using Nginx, the $_SERVER['REMOTE_ADDR'] variable comes, by default, with the IP Address of the Nginx machine, which makes sense, if you think about it. Meaning, in a scenario like the following, every single request hitting Nginx, will be forwarded to one of the nodes with the REMOTE_ADDR variable filled with the value 172.20.0.10.
Now, what I wanted was a way to know the client real IP address, which means, on the scenario I mentioned above, if I call a webservice from my computer, the IP address read from my scripts will be 10.104.3.88 instead of 172.20.0.10. But how?
There are several of websites giving you a way of accomplishing this by installing a mod on Apache called mod_rpaf (Reverse Proxy Add Forward) but this mode is not available on the default repositories which makes me unsure on having this running on my server. I want something more transparent.
Edit your nginx.conf located on /etc/nginx/ and add the following line:
proxy_set_header X-Real-IP $remote_addr;
Basically, adds the X-REAL-IP header containing the client ip address.
Reload Nginx, and run the following piece of php code:
<?php echo $_SERVER['HTTP_X_REAL_IP'] ?>
My thread on the official Nginx Forums: http://forum.nginx.org/read.php?11,231704
Listen, my website is crap. I know that. I do not sell goods or offer any kind of service other than the occasional “waste your time reading my posts”. That being sad (intentional typo here), the damage made was small (more like none) compared to big websites.
From a marketing and customer care perspective, whether I am a big website or not, is meaningless when we are talking about a failure of delivering service which I (the client) am paying for. So I wonder, who was the genious inside GoDaddy that thought sending an email with a 30% discount code for (and here’s the catch!) new purchases or renewals is a decent way to apologize for your service outage?