Tonight we are launching our Net Zero Carbon Roadmap for Leeds, which shows a pathway for how Leeds can get to net-zero emissions by the city’s target date of 2030.

Follow the live tweets @LeedsClimateCom #LeedsClimate #PCANcities
1/

🚔 HUGE #Tesla SERVICE PROBLEMS THREAD🚔

You might remember my 3 prior threads on how
TESLA. TREATS. ITS. CUSTOMERS. LIKE. TRASH.

Here's the 4th installment.
@tomkeinan @jonsey_lisa @jwmooc @tchanpoker @bryanthediamond @EconomicManBlog
$TSLA $TSLAQ 1/22

Welcome to Greta's 4th edition of #Tesla customers getting used and abused. Because that's the Elon Musk way.
@coffeebreakls @KocgibiHarun @omaragha @JayGhahari
$TSLA $TSLAQ 2/22

"The best service is no service." - Elon Musk a.k.a. #SpaceKaren
@briansaziz @FarSha998899 @thinktankfour @Billoday1
#Tesla $TSLA $TSLAQ 3/22

These #Tesla customers represent just the very tip of the iceberg. They are ones who have Twitter, have decided to complain about their #TeslaServiceIssues publicly, and were found by yours truly.
@yanismydj @hajelatweets @AlanHeldman @francislongo5 $TSLA $TSLAQ 4/22

Dear #Tesla customers: In California, if your vehicle has been out of service for >30 days total, it's a lemon. You can get punitive damages and attorney's fees. Don't sit around and take Elon's abuse. @13arm13arm @cecimar12 @richardson_skip @shootinglee $TSLA $TSLAQ 5/22

We’ve recently seen research about so-called “bots” and misinformation on Twitter and wanted to share our perspective on why findings that might seem remarkable at first are likely inaccurate. We’re working on a more detailed explanation, but some comments for now.

We continue to be excited by the research opportunities that Twitter data provides. Our service is the largest source of real-time social media data, and we make this data available to the public for free through our public API. No other major service does this.

Many researchers, academics, and journalists use our public API — a set of tools for programmatically accessing information on Twitter. We make all public Twitter content available via our APIs. You can learn more about them here:

The basic issue with much of the research based on our public APIs is simple: The APIs don't provide insight into our defensive actions to protect Twitter from manipulation, including bots.

Because of this, API-based research can't distinguish between accounts we've already identified as bad (and hidden or removed) and real, authentic ones.

Incumbents almost always prevail with sustaining innovation

In disruptive circumstances, the entrants are likely to beat the incumbents

H/t Clayton Christensen, The Innovator’s Solution

@zkat__ I'm in the position that I actually find npm / yarn the best ecosystem. Whenever I use something else I always end up stubbing my toe into something thats missing / feels wrong.

Ex. Cargo seems to neither have a concept of devDependencies nor peerDependencies.

I also can't understand why it wouldn't have an "add" command to add a new dependency. And I'm no fan of Toml, json is greate (easy to parse and build tooling around), and the better option in my opinion would be json5.

C / C++ seems to just not have language package managers. The linux / bsd crowd seem to have decided that the system package manager also should be the language package manager. Which might have been fine if every Linux distro used the same system package manager.

Instead we end up with a N x M problem. Where we have a bunch of different operating systems and they all support multiple system package managers. So there's no easy way of distributing, referencing and updating C / C++ packages.

It is also my opinion that the compiler / runtime should be a package dependency. I don't like Rust's split between rustup and cargo (they should have been one tool). Similarly it would be better if you added Node as a dependency to package.json, that way we wouldn't need NVM.