CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
cf_ob_info
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
_cfuvid
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
__cfruid
Used by the content network, Cloudflare, to identify trusted web traffic.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_ni
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_use_ob
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
If you haven’t stopped by yet, make sure you check out Scott Kelby’s blog today. I don’t want to spoil it too much but Scott wrote a really interesting post about what he’d like to see in Lightroom 4. Stop by and let him know what you think, if you agree or not, and any features that you think need to make it into Lightroom 4.
I’d like to be able to brush in additional white balance values. This mostly happens outside where there’s bright sunlight and shadows and inside when mixed light is in the shot. I’d like to brush in warmer or cooler light temperatures to correct such images.
Hey Matt, I know I am fairly late in posting to this thread but better late than never, yeah?
I am curious about the relationship between adjusting for exposure in Lightroom and adjusting during the shoot; specifically with exposure compensation. With the power of software like Lightroom, when does it become necessary to fine tune your exposure in the camera?
I know it is pretty easy to merge panorama’s from LightRoom in Photoshop, but it would we nice (and I think it is a pretty necessary function for a photo Editor) to be able to PhotoMerge photo’s directly in Lightroom.
hey Matt,
I shoot a lot of outdoors and a lot on mountains. I’m under the impression that it’s very hard to bring back the texture in the snow when overexposing. I focus on preserving the details in the bright areas in those situations. However I do agree on slight overexposing when there’s a lot in the photo that would need fill light in post later on. It’s best to keep that in mind and (over) expose according to that.
I read all the comments on Scott’s blog and was amazed to see that people are reporting slow performance even on 12 core Mega Macs. I was just about to add more RAM to my PC and am now holding off since none of my other applications needs it.
If all the improvements were implemented I wonder if Photoshop would be reserved for special effects and digital art rather than photographic workflow. It was interesting to read the comments about Aperture, which, as a PC user, I have never seen. I am sure that Adobe had a bad weekend after seeing this blog thread.
It was really disappointing to read this list of requested features, they looked really superficial and do not address any of the reasons why I dislike LR and do not use it at this time. Scott’s additions, if implemented, would do little to make LR a better photo-editing tool. Rather they will tend to produce bloatware that tries to be everything to everybody.
I would much rather see expanded non-destructive editing capabilities so we don’t have to go to PS so often, and don’t have to keep creating new versions of huge files every time we do so. Every third-party filter that now exists in LR does nothing more than create a TIFF copy of the image, work on that,and then add it back to the LR catalog. I have not spent much time in LR so I could be wrong, but I believe that these third-party edits are not reversible.
Writing the edit steps to a sidecar file is fine because it is fast and easy to proliferate across multiple images. How about giving the option of permanently writing them in the embedded JPEG preview of the original RAW file, even if it is not a DNG? We are then not tethered to LR for quick previews of a single image.
There are quite a few other things like that… Sigh, I really want to like LR and have test-driven every preview, from the original public release to LR3, and have never found a reason to start using it. It just feels like a wrapper around PS’s capabilities that does not add enough new things to justify its price.
While I agree with you, I still love Lightroom. It’s a double-edged sword as it keeps me out of Photoshop for about 90% of my images… but the fact that they say it’s designed to be part of a Photoshop workflow and I also think they need a better way to prevent making multiple copies of images and just stacking them together.
I really like your ideas a lot. And would LOVE them… but what’s the better option? Just storing negatives in a folder? Aperture?
I’m sure this has been asked before but would it be possible to download your great presets to CS5’s adobe raw as well?
Matt, this question has probably been asked before. Is it possible to import all your fabulous lightroom presets into Photoshop CS5 Adobe Raw? It sure would be handy.
ok I can’t say that my english will be good but…
few days ago you were showing how to make black or withe border with rounded corners… that is great…
it would be nice to choose the color
nice also to have a blur or fade function more efficient…
and I have to say, Matt, Thanks this is a great blog…
I would like to see more accurate masking. Not necessarily full blown masking like PS but better than what er have now.
It would be clever for you guys to have your web-slingers build a survey of all these collected features and host it on one of your blogs so users could answer a half dozen questions about their use of LR (or interest in purchasing) and other tools they also use…. and then somehow rank the top 10 features of interest to them… The results would be a handy thing for a development manager to consider along with a shopping list…. just sayin’…
That is a great idea.
Please, we need a larger navigator window so we can see the preset previews better.
Matt:
Make sure he knows about your wish for a movable post-crop vignette center! 😀
My biggest gripe so far is having to save a new watermark if I change the positioning of an existing watermark! I could see saving a new one if I changed the font or wording.
–John
Great ideas from Scott. But Matt, you’re the one with the Lightroom Killer Tips – what about your wish list?