2021-10-20 19:57:11 +00:00
|
|
|
############################################################################
|
|
|
|
|
# AUTH / OPTIONAL #
|
|
|
|
|
# if you want to work on logged in features, you'll need some kind of auth #
|
|
|
|
|
############################################################################
|
|
|
|
|
|
|
|
|
|
# github
|
|
|
|
|
GITHUB_ID=<YOUR GITHUB ID>
|
|
|
|
|
GITHUB_SECRET=<YOUR GITHUB SECRET>
|
|
|
|
|
|
|
|
|
|
# twitter
|
|
|
|
|
TWITTER_ID=<YOUR TWITTER ID>
|
|
|
|
|
TWITTER_SECRET=<YOUR TWITTER SECRET>
|
|
|
|
|
|
|
|
|
|
# email
|
|
|
|
|
LOGIN_EMAIL_SERVER=smtp://<YOUR EMAIL>:<YOUR PASSWORD>@<YOUR SMTP DOMAIN>:587
|
|
|
|
|
LOGIN_EMAIL_FROM=<YOUR FROM ALIAS>
|
|
|
|
|
|
|
|
|
|
# lnurl-auth
|
|
|
|
|
LNAUTH_URL=<YOUR PUBLIC TUNNEL TO LOCALHOST, e.g. NGROK>
|
|
|
|
|
|
Service worker rework, Web Target Share API & Web Push API (#324)
* npm uninstall next-pwa
next-pwa was last updated in August 2022.
There is also an issue which mentions that next-pwa is abandoned (?): https://github.com/shadowwalker/next-pwa/issues/482
But the main reason for me uninstalling it is that it adds a lot of preconfigured stuff which is not necessary for us.
It even lead to a bug since pages were cached without our knowledge.
So I will go with a different PWA approach. This different approach should do the following:
- make it more transparent what the service worker is doing
- gives us more control to configure the service worker and thus making it easier
* Use workbox-webpack-plugin
Every other plugin (`next-offline`, `next-workbox-webpack-plugin`, `next-with-workbox`, ...) added unnecessary configuration which felt contrary to how PWAs should be built.
(PWAs should progressivly enhance the website in small steps, see https://web.dev/learn/pwa/getting-started/#focus-on-a-feature)
These default configurations even lead to worse UX since they made invalid assumptions about stacker.news:
We _do not_ want to cache our start url and we _do not_ want to cache anything unless explicitly told to.
Almost every page on SN should be fresh for the best UX.
To achieve this, by default, the service worker falls back to the network (as if the service worker wasn't there).
Therefore, this should be the simplest configuration with a valid precache and cache busting support.
In the future, we can try to use prefetching to improve performance of navigation requests.
* Add support for Web Share Target API
See https://developer.chrome.com/articles/web-share-target/
* Use Web Push API for push notifications
I followed this (very good!) guide: https://web.dev/notifications/
* Refactor code related to Web Push
* Send push notification to users on events
* Merge notifications
* Send notification to author of every parent recursively
* Remove unused userId param in savePushSubscription
As it should be, the user id is retrieved from the authenticated user in the backend.
* Resubscribe user if push subscription changed
* Update old subscription if oldEndpoint was given
* Allow users to unsubscribe
* Use LTREE operator instead of recursive query
* Always show checkbox for push notifications
* Justify checkbox to end
* Update title of first push notification
* Fix warning from uncontrolled to controlled
* Add comment about Notification.requestPermission
* Fix timestamp
* Catch error on push subscription toggle
* Wrap function bodies in try/catch
* Use Promise.allSettled
* Filter subscriptions by user notification settings
* Fix user notification filter
* Use skipWaiting
---------
Co-authored-by: ekzyis <ek@stacker.news>
2023-07-04 19:36:07 +00:00
|
|
|
# VAPID for Web Push
|
|
|
|
|
VAPID_MAILTO=
|
|
|
|
|
NEXT_PUBLIC_VAPID_PUBKEY=
|
|
|
|
|
VAPID_PRIVKEY=
|
|
|
|
|
|
2021-10-20 19:57:11 +00:00
|
|
|
#######################################################
|
|
|
|
|
# LND / OPTIONAL #
|
|
|
|
|
# if you want to work with payments you'll need these #
|
|
|
|
|
#######################################################
|
|
|
|
|
|
|
|
|
|
# lnd
|
|
|
|
|
LND_CERT=<YOUR LND HEX CERT>
|
|
|
|
|
LND_MACAROON=<YOUR LND HEX MACAROON>
|
|
|
|
|
LND_SOCKET=<YOUR LND GRPC HOST>:<YOUR LND GRPC PORT>
|
|
|
|
|
|
|
|
|
|
###############
|
|
|
|
|
# LEAVE AS IS #
|
|
|
|
|
###############
|
|
|
|
|
|
|
|
|
|
# static things
|
|
|
|
|
NEXTAUTH_URL=http://localhost:3000/api/auth
|
|
|
|
|
SELF_URL=http://localhost:3000
|
2021-11-11 17:38:41 +00:00
|
|
|
PUBLIC_URL=http://localhost:3000
|
2021-10-20 19:57:11 +00:00
|
|
|
LND_CONNECT_ADDRESS=03cc1d0932bb99b0697f5b5e5961b83ab7fd66f1efc4c9f5c7bad66c1bcbe78f02@xhlmkj7mfrl6ejnczfwl2vqik3xim6wzmurc2vlyfoqw2sasaocgpuad.onion:9735
|
|
|
|
|
NEXTAUTH_SECRET=3_0W_PhDRZVanbeJsZZGIEljexkKoGbL6qGIqSwTjjI
|
|
|
|
|
JWT_SIGNING_PRIVATE_KEY={"kty":"oct","kid":"FvD__hmeKoKHu2fKjUrWbRKfhjimIM4IKshyrJG4KSM","alg":"HS512","k":"3_0W_PhDRZVanbeJsZZGIEljexkKoGbL6qGIqSwTjjI"}
|
Allow zapping, posting and commenting without funds or an account (#336)
* Add anon zaps
* Add anon comments and posts (link, discussion, poll)
* 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.
* 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"
* 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.
* Keep invoice modal open if focus is lost
* Skip anon user during trust calculation
* Add error handling
* Skip 'invoice not found' errors
* Remove duplicate insufficient funds handling
* Fix insufficient funds error detection
* Fix invoice amount for comments
* Allow pay per invoice for bounty and job posts
* Also strike on payment after short press
* Fix unexpected token 'export'
* Fix eslint
* Remove unused id param
* Fix comment copy-paste error
* Rename to useInvoiceable
* Fix unexpected token 'export'
* Fix onConfirmation called at every render
* Add invoice HMAC
This prevents entities which know the invoice hash (like all LN nodes on the payment path) from using the invoice hash on SN.
Only the user which created the invoice knows the HMAC and thus can use the invoice hash.
* make anon posting less hidden, add anon info button explainer
* Fix anon users can't zap other anon users
* Always show repeat and contacts on action error
* Keep track of modal stack
* give anon an icon
* add generic date pivot helper
* make anon user's invoices expire in 5 minutes
* fix forgotten find and replace
* use datePivot more places
* add sat amounts to invoices
* reduce anon invoice expiration to 3 minutes
* don't abbreviate
* Fix [object Object] as error message
Any errors thrown here are already objects of shape { message: string }
* Fix empty invoice creation attempts
I stumbled across this while checking if anons can edit their items.
I monkey patched the code to make it possible (so they can see the 'edit' button) and tried to edit an item but I got this error:
Variable "$amount" of required type "Int!" was not provided.
I fixed this even though this function should never be called without an amount anyway. It will return a sane error in that case now.
* anon func mods, e.g. inv limits
* anon tips should be denormalized
* remove redundant meTotalSats
* correct overlay zap text for anon
* exclude anon from trust graph before algo runs
* remove balance limit on anon
* give anon a bio and remove cowboy hat/top stackers;
* make anon hat appear on profile
* concat hash and hmac and call it a token
* Fix localStorage cleared because error were swallowed
* fix qr layout shift
* restyle fund error modal
* Catch invoice errors in fund error modal
* invoice check backoff
* anon info typo
* make invoice expiration times have saner defaults
* add comma to anon info
* use builtin copy input label
---------
Co-authored-by: ekzyis <ek@stacker.news>
Co-authored-by: keyan <keyan.kousha+huumn@gmail.com>
2023-08-11 23:50:57 +00:00
|
|
|
INVOICE_HMAC_KEY=a4c1d9c81edb87b79d28809876a18cf72293eadb39f92f3f4f2f1cfbdf907c91
|
2021-10-20 19:57:11 +00:00
|
|
|
|
2023-07-13 00:10:01 +00:00
|
|
|
# imgproxy
|
|
|
|
|
NEXT_PUBLIC_IMGPROXY_URL=
|
|
|
|
|
IMGPROXY_KEY=
|
|
|
|
|
IMGPROXY_SALT=
|
|
|
|
|
IMGPROXY_ENABLE_WEBP_DETECTION=1
|
|
|
|
|
IMGPROXY_MAX_ANIMATION_FRAMES=100
|
2023-08-10 17:17:33 +00:00
|
|
|
IMGPROXY_MAX_SRC_RESOLUTION=200
|
2023-08-15 17:55:16 +00:00
|
|
|
IMGPROXY_READ_TIMEOUT=10
|
|
|
|
|
IMGPROXY_WRITE_TIMEOUT=10
|
|
|
|
|
IMGPROXY_DOWNLOAD_TIMEOUT=9
|
2023-08-10 17:17:33 +00:00
|
|
|
# IMGPROXY_DEVELOPMENT_ERRORS_MODE=1
|
|
|
|
|
# IMGPROXY_ENABLE_DEBUG_HEADERS=true
|
2023-07-13 00:10:01 +00:00
|
|
|
|
2021-10-20 19:57:11 +00:00
|
|
|
# prisma db url
|
|
|
|
|
DATABASE_URL="postgresql://sn:password@db:5432/stackernews?schema=public"
|
|
|
|
|
|
|
|
|
|
# postgres container stuff
|
|
|
|
|
POSTGRES_PASSWORD=password
|
|
|
|
|
POSTGRES_USER=sn
|
|
|
|
|
POSTGRES_DB=stackernews
|
