* fix: WebLN QR fallback for anon users
* wip: clear zap color on payment fail
* reverse clearItemMeAnonSats
* webln-specific retry bypass
* cleanup
* send WebLN payment when user is Anon AND on QR
* skip wallet checking on anon
* Use WalletError for all errors in webln.sendPayment
---------
Co-authored-by: ekzyis <ek@stacker.news>
Co-authored-by: Keyan <34140557+huumn@users.noreply.github.com>
* Dynamically import MathJax
* Only load if there's math content; cleanup
* avoid loading RSH on Math, we have MathJax for that; cleanup
* support multiline mathjax
---------
Co-authored-by: k00b <k00b@stacker.news>
* Poll failed invoices with visibility timeout
* Don't return intermediate failed invoices
* Don't retry too old invoices
* Retry invoices on client
* Only attempt payment 3 times
* Fix fallbacks during last retry
* Rename retry column to paymentAttempt
* Fix no index used
* Resolve TODOs
* Use expiring locks
* Better comments for constants
* Acquire lock during retry
* Use expiring lock in retry mutation
* Use now() instead of CURRENT_TIMESTAMP
* Cosmetic changes
* Immediately show failed post payments in notifications
* Update hasNewNotes
* Never retry on user cancel
For a consistent UX and less mental overhead, I decided to remove the exception for ITEM_CREATE where it would still retry in the background even though we want to show the payment failure immediately in notifications.
* Fix notifications without pending retries missing if no send wallets
If a stacker has no send wallets, they would miss notifications about failed payments because they would never get retried.
This commit fixes this by making the notifications query aware if the stacker has send wallets. This way, it can tell if a notification will be retried or not.
* Stop hiding userCancel in notifications
As mentioned in a previous commit, I want to show anything that will not be attempted anymore in notifications.
Before, I wanted to hide manually cancelled invoices but to not change experience unnecessarily and to decrease mental overhead, I changed my mind.
* Also consider invoice.cancelledAt in notifications
* Always retry failed payments, even without send wallets
* Fix notification indicator on retry timeout
* Set invoice.updated_at to date slightly in the future
* Use default job priority
* Stop retrying after one hour
* Remove special case for ITEM_CREATE
* Replace retryTimeout job with notification indicator query
* Fix sortTime
---------
Co-authored-by: Keyan <34140557+huumn@users.noreply.github.com>
* Update price button accessibility
* Updated accName and accDescription for speech dictation and screen reader users.
* Update price.js
Replace double quote with single
* Update price.js
Remove trailing spaces
* make .visually-hidden global, use className rather than class
* make accessible button component
---------
Co-authored-by: Jason Hester <jhester@TPGLPT-LTC23.attlocal.net>
Co-authored-by: Keyan <34140557+huumn@users.noreply.github.com>
Co-authored-by: k00b <k00b@stacker.news>
* fix: cannot login with email on PWA
* adjust other email templates
* restore manual url on new user email
* no padding on button section
* cleanup
* generate 6-digit bechh32 token
* token needs to be fed as lower case; validator case insensitive
* delete token if user has failed 3 times
* proposal: context-independent error page
* include expiration time on email page message
* add expiration time to emails
* independent checkPWA function
* restore token deletion if successful auth
* final cleanup: remove unused function
* compact useVerificationToken
* email.js: magic code for non-PWA users
* adjust email templates
* MultiInput component; magic code via MultiInput
* hotfix: revert length testing; larger width for inputs
* manual bech32 token generation; no upperCase
* reverting to string concatenation
* layout tweaks, fix error placement
* pastable inputs
* small nit fixes
* less ambiguous error path
---------
Co-authored-by: Keyan <34140557+huumn@users.noreply.github.com>
Co-authored-by: k00b <k00b@stacker.news>
* basic query with limit/offset
* roughly working increment
* working limiting/pageable queries
* denormalize direct comments + full comments below threshold
* notifications in megathread + working nest view more buttons
* fix empty comment footer
* make comments nested resolver again
* use time in cursor to avoid duplicates
* squash migrations
* do not need item.comments undefined checks
* Fix parents not uncollapsed of router.query.commentId
* Fix code comment
* Use descriptive fragment name
* Add cache to effect dependencies
not sure if needed since also works without but probably safer to have than not
