telegram-crawler/data/instantview.telegram.org/rules.html
2021-04-24 12:40:10 +00:00

251 lines
20 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Contest Rules - Instant View</title>
<link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
<link rel="alternate icon" href="/favicon.ico?4" type="image/x-icon" />
<link href="/css/bootstrap.min.css?3" rel="stylesheet">
<link href="/css/bootstrap-extra.css?2" rel="stylesheet">
<link href="/css/telegram.css?212" rel="stylesheet">
<link href="/css/codemirror.css?1" rel="stylesheet">
<link href="/css/instantview.css?112" rel="stylesheet">
</head>
<body class="no-transition">
<header>
<div class="container">
<div class="row">
<div class="col-sm-12 col-lg-10 col-lg-offset-1">
<div class="header-wrap">
<div id="header-panel" class="header-panel">
<div class="header-breadcrumb header-breadcrumb-simple">
<ol id="breadcrumb" class="header-nav breadcrumb"><li class="iv-logo"><a href="/"><i class="iv-icon"></i><span class="iv-logo-title">Instant View</span></a></li><li class="active">Contest Rules</li></ol>
</div>
</div>
</div>
</div>
</div>
</div>
</header>
<main class="intro container">
<div class="row">
<div class="col-sm-3 col-sm-push-9 col-lg-offset-1 col-lg-3 col-lg-push-7">
<section class="nav-menu">
<ul class="nav nav-pills nav-stacked"><li><a href="/">Intro</a></li><li><a href="/templates">Templates</a></li><li><a href="/checklist">Checklist</a></li><li><a href="/contest/winners2017">2017 Contest Winners</a></li><li><a href="/contest/winners2019">2019 Contest Winners</a></li><li class="divider"></li><li><a href="/samples/">Sample Templates</a></li><li><a href="/my/" data-need-auth>My Templates</a></li><li><a href="/docs">Manual</a></li></ul>
<div class="nav-footer">
<a class="logged-link" href="/auth" data-need-auth>Login</a>
<span class="logged">
<span class="logged-label">Hello, anonymous&#33;</span>
</span>
</div>
</section>
</div>
<div class="col-sm-9 col-sm-pull-3 col-lg-7 col-lg-pull-3">
<div class="content">
<div id="dev_page_content_wrap" class=" ">
<div class="dev_page_bread_crumbs"></div>
<h1 id="dev_page_title">Template Competition Rules</h1>
<div id="dev_page_content"><!-- scroll_nav -->
<div class="dev_side_image">
<a href="/file/811140067/3/6oS3A6aSzxU.261217/1d6f75b81ed67c983a" target="_blank"><img src="/file/811140890/2/3WnXjPnynwU.52493/709f815bf5f24bff9c" title="Instant View Platform. Click for hi-res picture">
</a></div>
<p>We are holding a new <strong>$300,000+</strong> 2-month competition (4 Feb 2019 - 4 April 2019) to create <a href="/intro">Instant View Templates</a> for news websites and blogs, <strong>$100</strong> per template. Everyone is welcome to participate!</p>
<h3><a class="anchor-link" href="#goal"><i class="anchor-icon"></i></a><a class="anchor" name="goal"></a>Goal</h3>
<p>The goal of the competition is to use Telegram&#39;s <strong>Instant View Editor</strong> to create <a href="#criteria-for-a-good-template">perfect</a> <strong>Instant View templates</strong> for as many websites as possible from our <a href="https://instantview.telegram.org/contest">suggested domains list</a>.</p>
<p>Starting on <strong>February, 4</strong>, we will be adding <strong>500</strong> new domains to our <a href="https://instantview.telegram.org/contest">list of targets</a> approximately every <strong>10</strong> days. The contest will end when all of the <strong>3000+</strong> target domains get a <a href="#determining-winners">winning template</a>. We expect this to take <strong>2 months</strong>.</p>
<blockquote>
<p><a href="https://t.me/IVcontest">Subscribe to the IV contest channel »</a></p>
</blockquote>
<h3><a class="anchor-link" href="#prizes"><i class="anchor-icon"></i></a><a class="anchor" name="prizes"></a>Prizes</h3>
<p>The <strong>first person</strong> to submit a fully <a href="/checklist">valid and working template</a> for one of the websites on <a href="/contest">our list</a> gets <strong>$100</strong> for each website they conquered ahead of the others.<a href="#share-the-work-share-the-prize">*</a></p>
<p>The winner will be the person who creates the greatest number of <a href="/checklist">perfect templates</a> (without <a href="#finding-issues">valid issues</a>) that cover the largest number of domains from our <a href="https://instantview.telegram.org/contest">targets list</a>. The winner will be awarded <strong>$10,000</strong> in addition to the payout from their individual templates. For the second place, we will award a <strong>$5,000</strong> prize on top of the payouts for the individual templates. </p>
<h3><a class="anchor-link" href="#how-to-submit"><i class="anchor-icon"></i></a><a class="anchor" name="how-to-submit"></a>How to submit?</h3>
<p>You can submit your template to the contest as soon as it covers a sufficient number of articles. Make sure you&#39;ve enabled <a href="https://instantview.telegram.org/#tracking-changes"><strong>Track Changes</strong></a> for at least <strong>10-15</strong> different pages on the target website and all IV pages are generated correctly. </p>
<p>When ready, simply tap <strong>Submit to Contest</strong> next to a template in <a href="/my">My Templates</a> section:</p>
<div class="blog_image_wrap">
<a href="/file/811140021/2/zZEvkMN8bHI.15429/e7369f84b0e449b2ad" target="_blank"><img src="/file/811140021/2/zZEvkMN8bHI.15429/e7369f84b0e449b2ad" title="Submit button"/></a>
<p>Submit to Contest from My Templates</p> </div>
<p>We <strong>strongly recommend</strong> that you make sure that your template satisfies all the criteria for a <a href="/checklist">perfect template</a> before you submit. If you revoke your template to make any adjustments and resubmit it later, the template will lose its place at the top of the list. You could still win in case all the templates that were submitted before your fix also have valid issues, but it&#39;s better not to take chances.</p>
<p>For the same reason, if you see that your template has some issues, it is best to fix them and resubmit as soon as possible.</p>
<h3><a class="anchor-link" href="#finding-issues"><i class="anchor-icon"></i></a><a class="anchor" name="finding-issues"></a>Finding issues</h3>
<p><strong>Anyone</strong> can check the results (but not the code) of any templates that were submitted for the contest. This means you can take a couple of links and see if a template processes them correctly into perfect Instant View pages (<a href="/checklist">see detailed criteria here</a>).</p>
<p>If you see any issues, report them using the <strong>Report Issue</strong> button. Click to select and highlight incorrectly parsed blocks in the source page or in the Instant View result and provide a detailed explanation of what is wrong (check the <a href="#criteria-for-a-good-template">general criteria</a> and <a href="/checklist">detailed rules</a>). The author of the template will be able to see all issues, fix and resubmit their work. Note that it is the date of the <strong>latest resubmission</strong> that counts for the purposes of determining the winner.</p>
<h3><a class="anchor-link" href="#determining-winners"><i class="anchor-icon"></i></a><a class="anchor" name="determining-winners"></a>Determining winners</h3>
<p>The contest for each individual domain from the list of targets begins when the first corresponding IV template is published. The earliest submitted template is considered the <strong>winning candidate</strong> and participants get <strong>three days</strong> (72 hours) to find valid <a href="#finding-issues">issues</a> with that template. </p>
<p><strong>Telegram arbiters</strong> will check all issues, accept valid ones and decline non-issues and duplicates. If the winning candidate is rejected, the second-earliest submitted template takes its place.</p>
<p>If the reporting period ends with no valid issues accepted on the leading template, participants <strong>may no longer create new issues</strong> for that template. They still can and should create issues on any other templates which were submitted less than 72 hours ago. </p>
<p>Arbiters will perform a <strong>final check</strong> on all remaining issues for the domain they may also create and accept <strong>new issues</strong> of their own. If arbiters find no valid issues with the template, it is declared the <strong>winner</strong>.</p>
<h3><a class="anchor-link" href="#fallen-leaders"><i class="anchor-icon"></i></a><a class="anchor" name="fallen-leaders"></a>Fallen leaders</h3>
<p>If the leading template is <strong>rejected</strong> as a result of the <a href="#determining-winners">final check</a>, the contest is <strong>reopened</strong> and participants may submit issues again.</p>
<blockquote>
<p>Note that the 72-hour reporting period is always calculated from the moment when the template was <strong>submitted</strong>. This means that if there are two templates for a domain submitted at the same time, and the leading one falls, the second one has the potential to win instantly, if the arbiters find no issues with it. It is important to submit issues for all templates, not just the currently winning one. </p>
</blockquote>
<p>If as a result of this process all templates are rejected because none of them was able to achieve <a href="/checklist">perfection</a>, the contest for the domain starts again as soon as a new template is submitted. In some circumstances, Telegram may decide that the domain is unsuitable for IV and remove it from the contest.</p>
<h3><a class="anchor-link" href="#share-the-work-share-the-prize"><i class="anchor-icon"></i></a><a class="anchor" name="share-the-work-share-the-prize"></a>Share the work — share the prize</h3>
<p>When a template wins the competition for a particular domain, the users who helped the author to identify and fix issues will get a <strong>share</strong> of the prize at the end of the contest. We will award <strong>$2</strong> per each of the 25 most recently submitted valid issues. This money (up to $50 per winning template) will be deducted from the template author&#39;s reward.</p>
<p> This way, if a template wins after other users found many issues with it, the author may get only <strong>$50</strong> and the rest will be distributed among their helpers. Authors who submitted <a href="/checklist">perfect templates</a> right away will get the entire <strong>$100</strong> for each of their templates when they win.</p>
<h3><a class="anchor-link" href="#receiving-rewards"><i class="anchor-icon"></i></a><a class="anchor" name="receiving-rewards"></a>Receiving rewards</h3>
<p>Rewards will be paid out after the contest ends when all target domains are either declared unsuitable for IV or get a perfect template. We aim at completing the contest within approximately <strong>2 months</strong>.</p>
<p>For operational purposes, payouts to both template makers and their helpers who identified issues start at <strong>$200</strong>. Note that rewards <strong>below $200</strong> earned in the <strong>First Instant View Contest</strong> count towards the minimum limit in this <strong>Second Contest</strong>.</p>
<h3><a class="anchor-link" href="#criteria-for-a-good-template"><i class="anchor-icon"></i></a><a class="anchor" name="criteria-for-a-good-template"></a>Criteria for a good template</h3>
<blockquote>
<p>For more info on templates, see our <a href="/">Introduction</a> and <a href="/samples/">Sample Templates</a>.</p>
</blockquote>
<p>To be considered in the competition, the template must fulfil at least these five basic requirements:</p>
<h4><a class="anchor-link" href="#1-ivs-must-only-be-generated-for-pages-that-need-them"><i class="anchor-icon"></i></a><a class="anchor" name="1-ivs-must-only-be-generated-for-pages-that-need-them"></a>1. IVs must only be generated for pages that need them</h4>
<p>Instant View pages work best with relatively static articles. Dynamic pages, such as the main page of a news site that contains ever-changing lists of links to new articles, would hardly benefit from the IV treatment.</p>
<p>You must make sure that your template <strong>only</strong> generates IV pages for articles and does not affect service areas of the website, as well as any other sections unsuitable for IV. You must also make sure that IV pages are <strong>not</strong> generated for articles that have content that is not supported in IV. If such a page were generated, it would result in unacceptable loss of information (e.g., IV pages dont support dynamic maps — if you generate an IV page for a wiki article that consists of a dynamic map, the user wont see any useful info from the article).</p>
<p>Your template <strong>must</strong> have successfully passed automatic checks on at least 10-15 URLs from the target domain. Read more about automatic checks and <a href="https://instantview.telegram.org/#tracking-changes">tracking changes</a>.</p>
<h4><a class="anchor-link" href="#2-all-essential-content-must-be-represented"><i class="anchor-icon"></i></a><a class="anchor" name="2-all-essential-content-must-be-represented"></a>2. All essential content must be represented</h4>
<p>Your IV page should show the entire text of the article, along with all the headings and subheadings, quotes, cover and other photos, videos, and other kinds of embedded content from the source page.</p>
<h4><a class="anchor-link" href="#3-unnecessary-elements-must-be-eliminated"><i class="anchor-icon"></i></a><a class="anchor" name="3-unnecessary-elements-must-be-eliminated"></a>3. Unnecessary elements must be eliminated</h4>
<p>Your IV page must display the pure content of the source. Remove any bits of interface, ads, and any irrelevant embedded content. </p>
<h4><a class="anchor-link" href="#4-template-must-process-any-of-the-pages-it-covers"><i class="anchor-icon"></i></a><a class="anchor" name="4-template-must-process-any-of-the-pages-it-covers"></a>4. Template must process any of the pages it covers</h4>
<p>Check whether pages with irregular elements are processed correctly. Pay special attention that various types of media, embedded elements, quotes, and separators are all displayed nicely. Check at least 10-15 different links before submitting your template to the competition.</p>
<h4><a class="anchor-link" href="#5-no-extraneous-info-may-be-added"><i class="anchor-icon"></i></a><a class="anchor" name="5-no-extraneous-info-may-be-added"></a>5. No extraneous info may be added</h4>
<p>Any attempts to add content that is not present on the original page will lead to the rejection of the template.</p>
<p>It is allowed to assign the username of the <strong>official</strong> channel of the website that published the article to the <a href="https://instantview.telegram.org/docs#instant-view-format">channel property</a>. To be considered official, the channel must be named as such by the relevant company or person (on the website itself or on social media).</p>
<hr>
<h3><a class="anchor-link" href="#perfect-templates"><i class="anchor-icon"></i></a><a class="anchor" name="perfect-templates"></a>Perfect Templates</h3>
<p>What&#39;s listed <a href="#criteria-for-a-good-template">above</a> are the general guidelines. If you&#39;re looking for more precise information on what a <strong>perfect template</strong> is (and is not), see the <a href="/checklist">Perfect Template Checklist</a>.</p>
</div>
</div>
</div>
</div>
</div>
</main><div class="popup-container login-popup-container hide" id="login-popup-container">
<div class="popup">
<div class="popup-body">
<section>
<h2>Log In</h2>
<p>Log in here to create Instant View templates. Please enter your <b>phone number</b> in the <a target="_blank" rel="noopener" href="https://telegram.org/faq#login-and-sms">international format</a> and we will send a confirmation message to your account via Telegram.</p>
<div id="login-alert"></div>
<form id="send-form" class="login-form" onsubmit="return requestConfirmation(event);">
<div class="form-group">
<input type="tel" class="form-control iv-form-control input-lg" id="login-phone" placeholder="+12223334455" autocomplete="off"/>
</div>
<div class="popup-buttons">
<a class="btn btn-link btn-lg login-cancel-btn">Cancel</a><!--
--><button type="submit" class="btn btn-link btn-lg">Next</button>
</div>
</form>
<div id="login-form" class="hide">
<div class="form-group">
<span class="form-control iv-form-control input input-lg input-disabled"><strong id="login-phone-field"></strong> (<a class="login-back" href="/auth">Incorrect?</a>)</span>
<p class="help-block dots-animated">We&#39;ve just sent you a message.<br/>Please confirm access via Telegram</p>
</div>
<div class="popup-buttons">
<a class="btn btn-link btn-lg login-cancel-btn">Cancel</a><!--
--><a class="btn btn-link btn-lg login-back">Back</a>
</div>
</div>
</section>
</div>
</div>
</div>
<script src="/js/jquery.min.js?1"></script>
<script src="/js/bootstrap.min.js"></script>
<script src="/js/main.js?42"></script>
<script src="/js/codemirror/codemirror.js?1"></script>
<script src="/js/codemirror/simple.js?1"></script>
<script src="/js/codemirror/runmode.js?1"></script>
<script src="/js/codemirror-instantview.js?21"></script>
<script src="/js/instantview.js?71"></script>
<script>$(window).resize(updateNavBar);updateNavBar();
window.initDevPageNav&&initDevPageNav();
$("pre").addClass("cm-s-default").each(function(){CodeMirror.runMode($(this).text(),"instantview",this);});
function showLoginError(error_text) {
$('#login-alert').html('<div class="alert alert-danger"> <a class="close" data-dismiss="alert" href="#">×</a>' + error_text + ' </div>').show();
}
function requestConfirmation(event) {
event.preventDefault();
$('#login-alert').hide();
var phone = $('#login-phone').val();
$.ajax({
type: 'POST',
url: '/auth/request',
data: {
phone: phone
},
success: function(result) {
$('#login-phone-field').text(phone);
$('#send-form').addClass('hide');
$('#login-form').removeClass('hide');
checkAuth(result.temp_session);
},
error: function(xhr) {
showLoginError(xhr.responseText || 'Server error');
},
dataType: 'json'
});
return false;
}
function cancelConfirmation(event) {
event && event.preventDefault();
$('#login-alert').hide();
$('#login-phone-field').text('');
$('#send-form').removeClass('hide');
$('#login-form').addClass('hide');
$('#login-phone').focus();
clearTimeout(window.authTimeout);
return false;
}
function checkAuth(temp_session) {
clearTimeout(window.authTimeout);
window.authTimeout = setTimeout(function doCheckAuth() {
$.ajax({
type: 'POST',
url: '/auth/login',
data: {
temp_session: temp_session
},
success: function(result) {
if (result) {
location.reload();
} else {
checkAuth(temp_session);
}
},
error: function (xhr) {
showLoginError(xhr.responseText || 'Server error');
},
dataType: 'json'
});
}, 700);
}
$('#login-popup-container').on('popup:open', function() {
$('#login-phone').focus();
});
$('#login-popup-container').on('popup:close', function() {
cancelConfirmation();
if (location.pathname == '/auth') {
window.history && history.replaceState(null, null, '/');
}
});
App.unauth = true;
$('a[data-need-auth]').click(function(e) {
e.preventDefault();
openPopup('#login-popup-container');
});
$('#login-popup-container .login-cancel-btn').click(function(e) {
e.preventDefault();
closePopup('#login-popup-container');
});
$('.login-back').click(cancelConfirmation);
</script>
</body>
</html>