Take a longer expiry time to avoid the noise

Best Binary Options Brokers 2020:
  • Binarium
    Binarium

    The Best Binary Options Broker 2020!
    Perfect Choice For Beginners!
    Free Demo Account!
    Free Trading Education!
    Get Your Sing-Up Bonus Now!

  • Binomo
    Binomo

    Only For Experienced Traders!

Contents

Light Advice: Avoid Rejection for ‘Poor Lighting’ or ‘Lighting Problems’

Share this:

As a contributor, you may have received one of the following rejection reasons for a submission:

Poor Lighting: Image has exposure issues, unfavorable lighting conditions, and/or incorrect white balance.

Lighting Problems: Image contains color fringing and/or inappropriate lens flares.

Lighting and exposure issues are among the most frequent technical problems we come across in reviewing submissions, and can be caused by a number of different factors.

Avoiding ‘Poor Lighting’

Example: Overexposed image

If you’ve received a “Poor Lighting” rejection, it means that one or more of the following issues is present in the image:

– Incorrect white balance; color tones appear too cool (blue hues) or too warm (orange and yellow hues).

– The highlights in the image are overexposed and/or there is a loss of detail in the shadows or highlights.

– The overall quality of light is too flat or there is too much contrast.

– The subject is lit in a way that produces unflattering shadows.

Example: Underexposed image

The old adage, “measure twice, cut once” pertains not only to carpentry, but also to photography . While we now have a variety of methods for improving exposure after the fact, no amount of Photoshop magic can replace getting your lighting right at the time of the shoot.

If you’re shooting in a controlled lighting environment, like a studio, it’s important to get the light tested before you begin shooting. Establishing good lighting on set can save time and money by cutting your post-production costs, and it’s much easier to fix a lighting issue at the shoot than trying to adjust levels in post-production, which can degrade the quality of your image — even if you’re shooting in RAW.

When setting up your shoot, take a lot of well-focused test shots. If possible, shoot with your camera tethered to a computer with a large, color-calibrated monitor. Be sure to preview each image to determine where your lighting might need to be adjusted. There are a few other handy tools that can quickly improve your lighting. A light meter will tell you what the desired exposure should be, and a grey card is an easy reference for setting accurate white balance.

Measuring light from studio lights with flash meter by Sergey Novikov

If you’re shooting outdoors and relying on available light, keep in mind that the light will be changing throughout the day. Bracketing — taking a number of photos using a variety of camera settings — is a good way to experiment with alternatives to get the best exposure possible.

Avoiding ‘Lighting Problems’

“Lighting Problems” as a rejection reason refers to color fringing and lens-flare issues. Color fringing, or chromatic aberration, appears as colorful edges around objects. From a scientific perspective, this effect occurs when light wavelengths aren’t meeting correctly at the same point of convergence. Chromatic aberration is common among lower-quality lenses, but can occur in better lenses as well. Most photo-editing software offers tools to eliminate some aberration, but may not remove all of it. You can also zoom in to your image at 100% and erase the prominent fringing by hand in post-production.

Example: Color fringing Close-up: color fringing appears as purple haze around branches

Many contributors manipulate their white balance or utilize lens flare to enhance the feel of an image. As long as the effect adds a new and creative element, we love this type of work. The review team most often rejects an image if the white balance looks unintentionally warm or cool, or the lighting detracts from the subject matter. If you’re using lighting in a creative way, you can always leave a note for the reviewer stating your intention. It will help us evaluate the image with your vision in mind.

Example: Unintentional lens flare

Getting the perfect light in any shooting scenario can be tricky, but by following some of these simple rules, we hope your prep time will be well spent, and more of your images will become a part of the Shutterstock collection!

Vintage photo of summer sunset on field by Milosz_G

More articles in this series:

long expires time #3406

Comments

Copy link Quote reply

KonoromiHimaries commented Jan 5, 2020

most users have a old filters
and so happened
https://www.wykop.pl/link/4094131/brak-mozliwosci-zalogowania-do-mbanku-z-wlaczonym-ublockiem/

filters have min. 2 days expiries time

pls. change to 1 day

This comment has been minimized.

