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 一月11号 - 上午主日敬拜反思：从犹大书的问安看我们的身份

By -

主日敬拜反思：从犹大书的问安看我们的身份



地点：Langley Canadian Reformed Church

今天的主日讲道信息，出自《犹大书》短短却极其厚重的开头问安。起初我也和许多人一样，读圣经时往往很快略过这些“格式化”的开头，迫不及待想进入“重点内容”。但今天的信息提醒我：在圣灵默示下写下的每一个字，都不是多余的。

犹大没有急着进入警告假教师、呼吁争辩真道的主题，而是先用一个问安，为整封书信奠定了属灵的根基。也正是在这里，我重新被提醒：我是谁。

一、犹大是谁？——主耶稣基督的仆人

讲道中让我印象很深的一点，是犹大的自我介绍方式。他明明是主耶稣的弟弟，却没有以“主的家人”自居，而是称自己为“耶稣基督的仆人”。这不是谦虚的客套话，而是他真实的身份认知。

作为一名信徒，我也不得不反思：如果让我用一句话来定义自己，我会怎么说？是职业？家庭角色？成就？还是——耶稣基督的仆人？

“你们不是自己的人，因为你们是重价买来的。”（林前6:19-20） 这句话在今天的讲道中显得格外真实。我们确实是被释放了，但我们也是被买赎的。我们的人生不再属于自己，而是属于那位为我们舍命的主。

二、我们是谁？——蒙召、蒙爱、蒙保守的人

犹大书一开始，就用三个词来定义收信的信徒：蒙召的、在父神里蒙爱的、为耶稣基督保守的。

这是一个完全“被动”的身份描述。不是我们做了什么，而是神为我们做了什么。

  • 蒙召的：不是仅仅被邀请，而是被神亲自带进祂的国度。
  • 蒙爱的：神呼召我们，不是因为我们配得，而是因为祂爱。
  • 蒙保守的：不是我们紧紧抓住神，而是神紧紧抓住我们。

讲道中提到的那句诗歌反复在我心中回响： “祂必保守我，因我救主深爱我。” 在这个充满不确定、动摇信仰根基的时代，这样的确据实在宝贵。

三、真正顺服基督主权的动力

犹大写这封信，是因为教会正面对假教师的冲击。他们高举“自由”，却引人远离基督的主权。这让我意识到：这并不是一个遥远的历史问题，而是今天教会同样面对的挑战。

讲道中提出一个非常深刻的洞见：人之所以偏离基督的主权，往往不是因为不懂命令，而是因为对神的怜悯、平安和爱认识不足。

顺服不是靠意志硬撑，而是从心里被神的怜悯融化； 圣洁不是靠自律维持，而是因与神和好的平安； 忠心不是因为惧怕惩罚，而是因为深知自己被爱。

四、主餐中的再次确认

今天我们也一同领受了主的圣餐。那一小块饼、一小杯酒，再一次向我确认： 我是被重价买来的， 我与神之间有真实的平安， 我活在一份无法测透的爱中。

当我这样被提醒、被坚固，我也更愿意再次将自己交托在基督的主权之下，不是勉强，而是甘心。

愿神继续借着祂的话语，保守我们在这世代中站立得稳， 在真道上争辩， 在爱中持守， 直到主耶稣基督再来。

阿们。

❤️ 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 “A problem occurred starting process 'command node'” in Android Studio for React Native

By -
Image
Fix “A problem occurred starting process 'command node'” in Android Studio for React Native If you are building a React Native Android project and encounter this error during Gradle sync: A problem occurred evaluating project ':react-native-svg'. > A problem occurred starting process 'command 'node'' —even though node works perfectly in your terminal—this guide will show you how to fix it quickly. Common Misconceptions This error is often mistaken as a Node.js or PATH issue, but that is not always the case. Node.js is installed and working in your terminal. PATH and environment variables appear correct. Still, Android Studio Gradle sync fails with the above error. The Real Cause The issue typically arises because of an incorrect Gradle JDK configuration inside Android Studio . Gradle runs inside a JVM and uses that JVM to spawn external processes (like node ). If the Gradle JDK is incompatible or misconfigured, Gradle will...
Read more

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