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一月25日 - 主日下午听道反思：比利时信条第28条

By -

主日下午听道反思：比利时信条第28条

“凡要得救的人，必须加入教会。”



第28条的核心教导

今天下午的讲道围绕《比利时信条》第28条展开，强调信徒加入教会的必要性。信条明确指出：在教会之外没有救恩，教会是蒙救赎者的圣洁会众。

讲道澄清，这并不是说救恩来自某一个具体的教会或宗派，而是指出神设立教会，作为祂聚集和保守百姓的正常途径。

救恩与话语的事工

圣经清楚教导，救恩唯独借着信靠耶稣基督而来。罗马书第10章指出，人因听见福音、相信并承认基督而得救。

讲道强调，神通常借着教会中福音的宣讲，使人得着信心。话语的事工属于教会，神也应许要通过祂所差遣的传道人来成就救恩。虽然神能够以非常的方式施行拯救，但信徒并不应期待例外，而是当在神应许施恩的地方寻求祂。

什么是教会？

讲道提醒我们，“教会”并不首先指建筑物或聚会本身。圣经使用的词是 ekklesia，意为“被呼召、被聚集的人”。教会是信徒在基督里被召聚在一起的可见群体。

因此，加入教会不是可有可无的选择，而是属基督之人的必然结果。属于基督，也就属于祂的身体。

教会是蒙救赎者的圣洁会众

第28条称教会为“圣洁的”，意思是被神分别出来。教会并非完全无瑕，却是与世界有别的群体。在教会中，信徒接受教导、劝戒、鼓励，并被引导过敬虔的生活。

教会也是蒙救赎者的会众，是那些借着基督的宝血脱离罪恶、同在祂权柄之下生活的人。

作为基督身体的成员而生活

讲道最后指出，每一位信徒在教会中都有其位置与责任。圣灵赐下不同的恩赐，为要造就整个身体。积极参与、彼此关怀和服侍，是忠心教会生活的重要表现。

第28条呼召信徒不仅加入教会，也要顺服教会的教导与治理，这是神为保守信心、建立祂子民所设立的恩典方式。

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