The core functionality behind git last-modified was written by GitHub over many years (originally called blame-tree in GitHub’s fork of Git), and is what has powered our tree-level blame since 2012. Earlier this year, we shared those patches with engineers at GitLab, who tidied up years of development into a reviewable series of patches which landed in this release.

The free software ethos at its finest, this is enough to make a grown man cry 🥹

That’s the joke XD

I always shiver at the thought that no PHP formatter (that I know of) can wrap lines that are too long… and my codebase has too many 🥲

Misfortune for 500

Does the shirt become purple if I click it?

I can’t recall which right now, but there are ones that manage to scrape the entire content by spoofing the Google crawler.
Since websites want to maximise their SEO, they must provide the raw content to be indexed better

While true we always had them, I believe It’s a different implementation, since profiles made the old way aren’t accessible in the new interface.

Do you have the menu?

Yes, on version 144.0.2 on Fedora

I know what kind of pfp they put on, I JUST CAN’T PROVE IT

What line from article 3 makes you think that? It sounds to me like it’s only talking about data processors inside and outside the EU that handle data of people in the EU

Which is clearly…

The pen

Yes of course, but to this chapter anyways

The good ending 🙌

What is your comment on the article talking about? I’m out of the loop

I was just looking for something like this, love it!

Lmao, funnier that it wasn’t even intentional

Keypunch is pretty good

That was amazing haha

To measure them, actually!

could the black box be lifted revealing the contents of what it covered

If we’re talking raster images, then no, you’re not using some mathematical model to morph an image, you’re just overwriting pixels arbitrarily, so there would be no way to recover what’s “under” the box because there’s no second layer.
If instead it’s something like a PDF (vector), then placing an object over another without flattening the result would allow you to move it out of the way to reveal what’s under.

I would add, of course, make sure that the black box covers enough to prevent the possibility of inferring what’s under, so if it’s text or other organic things that can be “statistically” regenerated with some model, don’t leave any borders that can identify the item, reconstructed data may be synthetic, but can provide informed guesses