UndercoverUlrikHD

Children probably

It's just a research paper, not a product. It's about discovering and learning new possible methods and applications.

I thought they dissolved after Chester's suicide?

You could always ask someone to vouch for you. It could also be that you have open communities and closed communities. So you would build up trust in an open community before being trusted by someone to be allowed to interact with the closed communities. Open communities could be communities less interesting/harder for the bots to spam and closed communities could be the high risk ones, such as news and politics.

Would this greatly reduce the user friendliness of the site? Yes. But it would be an option if bots turn into a serious problem.

I haven't really thought through the details and I'm not sure how well it would work for a decentralised network though. Would each instance run their own trust tree, or would trusted instances share a single trust database 🤷‍♂️

That's possible, but that doesn't really answer my question which was if the dialect is the same/similar for each group internally on the map, or just a very rough generalisation. The map covers some incredible distances so it would surprise me if they managed to keep a consistent language across it all that space. Didn't mean to dunk on the map if that's how you interpreted it.

A chain/tree of trust. If a particular parent node has trusted a lot of users that proves to be malicious bots, you break the chain of trust by removing the parent node. Orphaned real users would then need to find a new account that is willing to trust them, while the bots are left out hanging.

Not sure how well it would work on federated platforms though.

Those are surprisingly large zones, I would have thought it would be much more fractured. Is it just a rough generalisation, or would someone in Mauritania speak similar to someone in Algeria?

Even this map of Norway doesn't really represent all the dialects in our tiny country.

Ubisoft are

• The format works for both lossy and lossless compression, depending on the use case and need. Photographs can be encoded in a lossy way much more efficiently than JPEG and things like screenshots can be losslessly encoded more efficiently than PNG.

Someone made a fair point that having a format being both lossy and lossless is not necessarily a great idea. If you download a jpeg file you know it will be compressed, if you download png it will be lossless. Shifting through jxl files to check if it's lossy or not doesn't sound very fun.

All in all I'm a big supporter of jxl though, it's one of the only github repos I actively follow.

Edit: if you see a still image, you may need to click on the gif for it to play.

It's not leak when it's an intended and documented feature...

They are probably the most complex machines ever created by humanity though, and requires expertise across the whole world to build. Even if they had blueprints, it would take years just to get the manufacturing right.