Have no experience with iced but interesting. Can you share a minimal example of what you'd like to do? At least the source code of Sandbox reads fn view(&self).
Yeah sorry, confused things. It's comes closer to a Mastodon thing. The point is that a big corporation like Facebook does not need to use AGPL code as long as they can just re-implement it. Compared to the total codebase used at Facebook, re-implementing something like lemmy or mastodon does not sound like a big deal.
(That's not an argument against using the AGPL)
Unfortunately it's still possible to rewrite a VC-backed clone and start making incompatible changes. Think about Facebook's "threads.net". They sure did not take Lemmy source code.
Spontaneous idea of how to use copyright law for keeping Meta out of the Fediverse (more for fun):
Introduction:
Parts of the Fediverse, including Mastodon, are software licensed under the APGL license. This license is a great choice because it forces the ones running the software to grant users access to the source code. GPL for example would allow to run proprietary services based on GPL code. The AGPL does not.
Companies like Meta and Google will likely not use AGPL code because it might force them to also publish their proprietary systems behind the scenes.
However, this does not help much for keeping the Fediverse save. They simply implement their own software which will not be open source.
Therefore we may need another approach. Defederating is the simplest and in my opinion currently the best. It's easy and keeps people in control.
However, there could be some 'automatic' approach using copyright law.
It's a hack which allows to use existing law to regulate the way instances can federate.:
instances would Federate only if the other side can provide a certain piece of information called X
X is protected by copyright law, therefore by default, instances are not allowed to provide X
However, X is released under a license which for permits to copy and distribute X under certain conditions
The conditions allow to tune who can legally federate
Conditions could be
The server software must be AGPL licensed
The instance must not be owned by a company with a certain amount of annual revenue
True. As an outsider I can only speculate what is going on there. As you say, other BigTech-financed projects seem fine.
About big tech companies sponsoring projects: The have an interest that Rust is maintained and many people write good crates which they can use. But they don't care so much about the world being able to profit from the ecosystem. If they do, then just because this is actually profitable for themselves.
I think this turns into a problem once a project get mainstream. Let's imagine that in twenty years Rust largely replaced C/C++. It would become part of the worlds critical infrastructure. I don't think it is good to let the monopolies have the governance. I don't believe that they act in interest of people. Often it may appear the way. But if it does, I'm convinced that there's usually a business interest behind.
For example, screwing people completely would be bad for business or might trigger the attention of regulation bodies. So they don't do it. Screwing people very gently such that they get used to it before they notice might happen. Slowly boiling the frog. This type of companies do that on a daily basis.
Alone the sponsors of the Rust Foundation I find very questionable (Amazon, Google, Huawei, Meta, Microsoft, https://foundation.rust-lang.org/ on the bottom). Unfortunately, corporatism is what you get from corporations. Happy to hear about the crab-lang fork.
Have no experience with iced but interesting. Can you share a minimal example of what you'd like to do? At least the source code of
Sandboxreadsfn view(&self).