Zap split UX confusion #140
Labels
No Label
Compat/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
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: degmods/degmods.com#140
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?
2 QR codes are generated to zap a mod post, where once the first zap is paid (for the creator) and confirmed, it'll auto swap to a new QR code (for the site) and that's it, causing a bit of a confusion as to what's happening.
I'm thinking of making this more obvious with UI changes (unless its figured out how we can do zap splits in one transaction qr without running a LN node), by adding the user's profile picture and name somewhere associated with the current QR and showing a preview and text details of the next QR that'd be shown.