Matrix is one example of such a system.

From a web developer’s standpoint, Safari is basically the modern Internet Explorer, though admittedly less extreme. It’s not rare for it to be the last of the major browsers to implement new standards/features, and it’s definitely the most common one to have an incomplete and/or buggy implementation. This sometimes goes on for years when Apple just doesn’t care about a feature. There are some fairly widely-used standards today that it still has a buggy/incomplete implementation of.

I hate Safari not because it’s owned by Apple, but because it makes my life more difficult when doing web development. It’s basically the modern Internet Explorer, though admittedly less extreme. It’s not rare for it to be the last of the major browsers to implement new standards/features, and it’s definitely the most common one to have an incomplete and/or buggy implementation. This sometimes goes on for years when Apple just doesn’t care about a feature. There are some fairly widely-used standards today that it still has a buggy/incomplete implementation of.

Nudity isn’t inherently sexual, and they pointedly have not mentioned it in the quoted text. It sounds like only explicit sexual content is forbidden, not nudity.

I do think even this is an overreach for a federated network, though, assuming Pixelfed is enforcing this on all instances (is that even possible?). It should be on the instance owners to make that decision. I couldn’t find where the quoted text is sourced from, however.

These previews are almost always specified by the website themself, using the OpenGraph protocol. The website is literally asking other services to “use this for the preview’s image, and this block of text for the description, please!”

As someone that often ends up doing a lot of web development, Safari is the rough modern equivalent of Internet Explorer.

LiDAR in particular actually kinda sucks at those conditions (basically any form of precipitation). It’s really only good in clear environments.

WebP is not proprietary. It’s an open format, is not patent-encumbered, and its reference implementation/libraries are open-source. It is driven mostly by Google, similar to Chromium.

It’s a better format than JPEG, GIF, or PNG, while doing the jobs of all of those, but better (in most cases), and is an open format. It also has wide compatibility nowadays. The only major downside is a lot of social media services don’t even think about it being a potential format due to a lack of awareness/wide usage, leading to a degraded experience when someone shares a WebP somewhere (lack of auto-embedding as an example). I suspect this is why it gets a lot of hate here, which is unfortunate because it’s not at all the fault of the format.

AVIF (based on AV1) is the up-and-coming format that beats WebP in most cases now, but support isn’t quite there yet (mostly due to Apple), and it has the same problems for social media as WebP. However, it doesn’t have any true lossless mode AFAIK. HEIF (based on HEVC) is also good, but is heavily patent-encumbered and not as open. JPEG-XL is dope and potentially even better in some aspects, but has very poor support across the board.