No. It's got a "source available" license allowing only non-commercial use, and revokes the license for anyone who tries to sue them.

I think they switched to usually using bing results last year. Their support site mentions they use both backends. I'd guess which one you get depends on which API is cheaper for each country.

I think that's still closed, just poorly done in a way that isn't very accessible.

That's what burned in means.

I added an extra line break, but it already looked fine in the default webview and in Jerboa. Normally lists don't need line breaks around them.

For anyone who wants to know the difference between these terms:

• subtitles - just includes the dialogue
• captions - also includes description of other sounds
• closed - text is stored separately from the video, and can turn on and off while watching
• open - text is part of the video image itself

New users to lemmy usually aren't going to join communities if they can't register there. And people who are really invested in a topic will want to have that domain for their account. You're cutting off a lot of the users that would grow your communities.

I don't mind the idea of a collective to handle a bunch of instances, but I feel like you're going about it the wrong way. When the same person make a bunch of instances about a variety of topics, it looks as if they aren't that invested in any specific community. From my experience, the most active communities start off with a few people who care almost obsessively about that topic.

Also the idea that communities can be 'neutral ground' doesn't make sense to me. People will leave or join based on how the admins and mods run them, whether or not the users are hosted there. In some situations it might work out fine, but if anyone thinks it's caused by how you're running your sites, they may defederate from the whole collection.

The biggest thing is probably non-destructive editing, so you can do stuff like apply filters without them changing the underlying image. Gtk3 should add better support for tablets and wayland. There's also better layer tools and font support. A lot of it was on the backend, which should eventually allow for using other color spaces like cmyk natively.

It's too bad that GLIMPSE fork never took off.

They've been working on porting it since back in 2012, and didn't want to redo a bunch of the porting work before they even released it.

I've had it freeze up on me several times, where I had to reset the app to get it working again. It works most of the time, but I wouldn't recommend it yet for general use.

There's also sepiasearch.org for PeerTube videos.

There's a list of people that have agreed to block it at https://fedipact.online/