The github page for overleaf seems to indicate the community edition is AGPL.

I would try !fdroid@lemmy.ml. There used to be !fossdroid@social.fossware.space but it looks like that site died.

Google is still appealing it, so at best that will happen next year. But yeah, they're probably adjusting their budget in anticipation.

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.

A lot of this bootstrapping stuff comes back to the 'trusting trust' attack. You could write a compiler that adds some malicious code to programs it compiles. But the thing is, it could also insert it's own malicious code when compiling a compiler. So you look at your code, and the code of your compiler, and everything looks fine, but the exploit is still there. Someone wrote an example in rust.

Theoretically there could also be bugs that propagate this way. So to fully trust your code is doing what you think it is, you'd need a chain of compilers back to hand coded assembly.

The main thing is that TinyCC has already been bootstrapped.

Check out this page on bootstrappable.org. Basically they start with a 200 something byte binary (hex0) that can act as an assembler, then using a bunch of layers of tools and compilers you can bootstrap a whole system. I think they use stage0 to build M2-Planet, use that to build GNU Mes, and use that to build TinyCC.

So a project like this fits neatly into that bootstrapping path. It could be done other ways, but starting from a fairly complete C compiler makes it a lot easier than building an entire path from scratch.

Cladistically dolphins are a type of toothed whale. They're more closely related to species like sperm whales than toothed whales and baleen whales are to each other.

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.

It's not brassica oleracea though, it's a different species, brassica rapa. The same species as napa cabbage, brocolli rabe, and bok choy. Rutabaga is actually a hybrid of the two species.

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

You might find a few, but it's not really possible long term. Either you block instances that are run by fascists or child abusers, or you get blocked by instances for allowing that on your server.