BC INTERNET
Saved by @Alex1Powell

Facebook -- having taken out full-page ads in the NYT, Washington Post, and WSJ -- is generally seen as the primary victim of the new app privacy controls coming in iOS14. But Google is perhaps even more vulnerable to ATT. Why has Google remained silent? (1/X)

 2/ First, background: here's a high-level overview of how ATT / IDFA deprecation impacts advertisers and ad networks, and why this whole ordeal has put advertisers and ad networks into a state of panic: https://t.co/vfGafKzKt2
3/ Google is equally as susceptible to harm from ATT as Facebook. Google's UAC product -- esp its tROAS and tCPA campaign objectives -- relies as much on IDFA-indexed monetization and engagement data as FB's mobile product does. But Google has one big weakness wrt ATT: YouTube
4/ Broadly, view-through attribution accounts for a disproportionate % of conversions from YouTube app install impressions. This means: user sees the YT ad, doesnt click, downloads app later, & Google is able to claim it by reconciling IDFA seen at impression to IDFA seen in app
5/ View-through attribution is nonexistent in the ATT paradigm as it relies on the IDFA; some significant portion of YT's attributed conversions will evaporate. So why isnt Google vocally opposing ATT? Two reasons: consumer optics and its duality as ad network / mobile platform
6/ Firstly, Google might do more harm than good by joining FB's PR campaign: of course Google, the ad network, wants to track ads. Consumers would think: if both Google & FB oppose a privacy feature, it must be good for me. Google likely stands to gain by *not* joining the fray
7/ Let FB and Apple battle it out in public over consumer goodwill and quietly relay guidance to advertisers (as it has minimally done: telling advertisers to shift away from tROAS campaigns on iOS). If FB fails to change Apple's mind, Google is no worse off
8/ Second: Google operates a mobile platform, Android, in addition to its ad network. Google cant come out too fervently against platform privacy because it'd advantage Apple as the "privacy friendly" platform relative to Android. Google must delicately thread a privacy needle
9/ Which is what it has done on the browser: Google agreed in principle to a shift away from 3rd party cookies but is taking MUCH longer to achieve that (2022 timeline versus Apple's ITP update blocking 3PC in March) https://t.co/7y8c1WqPzs
10/ Google is exploring clever measurement workarounds to 3PC with its privacy sandbox, eg. on-browser auction, TURTLEDOVE / FLoC, privacy budgets, etc. Google must moderate the impact of Chrome / GooglePlay privacy proposals against ad network performance https://t.co/iWaO8m9TSi
11/ My sense is that Google finds a way to militate against GAID deprecation -- while still appearing to be in privacy lockstep with Apple -- by using existing Firebase functionality to emulate SKAdNetwork differential privacy whille preserving its MAID https://t.co/Cuwmnvl493
12/ This approach strikes a convenient and satisfactory balance between privacy & ad effectiveness as well as between its two core interests: content distribution, ad network. But it's an abstruse compromise that Google would not want to necessarily champion loudly to consumers
13/ Also, the subdued comms strategy doesnt stoke red-hot regulatory embers. I disapprove of FBs PR narrative: I think itd be easier to make the case that reduced ads personalization robs consumers of the free products they love https://t.co/HdiGRIDsMk
14/ But even thats an abstract argument. FB *must* fight back because so much is at stake. And so Google can wait to see what happens: low probability that Apple changes course, high prob that ATT is roled out as-is, neither of which changes in Google's favor by an intervention
15/ And ultimately, Google can announce its own platform privacy solution that doesnt impair its ad network's efficiency for Android campaigns while remaining, theoretically, in privacy lockstep with Apple

More from Internet

Richard Geldreich
Richard Geldreich
@richgel999
Porting vanilla (minimal external API usage, no SIMD, no threading) C++ code to work in the browser with emscripten and WebAssembly is amazingly simple now. The Emscripten docs are excellent, but here are some things that could speed up the process of getting started:

1. Beware of code which does unaligned memory reads/writes (which "may be slow on some CPU architectures")
2. Test with -fsanitize=undefined -fsanitize=address
3. Link with "-s ALLOW_MEMORY_GROWTH=1" and "-s INITIAL_MEMORY=X", X is a multiple of 64k, allows the C++ heap to grow.

(I completely avoid unaligned memory reads/writes because when compiled to asm.js they "can fail silently".)

4. Link with "-s MALLOC=emmalloc" to reduce compiled size.
5. I usually test with -O1 because -O0 can take very long to load/execute.
6. For debugging link with -s DEMANGLE_SUPPORT=1 and -s ASSERTIONS=1

7. C++ printf() outputs to the Developer Console: Chrome Settings->More tools->Developer tools
8. If something crashes, try running in Firefox which may explain the error differently.
9. I use Web Server for Chrome for
INTERNET
Amit Ganguli
Amit Ganguli
@amit_ganguli
Many conversations happening on #WhatsApp (WA) groups about new #WhatsAppPrivacyPolicy .
This thread has arguments to help ditch WA & move to @signalapp:
https://t.co/En4fe9VxUN
Share, use, copy-paste, modify with understanding as you deem fit on any platform in whole or part
1/n

Note: No affiliations, conflict of interest
Info presented with NO bias, prejudice, malice or indemnity.
Open to corrections: individual tweets may be deleted, tweets added to thread or corrected as replies.
Points that are unclear or uncertain are marked with "(?)".
2/n

CONTENT OF WA MESSAGES SHALL REMAIN ENCRYPTED END TO END.
BUT, there's data: contacts, group affiliations, co-affiliations, locations (live?), frequency of contacts, *tags* generated when we send or forward a message or file to contacts or groups, links, clicks on links, etc.
3/n

It is unclear whether this data is anonymized.
NOTHING in latest policy *prevents* the collection, retention, sharing or sale by FaceBook (FB: owner of WA) of this data in part or whole whether with identifying information or anonymized.
Meme source:
https://t.co/nMDTUlb0rl
4/n


Companies need to make money & generate profits:
To create software, install & maintain infrastructure.
Google, FB, Insta, Amazon etc sell data created from our content & data generated from our interactions (searches, clicks, purchases etc).
This makes many uncomfortable.
5/n
INTERNET
Advertisement
David Frum
David Frum
@davidfrum
Yoga employs more Americans than coal. But compare and contrast 1/2


and 2/2


I think many of us carry in our minds an image of the US economy that looks like this


when the reality is this


and this
INTERNET
BlackRoomSec
BlackRoomSec
@blackroomsec
Or, you could let us know when you figure out why it was trending yesterday and the users are complaining which is why Vice wrote about it. Why I'm saying what I am.

There's an assumption here that this problem is fixed bc it was already hacked.

It's not.


We have ppl freezing and dying in TX right now because some ppl who thought they were really smart never spoke to anyone with actual experience with energy systems in extreme cold climates.

Texans are waiting for a solution to a preventable problem.

Farmers are saying that now, not during a crisis, they have to wait for a JD tech to arrive to help them.

The assumption that bc SOME farmers said screw this and used hacked firmware to get around that obstacle doesn't mean that all farmers are doing that.

If all farmers were using hacked firmware we wouldn't be discussing this right now would we?

Of course no one has pointed out that another issue here is that no one at John Deere has figured out they don't have enough staff to quickly and reliably SOLVE problems.

The locked firmware is just one of many issues here.

By not giving people a fast solution they're causing this and other issues.

So what I'm saying is somebody at John Deere needs to examine all of this.
INTERNET
Markus Amalthea Magnuson \u2744\ufe0f
Markus Amalthea Magnus...
@scifiagenda
I did more research into the Parler dump. What probably happened was not so much a "hack", but this: When Twilio/Okta shut them down, they just disabled email/phone verification to create an account. This means anyone could directly create huge amounts of accounts via their API.

Someone also found out that fetching Parler posts could be done by enumerating IDs (e.g 1, 2, 3) instead of random IDs that can't be guessed. Unclear if this was via the ordinary API endpoint, or that they found a separate one by monitoring app network traffic.

So you combine these two things and you can create a script to scrape all the posts on the entire platform, using a lot of different accounts to avoid suspicion. Anyone could download and run this script to spread it out over many IP addresses as well.

What I'm still not sure about is whether deleted (meaning flagged as deleted, it's common that services never actually delete data) posts could be fetched without any special handling.

