4e41f67e87
fix notification url replacement
2023-08-03 18:04:43 -05:00
8a5cd32be6
don't use next's script tag
2023-08-03 17:49:56 -05:00
94e975033c
fix fee button receipt background color
2023-08-03 15:13:07 -05:00
0ab9119739
improve notifications UX: highlight reply and distinguish new notifications
2023-08-03 14:56:59 -05:00
7596b0302a
improve click to context behavior and add ssrForceFetchDelay to apollo
2023-08-03 13:13:49 -05:00
c088a379d7
add lb based scaling health check
2023-08-02 21:33:53 -05:00
8f52d63569
try upgrading next to canary?
2023-08-02 20:32:56 -05:00
394b898bd8
downgrade next 13.4.11 due to buggy child processes
2023-08-02 19:44:26 -05:00
4bf0c46efc
npm dedupe
2023-08-02 17:56:43 -05:00
087e43ae8f
make sudo preserve env on build
2023-08-02 16:59:23 -05:00
98c3632f58
su webapp on deploy
2023-08-02 15:51:09 -05:00
16e882a1ce
upgrade back to node 18
2023-08-02 15:51:01 -05:00
a0632bc748
a dream: maybe its a bug in node that's been since patched
2023-08-02 14:58:49 -05:00
bbc997c5b1
remove unused gifs
2023-08-02 13:54:43 -05:00
599d3c41f0
fix next timeout typo
2023-08-02 12:13:40 -05:00
1e97726a66
make sure upstreams have longer keepalives
2023-08-02 11:36:23 -05:00
2f3551939c
let nginx manage keepalive
2023-08-02 10:40:03 -05:00
918c5a0d08
add keep alive timeout to next start
2023-08-02 05:50:53 -05:00
b1b8f9de56
implement our own nprogress bar
2023-08-01 21:06:15 -05:00
a426c8b539
fix 404 problem
2023-08-01 12:45:46 -05:00
2732e3bb83
fix rewards bug
2023-08-01 11:10:07 -05:00
f135eae16d
cast enum in reverse_withdrawl
2023-08-01 07:00:46 -05:00
6f445f2545
move prisma out of dev deps for eb
2023-07-31 16:19:27 -05:00
c7e2623461
increase apollo slowlog threshold
2023-07-31 16:02:50 -05:00
e1c51075a2
fix conditional nextFetchPolicy overriding cache-only on SSR and suppress time hydration warnings
2023-07-31 14:54:30 -05:00
b550f80b9f
make invoices/withdrawals clickable in satistics
2023-07-31 13:00:01 -05:00
f7bf77ebd4
fix BigInt Int mix in satistics
2023-07-31 12:47:41 -05:00
f91be5d70f
fix form skeleton
2023-07-31 12:35:58 -05:00
8c1ad530bc
downgrade to node v16
2023-07-31 12:22:26 -05:00
b42a934207
fix invites signup via lightning/slashtags
2023-07-31 09:19:53 -05:00
bc5a19c6ee
suppress hydration warnings when relative time is rendered
2023-07-31 09:12:56 -05:00
10e8cb35df
fix import on invites
2023-07-31 09:11:22 -05:00
8581088bd4
make sure dev db timezone is utc
2023-07-31 09:03:01 -05:00
d5aeea6dd3
bump packages again
2023-07-31 08:43:13 -05:00
d2216e80da
conform to linter
2023-07-31 08:39:10 -05:00
c909efb7b7
update wallet code to prisma 5, handle prisma 5 errors on serialization
2023-07-31 08:31:40 -05:00
acd8a8de5a
add dark mode to precache
2023-07-31 07:37:42 -05:00
c975bd8ebd
Fix unexpected token 'export'
2023-07-30 23:45:08 +02:00
ba04e6522d
Also strike on payment after short press
2023-07-30 23:45:08 +02:00
d186e869e1
Allow pay per invoice for bounty and job posts
2023-07-30 23:45:08 +02:00
f2f09b22c4
Fix invoice amount for comments
2023-07-30 23:45:08 +02:00
1cd9750be5
Fix insufficient funds error detection
2023-07-30 23:45:08 +02:00
773f658e00
Remove duplicate insufficient funds handling
2023-07-30 23:45:08 +02:00
28ea5ab70e
Skip 'invoice not found' errors
2023-07-30 23:45:07 +02:00
85162b6d33
Add error handling
2023-07-30 23:45:07 +02:00
f0d0d07bad
Skip anon user during trust calculation
2023-07-30 23:45:07 +02:00
6b4b5023f6
Keep invoice modal open if focus is lost
2023-07-30 23:45:07 +02:00
7dda8a1e01
Fix onSuccess called twice
...
For some reason, when calling `showModal`, `useMemo` in modal.js and the code for the modal component (here: <Invoice>) is called twice.
This leads to the `onSuccess` callback being called twice and one failing since the first one deletes the invoice.
2023-07-30 23:45:07 +02:00
853a389b65
Allow pay per invoice for stackers
...
The modal which pops up if the stacker does not have enough sats now has two options: "fund wallet" and "pay invoice"
2023-07-30 23:45:07 +02:00
fd8510d59f
Use payment hash instead of invoice id as proof of payment
...
Our invoice IDs can be enumerated.
So there is a - even though very rare - chance that an attacker could find a paid invoice which is not used yet and use it for himself.
Random payment hashes prevent this.
Also, since we delete invoices after use, using database IDs as proof of payments are not suitable.
If a user tells us an invoice ID after we deleted it, we can no longer tell if the invoice was paid or not since the LN node only knows about payment hashes but nothing about the database IDs.
2023-07-30 23:45:07 +02:00
keyan
ekzyis