mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2024-11-28 19:23:11 +01:00
Update content of files
This commit is contained in:
GitHub Action
parent
400a8a7342
commit
9c54bc994c
3 changed files with 7 additions and 7 deletions
|
|
@ -534,7 +534,7 @@ Check out our Advanced FAQ for more technical information.…">
|
|||
<h4><a class="anchor" name="q-can-i-translate-telegram" href="#q-can-i-translate-telegram"><i class="anchor-icon"></i></a>Q: Can I translate Telegram?</h4>
|
||||
<p>Telegram is officially available in English, Spanish, German, Dutch, Italian, French, Arabic, Portuguese, Korean, Malay, Russian and Ukrainian on most platforms, and we are gradually expanding the list of languages built into the apps.</p>
|
||||
<p>If you don’t like how a specific element in Telegram's interface is translated in your language, or would like to help us maintain the translation, check out our <a href="https://translations.telegram.org">localization platform</a>. Everyone can suggest translations and vote for the best ones, making Telegram localization a community-driven effort.</p>
|
||||
<p>If you're looking to go beyond suggestions for individual phrases and would like to help us maintain the official translation to your language on a continuous basis, you can contact <a href="https://t.me/telegramauditions">@TelegramAuditions</a>. Please include a hashtag with the English name of your language (e.g. #Albanian) and a few links to phrases on this platform with your <strong>translation suggestions</strong> or <strong>comments</strong>. Be sure read the <a href="https://translations.telegram.org/#style-guide"><strong>Style Guide</strong></a> carefully before you apply.</p>
|
||||
<p>If you're looking to go beyond suggestions for individual phrases and would like to help us maintain the official translation to your language on a continuous basis, you can contact <a href="https://t.me/telegramauditions">@TelegramAuditions</a>. Please include a hashtag with the English name of your language (e.g. #Albanian) and a few links to phrases on this platform with your <strong>translation suggestions</strong> or <strong>comments</strong>. Be sure to read the <a href="https://translations.telegram.org/#style-guide"><strong>Style Guide</strong></a> carefully before you apply.</p>
|
||||
<h4><a class="anchor" name="q-can-i-help" href="#q-can-i-help"><i class="anchor-icon"></i></a>Q: Can I help?</h4>
|
||||
<p>Yes, we are always looking for volunteers to help us with user support. If you would be interested in answering questions about Telegram to users from your country, contact our auditions account.</p>
|
||||
<p>Before you apply, please check out the <a href="https://core.telegram.org/tsi">Telegram Support Initiative</a>.</p>
|
||||
|
|
|
|||
|
|
@ -201,7 +201,7 @@ We've asked bot developers to ensure that their bots can respond to the /privacy
|
|||
<p><strong>March 24, 2021</strong></p>
|
||||
<ul>
|
||||
<li>Added <a href="#3-5-location-data">3.5. Location Data</a>.</li>
|
||||
<li>Improved stucture, moving 3.3.5 to <a href="#3-4-phone-number-and-contacts">3.4</a> and 3.3.6 to <a href="#3-6-cookies">3.6</a>.</li>
|
||||
<li>Improved structure, moving 3.3.5 to <a href="#3-4-phone-number-and-contacts">3.4</a> and 3.3.6 to <a href="#3-6-cookies">3.6</a>.</li>
|
||||
</ul>
|
||||
<p>Important changes made to this Privacy Policy will be notified to you via Telegram. </p>
|
||||
<h3><a class="anchor" name="12-questions-and-concerns" href="#12-questions-and-concerns"><i class="anchor-icon"></i></a>12. Questions and concerns</h3>
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ Every now and then users…">
|
|||
<hr>
|
||||
<h3><a class="anchor-link" href="#reporting-a-bug"><i class="anchor-icon"></i></a><a class="anchor" name="reporting-a-bug"></a>Reporting a bug</h3>
|
||||
<h4><a class="anchor-link" href="#1-search-known-issues"><i class="anchor-icon"></i></a><a class="anchor" name="1-search-known-issues"></a>1. Search known issues</h4>
|
||||
<p>We use <a href="https://trello.com">Trello</a> boards to keep track of bugs (sorry, these boards are TSF-only, <a href="/">here's how you join</a>), features and user suggestions, so your first stop when encoutering a bug report is <strong>Trello search</strong>. Most likely, we already know about the issue — sometimes it is not a bug at all. So make sure you study all the relevant cards.</p>
|
||||
<p>We use <a href="https://trello.com">Trello</a> boards to keep track of bugs (sorry, these boards are TSF-only, <a href="/">here's how you join</a>), features and user suggestions, so your first stop when encountering a bug report is <strong>Trello search</strong>. Most likely, we already know about the issue — sometimes it is not a bug at all. So make sure you study all the relevant cards.</p>
|
||||
<p>If you have found the issue on Trello, leave a comment in the card with your user's <strong>#tq tag</strong> and device info (skip this step if the card already has too many comments of that kind or is in the “Hot and Trending” list). Then go right to <strong><a href="#4-notify-the-user">step 4</a></strong>.</p>
|
||||
<div>
|
||||
<a href="/file/811140845/1/y4-CDGX0MNo/7774e8d703a4bf7112" target="_blank"><img src="/file/811140845/1/y4-CDGX0MNo/7774e8d703a4bf7112" title="Screenshot_1.png, 50.2Kb" class="dev_page_image" /></a>
|
||||
|
|
@ -145,7 +145,7 @@ Every now and then users…">
|
|||
<p>Once we're done, we need to get back to the user and tell them that we've located the issue or are investigating it. You never know how long that might take, but the user must know that he succeeded in alerting us — and helped us greatly. Parachutes and pasties</p>
|
||||
<ul>
|
||||
<li>Always include an <strong>issue ID hashtag</strong> in your reply in this situation.</li>
|
||||
<li>All trello cards have unique identifiers (open card, click on “share and more”, then 'link to this card', take the last part or the link, after /c/ — e.g. <em>vMFS4MZf</em>).</li>
|
||||
<li>All Trello cards have unique identifiers (open card, click on “share and more”, then 'link to this card', take the last part of the link, after /c/ — e.g. <em>vMFS4MZf</em>).</li>
|
||||
<li>We use this ID to create a hashtag (e.g. <strong>#issue_vMFS4MZf</strong>) and include it in our reply to the user with that problem. Like this, for example:</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
|
|
@ -212,7 +212,7 @@ Every now and then users…">
|
|||
<ul>
|
||||
<li>Make sure notifications are on in Telegram AND in phone settings (Settings > Notifications), check app version.</li>
|
||||
<li>Make sure notifications weren’t disabled for a specific chat or group.</li>
|
||||
<li>Shut down Telegram (go to home screen, swipe up or double tap home button, stop Telegram (swipe out), then go to Phone Settings and disable alerts. Relaunch Telegram, go to Phone Settings, enable alerts.</li>
|
||||
<li>Shut down Telegram (go to home screen, swipe up or double tap home button, swipe upwards on Telegram), then go to Phone Settings and disable alerts. Relaunch Telegram, go to Phone Settings, enable alerts.</li>
|
||||
</ul>
|
||||
<p>What we need to know if nothing helps:</p>
|
||||
<ul>
|
||||
|
|
@ -279,7 +279,7 @@ Every now and then users…">
|
|||
<li>In case of a photo/video, ask the user to forward it to us. <strong>Not</strong> upload it again, just forward the original message with the attachment.</li>
|
||||
</ul>
|
||||
<h4><a class="anchor-link" href="#connection-issues"><i class="anchor-icon"></i></a><a class="anchor" name="connection-issues"></a>Connection issues</h4>
|
||||
<p>When people are reporting connection issues, check twitter first: are there any widespread problems. If the problem is local, we need to find out a lot of information before things can be investigated. Things to ask:</p>
|
||||
<p>When people are reporting connection issues, check Twitter first: are there any widespread problems. If the problem is local, we need to find out a lot of information before things can be investigated. Things to ask:</p>
|
||||
<ul>
|
||||
<li>Do other (non-Telegram) apps work OK?</li>
|
||||
<li>What exactly is happening? (always 'connecting…' / always 'updating…' / seems ok, but messages are not sent / not delivered, etc.)</li>
|
||||
|
|
@ -292,7 +292,7 @@ Every now and then users…">
|
|||
<p>Don't forget to include with your report:</p>
|
||||
<ul>
|
||||
<li>User's footer tag.</li>
|
||||
<li>Results of <a href="https://t.me/connectivity_test">@connectivity_test</a>. Which GIFs are dowloaded slowly or not downloaded?</li>
|
||||
<li>Results of <a href="https://t.me/connectivity_test">@connectivity_test</a>. Which GIFs are downloaded slowly or not downloaded?</li>
|
||||
</ul>
|
||||
<p>It is possible that we'll need a Traceroute to our servers, <a href="https://telegram.wiki/kb/general/connection-and-sms-issues/">here's</a> how you get that. Wait for instructions from the server cultists to get the right IP to trace the route to — each case potentially requires a different one.</p>
|
||||
<h4><a class="anchor-link" href="#last-seen-time-is-not-displayed-correctly"><i class="anchor-icon"></i></a><a class="anchor" name="last-seen-time-is-not-displayed-correctly"></a>Last seen time is not displayed correctly</h4>
|
||||
|
|
|
|||
Loading…
Reference in a new issue