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