* Remove directReceive setting
* Never fallback to direct if proxy is enabled
---------
Co-authored-by: Keyan <34140557+huumn@users.noreply.github.com>
This function can be removed because it will never do anything when called.
It does not do anything for wrapped invoices, and it will never get called for direct payments (since we don't know when the invoice was paid).
These are the only two payment methods for the RECEIVE paid action since 5a8804d.
* Add Territory Sub management tab in Subscriptions
* don't use queryRawUnsafe
* auto width on select
* separate into pages for browser nav
* fix multiple separators
* simplify queries
---------
Co-authored-by: k00b <k00b@stacker.news>
* feat: add exact search for quoted phrases/words
* feat: get some highlighting for exact search
* feat: Add exact search for title and text fields in OpenSearch
* simplify and make it work with nlp script
---------
Co-authored-by: Keyan <34140557+huumn@users.noreply.github.com>
Co-authored-by: k00b <k00b@stacker.news>
* set boost max
* reduce max and apply to boost act
* make boost position aware paid action state
---------
Co-authored-by: Keyan <34140557+huumn@users.noreply.github.com>
Co-authored-by: k00b <k00b@stacker.news>
* Remove gun+horse streak
* Add wallet badges
* Fix empty recv wallet detected as enabled
* Resolve badges via columns and triggers
* Fix backwards compatibility by not dropping GQL fields
* Gun+horse notifications as streaks via triggers
* Fix error while computing streaks
* Push notifications for horse+gun
* Move logic to JS via pgboss job
* Fix argument to notifyNewStreak
* Update checkWallet comment
* Refactor notification id hack
* Formatting
* Fix missing update of possibleTypes
This didn't cause any bugs because the added types have no field resolvers.
* Add user migration
* Fix missing cast to date
* Run checkWallet queries inside transaction
* commented the lines to make sure dupes are also checked on subdomains
* chore: fix lint issues
* fix the underlying issue instead
---------
Co-authored-by: 김현희 <pygmal@gimhyeonhuiui-MacBookAir.local>
Co-authored-by: Keyan <34140557+huumn@users.noreply.github.com>
Co-authored-by: k00b <k00b@stacker.news>
* territory specific trust
* functional parity with master
* revert back to materialized view for ranking
* update query for populating subWeightedVotes
* fix anon hot comments
* fix zap denormalization, change weightedComments to be for zaps, order updates of ancestors to prevent deadlocks
* reduce weight of comment zaps for hot score
* do zap ancestor updates together
* initialize trust in new/unpopular territories
* simplify denormalization of zap/downzaps
* recompute all scores
* 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>
