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?
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.
I understood it as a technical limitation imposed by the changes Europe are demanding. They now have to allow different browser engines, so they can't just use Safari under the hood for PWAs. They will need some UI and the technical underpinning to allow the browser engine to be selected.
Edit: I missed part of the question. The repository below only references installing yay. Could you have the become_password as a vault secret in ansible and respond to the password prompt with expect?
I literally stumbled upon this a few hours ago, maybe it will help.
This is very informative and echoes a lot of my opinions.
I don't like my identity being tied to the instance I created an account on. I should own my identity, like on nostr.
My instance/relay having moderation decisions is not as clear cut. It's beneficial as long as your interests align; without it you end up having to manage crypto spam yourself. But moderation policies are fluid and work both ways on the fediverse.
It is important on the fediverse which instance you create an account on. Which is a huge barrier to entry for non tech users. Pointing them to the biggest instance by default compromises the decentralisation.
The best way I find to think about it is a padlocked box.
The public key is a box with an open padlock on it. I can give it to anyone. If someone puts a message inside the box they can lock the padlock, but they don't have the key to open it again.
I keep the key private. If someone sends me a locked box that has my padlock on it, only I have the key to open it and read the message.
There's an official Jellyfin app in the LG app store.
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.
They actually did somewhat start Edge from scratch originally. They made EdgeHTML as a rewrite of the IE 11 trident engine.
In the end they abandoned it and moved over to chromium. One of the reasons being Google intentionally breaking their sites for EdgeHTML.