![](https://lemmyunchained.net/pictrs/image/c85bde8b-aec9-405f-b515-bfbeb9f40156.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Peertube?
Decentralised. Federated. activity pub. Self Hosted. Open source.
Lachlan, creator of lemmyunchained.net
Peertube?
Decentralised. Federated. activity pub. Self Hosted. Open source.
Nah. I like the bullet points. Clear tell us always the opening sentences. If it’s helpful it’s helpful. If not. It’s not. I pay for gpt4, so if I haven’t used my quota, I like to use it answering questions.
Lemmy is a federated social network, similar to Mastodon, where anyone can create and run their own instance. This means it’s not centrally controlled by one entity. The reasons for having many instances include:
1. Decentralization: This reduces the power of any single entity over the entire network and prevents any central point of failure. If one instance goes down, others are unaffected. This design also helps resist censorship because content moderation is handled individually by each instance.
2. Community autonomy: Each instance can form its own unique community with its own rules and norms. This can promote diversity of thought and freedom of expression, as different communities can have different standards and policies.
3. Privacy and security: Having separate instances can provide a higher degree of privacy and security. The admin of an instance only has access to data from their instance, not the entire network.
Regarding the concern of popular instances becoming like Reddit, it’s worth noting that decentralization inherently provides a counterbalance. If an instance becomes too dominant or its policies become unpopular, users can migrate to or create a new instance. In the end, the federated nature of Lemmy allows for a much more democratic and user-driven online community.
I still appreciate the love ✌️💛
Damn. I may need to buy a couple
Just a barrier many won’t cross.
Most can detect traffic. Content itself, I do t know. Certainly some can.
Probably will remove you. Ban you. And pass on any data they may have to authorities.
It’s the main reason I don’t do it. Even if it’s extremely unlikely.
That’s what my homelab is for. But even then, it has its own problems.
Plex is preinstalled on most smart tvs’s. And in ones with very limited app stores.
Also easy for others to make their own plex account, and you just give access to that user through the UI.
jellyfin requires more on the client side. Beyond what my mum can do on her own.
Plex for sharing with others. Jellyfin for personal use only.
Well the last one would have just mass Overloaded instances. Just wondering how this one operates differently to prevent that.
So how does this operate now?
Can you boot from disk?
Yes. Because there’s no centralised list of communities, searching is extremely difficult. Or if not, very time consuming. Following every iteration of every node.
I’m not sure how that can be overcome.
I’m hosting one right now. Lemmyunchained.net
But in will have to Limit Users at some point.
I dont Think people properly understand they can be on any server. And join multiple communities. And it all Show up in their Feed. They don’t Need to worry about “which community has the Most Users”
AI GENERATED:
The ttionya/vaultwarden-backup tool is intended to work with Docker volumes. However, you are using a bind mount, not a named volume. Bind mounts refer to the use of local folders to store data, as in your case (./vaultwarden:/data/), while volumes create a specific place within Docker’s own filesystem for the data.
Although this tool is designed for volumes, it might still work with bind mounts if the backup container can access the data directory. You would need to modify the volume line in the Docker Compose file for the backup tool to point to the directory where your bind mount is located, i.e., to point it to your local ./vaultwarden directory.
So, you might want to adjust your docker-compose.yml file like this:
services: vaultwarden-backup: image: ttionya/vaultwarden-backup:latest container_name: vaultwarden-backup environment: - PUID=1000 - PGID=1000 - BACKUP_INTERVAL=12h - PRUNE_BACKUPS=7D volumes: - ./vaultwarden:/vaultwarden:ro - ./backups:/backups restart: unless-stopped
In this configuration, ./vaultwarden:/vaultwarden:ro line is the key. It mounts your local ./vaultwarden directory to /vaultwarden inside the backup container (readonly mode), which should allow the backup tool to access the data.