Copy link Quote reply

jspenguin2020 commented Jan 6, 2020 •

You can write ! Expires: 1 day although uBO will treat it as 2 days.
I do accept 1 day expire time on my side

This comment has been minimized.

Copy link Quote reply

gorhill commented Jan 6, 2020 •

The reason is to lower abusive behavior toward the servers which host the filter lists. Nobody pays for that bandwidth, and once it will be deemed abused, we will all be in trouble — last thing I want is GitHub asking me to find a host elsewhere. I might even raise the limit to 3 days if I judge it’s for the best.

This comment has been minimized.

Copy link Quote reply

gorhill commented Jan 6, 2020 •

@jspenguin2020 If you find this acceptable, good for you, please do not have your fork pull resources from here. Thanks.

This comment has been minimized.

Copy link Quote reply

jspenguin2020 commented Jan 6, 2020 •

If a filter maintainer thinks it’s appropriate, there is no reason to disallow 1 day expire time. He will deal with hosting problems himself if it turns out 1 day is too short. You are never forced to make uBlock filters update every day.

And you can also compress the filter. It has so many comments and white spaces, if that’s what you are distributing, I can’t be convinced that you worry about bandwidth.

This comment has been minimized.

Copy link Quote reply

jspenguin2020 commented Jan 6, 2020 •

There are so many ways to save bandwidth:

  • Compress the file that you distribute (remove comments, combine rules, etc)
  • Compress filter syntax, xhr for xmlhttprequest , css for stylesheet , etc
  • Differential update, this can be a bit difficult, but once setup, you hardly need to maintain it
  • Pack fresh filters in the extension and save an update

Instead, you choose to give users outdated filters while complaining about bandwidth. You can easily save a good 30% of bandwidth just by removing comments from the filters you distribute.

This comment has been minimized.

Copy link Quote reply

gorhill commented Jan 6, 2020

@jspenguin2020 Sure, I can go on any GitHub repo, including yours, and throw lots of ideas about how things could be better and question “why didn’t you do this?”, having ideas is the easy part.

It’s an ongoing project — you seem to have this strange idea that everything you can muster in your mind now should have been implemented in the past (on top of everything which was actually done), so that no issue whatsoever, small or big, should be afflicting the project now.

The bandwidth issue has been on my mind lately so as to not abuse GitHub, and it’s not because I do not throw ideas for all to read that is a sign I need to be educated about what can be done.

This comment has been minimized.

Copy link Quote reply

jspenguin2020 commented Jan 6, 2020 •

I’m not saying you should’ve have all that already implemented, I’m saying you should think about doing that instead of sticking the declined label and call it a day.

I’ve been compressing my filters a long time ago and I’ll compress the rest soon. I can host uBlock filters on my server if you are unhappy that Nano pulls them every 3 days instead of 5.

If you have ideas that are reasonable and implementable, I want to know what they are. You are welcomed to submit feature requests to my repositories. Having ideas might be the easy part, although what I pointed out above are easy to implement and have observable effect – at least the first two. I (will) have both implemented if you want to check them out.

This comment has been minimized.

Copy link Quote reply

jspenguin2020 commented Jan 6, 2020 •

There, 38% smaller (diff / avg) or 31% (diff / uncompressed); not counting the resource file which needs to be compressed in another way (uglify maybe?).

This comment has been minimized.

Copy link Quote reply

KonoromiHimaries commented Jan 6, 2020 •

2 days – 38% = 29.76 hours

This comment has been minimized.

Copy link Quote reply

mikhaelkh commented Jan 8, 2020 •

The reason is to lower abusive behavior toward the servers which host the filter lists.

You respect ! Expires: syntax, so if filter list set it to 1 day , why override it? Nobody’s asking you to set 1 day to default.

Nobody pays for that bandwidth. Last thing I want is GitHub asking me to find a host elsewhere

Maybe not directly, but they have analytics. If you’re worried, you can ask GitHub how they feel about being resources hosting for such a popular extension.

This comment has been minimized.

Copy link Quote reply

ssolidus commented Feb 23, 2020

This comment has been minimized.

Copy link Quote reply

