Protection x Freedom - Paid Sources

Asked

Viewed 79 times

1

We know that when a site decides to use a paid source on its site, it seeks design and at the same time differentiation.

But in order for the user to see the source at work on the page, the developer must somehow declare to the client to download it to thus view the source in behavior.

With that, do paid sources become free? Since somehow it is exposed to present to the client and allow the browser to display it in action..

Or, there are techniques to inhibit other people from capturing these sources, maybe something with Javascript, HTTP technique to inhibit other hosts,...?

  • Post an example site where you can’t find the source. this will remove all your doubts http://imasters.com.br/artigo/20429/css/font-face-typografia-sem-restricoes-na-web/

  • I will read, but beforehand I leave the site as an example, that by researching is paid and I did not find how to pick up the site.. http://viverdeblog.com -> Freight-sans-pro

  • http://goo.gl/myjO4z just press F12 and then Ctrl F + "Freight-sans-pro", your question is outside the programming scope.

  • Apparently this site uses a URL to capture the source, but the error is 403 when accessing, maybe it is a permission that only the site has with it and visitors.. as if it were a way for us not to catch the source, it can only be that in my view..

  • I have a question about the protection of paid fonts, it involves CSS and maybe even Javascript for protection of it with some technique, why outside the scope? I think I miswrote my topic..

No answers

Browser other questions tagged

You are not signed in. Login or sign up in order to post.