The verdict: The people who wrote Parler are fucking amateurs.
INTERNET

You May Also Like

Justin Kan
Justin Kan
@justinkan
1/ Throughout my startup career, I’ve seen many founders have an aversion to sales. This is a mistake that can kill your startup.

2/ Sales is often viewed as either a saving grace or proof that the product isn’t good enough (because it should sell itself). Neither are ever true. Some common mistakes that result in...

3/ Mistake 1: Hire a sales rep before reaching product/market fit to get your initial batch of customers. This is a mistake because founders need to work through their MVP with early adopters to truly understand what it is they’re selling.

4/ Mistake 2: Reach product/market fit, need to scale, and rely entirely on self-serve. For enterprise products that require big commitments and internal shifts, almost no product is self-explanatory enough to sell itself.

5/ Mistake 3: Make a first sales hire who isn’t scrappy enough to help mold the sales process from scratch. Some salespeople are amazing at their jobs, but not cut out to establish the processes that others end up following. This skillset is what @rdedatta calls a “sales ninja”.
STARTUPS
Zach Weinersmith
Zach Weinersmith
@ZachWeiner
Hey, for people interested in this stuff, here's a thread about a change we made to running our facebook account:

So, about 5 years ago, we got on facebook. Why? Well, facebook has a big audience and they like to consume on facebook. So, we started posting comics there, even though we got paid nothing and facebook made money off the free content.

