I’ve only skimmed it, I’ll admit, but all I saw was that it said there were 4 attempts. I didn’t see what they were, apart from the 1 I already knew of which was mentioned (the 2021 instance).

Wait, 4 attempts? I think I only heard about 1.

Basically, “X is one-third more than Y” means either X = (4/3) × Y or X = Y + 1/3. I’m fine with either interpretation.

The problem is that with the values of X and Y in this example, neither interpretation produces a valid equation.

“a half is one-third more than a third” should mean either

1/3 + 1/3 = 1/2

Or

1/3 + (1/3 × 1/3) = 1/2

Neither of which is true.

According to patreon I already did this?

I get the sense that this was meant to be another haiku, but it’s 13 syllables with the 5th not even ending at the end of a word.

Okay but they often don’t give users what they want

You should see the state of Firefox on iPad OS. I started using it earlier this year after they finally rolled out support for multiple windows—a feature Safari added in 2019 and Chrome had only a few months later.

Nice that they finally have this feature, but the browser itself is nearly unusable. It stutters constantly and freezes, locks up, or force reloads with some regularity. In a way that Chrome and Edge (and I assume Safari, though I have never really used that) never do.

Or on desktop OSes, a website I frequented around 2016–2018 used the column-span CSS property, which Firefox didn’t get around to implementing until December 2019.

It’s been very clear for some time that, whether it’s because they stretch themselves too thin or some other reason, Mozilla has been failing to continue to deliver an excellent product for their users.

This is being reported as a rumour that’s been debunked, but I’m doubtful how true that is. Seems quite likely to me they’ve bowed to pressure.

I agree in general, but

Maybe I’m over simplifying it though, I don’t know how their org operates.

This is exactly why just sticking to the 90 day standard is better. For the supposed security researcher it’s a CYA move at worst.

Maccas HQ should take the guy’s franchise off of him, then. They did it near me to a guy whose only crime was supporting the local community more than extracting maximum profit, surely making a political endorsement that HQ doesn’t agree with should be grounds for the same. Right‽

90 days is just the standard timeframe for responsible disclosure. And normally that’s just a baseline with additional time being given if there’s genuine communication going on and signs they’re addressing the problem.

Yup absolutely. I mentioned web APIs because that’s what I’ve got the most experience with, but .h files, class library public interfaces, and any other time users who are not the implementor of the functionality might want to call it, the code they’ll be interacting with should be tailored to be good to interact with.

If the doco we’re talking about is specifically an API reference, then the documentation should be written first. Generate code stubs (can be as little as an interface, or include some basic actual code such as validating required properties are included, if you can get that code working purely with a generated template). Then write your actual functional implementation implementing those stubs.

That way you can regenerate when you change the doco without overriding your implementation, but you are still forced to think about the user (as in the programmer implementing your API) experience first and foremost, rather than the often more haphazard result you can get if you write code first.

For example, if writing a web API, write documentation in something like OpenAPI and generate stubs using Swagger.

They’re known specifically for being pro-Russia, which is what made the comment amusing.

If they were really “the hero”, they’d follow the bare minimum of responsible disclosure best practices, and allow 90 days between privately alerting them of the issue and going public with it. Two weeks is absurd.

I think a colon would be the most apt punctuation here.

The tracks are now unruly and wild, the people tied to them: killed in crosswalks

But to be honest I was fine with no punctuation. The bit that most bothers me is the choice of preposition. You don’t go in a crosswalk. You go on it. Or maybe you’re at the crosswalk when you’re killed. But certainly not in.

More people exist who cannot drive than who have to drive due to disability. Car-centric infrastructure is incredibly ableist.

We could have used the tilde, which has been used in formal logic & maths for negation in very many contexts for a long time.

It’s used instead in C and many C-like languages for the far less useful bitwise negation. Of course, we could have had it work in the same way as bitwise vs logical and & or, by dialling up the symbol. Which would have massively improved its visibility compared to the bang.

But for some reason, no. They chose the bang instead.

It’s really unfortunate that Lemmy handles deleted posts in this way. It’s one of very few genuine advantages of the Reddit platform. Over there, if the OP deleted the post, the text they wrote would no longer be visible, but all the comments under it still would be. And people could continue to have that discussion, so long as they had the link.

The only country whose opinion should matter here is Taiwan. If and when they decide they want to be recognised officially, they should be. Not before, and not after.

I thought it was a rather simple analogue, but I guess it was too complicated for some?

I said nothing about JavaScript or Python or any other language with my 1/3 example. I wasn’t even talking about binary. It was an example of something that might be problematic if you added numbers in an imprecise way in decimal, the same way binary floating point fails to accurately represent 1/10 + 1/5 from the OP.