Skip to main content
This one is a little off topic, but I wanted to highlight some of the Firefox extensions which I am in love with and I would be lose without them. They are in order from most important to least important: - Lets me manage my gmail accounts, and keep tabs on how much email and spam each account has. - Another must have, allows you to tweak FF to enable the browser to run faster, things like allowing more connections per webserver and such. - Must have, can block ads and other items you don't want to see, allows for regexp matches. - This one you need to have it will do things like force gmail over SSL, customize the display of ads, and change the way pages are displayed and ranked in google. - You love tabs? We all love tabs. This one lets you manage the way your tabs behave. I love the fact that I can switch tabs by holding my mouse over them. It probably saves me 500 clicks per day :) - With the number of extensions you see I run, and always playing with another one or two, you know we need a solid extension manager. Well this tool takes the cake, its the best extension manager out there. - Lets you run certain tabs with the IE engine, and use regular expressions to auto load certain sites in ie. For example I load * Domains with IE from within FF. - Gotta keep in touch with the weather and sat maps right in your FF status bar. - Makes the scroll wheel on a mouse act more "smooth", and allows you to tune the way the wheel works in FF. - This one pretties up the view source, color coding the html and such. Makes it easier to read and analyze the source. - (Switch Proxy) This one allows you to manage and switch proxy servers quickly. I am often doing things that I don't want to be tracked to me, so I use this and my list of proxy servers to better hide myself as needed. - This one does search result aggregation, its pretty good, but I prefer using Copernic Agent for the most part. - This extensions allows you to search for a person on many sites at once. Its pretty handy, but I don't use it a whole lot.

I'm currently playing with this extension : - It shows the open tabs in a mini view, I'm not sure how useful it is yet.


Popular posts from this blog

Misunderstanding "Open Tracing" for the Enterprise

When first hearing of the OpenTracing project in 2016 there was excitement, finally an open standard for tracing. First, what is a trace? A trace is following a transaction from different services to build an end to end picture. The latency of each transaction segment is captured to determine which is slow, or causing performance issues. The trace may also include metadata such as metrics and logs, more on that later. Great, so if this is open this will solve all interoperability issues we have, and allow me to use multiple APM and tracing tools at once? It will help avoid vendor or project lock-in, unlock cloud services which are opaque or invisible? Nope! Why not? Today there are so many different implementations of tracing providing end to end transaction monitoring, and the reason why is that each project or vendor has different capabilities and use cases for the traces. Most tool users don't need to know the implementation details, but when manually instrumenting wi

NPM is Broken

As someone who bought and implemented NPM solutions, covered them as an analyst, and now watches the industry, one cannot help but notice that NPM(D) is broken. According to Gartner themselves, the data center is rapidly changing, the data center is going away, m aybe not as quickly as Capp states, but it’s happening. This is apparent by the massive public cloud growth posted by Amazon, Microsoft, and Google in their infrastructure businesses. This means that traditional appliance-based NPMD offerings will not work, nor will traditional ways of collecting packet data. Many of the flow offerings do not handle the new types of flows which these services generate, but most importantly they do not understand the internet, which is the most important part of assuring services in cloud hosted environments. The network itself is not just moving to overlay a-la NSX and ACI, it's moving inside of orchestrated containers, and new proxy/load balancing systems typically built off component

F5 Persistence and my 6 week battle with support

We've been having issues with persistence on our F5's since we launched our new product. We have tried many different ways of trying to get our clients to stick on a server. Of course the first step was using a standard cookie persistence which the F5 was injecting. All of our products which use SSL is being terminated on the F5, which makes cookie work fine even for SSL traffic. After we started seeing clients going to many servers, we figured it would be safe to use a JSESSIONID cookie which is a standard Java application server cookie that is always unique per session. We implemented the following Irule (slightly modified in order to get more logging): (registration is free) when HTTP_REQUEST { # Check if there is a JSESSIONID cookie if {[HTTP::cookie "JSESSIONID"] ne ""}{ # Persist off of the cookie value with a timeout of 2 hours (7200 seconds) p