chathistorysync: readme: mention meta.sr.ht scope access v1 REJECTED

jgart: 1
 readme: mention meta.sr.ht scope access

 1 files changed, 4 insertions(+), 0 deletions(-)

[PATCH chathistorysync] readme: mention meta.sr.ht scope access Export this patch

Hi,

Here's a patch for chathistorysync adding info for the user letting them
know that they have to register for a token with meta.sr.ht scope access.

Simon Ser <contact@emersion.fr>

1 year, 10 months ago

Thanks for the patch, but I'd rather not add this. The tool has nothing
specific to chat.sr.ht, it's a generic tool which can be used with other
IRC servers.

Next

Do you happen to know the minimum amount of access granting for meta.sr.ht
that can be used with chathistorysync?

Simon Ser <contact@emersion.fr>

1 year, 10 months ago

The docs at [1] have a link with the minimal grants.

[1]: https://man.sr.ht/chat.sr.ht/quickstart.md#connecting-with-your-own-irc-client

I can send an updated patch with just the scopes for meta.sr.ht that are
required. This will facilitate users quickly setting up this tool for use
(TLDR).

all best,

jgart

---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index cdc89aa..2cde779 100644
--- a/README.md
+++ b/README.md
@@ -22,6 +22,10 @@ For example, to sync chat.sr.ht logs locally:
 
     chathistorysync emersion@chat.sr.ht ~/chat-logs
 
+A [personal access
+token](https://man.sr.ht/meta.sr.ht/#personal-access-tokens) with scope
+access granted to meta.sr.ht is required to use chathistorysync.
+
 ## License
 
 AGPLv3, see LICENSE.
-- 
2.38.1

builds.sr.ht <builds@sr.ht>

1 year, 10 months ago

chathistorysync/patches/.build.yml: SUCCESS in 32s

[readme: mention meta.sr.ht scope access][0] from [jgart][1]

[0]: https://lists.sr.ht/~emersion/public-inbox/patches/38247
[1]: mailto:jgart@dismail.de

✓ #923703 SUCCESS chathistorysync/patches/.build.yml https://builds.sr.ht/~emersion/job/923703