Skip to content
This repository has been archived by the owner on Dec 17, 2023. It is now read-only.

Client "Amethyst" is unable to read the relay #32

Closed
piraces opened this issue Feb 28, 2023 · 2 comments
Closed

Client "Amethyst" is unable to read the relay #32

piraces opened this issue Feb 28, 2023 · 2 comments
Assignees
@piraces
Labels
bug Something isn't working triage Triaging the issue
Milestone
0.4.x

Comments

@piraces
Copy link
Owner

piraces commented Feb 28, 2023

Check for "Amethyst" client and review whether it can connect to rsslay or not.

Reported by: npub1c3twfcadj7szhcmt8quctan4pdn6whujn3khk9qvsy59fv5nd02q4qm42k,
@piraces piraces self-assigned this Feb 28, 2023
@piraces piraces added bug Something isn't working triage Triaging the issue labels Feb 28, 2023
@piraces piraces moved this to Todo in rsslay project Feb 28, 2023
@piraces piraces added this to the 0.4.x milestone Feb 28, 2023
@piraces
Copy link
Owner Author

piraces commented Feb 28, 2023 •
edited
Loading

Seems like Amethyst connects ok to current relay:

Amethyst screenshot

Nevertheless, for newer created profiles, it takes a bit to discover them and several tries.

@piraces
Copy link
Owner Author

piraces commented Mar 21, 2023

Seems that "Amethyst" can read the relay correctly, nevertheless tracking this in #48

@piraces piraces closed this as completed Mar 21, 2023
@github-project-automation github-project-automation bot moved this from Todo to Done in rsslay project Mar 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@piraces piraces

Labels
bug Something isn't working triage Triaging the issue
Projects
rsslay project
Status: Done
Milestone
0.4.x
Development

No branches or pull requests
1 participant
@piraces