Jason Leow

Using new payment provider Superpay https://superpayit.com/ because Wirize got acquired by it. 1% txn fee, not too bad at all

Rest is a form of productivity too...

Install patch-package
Edit package.json
Make changes to node_modules/module, added the correct offset function `new Date().setUTCMinutes(-180)` in `date-streaks` helper.js
Run npx patch-package package-name
Git commit and push

[UPDATE:] And it worked!!! 🎉

On the surface, 1% improvement don’t seem like much. But 1% compounded daily over a year means you’ll be 37.8 times better than when you started. The power of compounding is the reason why consistency matters as much as—or even arguably, more than—intensity....

While I work on the weird streak bugs (streaks going to zero then restored when you post) and the @mentions/notifications features which take more time on the backend, I didn't want to lose momentum by holding back all the other lower-hanging frontend features. So will be taking a concurrent approach, releasing smaller features while I work on the big ones!

📈 Total one-off revenue: $600
📊 MRR: $20

While working on features that take longer, I felt I needed to also concurrently work on the lower-hanging fruits so that there's a sense of momentum.

❌ new Date().toLocaleString('en-US', { timeZone: 'America/Sao_Paulo' })
✅ new Date().setUTCMinutes(-180)

Savvy Time had been super useful so far!

https://savvytime.com/converter/ca-los-angeles-to-az-phoenix-ny-new-york-city-trinidad-and-tobago-port-of-spain-brazil-sao-paulo-utc-switzerland-zurich-finland-helsinki-kuwait-al-ahmadi-india-kolkata-sgt-australia-melbourne

Streaks were 'breaking' and then restored due to the current day being hard-coded in UTC time by the `date-streaks` module. So I found that by shifting the timezone by a few hours (to UTC-3:00), it gives some of my US-based writers time to post for the day so that their streak didn't 'break' before they posted.

new Date().toLocaleString('en-US', { timeZone: 'America/Sao_Paulo' })

For indie hackers/makers, namely, developing, designing and marketing.

Taking a step back, to solve this new Date() doesn't apply offset issue, there seems to be 3 approaches I can take.

1. Patch date-streaks module directly by adding offset to new Date(), seems least effort, but hard to understand their code
2. Make my own streak.js plugin - making from scratch feels time-consuming but more control and less downstream gotchas
3. Use afterCreate lifecycle hooks within Strapi to save a new content-type streaks, so it's not calculated on the fly every time but saved as an integer as each post is created.

People are really liking it! https://animatedaccordionfaqs.carrd.co/

OK...... looks like the streak bug is still not completely dead, just like how cockroaches die hard. At least I identified the problem within a day, which is something to celebrate over. The first step to solving any bug is to isolate and identify, so that's a pat on my own back at least. My date streaks module uses `new Date()` in UTC to set the current day/date, and it doesn't apply user's timezone offset. So the array of published dates are offset to user's tz but it's always referenced to the the current date in UTC, which is why sometimes the streak breaks but restores when the user posts (e.g. if the user happen to write past the UTC midnight but still within his tz's midnight).

📈 Total one-off revenue: $480
📊 MRR: $20

Used `this.$nuxt.refresh()` to refresh just the page data for the comments (when user submits a comment), instead of an in-elegant entire page reload using `this.$router.go(0)`

Faced slight problem of input fields persisting even after submitting, so had to add `this.content = ' '`

await this.$axios.post('/comments', {
...
})
this.content = ' '
this.$nuxt.refresh()

Ref:
https://stackoverflow.com/questions/41518609/clearing-input-in-vuejs-form
https://nuxtjs.org/docs/2.x/concepts/context-helpers#refreshing-page-data

Tried using `${Intl.DateTimeFormat().resolvedOptions().timeZone}` in my SQL query but it didn't work. Didn't know how else to integrate that into my controller either. Discovered later I could try `date.getTimezoneOffset()` too, but had already went with using a combination of SQL function AT TIME ZONE, and getting users to set their timezone (I created a new table in the db to manually add their timezones first. If all works, will refactor to add a new column in the existing user's table).