I do not know the in’s and out of ircv3. But we use matrix/elements for videocalls. Groupcalls. Screen and videosharing etc as well; Not just text chats. Beeing able to quickly search all of your chat history across all your channels and dm’s are very nice. Not requiering a irc bouncer to recieve messages is essential.
Atleast for us having another vm among the thousands we host in our dc is not a huge cost, but i understand that is not the same for everyone.
Thank you for a detailed answer. We probably do not notice much of this problem yet, since we are in the low user count of 30-40 with mostly local channels.
I have never tried that. We use it to share powerpoints in meetings or do troubleshooting together. Or I use it to do family video calls with the kids. Fps are never an issue. There are times where there are compression artifacts tho. Especially if someone have a bad or variable connection. On a buss or a train or similar.
In what way are matrix expencive? You do not have to self host it. You can just make an account on any public matrix server.
I do not know what you talk about. I use screen sharing and voice chat daily on elements with our own hosted matrix server.
Edit: i felt wrong saying “voice chat” what even is that. I make regular calls and video calls with screen sharing in elements ;)
Matrix+elements is very easy to selfhost in any homelab. works well enough for goverments. Federated and easy end to end encryption. And one can easily set up a web archive bridge forvarchiveable rooms.
That beeing said i still think IRC is the best for pure text chat.
old post, but I so wonder why you got downwoted for saying it like it is. a good isp will give you a /56, the minimum best practice. a great isp will give you a /48 you’r router will also participate in the wan /64, but that is just the uplink, and not something that will be used on the lan. https://www.ripe.net/publications/docs/ripe-690/#4--size-of-end-user-prefix-assignment---48---56-or-something-else-
How often depends on how much work it is to recreate, or the consequences of loosing data.
Some systems do not have real data locally, get a backup every week. Most get a nightly backup. Some with a high rate of change , get a lunch/middle of the workday run.
Some have hourly backups/snapshots, where recreating data is impossible. CriticL databases have hourly + transaction log streaming offsite.
How long to keep a history depends on how likely an error can go unnoticed but minimum 14 days. Most have 10 dailes + 5 weeky + 6 monthly + 1 yearly.
If you have paper recipes and can recreate data lost easily. Daily seems fine.
Terribly sorry. This is probably my norwegian shining thru. Where concatination of words are very common.