All Activity

So once the letter writing function is activated how can I assign it to individual publishers or the group overseer to share with his group? Is there some functionality with that?

How does this work? I've marked apartments as not at home but I don't see it convert to letter writing automatically.

When I saw this I said oh they are going to do series based on the book of acts. Everyone thought I was crazy lol. Interestingly the brother who played Paul in that snippet gave a talk at my convention.

I'm keeping this around. A sister in my Cong is really sad and depressed recently, feeling that everyday goes wrong. We preached in the same car today and she was speaking about her wait for Armageddon... Or her own death. She is 40 years old. Basically hoping everyday that she is going to wake up in Paradise. Poor sister... I'm praying a lot for her. We will do a SC soon.

Job lost his 10 children, and Jehovah did not resurrect them at that time. Do you think Job missed them every day while waiting for Jehovah to resurrect them through Jesus in the future? David lost many sons. When Absalom died, he cried: David paced the floor of the roof chamber, crying: "My son Absalom, my son, my son Absalom! O that I might have died, I myself, instead of you, Absalom, my son, my son!" Before David died, he was always sick in bed, and Jehovah did not cure him at that time. Why do you think Jehovah will take away his pain now? He promises that in the future, if you trust in him, he will eliminate all the pains you have today. But it is necessary to fight every day. Psalms 37:28,29 For Jehovah loves justice, And he will not abandon his loyal ones. They will always be guarded; But the descendants of the wicked will be done away with.   The righteous will possess the earth, And they will live forever on it. Revelation 21:3, 4: The tent of God is with mankind, and he will reside with them, and they will be his people. And God himself will be with them. And he will wipe out every tear from their eyes, and death will be no more, neither will mourning nor outcry nor pain be anymore. The former things have passed away.” Hebrews 10:35-39 Therefore, do not throw away your boldness, which will be richly rewarded. For you need endurance so that after you have done the will of God, you may receive the fulfillment of the promise. For yet “a very little while,” and “the one who is coming will arrive and will not delay." “But my righteous one will live by reason of faith,” and “if he shrinks back, I have no pleasure in him.” Now we are not the sort who shrink back to destruction, but the sort who have faith for the preserving of our lives.

"Never for a moment have I doubted Jehovah's love...I just kept searching for EVIDENCE that the pain would go away." Those are deep strong words coming from a servant of Jehovah...especially when you consider the fact that we HAVE Jehovah...and the world has nothing to cling onto...except lies and meaningless drivel designed to occupy their brain until they die. Who said those words? I did. Why did I say them? Because I misunderstood a facet of a scripture we've read a thousand times over my lifetime: 2 Corinthians 1:3,4: "Praised be the God and Father of our Lord Jesus Christ, the Father of tender mercies and the God of all comfort, 4 who comforts us in all our trials so that we may be able to comfort others in any sort of trial with the comfort that we receive from God." I didn’t realize how much I was waiting for something to change...before I let myself feel comforted. And that made me stop and ask myself something uncomfortable: When did relief become the way I measured Jehovah’s nearness? As I read Paul’s words...“the God of all comfort, who comforts us in all our tribulation”...I noticed how quickly my mind jumped ahead. Ahead to the outcome. Ahead to the moment when the pressure would finally just lift...and just GO AWAY!! But Paul didn’t say Jehovah comforts us after the tribulation. He said Jehovah comforts us in it. So I had to ask myself: Have I been reading this verse as a promise of results…instead of what it mainly is...a promise of his presence? Have I been waiting for proof that the pain would end, instead of noticing that I was still standing? If Jehovah were truly absent, would I even be enduring at all? The Greek word Paul uses for “comfort” is paráklēsis...a word Jehovah's people know very well...a word that that means to be called alongside. Not to fix from a distance. Not to remove the weight immediately. But to come close enough to share the space. That realization shifted a lot of smaller little things for me personally. Because suddenly the question wasn’t, “Why hasn’t Jehovah taken this away yet?” It became, “What if Jehovah has been here the entire time...and I was just focused on results too much to even notice him?” Paul says Jehovah gives us the courage and strength to bear up. And that made me wonder: What if mere day to day survival isn't just somehow staggering along...but actual evidence of his presence by itself? In other words: What if endurance itself is the comfort I’ve been overlooking? What if Jehovah’s way of proving his care for me isn’t by changing the situation...but by refusing to leave me alone inside it? The September 2008 Watchtower states that Jehovah does not necessarily make our problems or pain disappear...but he DOES fortifiy us to cope with them. And for the first time, that didn’t sound like a lesser comfort. It sounded like a deeper one. https://www.jw.org/en/library/magazines/wp20080901/The-God-of-All-Comfort/ Because if Jehovah were TRULY distant, endurance would feel empty. If he had TRULY stepped away, courage wouldn’t keep showing up. If he weren’t in the room, the weight would be unbearable...if his holy spirit wasn't continuing to give me the power beyond what is normal...Tim simply couldn't survive...SPIRITUALLY! So maybe the real question isn’t why the pain is still here...and why hasn't it gone away? Maybe it’s this: When did I start believing that comfort had to look like proof...instead of presence?

