@PepeNewsNow

Parler has been hacked and user data has been downloaded. The following thread contains information from /u/BlueMountainDace on Reddit:

"so a group of developers latched onto the Press Release that Twilio put out at midnight last night. In that Press Release, Twilio

accidentally revealed which services Parler was using. Turns out it was all of the security authentications that were used to register a user. This allowed anyone to create a user, and not have to verify an email address, and immediately have a logged-on account.

Well,

because of that access, it gave them access to the behind the login box API that is used to deliver content -- ALL CONTENT (parleys, video, images, user profiles, user information, etc) --. But what it also did was revealed which USERS had "Administration" rights,

"Moderation" rights.

Well, then what happened, those user accounts that had Administration rights to the entire platform... The hackers, internet warriors, call it what you will, was able to use the forgot password link to change the password. Why? Because Twilio was no

longer authenticating emails. This meant, they'd get directly to the reset password screen of that Administration user.

This group of Internet Warriors then used that account, to create a handful of other ADMINISTRATION accounts, and then created a script that ended up

~8yrs ago (Dec’12) I got a job @Google. Those were still early days of cloud. I joined GCP @<150M ARR & left @~4B (excld GSuite). Learned from some of the smartest ppl in tech. But we also got a LOT wrong that took yrs to fix. Much of it now public, but here’s my ring-side view👇

By 2008, Google had everything going for it w.r.t. Cloud and we should’ve been the market leaders, but we were either too early to market or too late. What did we do wrong? (1) bad timing (2) worse productization & (3) worst GTM.

We were 1st to “containers” (lxc) & container management (Borg) - since '03/04. But Docker took LXC, added cluster management, & launched 1st. Mesosphere launched DCOS. A lot of chairs were thrown around re: google losing this early battle, though K8 won the war, eventually 👏

We were 1st to “serverless” (AppEngine). GAE was our beachhead -- it was the biggest revenue source early on but the world wasn’t ready for serverless primitives. We also didn’t build auxiliary products fast enough. Clients that outgrew GAE wanted “building block” IaaS offerings.

1st to hadoop (map-reduce ‘04) but our hosted Hadoop launched in ‘15. AWS EMR was ~200M ARR by then. 1st to cloud storage (GFS ’03), but didn’t offer a filestore till ‘18! Customers were asking for it since 2014. Didn’t launch archival storage or direct interconnect till v. late.

1/The next major problem set in #DeFi is #NFTLiquidity.

It has become very clear that, like fungibles, nonfungibles are their own financial asset class.

One path to see this is to envision the future of NFTs as “liquid

2/Some say that NFTs “shouldn’t be” liquid, yet the innovation process continues.

Just like photography has become much easier to create in the last 100 years, liquid NFTs will surely bring down price points of tokenized digital content but will also open expansive new markets.

3/The key observation is this: #NFTLiquidity is merely a technical problem for #DeFi, and the entire set of economic mechanisms is its solution space.

👉🏻 In particular, because of tokenization, *the NFT liquidity problem reduces to the NFT price discovery problem.*

4/In other words, if we could reliably price a set of NFTs, we could issue a token backed by their reliably priced future resale value.

This is a core mechanism that today is underutilized in the market, and one that — we will soon see — applies to all illiquid assets.

5/Today, NFT price discovery proceeds via three main mechanisms: sales, auctions, and ERC20 fractionalization.

And the fundamental problem with each of these mechanisms is capital efficiency: in each mechanism, participants need to spend *at least* $N to value something at $N.

As the United States deals with insurgent forces at home, security professionals should look to the Middle East for insight on how this threat may evolve:



There are a lot of parallels between right-wing US extremism, and post-colonial Islamic extremism.

The most prominent, I feel, is the one between the @newtgingrich era GOP and the Muslim Brotherhood. The Muslim Brotherhood, like most early Islamic terrorism, was a reaction to European colonialism in the Middle East.

What starts as a political movement interested in social change becomes an insurgent group engaged in violent extremism.



The same radicalization factors can be identified. It’s disenfranchisement and cultural erosion all the way down.

Both groups want a return to “tradition” to strengthen a culture they feel they’ve lost because of modernity. Both groups feel they’ve been economically and culturally disenfranchised by a foreign oppressor. You can see roots of this same problem in the Confederacy.

In our case at home, this is because of the inherent cultural divide between conservatives and liberals. Many conservatives do not feel that liberals are real Americans. This is an important factor for later.

@curaffairs The author doesn't know enough about search to have written that article and the reason he's having those problems is AI algos like Rank Brain and Google's attempts to use natural language processing nothing to do with SEOs.

1/x

YMYL is not evaluated at the site level, but the query level.

Again this is on Google, not SEOs because they want to surface better sites.

And those devaluations are part of Core Updates which SEOs like me recover sites from.

2/

Featured Snippets are not optimized for - you can use certain HTML to be pulled in one but there is no definite use case where Featured Snippets are shown or that your site's will show for it. Also doesn't always come from the #1 result.

& that's Google not the SEO.

3/

Also there are many times when an SEO doesn't want their site in the Featured Snippet cuz it doesn't result in a click to the website. But we have no control over what Google pulls as Feature Snippets except to put in a meta tag to exclude us from them

4/

And Neil Patel is not an SEO. Most senior level SEOs see him as nothing more than a scammer because reportedly he's ripped them off by stealing their content and articles and passing them off as his.

5/