TopHat

His comment didn’t address two key issues for me:

• The “crunch”/tight scheduling of projects which led to sloppiness to begin with
• The constant need to correct, ranging from simple mistakes to very problematic methods.

I’ve been enjoying solely the WAN Show, but hearing about constant mistakes in benchmarks while praising “We want to show factual information on benchmarks for once.”, is rubbing me in the wrong way. You can’t rush benchmarking without QA and publish those results as fact. You get to choose for accuracy, or fast to churn content.

And Linus not mentioning something concrete on the first issue is worrying to me, not showing a clear intent to ease on rushing those benchmarks.

Not to mention, it’s worth taking down a video if benchmarka are wrong even if the conclusion is “most likely to remain the same”, which one cannot conclude with certainty without redoing it. It would be better transparency wise to either not knowingly publish wrong information, or put a more clear notice on said videos besides the description and a pinned comment.

Don’t get me wrong - I think an included battery that’s rechargeable through USB is fantastic. Less customer inconvenience. But they should either go with a standard that’s easily reproducible or go with regular rechargeable batteries.

If it was so easy to replace them, with each Li-Ion battery being different for every type of device.

Since I got those from Ikea, I just want devices to go back to those types of batteries instead of internal battery packs. Still got to appreciate the Xbox controllers sticking to that principle (for now).

Any thoughts on overhauling cross-posting, to allow more interaction with the source interaction?

As far as I’m aware: currently when you cross-post, only the recipient instance gets all interactions (comments, upvotes), instead of duplicating to or having the origin solely receive those.

The current implementation hampers the growth of smaller instances when reposting something to a bigger one. Discoverability is still there due to seeing from which instance the post originates from, but that’s arguably not enough.