Mobile flow with Fedi app #180
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sigit/sigit.io#180
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It should be possible to create and complete a sigit round when the creator is using the Fedi app on mobile
https://github.com/fedibtc/fedi-alpha/releases
Confirmed successful creation and completion with the google play store version of the app on the android.
Manually added staging sigit url as a mod and logged in with
nsec
.This is great!
However, nsec login is available for development purposes only, it's not a recommended (nor secure) way to use sigit.
Can we test again using the native Fed (NIP-07) signing mechanism?
Logged in successfully with the native Fedi mechanism, prerequisite was joining a community for the "Login with extension" button to become available.
Publishing a sigit fails due to Fedi not having a nip04 encrypt implementation. Source code points that they only support mandatory nip07 features (no optional nip04 or nip44 encrypt/decrypt).
Link to Fedi Issue: https://github.com/fedibtc/fedi-alpha/issues/9