If I remember correctly, Leonard said the Cohanim in the congregation - cannot remember if this was during a particular holy day - would raise their hands in this manner towards the congregation, and then speak the words at Num. 6:24-26.

Notice the phrase “thinks he is standing.” The danger is not instability. The danger is perceived stability. We begin to measure strength by recent performance. A temptation resisted. 'I changed the channel! Not going to watch that.' A reaction controlled. 'Traffic no longer frustrates me.' A season of calm. 'My wife and I are so much closer. Our marriage is tight. Nothing can ruin this' None of those are wrong. In fact, they are evidences of growth. But growth can quietly mutate into self-trust. A structure can appear firm when no wind is blowing. The absence of visible stress is not proof of anchoring. Foundations are tested by pressure, not by stillness. We may feel steady simply because circumstances have been favorable. Remove the pressure, and stability can be mistaken for maturity. The most reliable footing is not confidence in progress; it is humility in the present. Standing shows itself not by yesterday’s victories, but by today’s reliance.

Wednesday, February 25 Let the one who thinks he is standing beware that he does not fall.—1 Cor. 10:12. Likely, we can rid ourselves completely of some imperfect tendencies. But we might find that other inclinations continue to give us trouble. Consider the case of the apostle Peter. He gave in to fear of man when he denied Jesus three times. (Matt. 26:69-75) Peter seemed to have overcome that fear when he gave a bold witness before the Sanhedrin. (Acts 5:27-29) However, some years later, “fearing those of the circumcised class,” he temporarily stopped eating with Gentile Christians. (Gal. 2:11, 12) Peter’s fear had returned. Perhaps he was never completely free of it. We might find ourselves in a similar situation. However, we can resist a persistent tendency by following Jesus’ counsel to “keep on the watch.” (Matt. 26:41) Even when you feel strong, continue to avoid situations that can lead to temptation. Keep applying the strategies that brought you success.—2 Pet. 3:14. w24.07 18-19 ¶17-19

Sitting every day for 8 hours or more will cause premature death just as surely as smoking cigarettes will.

Here is a new one with a JW theme Empty Chairs

You may be able to satisfy his needs by the way you set up the S-13 report. (See S-13_02.png) If you make sure to select records for 2 service years, the actual S-13 assignment blocks will show everything he needs to know. He needs to count how many territories have not been worked in last 12 months. So if he has assignment records for current (partial) service year and the previous full year, he can easily make his count. The column marked "Last Completed Date" makes it even simpler for him: The program grabs the 'Completed' date from the last time the territory was turned in, and places it in this column for him. The CO can just examine this one column: If he sees a date that is older than the current date 1 year ago, then he knows the territory has not been worked in last year. (See S-13_01.png)

O and when the warning expires tonight (Tuesday) at 7 pm then we’re under an advisory till 7 pm tomorrow. The way this winter has been going they’ll either extend it or upgrade it. 🙄

I only have two people who have sharing enabled and are in #1433, and the data loss I described occurs every time.

It's a known issue the NWS brothers are working on. You'll see the following alert when you go to report this issue from their website..

ok, I saw in the "problems" section that I am aware of the problem, let's hope they solve it quickly, hugs

Sorry, dear brothers, but are you having the same problem? The maps are no longer visible... stiamo usando openstreetmaps

