alltheseas

Will you require curators to verify hash?

> there are too many releases to expect people/curators to keep checking and validating hashes for. Ok, noted, curators are not required to verify hash. If a curator does decide...

> Maybe a “⚠️warning: closed source ⚠️” label. The source code cannot be audited, or verified. By using this app you sign up to a greater risk of rugpull, and...

> @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...

@brugeman @pablof7z @reyamir

> 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...

> > 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"...

> 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...

Nice. Reducing friction to testing out new apps/POCs is important. Also important is that the people are not just testing a single app, but likely nostr as a whole.

Somewhat related Wishlist: translate button: https://github.com/vitorpamplona/amethyst/issues/61