gorhill commented Feb 23, 2020

I figured I lost the argumentation, hence the fix.

This comment has been minimized.

Copy link Quote reply

ssolidus commented Feb 23, 2020 •

I figured I lost the argumentation, hence the fix.

Well yeah, but regardless of outcome, you are unnecessarily rude and belligerent on almost every bug or pull request that comes your way.

This comment has been minimized.

Copy link Quote reply

gorhill commented Feb 23, 2020

Can you point me to an example of this? I want to understand your perception.

This comment has been minimized.

Copy link Quote reply

ssolidus commented Feb 24, 2020 •

Can you point me to an example of this? I want to understand your perception.

I’ve watched this repository for a good year or so now, and its just the impression I get from your responses to bugs, and in particular, criticism. It’s like a syndrome where a developer runs a project, open-source or otherwise, that garners a lot of attention, and then they become egotistical or neurotically protective of their work. I see it everywhere.

If you really want examples, I’ll email you or something.

This comment has been minimized.

Copy link Quote reply

seanrand commented Feb 24, 2020 •

@thomasklash see #2649 (comment) for some context. Community management/moderation can be taxing, it’s nothing personal. I’ve seen devs abandon their projects because they didn’t want to deal with the constant flow of nonsense once it reached a certain popularity. The signal-to-noise ratio tends to reach lows especially on general purpose projects that have lots of non-technical users.

Nonetheless, setting up a few more reply templates apart from the usual “as per contributing.md” (especially for filter issues) could go a long way and might ease the blow people feel when they have a “declined/invalid” tag stuck on their issue.

This comment has been minimized.

Copy link Quote reply

ssolidus commented Feb 24, 2020

@seanrand Yes, I know. I am involved in the Arch community and have seen this happen frequently: see the most recent developments with the now discontinued pacaur utility.

However, in that case, this case and many others, all of these non-technical users that flood in mean well, apart from some rudeness and some trolls. I know sometimes you need to give people a hard no, but too often I see people going the Torvalds route and just raining down on someone who is simply inexperienced, not that intelligent, or whatever.

The last thing the softdev/engineering/compsci/IT community and industry needs is more cynical assholes who have had their share of shit thrown at them and are now bitter and rude towards anyone not intimately familiar with the project, its scope, or just how things work in development general.

This comment has been minimized.

Copy link Quote reply

Hrxn commented Feb 24, 2020

@thomasklash You’re just projecting. Stop making up problems where none exist.

This comment has been minimized.

Copy link Quote reply

mikhoul commented Feb 24, 2020 •

Can you point me to an example of this? I want to understand your perception.

I’ve watched this repository for a good year or so now, and its just the impression I get from your responses to bugs, and in particular, criticism. It’s like a syndrome where a developer runs a project, open-source or otherwise, that garners a lot of attention, and then they become egotistical or neurotically protective of their work. I see it everywhere.

I agree 200% with @thomasklash , I stopped to report bugs or make suggestion on UBO because of the attitude of the maintainer. Also I’ve been involved and I’m involved on MANY other Open source projects and from my personal experience I never seen an attitude such bad as here when somebody make suggestions or ask for help.

I’m so happy for the fork of @jspenguin2020 since it’s “fresh air” with an “open mind”. It may not agree with all suggestion but you don’t feel like Sh***it when he answer to you. You feel that he realy care about the user,

@gorhill attitude is like Mozilla/Firefox attitude with their users. they pretend know better than users what they need and want sadly and don’t really listen unless it’s the way they see things.

N.B.: This message is not to bash @gorhill, I thank him for his contribution but I hate his attitude and closed mind when he answer here on Github.

This comment has been minimized.

Copy link Quote reply

Hrxn commented Feb 24, 2020

You’re the ones ruining open source projects. That is for sure.

This comment has been minimized.

Copy link Quote reply

thewriteway commented Feb 24, 2020 •

