A New Collection of Thoughtful Learning Apps — Now Available on iOS & Android

By -
Image
I’m excited to share a set of mobile apps I’ve recently completed and published on both the Google Play Store and the Apple App Store. These apps are designed with a simple goal in mind: to make meaningful, structured content more accessible, whether you’re studying theology or improving your English vocabulary. 📱 Now Available on Both Platforms All apps are live and available for download: Google Play Developer Page: https://play.google.com/store/apps/dev?id=5835943159853189043 Apple App Store Developer Page: https://apps.apple.com/ca/developer/q-z-l-corp/id1888794100 📖 Theology & Confession Study Apps For those interested in Reformed theology and classical Christian teachings, I’ve developed a series of apps that present foundational texts in a clean, focused reading format: The Belgic Confession Canons of Dort Heidelberg Catechism Westminster Shorter Catechism Each app is designed to provide a distraction-free experience, making it easier to read, reflect, and revisit these im...
Post a Comment

2026年2月15日 主日早晨听道反思: 当警告也是一种爱

By -

当警告也是一种爱



这次讲道从犹大书的一句严肃宣告开始：“他们有祸了。”整段信息围绕一个核心展开——人所走的道路，最终都会显明方向与结局。

讲员从历史人物、自然图像和古代文献三个角度，一次次回到同一个重点：远离神的生命，看起来可能吸引人、轻松甚至合理，但最终是空的，也是危险的。

让我印象最深的是关于“隐藏危险”的提醒。那些看起来没有问题、甚至让人感觉舒服的声音，并不一定真正带来生命。有些影响不会立刻显出破坏力，却会慢慢让人偏离方向。

这让我开始反思：信仰对我来说，是习惯，还是生命？是外在参与，还是内在真实？我是否愿意接受提醒，还是只愿听让人轻松的话？

讲道也用了许多自然界的比喻：没有雨的云、不结果子的树、漂流不定的星。这些画面都指向一个共同点——外表存在，却没有真正的生命供应。听到这里，很难不问自己：我的生命有没有带来一点真实的果子？

关于审判的信息听起来不轻松，但整篇信息给我的感受不是压迫，而是认真。真正关心人的提醒，不只是安慰，也包含警醒。因为如果方向错了，再轻松的路也不会带到正确的地方。

这次听道留下的一个简单祷告是：愿意被提醒，愿意被修正，也愿意继续走在正确的方向上。

信仰不是一次决定，而是每天的道路。

❤️ Support This Blog

If this post helped you, you can support my writing with a small donation. Thank you for reading.

Coffee ☕ Thanks 🙏 Extra Support ❤️

Comments

Post a Comment

Popular Posts

Fix up watchman issue with Ghost

By -
# Issue >>     >>     at BunserBuf.<anonymous> (/home/errong_leng/Ghost/core/client/node_modules/fb-watchman/index.js:95:23) >>     at emitOne (events.js:116:13) >>     at BunserBuf.emit (events.js:211:7) >>     at BunserBuf.process (/home/errong_leng/Ghost/core/client/node_modules/bser/index.js:292:10) >>     at /home/errong_leng/Ghost/core/client/node_modules/bser/index.js:247:12 >>     at _combinedTickCallback (internal/process/next_tick.js:131:7) >>     at process._tickCallback (internal/process/next_tick.js:180:9) >> A non-recoverable condition has triggered.  Watchman needs your help! >> The triggering condition was at timestamp=1509698956: inotify-add-watch(/home/errong_leng/Ghost/core/client/node_modules/ember-cli-node-assets/node_modules/broccoli-funn...
Read more

Using Mutual TLS (mTLS) in Next.js (Server-Side Only)

By -
Image
Using Mutual TLS (mTLS) in Next.js (Server-Side Only) In the previous posts, we covered: Part 1: Making mTLS API requests from Node.js clients Part 2: Enabling mTLS in Node.js servers Now we focus on Next.js applications and how mTLS works depending on deployment. Next.js Cannot Access TLS Handshake Directly Next.js middleware and API routes run after the TLS handshake They cannot see client certificates or verify them Next.js built-in server does not expose Node's HTTPS options like requestCert In short: Next.js middleware cannot enforce mTLS or access TLS handshake details . Any enforcement must happen before the request reaches Next.js. Next.js as an mTLS Client (Server-Side API Calls) Next.js can securely call mTLS-protected APIs from server-side code, such as: API routes Server actions import fs from 'fs'; import https from 'https'; import axios from 'axios'; export async function GET(req) { const...
Read more