A Reactive, Privacy-First Architecture When developing Baruch, architecture is not just a technical concern — it directly affects trust, stability, and peace of mind. With Baruch, I've made a deliberate architectural shift. A foundation that is: Deterministic Privacy-conscious Offline-first Maintainable long-term Here I explains the architecture behind Baruch — and what it means for elders, planners, and publishers who use it. State-Driven, Not Event-Driven Traditional software applications often grow organically: UI events mutate domain objects Services update databases Sync logic reacts afterward State is spread across layers Over time, this leads to hidden side effects, fragile flows, and increasing complexity. Baruch takes a different approach. Instead of letting changes happen everywhere, we centralize change into structured state modules. Baruch v2 is built in six clear layers: 1. User Interface Layer The UI layer is intentionally simple. It: Sends user intents (e.g., “NameChanged”) Reflects application state Handles layout and visual validation It does not: Contain business logic Manage persistence Handle synchronization This keeps screens predictable and stable. 2. Reactive Module Layer Each bounded context — such as Congregation, Assignments, or Families — has its own module. Each module contains: Immutable State (record types) Intents (user-driven actions) A pure Reducer (state transition logic) Every change flows through a single deterministic pipeline: Intent → Reducer → New State No hidden mutations. No silent side effects. This makes the system transparent and testable. 3. Domain Core Layer This is where the real congregation logic lives. Examples: Assignment calculation engine Qualification rules Rotation algorithms Availability rules The domain layer is: Pure Side-effect free Independent of UI and storage Given the same inputs, it always produces the same outputs. This is essential for fairness and reliability in planning. 4. Application Services Layer This layer orchestrates use cases: Generate next schedule Import existing data Export reports Migrate data It coordinates modules, domain logic, and persistence — but contains no UI or business rules itself. 5. Persistence & Sync Infrastructure Baruch is designed to be offline-first. Local storage is the primary source of truth. Cloud synchronization: Uses anonymous identifiers Does not store personal identifiable information (PII) - implicit GDPR compliant Operates as a synchronization layer, not a master database This greatly reduces risk exposure. 6. Privacy Boundary A key architectural decision in Baruch is explicit separation between: Local-only personal data Names Phone numbers Addresses Notes and Cloud-safe data Anonymous IDs Assignment structures Scheduling metadata By design, sensitive personal data is never centralized in the cloud. Why This Architecture Matters for Us Architecture is invisible — until it fails. Here’s what this approach means in practical terms for elders and congregation members. 1. More Reliable Scheduling Because planning engines are deterministic: The same input always produces the same schedule There are no hidden side effects Assignments are calculated consistently This improves fairness and predictability in congregation responsibilities. 2. Fewer Errors and Surprises When state changes are centralized: There are fewer race conditions No unexpected overwrites Reduced risk of conflicting updates This leads to smoother coordination. 3. Offline Stability Baruch does not depend on constant internet access. If the internet connection fails: Planning continues Data remains accessible No interruption to congregation work This is especially important in regions with unstable connectivity. 4. Reduced Privacy Risk Because personal data remains local: There is no central database containing congregation member details The impact of a cloud incident is significantly minimized Compliance complexity is reduced For elders, this lowers administrative and legal burden. For members, it increases trust. 5. Long-Term Maintainability A deterministic, modular architecture ensures that: Features can be added without destabilizing existing ones Bugs are easier to isolate Future modules can integrate cleanly This protects the investment congregations make in adopting the system. 6. Foundation for Future Growth Baruch’s architecture supports: Undo/redo capabilities Advanced reporting Smarter assignment engines Expanded mobile capabilities Without needing to redesign the core again. Technical note: I use MAUI.NET in combination with Rx.NET for implementation.

*DEAR BROTHERS AND SISTERS* _Greetings to you all, my dear brothers and sisters. Hopefully we are all doing well under Jehovah’s loving care._ *Truly* , _the times we are living in are not easy. The pressures of these “critical times hard to deal with” can weigh heavily on many. 2 Tim. 3:1_ _But how comforting it is to know that we are not alone. We belong to a loving spiritual family._ _The Bible reminds us at Hebrews 10:24, 25 that we should “consider one another so as to incite to love and fine works… encouraging one another.” Now more than ever, our brothers and sisters need to feel that love and support._ _Sometimes, a simple message — “How are you doing?” — can mean so much. A short phone call, a visit, or even sitting beside someone quietly at the Kingdom Hall can strengthen a heart that is tired. As 1 Thessalonians 5:11 says: “Keep encouraging one another and building one another up.”_ _Let us remember that some may be fighting silent battles — health challenges, financial pressure, family problems, or emotional stress. We may not see their struggles, but Jehovah sees them. And he can use us to be a source of comfort._ *Isaiah 41:10* _assures us: “Do not be afraid, for I am with you… I will really help you._ _When we remind our brothers and sisters of Jehovah’s promises, we strengthen their faith and our own as well._ _Dear brothers and sisters, let us:_ *Check on one another regularly* *Speak kindly and listen patiently* *Pray for one another* *Be quick to forgive and slow to judge* _A congregation filled with encouragement is a strong congregation. Even a small act of kindness can Make a big difference._ _May Jehovah continue to bless our efforts to love one another deeply from the heart. Let us keep holding on — the best days are ahead of us._ *With warm Christian love* .♥️

I agree with Floyd that your cirduit overseer is a little mixed up. The only thing that is supposed to be entered in that column is the actual true date that the territory is completed. He may be misinterpreting the question on the CO report he sends in - "How many territories have not been completed in the last year?" (Or simildar wording if it hasn't changed)That doesn't have anything to do with the service year, it means a calendar year. If the circuit overseer checks the records on February 24, 2026, he would determine how many territories have not been completed since February 24, 2025. In the U.S. there are rural congregations that have not completed their territories in 2-3 years. There are other congregations that work their entire territory every week. The Branch is just getting a broad idea of areas that need help.