I think its @thomasklash who is disrespectful to mount a personal attack on Gorhill. People come here demanding features at the snap of a finger. That isn’t how open source works. If you want something added that you feel is super important to you then work on the solution yourself and contribute it back for others if you are feeling so in kind. Gorhill does his best to make the project the best possible and I don’t think you are in a position to grand stand and make accusations when you haven’t (I’m assuming) committed anything to this project? Just be grateful uBlock even exists, I know I am and I wouldn’t rag on the developers for things you consider important, because at the end of the day its their time being spent doing things not yours!!

This comment has been minimized.

Copy link Quote reply

mikhaelkh commented Feb 24, 2020 •

This is not a question of rudeness but rather a question of resources. The author simply does not have the time to explain every decision and in this issue he forgot to check it after he closed it. And here he changed his mind because of the arguments — so if you are willing to fight for your opinion, your opinion will be heard.

This comment has been minimized.

Copy link Quote reply

Best Binary Options Brokers 2020:
  • Binarium
    Binarium

    The Best Binary Options Broker 2020!
    Perfect Choice For Beginners!
    Free Demo Account!
    Free Trading Education!
    Get Your Sing-Up Bonus Now!

  • Binomo
    Binomo

    Only For Experienced Traders!

tomasz1986 commented Feb 25, 2020 •

I think that one of the problems may be that software developers (and computer savvy people in general) are very far from the reality of “normal” computer users. Most people have completely no idea about how programs are written (open source or not), or how they work. They just see that something is wrong, and look for a way to report their problem to the program’s author. They may have never heard of GitHub before, they do not know how it works, and the bug report may be the first one in their lifetime.

When it comes to uBlock, I really doubt that the majority of its users really understand the distinction between the program itself and the filter lists. So they come here and report their issues. Then they are greeted with a “declined” label with a short note that they are unable to understand. The result often is that they simply get angry and bash the software and its author. The more popular a piece of software is, the more such inexperienced users will use it (and come here with their problems).

I am not bashing or complaining, but maybe a more detailed explanation (even if just copied & pasted) would simply help those users understand better why their bug report has been declined, and let them know what they should do next?

This comment has been minimized.

Copy link Quote reply

Hrxn commented Feb 25, 2020

I hope this is some sort of joke.
Sorry, but if you are “computer savvy” enough to know this site (GitHub), know how to create an account on this site, know how to log in and use said account, know how to navigate to the repository home page,
know that you have to click on “Issues”, and know that you then can click on “New Issue” to open a new entry on here, then it is definitely not possible to explain how you missed the text right in front of you, that clearly says that you should read CONTRIBUTING.md first, and that info box now always displayed by GitHub that also tells you to “Take a look before submitting an issue: . “ and directly links the Contributing guidelines for you, you’re running out of excuses pretty quick. And don’t let it be laziness and/or ignorance, please..

This comment has been minimized.

Copy link Quote reply

jspenguin2020 commented Feb 25, 2020 •

@Hrxn That is exactly my expectation, especially for other developers, but as I learnt from my experience, this is not reasonable to expect. In earlier 2020, Adguard devs basically put a giant middle finger towards my previous (now deleted) contribution guideline in their app, and it’s how the silly fight happened as I expected them to read my contribution guideline.

Expecting people to read and follow your contribution guideline will end in conflict. Having a guideline is good, but expecting that you can peacefully enforce it is not. People simply do not read, have you wondered why it is so difficult report bugs at times? Big software companies use bots to screen out noise, and will only alert developers when enough reports on the same issue are filed.

This comment has been minimized.

Copy link Quote reply

This comment has been minimized.

Copy link Quote reply

jspenguin2020 commented Feb 25, 2020 •

I usually avoid controversial issues of this type, but I’ll put my 2 cents in.

First, I’m neutral on how gorhill is handling moderation, although I agree that his saved replies should be improved (which he did as far as I see), I don’t agree that he should always argue with you and explain everything. On one side, it is hard to imagine not understanding a concept, on the other hand, developers are not teachers and have a hard time passing the knowledge over in an understandable way. It is totally OK to leave an issue closed and ignore it, or to lock it, if a decision is made. (I think a direct link to Reddit in the popup menu should help in reducing noise in issues tracker though.)

However, looking back, a project of this scale is basically a one-man-show clearly indicates something is not right. It is fine to immediately close suggestions that are ridiculous as per common sense of developers, but those that are hard to tell should be left open for further discussion.

