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月1日（下午）讲道反思： 关怀就是：彼此认罪

By -

关怀就是：彼此认罪



今天下午听了教会关于关怀小组主题的一篇讲道，主题是： 彼此认罪。

说实话，这不是一个让我觉得“舒服”的主题。 如果要列出我们彼此关怀的方式，这大概不会排在前几名。 向神认罪，我可以理解；向另一个人认罪，就感觉很冒险。

讲道一开始就点出了这个张力。是的，罪最终是得罪神的， 也只有神能赦免罪。这一点没有争议。 但雅各书 5:16 仍然说： “你们要彼此认罪，互相代求，使你们可以得医治。”

让我印象最深的不是“你必须去做”，而是为什么要这样做。 不是为了暴露自己，也不是为了情绪宣泄， 而是为了得到安慰和劝勉。

有时候，我们已经向神认过罪了， 但心里的愧疚感仍然挥之不去。 或者反复跌倒，让人开始怀疑： 我真的悔改了吗？神真的饶恕我了吗？

这时，有另一个基督徒能把福音再一次对你说出来， 用神的话安慰你，并为你祷告， 这本身就是神赐下的一种医治方式。

讲道也提到，罪是很顽固的。 隐藏它，往往只会让它更强。 把它带到光中，才可能有人陪你一起面对， 给你实际的提醒和帮助。

我也很受提醒的一点是： 关怀不仅是“去认罪”， 也是如何接住别人的认罪。 不是论断，不是好奇， 而是温柔、福音，以及把事情带到神面前。 而且，它应该止于你。

最后有一个比喻我很喜欢。 我们的生命像一栋房子，有不同的房间。 不是每个人都能进每一个房间，这很正常。 但不应该有一个永远上锁、谁都不能进的房间。

至少，应该有一个人， 能看见整栋房子。

这不是一件容易的事。 但我离开教会时在想， 也许正是这样的真实和敞开， 神用来带来医治、自由， 以及真正彼此相爱的教会生活。

❤️ 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