![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Exactly. Torrents are popular because of the moderation and curation the indexers perform. It’s why it essentially won over purely distributed competitors.
It won’t take much to create some fake swarms that make this tool useless.
Exactly. Torrents are popular because of the moderation and curation the indexers perform. It’s why it essentially won over purely distributed competitors.
It won’t take much to create some fake swarms that make this tool useless.
Wayland does only do the most basic stuff and leaves everything else to the compositor (aka Gnome or KDE). That means every compositor will implement their own hacky version of the missing functionality and it takes ages until that gets unified again, so that apps can actually use that functionality.
Would this functionality be mostly the same? Could they get together to make a shared libcompositor that implements the bulk of the functionality? Or is it so tied to specifics of the desktop environment that there’s little commonality. In which case, Wayland not doing it would be the right call.
Is there a difference between networking approaches?
With rootful podman containers the only difference I noticed is that bridge networks aren’t isolated by default.
Why would you need to reconfigure the port mappings?