Skip to main content

DMCA

Digital Millenium Copyright Act Policy (DMCA) 

It is my policy to respond to clear notices of alleged copyright infringement. If you believe that your intellectual property rights have been infringed upon by one of our users, I need you to send us a proper notification. All notices should comply with the notification requirements of the DMCA. You MUST provide the following information:

1. Identify yourself as either: - The owner of a copyrighted work(s), or - A person “authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.”

2. Identify the copyrighted work claimed to have been infringed. 

3. Identify the material that is claimed to be infringing or to be the subject of the infringing activity and that is to be removed or access to which is to be disabled by providing me the exact location of the infringing file with the exact link

4. Provide me the web address under which the link has been published. 

5. Provide your contact information which includes, your full name, address, and telephone number. 

You should be aware that, under the DMCA, claimants who make misrepresentations concerning copyright infringement may be liable for damages incurred as a result of the removal or blocking of the material, court costs, and attorney fees.

A proper notification MUST contain the information above, or it may be IGNORED. You should also be aware that I cannot delete Stream and Files on hosts such as YouTube and other Dedicated Servers etc.

Send notifications to yasin.buet@gmail.com

Please allow up to 2-3 business days for an email response. Thank you for your understanding.


Comments

Most Loved Posts

Threadpool - A deadly poison wait for SQL Server (The What, When and How)

Introduction  Threadpool is a  poison  wait. Yes, I mean it. Its poison for SQL Server, its poison for the Business and of course, the end-users! The most devastating thing about threadpool is you hardly recognize it because it comes in disguise, meaning you see no memory or cpu pressure in the system, yet you cannot run any query, it seems like your SQL Server is frozen solid. That scary, isn't it?

How to configure your Availability Group listener to ASP.NET

SQL Server’s availability group Always On feature is great to have features for your Database. Anytime one of your database nodes goes down, your secondary replica will automatically take over. After a failover, your secondary cluster node becomes the primary cluster. Now the question arises, “Do I need to configure my APP server connectionstring each time I face a failover cluster?”. The answer is NO, you don’t have to configure your app server connectionstring every time. Default ConnectionString By default, your App server connectionstring looks something like this – <connectionStrings>    <add name="ConnStringDb1" connectionString="Data Source=localhost;Initial Catalog=YourDataBaseName;Integrated Security=True;" providerName="System.Data.SqlClient" />   </connectionStrings> ConnectionString for Failover Partner You can manually specify the failover partner in your connectionstring like this <connectionStrings>     <a...