Why? Because back then, once in a while, you would say "also hey, I sell books" or "hey, I'm going to be signing at this event" and your facebook followers would actually see it.

Effectively, the implicit old arrangement was "facebook lets me reach readers efficiently, and I supply facebook with free content they run ads on."

Over time, like a bad business partner, facebook basically made it impossible to reach your audience without *paying them*. Thus, you supply them free content on which they run ads, and you get nothing in exchange.
MARKETING
Advertisement
John Papa
John Papa
@John_Papa
Choosing the Right JavaScript Framework

Thanks for joining me @pluralsight to talk about javascript frameworks. We had 150+ awesome questions, so I'll try to answer the ones I couldn't get to online right here in a tweet stream

Watch the video -->
https://t.co/G7zeiKhXme


Q. Do arrow functions really make dealing with JavaScript's "this" keywords easier?

A. Yes! When using arrow functions, the scope of "this" is effectively passed in from the outer scope. See here in this REPL

1/n


Q. Where does Polymer fit in? Is it considered a framework like the others?

A. @Polymer is an excellent way to create web components, which are ideal for creating sets of interactivity that can be shared in web apps.

2/n

Q. Have we gone framework crazy?

A. At one time, quite possibly. A few years back we literally had framework overload. I feel it really has solidified into a few very strong choices.

3/n

Q. [Is] there no more need for @polymer?

A. See my previous question on this ... but in general, I think there is a lot of room for Web Components with frameworks.

4/n
ALL
Ethan \U0001f468\u200d\U0001f3a4
Ethan 👨‍🎤...
@Booligoosh
First update to https://t.co/lDdqjtKTZL since the challenge ended – Medium links!! Go add your Medium profile now 👀📝 (thanks @diannamallen for the suggestion 😁)


Just added Telegram links to https://t.co/lDdqjtKTZL too! Now you can provide a nice easy way for people to message you :)


Less than 1 hour since I started adding stuff to https://t.co/lDdqjtKTZL again, and profile pages are now responsive!!! 🥳 Check it out -> https://t.co/fVkEL4fu0L


Accounts page is now also responsive!! 📱✨


💪 I managed to make the whole site responsive in about an hour. On my roadmap I had it down as 4-5 hours!!! 🤘🤠🤘
MAKERS
STEALTH JEFF
STEALTH JEFF
@drawandstrike
So it's now October 10, 2018 and....Rod Rosenstein is STILL not fired.

He's STILL in charge of the Mueller investigation.

He's STILL refusing to hand over the McCabe memos.

He's STILL holding up the declassification of the #SpyGate documents & their release to the public.

I love a good cover story.......

The guy had a face-to-face with El Grande Trumpo himself on Air Force One just 2 days ago. Inside just about the most secure SCIF in the world.

And Trump came out of AF1 and gave ol' Rod a big thumbs up!

And so we're right back to 'that dirty rat Rosenstein!' 2 days later.

At this point it's clear some members of Congress are either in on this and helping the cover story or they haven't got a clue and are out in the cold.

Note the conflicting stories about 'Rosenstein cancelled meeting with Congress on Oct 11!"

First, rumors surfaced of a scheduled meeting on Oct. 11 between Rosenstein & members of Congress, and Rosenstein just cancelled it.
ALL