[Feature Request] Scrape comments on channel posts

[fabrei]

Hi,

thanks for developing this nice tool =)

In the upcoming changes you want to implement the ability to scrape comments in channel posts:

Giving the archiver module the ability to archive comments on channel posts.

This would be a nice feature; do you have an idea when it is ready?

[proseltd]

Hey there. Right now I’m not certain on the timeframe. Between everything else happening I’ve taken a bit of a pause of major developments to Telepathy. A current workaround is already included with the scripts available—channels that have comments enabled will have an associated group, by archiving that group as well as the channel it’s theoretically possible to cross reference the channel post ID with the reply ID of messages within the group. This is a bit awkward right now, but at least provides the basics.

…

On Sat, Mar 5, 2022 at 15:48, fabrei ***@***.***> wrote: Hi, thanks for developing this nice tool =) In the [upcoming changes](https://github.com/jordanwildon/Telepathy#upcoming-changes) you want to implement the ability to scrape comments in channel posts: > Giving the archiver module the ability to archive comments on channel posts. This would be a nice feature; do you have an idea when it is ready? — Reply to this email directly, [view it on GitHub](#7), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AVGBB53MJFZVXJ3ZIO4UCNLU6NX4ZANCNFSM5P7Y4TBA). Triage notifications on the go with GitHub Mobile for [iOS](https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or [Android](https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub). You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[aaarghhh]

Hi,
my PR does exactly that feature you looking for. The flag -r will generate a new file in the archive directory.

[proseltd]

This has perplexed me, I definitely hit merge on it, and didn’t select to close it at all. Really confused at to what happened there

…

On Sun, Oct 9, 2022 at 09:12, Giacomo Giallombardo ***@***.***> wrote: My PR does exactly that feature you looking for. The flag -r will generate a new file in the archive directory. PS: why my PR was closed and not merged? — Reply to this email directly, [view it on GitHub](#7 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AVGBB552PBBFFGYXDKF5FADWCKEBTANCNFSM5P7Y4TBA). You are receiving this because you commented.Message ID: ***@***.***>

[aaarghhh]

Don''t worry was my issue. I used Pycharm which was binded to an email that isn't in Github. When I pushed the commit I used an unrecognized email and Github wasn't able to match my account. I fixed it just adding a secondary emails in profile. There are tools that parse repos in order to find information about this, the email is in cleartext inside the commit ^^.