neko
/
SpywareWatchdog
mirror of https://codeberg.org/shadow/SpywareWatchdog.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

added tor metadata

This commit is contained in:
Baobab 2020-10-13 21:32:31 +02:00
parent d5efc76154
commit 0538325717
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
articles/telegram.html
View File

@ -4,6 +4,7 @@
<head>
<meta http-equiv="Content-type" content="application/xhtml+xml;charset=utf-8"/>
<meta name="viewport" content="width=device-width,initial-scale=1"/>
<meta http-equiv="onion-location" content="http://spywaredrcdg5krvjnukp3vbdwiqcv3zwbrcg6qh27kiwecm4qyfphid.onion/articles/telegram.html"/>
<link rel="icon" href = "../images/favicon.ico"/>
<title>Telegram - Spyware Watchdog</title>
<link href="../style.css" rel="stylesheet" type="text/css" media="all"/>
@ -27,7 +28,7 @@
<h3>Telegram does not follow its GPLv2 Obligations</h3>
<p>Telegram clients are advertised as free software, but in practice the source code is not immediately accessible.<sup><a href="#two">[2]</a></sup>, the delay sometimes being up to 5 months. So, unknown spyware features could be in the official Telegram client binaries that you download, without you knowing. It's recommended that you build an outdated version of telegram from its source code, since it's not provable whether or not the binaries that are distributed have unknown spyware or not.</p>
</div>
<hr></hr>
<hr></hr>
<div class="center">
<h2>Sources</h2>
<p><a id="one">1.</a><a href="https://telegram.org/privacy">Telegram Privacy Policy</a> <a href="https://web.archive.org/web/20201012074908/https://telegram.org/privacy">[web.archive.org]</a></p>