Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create "account" does not work with any service provider (siamstr.com also seems to be down) #6

Open
alltheseas opened this issue Jun 10, 2024 · 14 comments

Comments

@alltheseas
Copy link

what happens

  1. in https://keypub.coracle.social/ I try to create an "account"
  2. I can type in a "username"
  3. I can select from the dropdown a domain
  4. I cannot continue - nothing happens when I tap the continue button
    Screenshot 2024-06-10 at 8 45 20 AM

cc @dtonon

@dtonon
Copy link
Collaborator

dtonon commented Jun 10, 2024

There is a problem with siamstr.com, it is returning a 404 for /.well-known/nostr.json?name=xxxxxx
(you can spot this with the console)

@vazw can you check this, please?

/cc @fiatjaf

@dtonon dtonon changed the title Create "account" does not work on keypub.coracle Create "account" does not work with siamstr.com Jun 10, 2024
@dtonon
Copy link
Collaborator

dtonon commented Jun 10, 2024

@alltheseas I renamed the issue because the problem is not actually related to keypub.coracle, but to the provider.
A suggestion: in this situations is often a good idea to do a cross-check changing options, or website.

@alltheseas
Copy link
Author

alltheseas commented Jun 10, 2024

@alltheseas I renamed the issue because the problem is not actually related to keypub.coracle, but to the provider. A suggestion: in this situations is often a good idea to do a cross-check changing options, or website.

I cannot proceed forward with any of:

  1. highlighter.com
  2. lume.nu
  3. siamstr
  4. nsec.app

I renamed the issue to reflect the above. Siamstr not working is a related, and separate issue.

@alltheseas alltheseas changed the title Create "account" does not work with siamstr.com Create "account" does not work with any service provider (siamstr.com also seems to be down) Jun 10, 2024
@dtonon
Copy link
Collaborator

dtonon commented Jun 10, 2024

Damn, all providers seem to have a (different) problem...

@alltheseas
Copy link
Author

@brugeman
@pablof7z
@reyamir

@alltheseas
Copy link
Author

Damn, all providers seem to have a (different) problem...

@dtonon is it possible for window nostr js to add periodic "is this provider working as expected" checks (i.e. does create "account" work; does log in work)? For instance, every week.

@vazw
Copy link

vazw commented Jun 10, 2024

There is a problem with siamstr.com, it is returning a 404 for /.well-known/nostr.json?name=xxxxxx (you can spot this with the console)

@vazw can you check this, please?

/cc @fiatjaf

As for Nip-05 it seem to be just work. you can check how the API work here
But I did done implementing the creating account part YET since I did not have much confident holding people's keys for now. I did have some experiments on a remote-signer project here that let our community #siamstr playing around with. there is a lot to be done.

@alltheseas
Copy link
Author

Damn, all providers seem to have a (different) problem...

@dtonon is it possible for window nostr js to add periodic "is this provider working as expected" checks (i.e. does create "account" work; does log in work)? For instance, every week.

created new test suite issue #7

this is a negative user experience that will scare away people from

  1. testing individual apps
  2. using window nostr js
  3. using nostr as a whole

@fiatjaf
Copy link
Owner

fiatjaf commented Jun 10, 2024

This must be solved at relay level.

WNJ only fetches announcement events from some relays, these relays must perform filtering and remove events from providers that are not working or are not trustworthy.

Or at least that's my vision for the future and plans.

No one has worked on this yet because no one is using NIP-46 for anything real yet and all providers are broken so it makes no sense to filter them. We're all debugging in production.

@fiatjaf
Copy link
Owner

fiatjaf commented Jun 10, 2024

It can't be left for WNJ to filter on the client side because anyone could just advertise a million fake providers and currently that would work successfully in breaking the user experience entirely.

@alltheseas
Copy link
Author

This must be solved at relay level.

So the relay will run tests, and filter broken / fake providers?

Who is the right person to work on this? @mikedilger ?

@fiatjaf
Copy link
Owner

fiatjaf commented Jun 10, 2024

So the relay will run tests, and filter broken / fake providers?

Yes, that would be it, I think.

Who is the right person to work on this?

Everybody, but I can't think of anyone specifically.

@mikedilger
Copy link

Who is the right person to work on this? @mikedilger ?

I don't think these are relay issues that https://github.com/mikedilger/relay-tester would include a test for, they are NIP-46 bunker service provider issues right? Maybe relay-tester could have a bunker-tester module, I dunno. I'll keep it in mind.

@reyamir
Copy link

reyamir commented Jun 11, 2024

@alltheseas I renamed the issue because the problem is not actually related to keypub.coracle, but to the provider. A suggestion: in this situations is often a good idea to do a cross-check changing options, or website.

I cannot proceed forward with any of:

  1. highlighter.com
  2. lume.nu
  3. siamstr
  4. nsec.app

I renamed the issue to reflect the above. Siamstr not working is a related, and separate issue.

Hi, sorry for the inconvenience, I've fixed the lume.nu provider, it's should work fine now.

Arc.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants