Mankind has the honor of quite possibly being the most destructive force to ever hit mother nature. This list looks at some of the more recent, probably lesser known extinctions that humans have lent a helping hand to. Whether by over hunting or over population, driving a species to extinction is nothing to be proud of and it’s certainly not slowing down.
Commonly known as the Tasmanian Tiger, the Thylacine was the largest known carnivorous marsupial of modern times. Virtually wiped out in the wild due to constant hunting (they were thought to be a threat to sheep and other small farm animals) and the encroachment of humans on their already limited habitat the Thylacine was finally recognized as being in danger of becoming extinct in 1936, too little, too late as that same year the last Thylacine, named Benjamin, died on 7 September as the result of neglect — locked out of its sheltered sleeping quarters and exposed to freezing temperatures at night in Hobart Zoo, Tasmania. 60 years on there are still claims of sightings but all are yet to be confirmed.
The Quagga was a southern subspecies of the Plains Zebra. It differed from other zebras mainly in having stripes on the head, neck, and front portion of its body only, and having brownish, rather than white, on its upper parts. The last free Quaggas may have been caught in 1870. The last captive Quagga, a mare, died on 12 August 1883 in Amsterdam Zoo, where she had lived since 9 May 1867. It was not realized that this Quagga mare was the very last of her kind. Because of the confusion caused by the indiscriminate use of the term “Quagga” for any zebra, the true Quagga was hunted to extinction without this being realized until many years later. The Quagga became extinct because it was ruthlessly hunted down for meat and leather by South African farmers, also they were seen by the settlers as competitors, like other wild grass eating animals, for their livestock, mainly sheep and goats.
The story of the Passenger Pigeon is one of the most tragic extinction stories in modern times. As recently as around 200 years ago they weren’t anywhere near extinction. In fact, they were actually the most common bird in North America, and some reports counted single flocks numbering in the billions. Pigeon meat was commercialized and recognized as cheap food, especially for slaves and the poor, which led to a hunting campaign on a massive scale. Furthermore, due to the large size of their flocks, the birds were seen as a threat to farmers. The last Passenger Pigeon, named Martha, died alone at the Cincinnati Zoo at about 1:00 pm on September 1, 1914.
The first record of the Golden Toad was by herpetologist Jay Savage in 1966. The toad, recognized by its brilliant golden orange color, was native to the tropical cloud forests which surround Monteverde, Costa Rica. None have been seen since 1989. It last bred in normal numbers in 1987, and its breeding sites were well known. In 1987, due to erratic weather, the pools dried up before the larva had matured. Out of potential 30,000 toads, only 29 had survived. In 1988, only eight males and two females could be located. In 1989, a single male was found, this was the last record of the species. Extensive searches since this time have failed to produce any more records of the golden toad.
The Caribbean Monk Seal was the only known seal which was native to the Caribbean Sea and the Gulf of Mexico. It is also the only species of seal to go extinct directly due to human causes. The Caribbean monk seal was the first New World mammal to be discovered by Columbus and his company on the coast of Santo Domingo in 1494. It appears in the account of Columbus’ second voyage to America. Columbus promptly ordered his crew to kill eight of the animals, which he called “sea-wolves”, for food, paving the way for exploitation of the species by European immigrants who came in his wake. Since then, the once abundant seals have been hunted for their oil and slaughtered by fishermen, who regarded the animals as competitors. It was officially declared extinct just last year, on June 6th, 2008, although the last recorded account of the species was made at Serranilla Bank between Honduras and Jamaica in 1952. Like other true seals, the Caribbean Monk Seal was sluggish on land. This, along with its lack of fear for man, unaggressive and curious behavior, as well as human hunting, and early habitat exclusion by humans throughout their range may have dramatically speed up their decline and likely contributed to its demise.
From: listverse.com/2009/07/25/10-recently-extinct-animals/
Author: Brien Posey
Over time, you may find that your Active Directory database becomes cluttered with obsolete data (such as references to users or servers that no longer exist) or that it begins to malfunction. Here are some things you should consider before you set out to clean up or repair your Active Directory.
Note: This article is also available as a PDF download.
In spite of outward appearances, erratic Active Directory behavior is not always related to a corrupt Active Directory database. For instance, take a situation in which you can’t create or remove a domain. While it is possible for a corrupt database to cause this problem, it’s more likely that the domain controller hosting the FSMO roles for the domain is down. Another possibility is that the user who is attempting to perform the operation may not have the necessary permissions.
Active Directory is completely dependent on DNS. So if your DNS server fails, it will be only a matter of time before Active Directory begins to have problems too. If you are receiving error messages such as Domain Not Found, Server Not Available, or RPC Server is Unavailable, you may have a DNS server issue.
Windows domain controllers include a command-line utility called DCDIAG. Running this utility performs a number of diagnostic tests on a domain controller. Often times, DCDIAG will help you quickly determine the cause of the problem.
One of the most common issues with Active Directory is that it contains numerous entries related to servers that no longer exist. While you can use ADSI Edit to manually remove references to extinct servers, doing so often does more harm than good. Active Directory is a relational database. Removing an entry for an extinct server can orphan other database entries and cause a whole slew of problems. A better approach is to use the NTDSUTIL tool’s METADATA CLEANUP option. This TechNet article provides a full set of instructions on the process.
You can use ADSI Edit to manually create and delete Active Directory entries. However, ADSI Edit is very unforgiving. Making a mistake can destroy your entire Active Directory. Therefore, it is important to know when and when not to use it. For example, Exchange 2007 can’t be uninstalled until the last public folder has been removed, but a bug prevents you from removing the remaining public folders. I have found ADSI Edit to be useful in working around this issue, but I am extremely hesitant to use it for other purposes.
With virtualization all the rage, it’s no surprise that many organizations have virtualized their domain controllers. Most of the server virtualization products on the market allow you to create a snapshot of a server. That way, if something goes wrong with the server, you can roll it back to a previous state without having to restore a backup.
While I’m all in favor of backing up your domain controllers before attempting to repair Active Directory, you shouldn’t use snapshots. Rolling back a snapshot of a domain controller can have catastrophic consequences. Active Directory transactions are numbered. Rolling back a domain controller causes the numbering sequence to be disrupted. This leads to all sorts of domain synchronization issues.
Normally, NTDSUTIL is the tool of choice for repairing Active Directory problems. But in the case of severe corruption, NDTSUTIL may not be able to fix the problem. If this happens, your best bet is to restore a backup. If that isn’t an option, though, you can try using ESEUTIL.
ESEUTIL is a database maintenance tool for extensible storage engine databases. You can use it to repair structural problems within the database. You should use this technique only as a last resort because data loss is a possibility during the repair process.
When you restore the Active Directory database on a domain controller, the restoration is usually non-authoritative. This means that the restoration process restores the domain controller to the point at which it existed when the backup was made. The domain controller is brought into a current state by the replication process. Other domain controllers replicate any missing entries to the recently restored domain controller.
An authoritative restore does not backfill a restored domain controller using data from other domain controllers. Instead, you are effectively telling Windows that the recently restored domain controller contains the desired data and that you want to remove any subsequent data from the other domain controllers in the organization.
When Active Directory related services fail to start on a domain controller, the problem is often mistaken for database corruption. But often, an overzealous administrator has recently tried to secure the system volume. Excessive NTFS permissions can actually prevent Active Directory from starting. Microsoft discusses this problem in Knowledgebase Article 258062.
Before you perform any major repair or cleanup work on your Active Directory, it is imperative that you perform a full system state backup of your domain controllers. As I’m sure you know, countless knowledgebase articles talk about the importance of backing up a system prior to modifying the registry — and modifying the Active Directory database is much more dangerous than editing the registry. If you make a mistake when editing the registry, you can destroy Windows. If you make a mistake in Active Directory, you can destroy the whole thing, which potentially affects every system in your organization. Therefore, you should never underestimate the importance of a good backup.
by:blogs.techrepublic.com.com
1) Learn about endangered species in your area
Teach your friends and family about the wonderful wildlife, birds, fish and plants that live near you. The first step to protecting endangered species is learning about how interesting and important they are. Our natural world provides us with many indispensable services including clean air and water, food and medicinal sources, commercial, aesthetic and recreational benefits.
Check out our endangered species pages
For more information about endangered species, visit endangered.fws.gov
2) Visit a national wildlife refuge, park or other open space
These protected lands provide habitat to many native wildlife, birds, fish and plants. Scientists tell us the best way to protect endangered species is to protect the places where they live. Get involved by volunteering at your local nature center or wildlife refuge.
Go wildlife or bird watching in nearby parks. Wildlife related recreation creates millions of jobs and supports local businesses.
To find a wildlife refuge near you, visit www.fws.gov/refuges/
To find a park near you, visit www.nps.gov
To find a zoo near you, visit www.aza.org
3) Make your home wildlife friendly
Secure garbage in shelters or cans with locking lids, feed pets indoors and lock pet doors at night to avoid attracting wild animals into your home.
Reduce your use of water in your home and garden so that animals that live in or near water can have a better chance of survival.
Disinfect bird baths often to avoid disease transmission.
Place decals on windows to deter bird collisions. Millions of birds die every year because of collisions with windows. You can help reduce the number of collisions simply by placing decals on the windows in your home and office.
For more information on what you can do, check out these tips from the US Fish and Wildlife Service.
4) Provide habitat for wildlife by planting native vegetation in your yard
Native plants provide food and shelter for native wildlife. Attracting native insects like bees and butterflies can help pollinate your plants. The spread of non-native species has greatly impacted native populations around the world. Invasive species compete with native species for resources and habitat. They can even prey on native species directly, forcing native species towards extinction.
For more information about native plants, visit http://www.plantsocieties.org
5) Minimize use of herbicides and pesticides
Herbicides and pesticides may keep yards looking nice but they are in fact hazardous pollutants that affect wildlife at many levels. Many herbicides and pesticides take a long time to degrade and build up in the soils or throughout the food chain. Predators such as hawks, owls and coyotes can be harmed if they eat poisoned animals. Some groups of animals such as amphibians are particularly vulnerable to these chemical pollutants and suffer greatly as a result of the high levels of herbicides and pesticides in their habitat.
For alternatives to pesticides, visit http://www.beyondpesticides.org
6) Slow down when driving
Many animals live in developed areas and this means they must navigate a landscape full of human hazards. One of the biggest obstacles to wildlife living in developed areas is roads. Roads divide habitat and present a constant hazard to any animal attempting to cross from one side to the other. So when you’re out and about, slow down and keep an eye out for wildlife.
7) Recycle and buy sustainable products
Buy recycled paper, sustainable products like bamboo and Forest Stewardship Council wood products to protect forest species. Never buy furniture made from wood from rainforests.
Recycle your cell phones, because a mineral used in cell phones and other electronics is mined in gorilla habitat.
Minimize your use of palm oil because forests where tigers live are being cut down to plant palm plantations.
Never purchase products made from threatened or endangered species
Overseas trips can be exciting and fun, and everyone wants a souvenir. But sometimes the souvenirs are made from species nearing extinction. Avoid supporting the market in illegal wildlife including: tortoise-shell, ivory, coral. Also, be careful of products including fur from tigers, polar bears, sea otters and other endangered wildlife, crocodile skin, live monkeys or apes, most live birds including parrots, macaws, cockatoos and finches, some live snakes, turtles and lizards, some orchids, cacti and cycads, medicinal products made from rhinos, tiger or Asiatic black bear.
9) Report any harassment or shooting of threatened and endangered species
Harassing wildlife is cruel and illegal. Shooting, trapping, or forcing a threatened or endangered animal into captivity is also illegal and can lead to their extinction. Don’t participate in this activity, and report it as soon as you see it to your local state or federal wildlife enforcement office.
You can find a list of state wildlife departments at http://www.fws.gov/offices/statelinks.html
10) Protect wildlife habitat
Perhaps the greatest threat that faces many species is the widespread destruction of habitat. Scientists tell us the best way to protect endangered species is to protect the special places where they live. Wildlife must have places to find food, shelter and raise their young. Logging, oil and gas drilling, over-grazing and development all result habitat destruction. Endangered species habitat should be protected and these impacts minimized.
By protecting habitat, entire communities of animals and plants can be protected together. Parks, wildlife refuges, and other open space should be protected near your community. Open space also provides us with great places to visit and enjoy. Support wildlife habitat and open space protection in your community. When you are buying a house, consider your impact on wildlife habitat.
To get involved, contact the Endangered Species Coaltion staff.
or find a group near you on our ESC member organization list.
Thanks for caring about our nation’s wildlife and wild places!
by: stopextinction.org
How is thispossible? Well when a video has been removed from YouTube, it is not immediately deleted from their servers. Just like our hard drive. When we delete a file and empty the recycle bin, is it not really deleted. It is only marked as deleted and is ready to be overwritten. So if it is not being overwritten, we can still view the videos but of course not from youtube.com.
undelte youtube video
Viewing removed YouTube videos is easy. Here’s how to do it.
First of all, you need to know the Video ID which is at the end of the YouTube link. An example of a YouTube video link is http://www.youtube.com/watch?v=UzeV1Ux5YlI
The video ID for the link above is UzeV1Ux5YlI
Just copy and paste it in the ID text box and click view video. Here are a few sites that is able to play deleted YouTube videos. Surprisingly, they are all not the same. I’ve tested a deleted video ID on all 3 sites but one of it reported that it could not find deleted video. So if you desperately need to watch a deleted video, try on all of the sites and you might get to watch it.
A normal deleted youtube video viewer. Works well.
- This is a bit special compared to the other two because you are able to search for deleted YouTube video through the VideoID or YouTube User. If you know the user that uploaded the deleted video, you can search the user name.
did not like this site so much because there are full of advertisements. Before get to watch a video, I need to wait 4 seconds. Not only that, this is the site that couldn’t find the deleted youtube video that I am looking for.
Tera mera net ka piyar
Rim jhim rim jhim pare pohaar
Tera mera net ka piyar
Jhan jhan bajeen man k taar
Tera mera net ka piyar
Aye mere paas tue aise
Duur kabhi na jaye
Murjhayeen na khil k kaliyan
Asi bhi ruth aye
Aye na pat jhar rahe bahar
Tera mera net ka piyar
Aaa bachpan k bichre sathi
Kyun muj ko tarsaye
Umr guzari ro ro main ne
Kahye dair lagaye
Samne aaa ja phir ek bar
Tera mera net ka piyar
رم جھم رم جھم پرے پھوہاڑ
تيرا ميرا نيٹ کا پيار
جھن جھن باجيں من کے تار
تيرا ميرا نيٹ کا پيار
آئے ميرے پاس تو ايسے
دور کبھي نا جائے
مرجھائيں نا کھل کے کلياں
ایسي بھي رت آئے
آئے نا پت جھڑ رہے بہار
تيرا ميرا نيٹ کا پيار
آ بچپن کے بچھڑے ساتھي
کيوں مجھ کو ترسائے
عمر گزاري رو رو ميں نے
کاہے دير لگائے
سامنے آ جا پھر ايک بار
تيرا ميرا نيٹ کا پيار
اس درجہ عشق موجب رسوائي بن گيا
ميں آپ اپنے گھر کا تماشائي بن گيا
دير و حرم کي راہ سے بچ گيا مگر
تيري گلي کے موڑ پہ سودائي بن گيا
بزم وفا ميں آپ سے اک پل کا سامنا
ياد آ گيا تو عہد شناسائي بن گيا
بے ساختہ بکھر گئي جلوؤں کي کائنات
آئينہ ٹوٹ کر تیري انگڑائي بن گيا
ديکھي جو رقص کرتي ہوئي موج زندگي
ميرا خيال وقت کي شہنائي بن گيا
iss darja ishq mojab ruswai ban gaya
mein aap apnay ghar ka tamashayi ban gaya
dair o haram ki raah say bach gaya magar
teri gali kay more peh sodai ban gaya
bazm wafa mein aap say ik pal ka saamna
yaad aa gaya tou ehad shanasaai ban gaya
bay sakhta bikher gayi jloon ki kainaat
ainaa toot kar tari angrai ban gaya
dekhi jo raqs karti hui mouj zindagi
mera khayaal waqt ki shehnai ban gaya
A common question among newer Object-Oriented Programmers is “Why should I use and prefer to use getter and setter methods for my objects variables when I can simply set them as public?” For example, let’s consider the trivial object below:
[highlight=C++]class myObject
{
int myVar;
public:
myObject() : myVar(0)
{
}
int getMyVar()
{
return myVar;
}
void setMyVar(int x)
{
myVar = x;
}
};[/highlight]
It would appear to a casual observer, and could be pretty well argued, that there’s no need to have two methods just to set one variable and get one variable inside of an object, aside from the knee-jerk reaction to encapsulate everything. A public variable would accomplish the same goal, and would be far easier to read and write, like so:
[highlight=C++]class myObject
{
public:
int myVar;
myObject() : myVar(0)
{
}
};[/highlight]
To someone who hasn’t experienced any problems with this way of doing things, it may seem odd to want to write more unnecessary code when all this time we’ve been trying to find ways to avoid writing more code. The aforementioned way looks more computationally expensive, harder to understand, and completely unnecessary.
Well… no, it isn’t. Encapsulation is the basic principle that teaches us to always do this, but we’re not writing all of this just to appease the Encapsulation Police, we’re doing it for a very good reason, and that’s flexibility with our objects. I’m going to venture a proposition… never in the history of programming has there ever once been someone who completely wrote a non-trivial object and didn’t need to change it ever again. What I am saying is that I guarantee to you you’ll find yourself in situations where you’re going to need to change some internal mechanisms of an object to add functionality, or make it more efficient, or for any other assorted reason. I’ll now prove this to you.
Let’s continue to utilize the object above, but let’s say, for some reason, you need a new function that “rewinds” and “fast forwards” the returned value from getMyVar(), so you’ll need to keep some kind of internal mechanism as to how to rewind/FF it. Let’s also say that you need to keep count of how many times myVar was changed, as well as add a new overloaded constructor to allow the user to set any value as the initial value (instead of just 0).
[highlight=C++]class myObject
{
unsigned long tChanged;
bool looped;
std::vector<int> myVars;
std::vector<int>::iterator retNum, endPoint;
void setup(int x)
{
myVars.reserve(20);
myVars.push_back(x);
retNum = myVars.begin();
endPoint = myVars.end();
}
public:
myObject() : tChanged(0)
{
setup(0);
}
myObject(int x) : tChanged(0)
{
setup(x);
}
int getMyVar()
{
return *retNum;
}
/* I wanted to ensure I didn’t have to do any additional
dynamic memory allocation for this method in the case
of setMyVar being called more than 20 times, so I made
it so after the 20th call, setMyVar simply wrapped
around the vector and treated the first number as if
it were the 21st, but that means rewind can’t go further
back than 20 numbers. That’s okay. 
*/
void setMyVar(int x)
{
if (myVars.size() >= 20)
{
if (endPoint >= myVars.end())
{
endPoint = myVars.begin();
looped = true;
}
*endPoint = x;
++endPoint;
}
else
{
myVars.push_back(x);
endPoint = myVars.end();
}
retNum = endPoint – 1;
++tChanged;
}
void rewind()
{
if (retNum >= endPoint)
{
if (–retNum < endPoint)
retNum = endPoint;
}
else
{
if (–retNum < myVars.begin())
{
if (looped)
retNum = myVars.end() – 1;
else
retNum = myVars.begin();
}
}
}
void rewind(int x)
{
for (int iii = 0; iii < x; ++iii)
{
rewind();
}
}
void fastForward()
{
if (retNum < endPoint)
{
if (++retNum >= endPoint)
retNum = endPoint – 1;
}
else
{
if (++retNum >= myVars.end())
{
retNum = myVars.begin();
}
}
}
void fastForward(int x)
{
for (int iii = 0; iii < x; ++iii)
{
fastForward();
}
}
unsigned long getTimesChanged()
{
return tChanged;
}
};[/highlight]
As you can tell, this object has become much less trivial! But here’s the real advantage to using your getter/setter methods: Any other code you made that utilized the myClass object doesn’t have to change at all and it is still fully functional! While your getter and setter methods have wildly changed in implementation, and new methods have been added to the object, your older code that still used the old getter/setter methods will still be able to use this object exactly as if nothing had changed at all, and you won’t need to worry about updating your entire code base to reflect what could be only one or two changes in a single object! This is absolutely vital in any project with more than a few source code files, since tracking down individual changes can be a difficult and time-consuming task, as well as could produce many difficult to find, and fix, bugs!
When people talk about flexibility with code, and a need for abstraction, this is a great example of what they mean. While the ideas of encapsulation and abstraction extend far beyond this simple example, this is a very much real code example as to what’s going on, and why it is so important to do. Imagine if you had chose to instead go with a public variable that could be changed by any object, by doing so you’ve suddenly lost any flexibility to count the number of times that public variable has changed, or to extend the functionality of the object with that variable. You’ve lost a significant amount of versatility in your code, and through experience many developers have learned that this is the best way to go about things. That is why we use getter and setter methods!
To close, I want to address some of the challenges to getter/setter methods, and emphasize when using these methods is appropriate. Remember that divulging implementation details, such as what certain internal “has-a” objects contain, or what those objects are doing and what their states are, is a completely inappropriate use of getter/setter methods. Objects in themselves should be doing that kind of legwork, not the other objects using them. The article writer asserts that all getter/setter methods break encapsulation and provides no evidence of this supposedly obvious truth, but it doesn’t. The reason these methods exist is to maintain encapsulation, as I’ve just shown. The entire implementation can be changed in the object, and so long as there’s something to capture those get/set methods, then things will continue to work. Getter/Setter methods are intended to be part of the interface of an object, and part of it’s functionality, not an exposure to implementation details, and this distinction is important.
Hope this all helped!
.. I love to speak my mind, at the beginning I didn't agree with the idea of blogging because I am not a writer but I found later it is such a good way to vent... So let me say: welcome to my blog.
-
