Alexa had “no profit timeline,” cost Amazon $25 billion in 4 years
As I said, I don't care if you "intended" to be condescending, I'm saying you were. Judging by your comment history you often are, so maybe get used to people responding with a bit of attitude.
You used polite words, but you were condescending. I'm not interested in whether that was intentional or not, but that is the vibe you gave.
Yeah well, apologies for being a little sassy, but I'm not exactly a big fan of your tone either.
Can you explain to me exactly how moving where profit is recorded from one division to another in the same organization reduces their tax burden? Because, excuse me, I know I only did a year or two of accounting courses before dropping the degree, but that's not how I understand taxes to work.
Also to be turning a profit by "doing well collecting data", the open market value of the data Alexa alone annually generates would need to be around 8% of the entire global data market. If you can justify how millions of instances of "Alexa set a timer for 10 minutes", "Alexa what is the weather", or "Alexa play despacito" generates that much value, maybe you have a point.
It's a good thing their reason is explained very clearly in the article linked in this post. They believed Alexa would have a high "downstream impact", i.e.generate sales or subscriptions elsewhere in the company. Which it has so far failed to do.
having an always on listening device in someone’s home
They very explicitly do not collect audio when you haven't used a wake word or activated it some other way. They will not "know what is discussed within the house for data on ad penetration/reach" (which is pretty much the only valuable data you've mentioned here), nor will they "have a backchannel to television viewing and music listening patterns" unless you actively discuss it with your device.
I'm not going to put words in your mouth, but if whoever reads this is thinking of replying "are you going to trust that" etc, yes I am. We can track which data an Alexa transmits in real time and directly verify this "always listening" isn't happening. Even if we couldn't independently verify that his is the case, and lets say they contradict their privacy policy and public statements and do it anyway, that's a crazy liability nightmare. Amazon has more than enough lawyers to know that unconsentually recording someone and using that data is very illegal in most places, and would open them up to so many lawsuits if they accidentally leaked or mishandled the data. Take the conspiracy hat off and put your thinking cap on.
Send it to cheap overseas transcribers, use it to train and improve voice recognition and automatic transcription.
Bad for privacy, but also not a $25 billion dollar source of revenue.
Alexa, Google Home, and Siri devices are not good sources of data. If they were, why would Google, king of kings when it comes to data collection, be cutting their Assistant teams so much?
I'm very skeptical that the data Alexa collects is anywhere near as valuable as people seem to believe it is.
Yeah, for some reason they only let you charge the NES/Famicom controllers as if they were Joycons. The SNES controller just uses USB-C so I don't know why they didn't do that across the board.
But this conversation has absolutely nothing to do with the topic at hand
They stop their ads for the same reason you don’t shit talk at a funeral: its disrespectful and makes you look like a prick.
I'm using an ✨analogy✨ to explain to you why, even if they are "serious about the topic in the ads", they would stop them when someone dies or a tragedy occurs. Its not some conspiracy about "planned division", it's because speaking ill of someone under those circumstances makes you look like (and be) a disrespectful dick.
I'm not asking if you remember them as an arsehole and speak of them like that. I'm asking if you do that at their funeral.
I'd be interested to hear whether you regularly attend funerals and speak ill of the deceased. They stop their ads for the same reason you don't shit talk at a funeral: its disrespectful and makes you look like a prick.
She drew crosshairs on congressional districts and tweeted it with the text "Don't Retreat, Instead - RELOAD". That is stated in literally the first paragraph of the article your citing, and I can't help but feel you're intentionally misrepresenting it to draw a false equivalency.
An audience member was killed according to ABC News (Australia)
Making a breaking change to the mobile API also breaks old outdated installations of the app. Websites and their APIs are usually synced, apps not so.
If they were really motivated to stop your method, they could just obfuscate the frontend with webpack and break your scraper every time they make an update.
I suspect that any of the methods proposed here would be prone to a C&D, but IMO the safest legally would probably be the RSS method (not a lawyer though). Reddit's RSS feeds are public, documented, and available without the need for private APIs, authentication, or an API key, so I don't see how they could claim that a wrapper is unauthorised/illegal. Documenting their private API however seems like a gray area. Google LLC v. Oracle America, Inc. found that APIs are copyrightable, but this use may constitute fair use.
Is there a reason you're scraping data rather than attaching a network sniffer/reverse engineering the official apps and documenting the results? Or map the RSS feed to an API? The main thrust behind my comment is that I think scraping is pretty fragile, so I'm interested as to why other options are infeasible.
Thank you for adding this! If people want a real life example of the effect shown in this pseudocode, here is a side-by-side comparison of real production code I wrote and it's decompiled counterpart:
override fun process(event: MapStateEvent) {
when(event) {
is MapStateEvent.LassoButtonClicked -> {
action(
MapStateAction.LassoButtonSelected(false),
MapStateAction.Transition(BrowseMapState::class.java)
)
}
is MapStateEvent.SaveSearchClicked -> {
save(event.name)
}
// Propagated from the previous level
is MapStateEvent.LassoCursorLifted -> {
load(event.line + event.line.first())
}
is MapStateEvent.ClusterClick -> {
when (val action = ClusterHelper.handleClick(event.cluster)) {
is ClusterHelper.Action.OpenBottomDialog ->
action(MapStateAction.OpenBottomDialog(action.items))
is ClusterHelper.Action.AnimateCamera ->
action(MapStateAction.AnimateCamera(action.animation))
}
}
is MapStateEvent.ClusterItemClick -> {
action(
MapStateAction.OpenItem(event.item.proposal)
)
}
else -> {}
}
}
decompiled:
public void c(@l j jVar) {
L.p(jVar, D.f10724I0);
if (jVar instanceof j.c) {
f(new i.h(false), new i.r(c.class, (j) null, 2, (C2498w) null));
} else if (jVar instanceof j.e) {
m(((j.e) jVar).f8620a);
} else if (jVar instanceof j.d) {
List<LatLng> list = ((j.d) jVar).f8619a;
j(I.A4(list, I.w2(list)));
} else if (jVar instanceof j.a) {
d.a a7 = d.f8573a.a(((j.a) jVar).f8616a);
if (a7 instanceof d.a.b) {
f(new i.j(((d.a.b) a7).f8575a));
} else if (a7 instanceof d.a.C0058a) {
f(new i.a(((d.a.C0058a) a7).f8574a));
}
} else if (jVar instanceof j.b) {
f(new i.k(((j.b) jVar).f8617a.f11799a));
}
}
keep in mind, this was buried in hundreds of unlabeled classes and functions. I was only able to find this in a short amount of time because I have the most intimate knowledge of the code possible, having written it myself.
It's not impossible, just very labour intensive and difficult. Compiling an abstract, high level language into machine code is not a reversible process. Even though there are already automated tools to "decompile" machine code back to a high level language, there is still a huge amount of information loss as nearly everything that made the code readable in the first place was stripped away in compilation. Comments? Gone. Function names? Gone. Class names? Gone. Type information? Probably also gone.
Working through the decompiled code to bring it back into something readable (and thus something that can be worked with) is not something a lone "very smart person" can do in any reasonable time. It takes likely a team of smart people months of work (if not years) to understand the entire structure, as well as every function and piece of logic in the entire program. Once they've done that, they can't even use their work directly, since to publish reconstructed code is copyright infringement. Instead, they need to write extremely detailed documentation about every aspect of the program, to be handed to another, completely isolated person who will then write a new program based off the logic and APIs detailed in the documentation. Only at that point do they have a legally usable reverse engineered program that they can then distribute or modify as needed.
Doing this kind of reverse engineering takes a huge amount of effort and motivation, something that an app for 350 total sneakers is unlikely to warrant. AI can't do it either, because they are incapable of the kind of novel deductive reasoning required for the task. Also, the CarThing has actually always been "open-source", and people have already experimented with flashing custom firmware. You haven't heard about it because people quickly realised there was no point - the CarThing is too underpowered to do much beyond its original use.
Read the next paragraph, I already addressed you armchair conspiracy theoriests. We can independent verify their claims by analysing the device's network traffic, I've literally done it myself and seen with my own eyes that it doesn't happen. If you don't believe me, you can also check for yourself.