![]() | This article is rated B-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||||||
|
Name change
Was there a name change discussion related to this page? I haven't been following it too closely but I just noticed the change from about 10 months back [1]. I don't see any discussion related to the change. I think the older title was more appropriate as this is more complex than simple "denial". I also don't see discussions associated with the changes to the lead. The current lead conflates the activities of Exxon, Mobile and the later ExxonMobile company as if they were a single organization the whole time. That should probably be cleaned up and clarified. Ping involved editors @William M. Connolley and InvadingInvader: Springee (talk) 13:44, 18 August 2023 (UTC)
- I changed the name since this article mostly revolves around Exxon and later ExxonMobil's activities relating to the denial of climate change specifically. I think it's a more precise title. InvadingInvader (userpage, talk) 21:17, 18 August 2023 (UTC)
- Service: The name was changed from "ExxonMobil climate change controversy" to "ExxonMobil climate change denial" in November 2022.
- It's annoying when people do not mention the actual names (before and after) in such situations, especially years later. --Hob Gadling (talk) 05:41, 14 May 2024 (UTC)
ExxonMobil's support for carbon tax
There's a sentence "In 2015 it expressed support for a carbon tax.", and the cited article from the Economist is from 2015, but it explicitly mentions, that EM support carbon tax since 2007 ([2]). On the other hand, EM's own website says 2009 ([3]).
Moreover, there's a kind of a followup on The Guardian from 2021 ([4]), which says in the first paragraph, with a link to a video:
"Lobbyists for ExxonMobil have described the oil giant’s backing for a carbon tax as a public relations ploy intended to stall more serious measures to combat the climate crisis." Tr00per (talk) 22:21, 13 May 2024 (UTC)
You must be logged in to post a comment.