They love to do this. 2 years ago they renamed Office (the online, browser based version) to Microsoft 365 https://www.computerworld.com/article/1614302/office-to-be-rebranded-microsoft-365.html

They can present the "new" apps to shareholders

MicroG devs are working on fakeing play integrity api since 2023: https://github.com/microg/GmsCore/issues/2050

it seems that play integrity continue to change internally day to day... He is waiting that google stabilize it. Then will be a pull request.

Nice job! It's not that hard to find where you worked if you include some text, it's here: https://www.osm.org/#map=17/41.44296/31.74970

Some tips:

• A rectangles should be rectangular. You can assume a football field or similar sport field has right angles, so you should draw it as a rectangle. There is a built in tool for that. In the iD editor you used, select the field, rightclick-> Square, or press the Q key on your keyboard. This is usually true for semi detached houses as well. People like to build rectangles.
• I think the place=locality tag on this thing is wrong: https://www.openstreetmap.org/way/1302651829 I can't figure out what is that from the aerial imagery, but locality in osm terminology is something different:

The place=locality tag is used to name an unpopulated location for which there is no extant feature to which the tag could be associated.

Maybe the translation is wrong in the editor for this item, I see you used Turkish language. If it's some kind of an empty plaza or paved place, use place=square (wiki) or highway=pedestrian + area=yes: a hard-surfaced, open pedestrian area: https://wiki.openstreetmap.org/wiki/Square

These are small problems, it's really nice, keep up the good work!

It's also recommended to reach out to the local community, they can help a lot. You can find your official channels on this site for any place of the World: https://openstreetmap.community/?map=36.94533,34.03161&zoom=5.52

Simply noone ever looked and it's not documented. And the api is locked to work only on google domains so it wasn't usable to anyone to accidentally notice what's going on.

The code doesn't do anything on non-Google domains.

Luca says this - I'm inclined to agree:

This is interesting because it is a clear violation of the idea that browser vendors should not give preference to their websites over anyone elses.

Follow up question: How many other parts of the chromium codebase limited to work on (maybe other) specific domains?

No, they are called metallophones, glockenspiel is just one of them. Other common metallophones are the tubular bells and the vibraphone

That's changeing: in the ongoing SFC vs Vizio, SFC is just a regular user: https://sfconservancy.org/copyleft-compliance/vizio.html

Even FSF updated it's FAQ, that it's not true anymore: https://www.fsf.org/news/fsf-to-be-deposed-in-sfc-v-vizio-updates-relevant-faq-entry

Most of reddit was already archived before: https://the-eye.eu/redarcs/

Very useful video. I miss that you don't list the Chromium browsers. A lot of people, the target audience of this video don't know that edge, opera, vivaldi, brave are all affected some way.

Here: https://kernel.org/

I can already read the title of the page and see the favicon, so it actually doesn't show new information. If I accidentally move my mouse there it covers a big part of the page i'm looking at