So true what the Bible says..

Proverbs 28:12b NKJV
...But when the wicked arise, men hide themselves.

Everyone seem to be in hiding, Killers and their sponsors seem to be on a killing spree and the nation looks helpless. Not anymore in Jesus name.

This is what God says;

Jeremiah 48v28 MSG
"Leave town! Leave! Look for a home in the cliffs...(whether they are foreign killers or locally sponsored killers, the Lord says, "leave town")

Jeremiah 50:25 KJV
The Lord hath opened his armoury, and hath brought forth the weapons of his indignation: (
The Lord has opened His armoury)

They will bare the wrath of God.

They have sown wind.

Hosea 8:7 KJV
For they have sown the wind, and they shall reap the whirlwind:

Let all those sponsoring terror, bloodshed, banditry, kidnapping reap the whirlwind of God

Zech 10:6b MSG
Because I am their very own God, I'll do what needs to be done for them.

God will do whatever needs to be done in this country.

We have a lot to pray about. For our nation and for ourselves, this Sunday night at 8pm. (Live on Facebook and Instagram)

Join me if you can, and if

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

More from Messagethreadreaderapp unroll

You May Also Like

Recently, the @CNIL issued a decision regarding the GDPR compliance of an unknown French adtech company named "Vectaury". It may seem like small fry, but the decision has potential wide-ranging impacts for Google, the IAB framework, and today's adtech. It's thread time! 👇

It's all in French, but if you're up for it you can read:
• Their blog post (lacks the most interesting details):
https://t.co/PHkDcOT1hy
• Their high-level legal decision: https://t.co/hwpiEvjodt
• The full notification: https://t.co/QQB7rfynha

I've read it so you needn't!

Vectaury was collecting geolocation data in order to create profiles (eg. people who often go to this or that type of shop) so as to power ad targeting. They operate through embedded SDKs and ad bidding, making them invisible to users.

The @CNIL notes that profiling based off of geolocation presents particular risks since it reveals people's movements and habits. As risky, the processing requires consent — this will be the heart of their assessment.

Interesting point: they justify the decision in part because of how many people COULD be targeted in this way (rather than how many have — though they note that too). Because it's on a phone, and many have phones, it is considered large-scale processing no matter what.
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.