I'm building a system to control where my company's ads are placed. Amongst our concerns are potentially malicious code on the target page. Is there any library / database / system that can detect this content and is either open source or free?
~downer
In this case, you could look at Google's Safe Browsing API:
Single search:
http://www.google.com/safebrowsing/diagnostic?site=www.example.com
Signup for API key:
http://code.google.com/apis/safebrowsing/key_signup.html
From what I understand, you just want to make sure that your company's ad does not appear on the pages that are serving malware/spyware.
As mentioned earlier, google api can be used for querying Safebrowsing database. Also, if the marketing company who is going to be running your campaign can provide you the the list of target pages, you can additionally use McAfee Site advisor. Two checks are better than one.
Site Advisor: http://www.siteadvisor.com/websecurity/index.html
Related
I want to build an HTML, CSS, and Js for my home page and my landing pages and a Shopify store for my product pages but I want to be on the same domain so that the flow doesn't break and my SEO and analytics be more precise.
How can I achieve that?
I would venture that you have two options (there may be more, but these popped in my head first):
Create a subdomain of your primary domain. This wouldn't mess with your current domain's SEO and you may actually see benefits from future SEO since the two are connected by a common domain. I know search engines treat subs as their own, but your sites will be driving traffic between each other and this would keep your customers within your overall domain.
Create a page/series of pages under your primary domain with pictures and Shopify buttons for each item. This is highly redundant and, frankly, a waste of time and energy, but I am putting it out there, nonetheless.
Use the Buy button SDK over your main content website to append the product from Shopify and utilize the Shopify cart functionalities.
I think this is the best option when you want to have a separate website along with Shopify, its cost is lower than the regular Shopify plan.
Here are some links:
buy Button
Documentation
Shopify Lite
Storefront API with Checkout API also provide all the power of Shopify to those that do not want to host on the Shopify online store platform. Would suit your use case fine it seems.
I'm currently trying to place the docusign console onto my website. My current method is using an iFrame but I'm wondering if that is secure and the optimal way of doing it. I was also wondering if the docusignAPI has a solution to that implemented already because I couldn't find one after playing around on the website with various code sources.
Preferably, users would be able to go to some part of the website, view the contract or document they need to sign on the website without having the leave the website. This includes viewing the document on the website as well such as using an iFrame allows.
Using iframes to host DocuSign embedded signing is not a good idea for a few reasons.
Typically to have a good experience it is recommended to use a large window.
Security Concerns. The users of your app wouldn't be able to see the DocuSign URL as well as the green check to know they're using a secure website which should make them feel more confident about using your integration.
I'm new to web development, and I'm currently making a presentation website(home, services, news, vacancies) for a small company. I'm using Node.js,Express and MongoDB.
The client wants to manage certain content on the website, therefore there needs to be a dashboard, where only admins could login/register. But website design does not provide any login/registration system for users.
The question is, where do I put a dashboard and how should I hide it from ordinary users? Should I just use url, like mysite.com/admin, which should be typed by the admin, whenever he wants to get to the admin login/dashboard zone(it seems quite unsafe, since everybody on the internet could type that and get to the login form)? Or maybe I should make a separate desktop app for managing website content?
How should I approach this problem, what are the best practices?
Thanks!
You don't need to reinvent the wheel as i think you can first explore CMS systems and check if the tools covers your requirement . Since CMS tools brings in lot of website admin capabilities as out of the box features.
Following links will get you started.
https://en.wikipedia.org/wiki/Content_management_system
https://en.wikipedia.org/wiki/Web_content_management_system
So, apparently I need to provide a Privacy Policy URL for my Instagram application.
The only reason I'm using this application, is for a website I built for a client of mine. The client wanted an automatic integration for her Instagram, so I went through the whole Instagram API hassle.
Now, the website is ready for production, so I wanted to get my app out of sandbox mode, but it looks like I need this Privacy Policy URL.
What's the best way to go about this?
Put a Privacy Policy page up on their website (really any website you can link to) and use that link. It can be a static HTML page, as long as you can link to it.
Instagram won't let you take an application like this out of Sandbox, btw. Your use case is not an approved use case. From Instagram's Developer Documentation under Invalid Use Cases:
One-off Projects. If you are an agency building websites or other integrations, note that we don't grant permissions to clients created for one-off projects. If you are interested in building a product, platform, or widget that will be used as a service across multiple projects, then you may submit a single client_id that you can use across multiple projects.
You can (probably) still achieve the outcome you're looking for but you will need to go back to the drawing board and rethink your application's use case before getting out of the Sandbox. I know some developers who really just don't understand (or care to understand) the policies and never make it out of Sandbox. It's a shame because they can read the technical portions of the documentation so easily but just can't/don't read/understand the more critical parts (like the Invalid Use Cases section).
I'm investigating the possibility of re-using Google Apps/Docs in a local hybrid desktop/browser application.
I've been going through the Google documentation on manipulating docs, eg. the Spreadsheet. I can't seem to find any info on actually hosting the UI. Is this possible, or does it require some form of permission from Google?
You want to basically embed an browser control in your application pointed at the URL of a Google Apps doc? You could use the Google Document List API to retrieve the documents for a user, then use the URLs of those documents in your embedded browser control.
You don't need Google's permission to do that; you're writing a browser with some extra smarts built in.
What do you mean by "hosting the UI?" These apps are HTML/CSS/JavaScript. Are you thinking about embedding them in AIR or Titanium, or in some kind of web control in another app?
i briefly looked into doing this, and figured if i really wanted to i could just load the gdocs page content dynamically, and use javascript to strip away the superflous elements like header and footer. but instead i'll probably just use an OS alternate because they have come a long way and I want rich hooks.