Proxmox does VMs and containers (LXC). You can run any docker / podman manager you want in a container.

Benefits of having Proxmox as the base is ZFS / snapshoting and easy setup of multiple boot drives, which is really nice when one drive inevitably fails 😏

Yeah, I would use a bot like this on Telegram. Could hook it up to a tiny LLM (The Phi for example) and give it instructions to play along and then block after some time.

This looks great! Solid Pods is Tim Berners-Lee’s attempt at solving selfhosting and decentralization, but it has struggled to gain traction. Connecting it to the fediverse is a very good move.

This is what I have done. Pixelfed has the option to assign a license to individual post, so it should not be that hard to implement the same for the rest of the fediverse.

I mainly choose the noncommercial license to stop big actors like Meta from displaying my content alongside their ads. They probably will not respect it, but if this becomes the standard on the social web, we might have some collective leverage down the road, i.e. for a class action lawsuit.

I host my own instance and use the Creative Commons Non-Commerical license on my content. The idea is that this makes federation with other non-commercial instances no problem, but as soon as an instance mixes in ads in the feed, they (technically) can’t show my posts alongside it.

I know Pixelfed has a license field for every post/picture so you get fine grained control, but I don’t believe this is the case for the Mastodon API yet, so I have added the license information in my bio. It would be nice to attach license information to individual posts, and to assign a default license.

My hope is that this will make it more difficult for Meta and the like to mix in ads with my content. Time will tell if it works 😆

We should avoid making blanket demands like this to the fediverse as a whole. I happen to support your position, but we should take into account the diverse nature of the social web.

Instead of making demands, explain your reasoning and leave each community to make up their own mind. This is the beautiful nature of the social web; we have broken decision making down into many smaller units instead of one mega instance/corporation.

Find a community that resonates with your own thinking on this issue, and over time a thousand different servers will gather experiences and a picture will start to form; was federation with Meta a good or a bad thing?

No, but they can poison it. Luckily, it is possible to block their servers.

I see mentions of Jekyll, but is this a solution that can be integrated with any static site generator somehow? I use Hugo and would love to have a tighther integration with the social web.

As has been mentioned before, Meta can scrape most data from the Fediverse already as it is publicly available.

One strategy could be to default to publish to followers only, and not public? It would be a great loss for the open web, but it might be a necessary one to make sure blocked instances do not get access to most of our data.

Another solution could be to publish all posts under a Non-Commercial Creative Commons 4.0 license, which I assume would legally block Meta from using our content in any context as they earn piles of cash on mixing user generated content with ads. Not sure if they would respect it, but it might give us an option for a class lawsuite in the EU?