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年二月一日，主日早堂讲道反思：犹大书中的一个必要提醒

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 “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