🤬
Revision indexing in progress... (symbol navigation in revisions will be accurate after indexed)
  • ■ ■ ■ ■ ■
    README.md
    skipped 4 lines
    5 5  The toolkit has already seen a wide variety of use cases, including but not limited to: in investigative and data journalism, by academic and research institutions, and for intelligence gathering and analysis.
    6 6   
    7 7   
    8  -## !! IMPORTANT:
    9  -With the update to 2.3.0, you will need to delete your login.txt file to prevent errors if using the alternative login feature. Upon first use, Telepathy will guide you through setup of the details once again. To work around this, instead of deleting and recreating the file, you can add a newline character to the end of your current API details to ensure Telepathy scans the file correctly.
    10  - 
    11  -A note on unique identifiers per account: You will notice that depending on which alternative account you use, the access hash will vary. The same will happen with User IDs, which are unique to each Telegram account accessing them. For deeper data analysis based on user IDs, this is important to bare in mind as users will have as many unique IDs as accounts you've used to access information. In future, Telepathy may include a feature to assign unique identifier per account found based on a hash of the available information, regardless of which account accessed the data.
     8 +## Are you looking for a enterprise-grade version of Telepathy?
     9 +Visit [prose.ltd](https://prose.ltd) to find out how we can turbocharge your Telegram data collection with Telepathy Pro. No accounts, dealing with the command line, or hassle needed!
    12 10   
    13 11   
    14 12   
    skipped 158 lines
    173 171  Upcoming features include:
    174 172   
    175 173   - [ ] Adding a time specification flag to set archiving for specific period.
    176  - - [x] The ability to gather the number of reactions to messages, including statistics on engagement rate.
    177  - - [ ] Finding a method to once again gather complete memberlists (currently restricted by the API).
    178  - - [ ] Improved statistics: including timestamp analysis for channels.
    179  - - [ ] Generating an entirely automated complete report, including visualisation for some statistics.
    180  - - [ ] Hate speech analytics.
    181  - - [ ] Include sockpuppet account provisioning (creation of accounts from previous exported lists).
    182  - - [ ] Listing who has group admin rights in memberlists.
    183  - - [ ] Media downloaded in the background to increase efficiency or progress bars for media downloads to give a better estimation of runtime.
    184  - - [x] When media archiving is flagged, the location of downloaded content will be added to the archive file.
    185  - - [ ] Exploring, and potentially integrating, media cross-checks based on https://github.com/conflict-investigations/media-search-engine.
     174 + - [ ] A new method to once again gather complete memberlists (currently restricted by the API).
    186 175   - [ ] Ensuring inferred channel memberlists don't contain duplicate entries.
    187  - - [ ] Introducing local chat retrival within the location lookup module.
    188  - - [x] Further code refactoring to ensure long-term maintainability.
    189  - - [x] Adding additional alternative logins.
    190  - - [ ] Improved language support.
    191  - - [ ] Correctly define destinction between reply (as in a chat) and comment (as in channel).
    192 176   - [ ] Exploration of whether channel events can be included, such as name changes.
    193  - - [x] Including last seen on user lookup.
    194 177   
    195 178  ## feedback
    196 179   
    197  -Please send feedback to @jordanwildon on Twitter. You can follow Telepathy updates at @TelepathyDB.
     180 +Please send feedback to @jordanwildon on Twitter. You can follow Telepathy updates at @proseltd.
    198 181   
    199 182   
    200 183  ## Usage terms
    201 184   
    202  -You may use Telepathy however you like, but your usecase is your responsibility. Be safe and respectful.
     185 +You may use Telepathy however you like, but your usecase is your responsibility. Be safe and respectful. If your usecase is for commercial purposes, please consider cour enterprise options at [prose.ltd](https://prose.ltd)
    203 186   
    204 187   
    205 188  ## Credits
    206 189   
    207 190  All tools created by Jordan Wildon (@jordanwildon). Special thanks go to [Giacomo Giallombardo](https://github.com/aaarghhh) for adding additional features and code refactoring, [jkctech](https://github.com/jkctech/Telegram-Trilateration) for collaboration on location lookup via the 'People Near Me' feature, and Alex Newhouse (@AlexBNewhouse) for his help with Telepathy v1. Shoutout also to [Francesco Poldi](https://github.com/pielco11) for being a sounding board and offering help and advice when it comes to bug fixes.
    208 191   
    209  -Where possible, credit for the use of this tool in published research is desired, but not required. This can either come in the form of crediting the author, or crediting Telepathy itself (preferably with a link).
     192 +Where possible, credit for the use of this tool in published research is desired, but not required. This can either come in the form of crediting Jordan Wildon, Prose Intelligence, or crediting Telepathy itself.
    210 193   
Please wait...
Page is in error, reload to recover