mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2024-11-28 19:23:11 +01:00
340 lines
23 KiB
HTML
340 lines
23 KiB
HTML
<!DOCTYPE html>
|
||
<html>
|
||
<head>
|
||
<meta charset="utf-8">
|
||
<title>Telegram Support Force</title>
|
||
<meta name="twitter:card" content="summary"></meta>
|
||
<meta property="og:title" content="TSF BIOS">
|
||
<meta property="og:image" content="7d623d30a6afa5abe9">
|
||
<meta property="og:description" content="This page will help you navigate our docs and interfaces in any situation.
|
||
It will only be of interest to TSF members.…">
|
||
|
||
<link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
|
||
<link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
|
||
<link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
|
||
<link rel="icon" type="image/png" sizes="16x16" href="/img/favicon-16x16.png">
|
||
<link rel="alternate icon" href="/img/favicon.ico" type="image/x-icon" />
|
||
<script>document.cookie="stel_dt="+encodeURIComponent((new Date).getTimezoneOffset())+";path=/;max-age=31536000;samesite=None;secure"</script>
|
||
|
||
<link href="//telegram.org/css/font-roboto.css?1" rel="stylesheet" type="text/css">
|
||
<link href="//telegram.org/css/bootstrap.min.css?3" rel="stylesheet">
|
||
<link href="//telegram.org/css/bootstrap-extra.css?2" rel="stylesheet">
|
||
<link href="/css/telegram.css?234" rel="stylesheet">
|
||
<link href="/css/tsf.css?7" rel="stylesheet">
|
||
<link href="/css/jquery-ui.min.css?1" rel="stylesheet">
|
||
<link href="/css/health.css?136" rel="stylesheet">
|
||
<link href="/css/tchart.min.css?10" rel="stylesheet">
|
||
<link href="/css/billboard.css?17" rel="stylesheet">
|
||
|
||
</head>
|
||
<body class="emoji_image no-transition">
|
||
|
||
<div id="aj_progress" class="progress-bar"></div>
|
||
|
||
<div id="aj_content"><div class="tr-container">
|
||
<header>
|
||
<div class="container">
|
||
<div class="header-wrap">
|
||
<div id="header-panel" class="header-panel">
|
||
<div class="header-auth">
|
||
<div class="header-auth-item"><a class="header-search-btn"></a></div><div class="header-auth-item"><a class="header-auth-link login-link" href="/auth">Login</a></div>
|
||
</div>
|
||
<div class="header-breadcrumb header-breadcrumb-simple">
|
||
<ol id="breadcrumb" class="header-nav breadcrumb"><li><a href="/">Telegram Support Force</a></li></ol>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</header>
|
||
<main class="container">
|
||
<nav class="tr-menu">
|
||
<div class="tr-menu-section">
|
||
<div class="tr-menu-header">
|
||
<div class="tr-menu-header-label">Resources</div>
|
||
</div>
|
||
<ul class="tr-menu-items"><li>
|
||
<a class="tr-menu-item" href="/">
|
||
<span class="nav-label">Introduction</span>
|
||
</a>
|
||
</li><li class="active">
|
||
<a class="tr-menu-item" href="/manuals">
|
||
<span class="nav-label">Manuals</span>
|
||
</a>
|
||
</li></ul>
|
||
</div>
|
||
|
||
|
||
</nav>
|
||
<section class="content clearfix">
|
||
<section class="tr-content"><div id="dev_page_content_wrap" class=" ">
|
||
<div class="dev_page_bread_crumbs"><ul class="breadcrumb clearfix"><li><a href="/" >Telegram Support Initiative</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/manuals" >Manuals</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/manuals/bios" >TSF BIOS</a></li></ul></div>
|
||
<h1 id="dev_page_title">TSF BIOS</h1>
|
||
|
||
<div id="dev_page_content"><!-- scroll_nav -->
|
||
|
||
<blockquote>
|
||
<p>This page will help you navigate our docs and interfaces in any situation.<br>It will only be of interest to TSF members. Here's how you <a href="/">become one</a>.</p>
|
||
</blockquote>
|
||
<h3><a class="anchor-link" href="#1-getting-started"><i class="anchor-icon"></i></a><a class="anchor" name="1-getting-started"></a>1. Getting started</h3>
|
||
<p><a href="/manuals/answering_questions">Answering Questions</a> is our constitution. Come back to it anytime you're in doubt.</p>
|
||
<ol>
|
||
<li>Our <a href="/manuals/answering_questions#general">creed</a> and <a href="/manuals/answering_questions#the-result">goals</a></li>
|
||
<li><a href="/manuals/answering_questions#what-if-i-don-39t-know-the-answer">I don't know the answer</a></li>
|
||
<li><a href="/manuals/answering_questions#chatting">User wants to chat</a></li>
|
||
<li><a href="/manuals/answering_questions#real-life-problems">User has real life problems</a></li>
|
||
<li><a href="/manuals/answering_questions#insults">User is insulting me</a></li>
|
||
</ol>
|
||
<p>The <strong>TSupport client</strong> is your rifle.<br>Learn all its <a href="https://bugs.telegram.org/c/554"><strong>features</strong></a>, and use an up to date template file. </p>
|
||
<h4><a class="anchor-link" href="#1a-asking-teammates-for-help"><i class="anchor-icon"></i></a><a class="anchor" name="1a-asking-teammates-for-help"></a>1a. Asking teammates for help</h4>
|
||
<p>Never hesitate to ask for help in your local TSF group. But remember: Not everyone in your group uses the same support account and speaks the same languages as you. When you want to ask something:</p>
|
||
<ol>
|
||
<li>Write a <strong>summary</strong> of the user's question in one message (don't copy-paste, be brief)</li>
|
||
<li>Always use <strong>English</strong> (there are team members in your group who don't speak your language)</li>
|
||
<li>Always include the entire <strong>footer</strong> from the question (all hashtags)</li>
|
||
</ol>
|
||
<h4><a class="anchor-link" href="#1b-coming-back-from-the-dead"><i class="anchor-icon"></i></a><a class="anchor" name="1b-coming-back-from-the-dead"></a>1b. Coming back from the dead</h4>
|
||
<p>If you notice that you haven't answered any questions lately, go read the <a href="/manuals/come-and-go">Coming and Going</a> manual.</p>
|
||
<h3><a class="anchor-link" href="#2-tracing-your-progress"><i class="anchor-icon"></i></a><a class="anchor" name="2-tracing-your-progress"></a>2. Tracing your progress</h3>
|
||
<p>You can check our <a href="/">TSF Panel</a> to see your stats and how you compare against other TSF members. You can also add a little TSF Bio in the panel, so that others know more about you, what you like, what you do, what devices you have and what languages you can speak.</p>
|
||
<h3><a class="anchor-link" href="#3-basic-questions"><i class="anchor-icon"></i></a><a class="anchor" name="3-basic-questions"></a>3. Basic questions</h3>
|
||
<p>You should be able to handle these easily. Here's where you find information:</p>
|
||
<ol>
|
||
<li><a href="https://telegram.org/faq">FAQ</a></li>
|
||
<li><a href="https://bugs.telegram.org/kb">Knowledge Base</a></li>
|
||
<li><a href="https://bugs.telegram.org/c/563">App comparison table</a></li>
|
||
<li><a href="https://translations.telegram.org">Screenshots</a> (Translations Platform)</li>
|
||
<li><a href="http://data.telegram.wiki/tl_general_en.txt">Answer templates</a> (wiki)</li>
|
||
<li><a href="https://telegram.org/press">Articles about Telegram in the media</a></li>
|
||
</ol>
|
||
<p>Whenever you learn something that was not in the docs,<br>make sure that this new info <strong>finds</strong> its way into the docs!</p>
|
||
<h3><a class="anchor-link" href="#4-bug-reports"><i class="anchor-icon"></i></a><a class="anchor" name="4-bug-reports"></a>4. Bug reports</h3>
|
||
<p>Ask in your local group if anything is not clear. Use the <a href="https://bugs.telegram.org/c/549">bug report groups</a> if you need to test things on devices you don't have.</p>
|
||
<ol>
|
||
<li><a href="/manuals/answering_questions#reporting-bugs-in-telegram">Reporting bugs</a> from <strong>Answering Questions</strong></li>
|
||
<li><a href="/manuals/bugs">Bug Handling Manual</a></li>
|
||
<li><a href="/manuals/bug_hunting">Investigating Bugs</a></li>
|
||
<li><a href="https://bugs.telegram.org/c/452">Bug Platform Lore</a></li>
|
||
</ol>
|
||
<h3><a class="anchor-link" href="#5-user-suggestions"><i class="anchor-icon"></i></a><a class="anchor" name="5-user-suggestions"></a>5. User suggestions</h3>
|
||
<p>Search the bug tracker (it could be a bug, a feature or a known suggestion). You can submit a suggestion yourself — please use common sense and the feature philosophy.</p>
|
||
<ol>
|
||
<li><a href="/manuals/answering_questions#handling-user-suggestions">Handling user suggestions</a> from <strong>Answering Questions</strong></li>
|
||
<li><a href="/manuals/feature_philosophy">Feature philosophy</a></li>
|
||
<li><a href="https://suggestions.telegram.org/">Suggestions Platform</a></li>
|
||
</ol>
|
||
<h3><a class="anchor-link" href="#6-projects-and-suggestions-for-the-tsf"><i class="anchor-icon"></i></a><a class="anchor" name="6-projects-and-suggestions-for-the-tsf"></a>6. Projects and suggestions for the TSF</h3>
|
||
<p>The Telegram Support Force is full of brilliant and creative people, and there are many more useful things that can be done besides answering questions. Global events are announcements in our notifications chat, and you can also start your own projects together with interested teammates.</p>
|
||
<p>If you have suggestions and ideas for the general workings of the TSF, our internal communication, manuals, templates, interfaces, tools and so on, don't hesitate to contact Markus or Daria about it. Oh, and: Rude frescoes. If you have no idea what this last thing was about, read on to the end of this document.</p>
|
||
<!--
|
||
If you're interested in doing more, check out the TSF Projects board where you'll find a list of currently active projects initiated by our TSF members. Find one to your liking or just [sign up](https://trello.com/c/Km5faOdu/2-how-can-i-help) to be notified when something that requires your skills is going on.
|
||
|
||
The list of projects is not very long for now, but we're working on adding more. If you have an idea for a project, see [this card](https://trello.com/c/ktEz53WR/38-what-if-i-have-a-project-idea).
|
||
-->
|
||
|
||
<blockquote>
|
||
<p><strong>WARNING:</strong> If you've just joined the TSF and are still figuring out what's going on, we'd suggest not to get too involved with things like side projects. It's a better idea to first get comfortable with answering user questions before you spread out.</p>
|
||
</blockquote>
|
||
<h3><a class="anchor-link" href="#7-security-questions"><i class="anchor-icon"></i></a><a class="anchor" name="7-security-questions"></a>7. Security questions</h3>
|
||
<p>Stick to the FAQ in case of ordinary users. <strong>Always</strong> consult Markus (unless the matter is fully covered in the Bestiary). If Markus is not available at the moment, ask in your local group. Don't be afraid to tell an advanced user that you are not a specialist — you don't have to be.</p>
|
||
<ol>
|
||
<li>Ask users for the source of their doubts, most likely you'll get a link</li>
|
||
<li><a href="/techfaq">Advanced FAQ</a> gives more info about MTProto for advanced users.</li>
|
||
<li>Advanced concerns and questions should be mailed to <strong>security@telegram.org</strong></li>
|
||
</ol>
|
||
<!--
|
||
To use trello search for links, remove the http(s):// part. E.g.:
|
||
|
||
<div>
|
||
<a href="/file/811140900/1/MFYP2Cb7EC0/1741dcf258433dd879" target="_blank"><img src="/file/811140900/1/MFYP2Cb7EC0/1741dcf258433dd879" title="Screenshot_44.png, 16.6Kb" class="dev_page_image" /></a>
|
||
</div>
|
||
|
||
Trello search is not perfect for links even this way, so may be a good idea to take a personal look at the Bestiary if the search doesn't return anything. New links for problems that are covered in the Bestiary should be added to the relevant cards.
|
||
-->
|
||
|
||
<h3><a class="anchor-link" href="#8-new-language-requests"><i class="anchor-icon"></i></a><a class="anchor" name="8-new-language-requests"></a>8. New language requests</h3>
|
||
<p>Anyone can use the <a href="https://translations.telegram.org">Translation platform</a> to suggest improvements to our current translations — or create their own custom language packs and translate Telegram into any language.</p>
|
||
<ol>
|
||
<li><a href="https://telegram.org/faq#q-can-i-translate-telegram">Translations instructions in the FAQ</a></li>
|
||
<li><a href="https://translations.telegram.org/">Translations section</a></li>
|
||
</ol>
|
||
<h3><a class="anchor-link" href="#9-join-support-force-requests"><i class="anchor-icon"></i></a><a class="anchor" name="9-join-support-force-requests"></a>9. Join support force requests</h3>
|
||
<p>Don't give our manifesto to just anybody. Try to see if the user is reasonable. If not, you can tell them that finding how to join us is the first test.</p>
|
||
<h3><a class="anchor-link" href="#10-media-requests"><i class="anchor-icon"></i></a><a class="anchor" name="10-media-requests"></a>10. Media requests</h3>
|
||
<p>Explain that you're a volunteer and can't handle press requests, but they can submit a request to <a href="https://t.me/PressBot">@PressBot</a>.</p>
|
||
<p>Never promise anything. Be extra careful when handling <strong>any</strong> questions from journalists. If it's something related to simple Telegram features, reply – but make sure they understand that you've volunteered to help users in support and are not a spokesperson for Telegram.</p>
|
||
<p>If it's anything more complicated, e.g.:</p>
|
||
<ul>
|
||
<li>Touches on <strong>any</strong> sensitive subjects like encryption, privacy, moderation, etc. <strong>in any way</strong></li>
|
||
<li>Contains a <strong>list of questions</strong></li>
|
||
</ul>
|
||
<p>=> Simply direct to <a href="https://t.me/PressBot">@PressBot</a>.</p>
|
||
<h3><a class="anchor-link" href="#11-legal-stuff"><i class="anchor-icon"></i></a><a class="anchor" name="11-legal-stuff"></a>11. Legal stuff</h3>
|
||
<p>You as our volunteers are not trained in legal matters, so it's safer to do <strong>nothing at all</strong>, should you encounter any kind of legal requests. Lawyers know how to reach us. So simply ignore those messages, do not open, do not reply, do not worry. We'll handle everything.</p>
|
||
<h3><a class="anchor-link" href="#12-secret-words"><i class="anchor-icon"></i></a><a class="anchor" name="12-secret-words"></a>12. Secret words</h3>
|
||
<p>By the way, when reading our manuals, you will sometimes notice words that are <strong>definitely</strong> out of place. For example, a text may at some point say something like <em>Bionic sycophants</em> out of the blue – only in real life the strange words won't be highlighted in italics. If you find such words in our manuals, talk to <a href="https://t.me/gladosbot">@Gladosbot</a> and send her the <strong>/sendsecret</strong> command (without parameters). The bot will ask you for the secret words you've found and respond if you've entered them correctly.</p>
|
||
<p>Try this now with the secret words you've just found in the paragraph above – and keep your eyes opened for more of them in other documents. Please don't neglect this! Secret words help us understand whether or not you are up to date on our docs in a friendly way.</p>
|
||
<h3><a class="anchor-link" href="#13-spam-related-requests"><i class="anchor-icon"></i></a><a class="anchor" name="13-spam-related-requests"></a>13. Spam-related requests</h3>
|
||
<p>Some users will complain that they were unfairly limited to only sending messages to their mutual contacts. We at the TSF do not have the tools to handle such requests, but our friendly <a href="https://t.me/spambot">@spambot</a> is always ready to help them – and it speaks many different languages, including those that we don't. Feel free to send the <em>spambot</em> template to such users. If they keep insisting that you do something about their situation, it is OK to ignore them.</p>
|
||
<p>Some users will have you believe that somebody reported them 'for fun' or 'by mistake', but the reality is usually very different. We have a dedicated team of moderators that process every report aided by sophisticated algorithms, so it is not easy to get limited by mistake. Naturally, both humans and algorithms can err, but the <a href="https://t.me/spambot">@spambot</a> has all the tools necessary for filing an appeal.</p>
|
||
<p>And remember: the vast, absolute majority of Telegram users never get reported at all, most reports are declined, and most of the people that do get limited never even notice it. They can talk to anyone they've talked to before, they can reply to any messages other people send them, and the initial limitation lasts for only a short period of time. Most likely, you wouldn't notice if we limited your account for a week or even a month.</p>
|
||
<p><a href="https://bugs.telegram.org/c/544">Learn more about our antispam systems in the Knowledge Base»</a></p>
|
||
<h3><a class="anchor-link" href="#14-abuse-requests"><i class="anchor-icon"></i></a><a class="anchor" name="14-abuse-requests"></a>14. Abuse requests</h3>
|
||
<p>The Telegram Support Force is an organization of volunteers that exists to help Telegram users find their way around the apps; you, our volunteers, are <strong>not qualified</strong> to solve cases involving illegal content — and neither am I (Markus). It is not an issue of trust, rather consider this:</p>
|
||
<ol>
|
||
<li>We would like our volunteers to be safe from possible legal consequences in case of misunderstandings and incorrectly handled cases.</li>
|
||
<li>Exposure to certain materials can result in life-long mental scarring, so we want to leave this to professionals that choose to handle such materials for a living.</li>
|
||
</ol>
|
||
<p>For these good reasons the Telegram abuse department is <strong>completely separate</strong> from the TSF and is staffed by professionals and not volunteers. It is their job to deal with any public content and abuse-related disputes. Please tell users to write to <a href="mailto:abuse@telegram.org">abuse@telegram.org</a> and include all the details and links — or use the built-in report buttons in our apps.</p>
|
||
<blockquote>
|
||
<p>Please note: spam@telegram.org is <strong>NOT</strong> used for complaints <strong>about</strong> spam. <a href="https://telegram.org/faq#can-39t-send-messages-to-non-contacts">More info</a></p>
|
||
</blockquote>
|
||
<h3><a class="anchor-link" href="#15-stick-to-the-bios"><i class="anchor-icon"></i></a><a class="anchor" name="15-stick-to-the-bios"></a>15. Stick to the BIOS</h3>
|
||
<p>This is where you go whenever you're not sure of what to do next. If you don't find your answer in the BIOS, tell Markus about it. It's important to keep this document up to date.</p>
|
||
<hr>
|
||
<h3><a class="anchor-link" href="#tsf-manuals"><i class="anchor-icon"></i></a><a class="anchor" name="tsf-manuals"></a>TSF manuals</h3>
|
||
<p><div class="dev_page_nav_wrap"></p>
|
||
<ul>
|
||
<li><a href="/">TSF Manifesto</a></li>
|
||
<li><strong><a href="/manuals/bios">BIOS</a></strong> (you are here)</li>
|
||
<li><a href="/manuals/answering_questions">Answering questions</a></li>
|
||
<li><a href="/manuals/bugs">Bug handling and troubleshooting</a></li>
|
||
<li><a href="/manuals/feature_philosophy">Feature Philosophy</a></li>
|
||
<li><a href="/manuals/come-and-go">Leaving and coming back</a></li>
|
||
</ul>
|
||
<p></div></p>
|
||
</div>
|
||
|
||
</div></section>
|
||
</section>
|
||
</main>
|
||
</div><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 access your TSF stats. 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>
|
||
|
||
<form id="send-form" class="login-form">
|
||
<div class="form-group">
|
||
<input type="tel" class="form-control tr-form-control input-lg" id="phone-number" 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 tr-form-control input input-lg input-disabled"><strong id="phone-number-field"></strong> (<a class="login-back" href="/auth">Incorrect?</a>)</span>
|
||
<p class="help-block dots-animated">We'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></div>
|
||
<script src="//telegram.org/js/jquery.min.js?1"></script>
|
||
<script src="//telegram.org/js/bootstrap.min.js"></script>
|
||
<script src="//telegram.org/js/main-aj.js?67"></script>
|
||
<script src="/js/main.js?47"></script>
|
||
<script src="/js/tsf.js?3"></script>
|
||
<script src="/js/jquery-ui.min.js?1"></script>
|
||
<script src="/js/tchart.min.js?18"></script>
|
||
<script src="/js/billboard.min.js?1"></script>
|
||
<script src="/js/stats.js?18"></script>
|
||
|
||
<script>ajInit({"version":800,"apiUrl":"\/api?hash=telegram-crawler","unauth":true});</script>
|
||
<script id="aj_script">window.initDevPageNav&&initDevPageNav();
|
||
Aj.onLoad(function(state) {
|
||
function requestConfirmation(event) {
|
||
event && event.preventDefault();
|
||
var phone = $('#phone-number').val();
|
||
$.ajax({
|
||
type: 'POST',
|
||
url: '/auth/request',
|
||
data: {
|
||
phone: phone
|
||
},
|
||
success: function(result) {
|
||
$('#phone-number-field').text(phone);
|
||
$('#send-form').addClass('hide');
|
||
$('#login-form').removeClass('hide');
|
||
checkAuth(result.temp_session);
|
||
},
|
||
error: function(xhr) {
|
||
showAlert(xhr.responseText || 'Server error');
|
||
},
|
||
dataType: 'json'
|
||
});
|
||
return false;
|
||
}
|
||
function cancelConfirmation(event) {
|
||
event && event.preventDefault();
|
||
$('#phone-number-field').text('');
|
||
$('#send-form').removeClass('hide');
|
||
$('#login-form').addClass('hide');
|
||
$('#phone-number').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) {
|
||
showAlert(xhr.responseText || 'Server error');
|
||
},
|
||
dataType: 'json'
|
||
});
|
||
}, 700);
|
||
}
|
||
$('#login-popup-container').on('popup:open', function() {
|
||
$('#phone-number').focus();
|
||
});
|
||
$('#login-popup-container').on('popup:close', function() {
|
||
cancelConfirmation();
|
||
if (location.pathname == '/auth') {
|
||
window.history && history.replaceState(null, null, '/');
|
||
}
|
||
});
|
||
$('#login-popup-container #send-form').on('submit', requestConfirmation);
|
||
$('#login-popup-container .login-cancel-btn').on('click', function(e) {
|
||
e.preventDefault();
|
||
closePopup('#login-popup-container');
|
||
});
|
||
$('#login-popup-container .login-back').on('click', cancelConfirmation);
|
||
$('.login-link').on('click', function(e) {
|
||
e.stopImmediatePropagation();
|
||
e.preventDefault();
|
||
openPopup('#login-popup-container');
|
||
});
|
||
});
|
||
Aj.onUnload(function(state) {
|
||
$('#login-popup-container').off('popup:open');
|
||
$('#login-popup-container').off('popup:close');
|
||
$('#login-popup-container #send-form').off('submit');
|
||
$('#login-popup-container .login-cancel-btn').off('click');
|
||
$('#login-popup-container .login-back').off('click');
|
||
$('.login-link').off('click');
|
||
});
|
||
</script>
|
||
<script>Aj.pageLoaded();</script>
|
||
|
||
</body>
|
||
</html>
|
||
|