zlacker

[parent] [thread] 7 comments
1. Waterl+(OP)[view] [source] 2023-05-25 23:35:23
I’m always glad that PR people can’t help but speak in such inhuman language that makes it obvious that it’s not a real sentiment but just part of the play.
replies(1): >>Wowfun+t3
2. Wowfun+t3[view] [source] 2023-05-26 00:01:07
>>Waterl+(OP)
Honestly, I thought it was a pretty strong statement. They basically said "we screwed up."
replies(3): >>candid+q6 >>lolind+09 >>accoun+nyc
◧◩
3. candid+q6[view] [source] [discussion] 2023-05-26 00:24:43
>>Wowfun+t3
They used the words "stopped running" instead of "removed"...
replies(1): >>Aeolun+C8
◧◩◪
4. Aeolun+C8[view] [source] [discussion] 2023-05-26 00:43:02
>>candid+q6
I mean, I wouldn’t expect them to be able to pull the whole thing out of the code at the drop of a hat.
replies(1): >>Zuiii+Ry
◧◩
5. lolind+09[view] [source] [discussion] 2023-05-26 00:46:07
>>Wowfun+t3
"Stopped running the ad experience" tells me the kind of language they've been using internally to describe projects like this, and it is not language that I'm okay with from Mozilla. Using the toxic language in the retraction doesn't breed confidence that they really understand what the error was.
replies(1): >>Waterl+Ma
◧◩◪
6. Waterl+Ma[view] [source] [discussion] 2023-05-26 01:02:01
>>lolind+09
It’s not an “error,” it’s an “ad experience misadventure.”
◧◩◪◨
7. Zuiii+Ry[view] [source] [discussion] 2023-05-26 04:39:01
>>Aeolun+C8
For a browser that claims to be privacy focused, I would expect them to tightly contain the code in an external module that can easily be turned off.

I would absolutely expect them to pull the whole thing out.

◧◩
8. accoun+nyc[view] [source] [discussion] 2023-05-30 15:36:53
>>Wowfun+t3
Then you are either a fool or extremely naive. The statement they made actually says "we expected the frog to be more used to the heat by now and will try again later when it is".
[go to top]