That being said, gorhill is the king in his repositories, open source does not imply democracy, it just means you can create your own kingdom by clicking Fork. Open source projects can live with just 1 user but can die even if it has thousands, the ultimate decision is up to the developers, who are ultimately the only users that matters.

I stopped to report bugs or make suggestion on UBO because of the attitude of the maintainer.
Also I’ve been involved and I’m involved on MANY other Open source projects

Let me tell you, every project can live without you. You simply do not bring this up like a threat.
From your past comments in my repository, I can tell that your coding skill is rather limited. You are one of the vocal minority defending legacy technology, and that is not helpful in most projects.

If you ever need to put a weight on your contribution to “MANY other Open source projects”, show it in action, not in words. Fork it and show that your involvement would’ve been helpful.

This comment has been minimized.

Copy link Quote reply

tomasz1986 commented Feb 25, 2020 •

I hope this is some sort of joke.
Sorry, but if you are “computer savvy” enough to know this site (GitHub), know how to create an account on this site, know how to log in and use said account, know how to navigate to the repository home page,
know that you have to click on “Issues”, and know that you then can click on “New Issue” to open a new entry on here, then it is definitely not possible to explain how you missed the text right in front of you, that clearly says that you should read CONTRIBUTING.md first, and that info box now always displayed by GitHub that also tells you to “Take a look before submitting an issue: . ” and directly links the Contributing guidelines for you, you’re running out of excuses pretty quick. And don’t let it be laziness and/or ignorance, please..

I did exaggerate a little �� , but if you have in fact seen how non-tech savvy people deal with computers and software, then I would not be so sure about it.

From my experience, as someone who has helped hundreds of people with their computers, people never actually read any documentation unless absolutely necessary. This includes all kinds of readmes, licenses, and other similar documents (such as CONTRIBUTING.md too). If people have read them, then I am pretty sure that at least half of the reported “issues” would not have had existed in the first place. I am not saying that it should be like that. I am rather just stating the reality, especially since GitHub is not some kind of a closed mailing list for developers, but is an open platform where anyone can register and post.

Is is due to their laziness? Maybe. I actually believe that they simply do not consider the software and its issues important enough to spend more time on studying them. They just want a “quick fix”.

Long Life

Todd: So, Monica, a minute ago we were talking about Tai Chi and about how it helps longevity, helps you live a long life. One time when I was in Bangkok, I met a guy and he was doing Tai Chi and he looked really young, but he said the secret to his old life . he said the secret to looking young, was Tai Chi and cold showers. He took a cold shower every morning.

Monica: Oh, wow!

Todd: Could you do that?

Monica: No, I don’t think I could actually.

Todd: Yeah, you know, I actually tried it for awhile and I tried it for about a week and I did feel so energized and it was easy in Bangkok, cause it’s really warm but I couldn’t keep it up , especially not that I’m in the cold climate. There’s no way.

Monica: Yeah, I remember when I was young, my mother used to teach me to splash my face with cold water in the morning because she believed that helped wake you up, and I remember as a child not liking that at all because I found it too cold. I preferred to splash my face with warm water.

Todd: So, have you heard about any other secrets to having a long life?

Monica: Yeah, I’ve heard of quite a few different secrets to having a long life. I guess one secret that a lot of different cultural groups seem to share is diet. If you take the Japanese as an example, and Japanese people do have a long life expectancy in comparison to other people from ofher countries. I think the Japanese eat a diet that’s quite low in fat and reasonably low in salt as well, and I think their fluid intake is quite healthy because they drink a lot of green tea which has antioxidants in it, and a they drink a lot of miso soup which has a lot of vegetables in it, and is made from fermented barley , so I think that’s very healthy.

Todd: I’ve also heard that people in the Mediterranean, they also often have a long life span in certain regions and maybe the combination of wine, just a little wine, not too much, but wine and olive oil, and then a lot of fish, seafood is also maybe beneficial to a long life.

Monica: Yeah, that’s true. I’ve heard French people for example live a long life and that has often been said due to a glass of red wine a day, and I know people think differently about alcohol and it’s affect on the body these days.

