WHY SHOOT OUR WOUNDED?
Yes, read that again...Why Shoot Our Wounded?

- Ps. 109:21-31
A Detroit newspaper reportd that a patient in a local hospital was shot and killed as he lay in his bed recovering from a previous gunshot wound. The victim had been listed in fair condition

prior to the shooting and was looking forward to going home. Hospital patients and employees were stunned. A spokesperson said that nothing like this had happened in the 50yrs of the hospital's existence.

Wouldn't it be wonderful if we could say the same for our churches?
Wouldn't it be encouraging if we were able to say that in 50yrs of meeting together for worship, fellowship and spiritual healing, we had not had a single instance of a wounded member being cut down by the unkindness of a fellow Christian?

Many among us have experienced the
pain that David expressed in Psalm 109. When he was hurt and vulnerable, insensitive people took advantage of him. Certainly, if he ad sinned, he needed their loving correction. what he didn't need was their scorn, gossip, and selfish neglect. Who shoots his foot after stubbing
his toe? No one in his right mind. Neither should anyone with the mind of Christ act unmercifully toward a wounded brother or sister in the body of Christ. Rather, we must "show mercy" (v.16).

Give me, Lord, a lot of mercy
For my fellow men each day,
Mercy in their many failures

More from Pastor 't.O.s.I.n. Olunuga

More from Messagethreadreaderapp unroll

You May Also Like

12 TRADING SETUPS which experts are using.

These setups I found from the following 4 accounts:

1. @Pathik_Trader
2. @sourabhsiso19
3. @ITRADE191
4. @DillikiBiili

Share for the benefit of everyone.

Here are the setups from @Pathik_Trader Sir first.

1. Open Drive (Intraday Setup explained)


Bactesting results of Open Drive


2. Two Price Action setups to get good long side trade for intraday.

1. PDC Acts as Support
2. PDH Acts as


Example of PDC/PDH Setup given
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.