Todd: Right.

Monica: Yeah, because alcohol used to be considered quite a bad thing and discouraged in all forms but now people tend to think that a glass a day is actually quite beneficial to your health.

Todd: I’ve also actually heard that laughter, that people that laugh a lot tend to live longer.

Monica: Yeah, I’ve heard that too, actually, because laughing releases natural endorphins, and I think that helps you physiologically, and also I think psychologically you’re happier if laughing so. Yeah, I think that long life is related to how you are feeling, and I think a lot of it is psychological as well as physical, for example, how much you are eating and what types of food you’re eating.

Todd: Yeah, I guess, I’m kind of in the same boat , but I just don’t know if I laugh that much. Maybe I’m in trouble.

I couldn’t keep it up.

To ‘keep it up’ means to continue doing something. Here, Todd could not continue taking cold showers because of the cold weather. Notice the following.

  1. I joined a fitness club and went almost every day, but I couldn’t keep it up.
  2. Chin took a part time job at McDonald’s, but she became so busy with school, she couldn’t keep it up.

I need to splash my face with cold water.

We usually splash water with a fast movement of our hands. The water hits us, someone or something. Here are two samples.

  1. I had no time to shower so I splashed some water on my face and ran off to school.
  2. Thais celebrate the Thai New Year by splashing each other with water.

Japanese people have a long life expectancy.

Life expectancy talks about how long people live. If you avoid smoking, get a lot exercise and eat healthy food, your life expectancy will probably be longer. Notice the samples.

  1. A recent study showed that smoking reduces life expectancy by 10 years.
  2. Regular exercise will not only increase your life expectancy, but also increase the number of years you are healthy.

Their fluid intake is quite healthy.

‘Fluid intake’ talks about how much water, or in this case tea, we drink. Here are some samples.

  1. During the summer, you need to increase your fluid intake.
  2. Correct fluid intake is an important part of distance running.

It is made from fermented barely.

Something that is fermented has been stored for a period of time causing a chemical change. This process is part of the production of alcoholic drinks such as wine and beer. Notice the sample sentences.

  1. Nearly all beer includes fermented barley as the main ingredient.
  2. Kimchee is a traditional Korean dish made of fermented vegetables – mainly cabbage – and various seasonings.

in the same boat

I’m kind of in the same boat.

To be ‘in the same boat’ means we have the same problem or situation as others. The phrase is usually negative. Notice the following.

  1. Min Ho didn’t get the classes he wanted. We both registered late so we are in the same boat.
  2. Though many nations disagree about climate change, the fact is, we’re all in the same boat.

“take too long” vs “take a long time”

As far as I know “take too long ” and “take a long time ” are different. And I once read two examples on Internet they considered to be incorrect.As follows :

1)Let’s plan on using email to inform the client, because regular mail (takes a long time) .

2)Please expect for the project to be completed by 2020 because creating an index (takes too long).

Correct Ans: 1) takes too long 2) take a long time

My question is, why those are incorrect? what’s the difference? Would anybody give me detailed explanations?

2 Answers 2

Take a long time is an idiom, a special meaning of take referring to duration of some event.

  • The train took a long time to pass.

It’s one version of the Event take Duration idiom

    Making egg rolls takes all day

It takes all day to make egg rolls.

Take too long uses the same durational sense of take, but the too marks it as a Negative.
Too Adjective means ‘so Adjective that Not S , where Not S is some negative outcome.

  • He was too sick to come. = He was so sick that he didn’t come.

Thus take too long means ‘take so much time that something is wrong’.

  • The train took too long to pass.

means that it was slow, or it was late, or the drivers honked their horns at it, or the speaker was irritated, or something — details are not always specified. But something was out of expectation.

Best Binary Options Brokers 2020:
  • Binarium
    Binarium

    The Best Binary Options Broker 2020!
    Perfect Choice For Beginners!
    Free Demo Account!
    Free Trading Education!
    Get Your Sing-Up Bonus Now!

  • Binomo
    Binomo

    Only For Experienced Traders!

Like this post? Please share to your friends:
Binary Options Trading For Beginners
Leave a Reply

;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: