Search the Community

I was watching the second last WAN show recently and saw Linus talking about how good would be if messaging apps had interopatibily and I find that is something almost impossible to do with most messaging apps. First of all I probably should clarify what I meant by interopatibily, which is the wikipedia and dictionary definition of it: "Interoperability is a characteristic of a product or system to work with other products or systems.". There's two main reasons that I think that is something impossible to do. First of all is that the way that messaging applications works at server level where they work differently from each other, for example telegram uses MTProto while WhatsApp uses a modified version of XMPP, this alone makes impossible to WhatsApp and Telegram to talk between each other without major rewrites to the core software and the clients if they don't create a common protocol between then. The second main reason is the lack of federation "A federation is a group of computing or network providers agreeing upon standards of operation in a collective fashion.", which basically is a protocol to make the interopatibily of two distinct softwares, so a way to make telegram and whatsapp to talk without they needing to use the same core protocols and servers(basically invalidating the first point), e-mail is nowadays the most famous federated protocol out there as you can send an e-mail between different servers and domains The main problem with federation is that the federation itself isn't a protocol itself but a term, so if the EU regulation doesn't specify a commom federated protocol for them to work together, that wouldn't solve anything as Apple, Telegram, Facebook, Google and etc. can each own to create their own "federated" protocols making them able to cripple and limit third-party software access to it. This would force that each messaging app to implement their own integration with other service. So, here's would be my (maybe not so good) solution to solve this: The first one would be to EU to create a federation messaging standard and force the companies to implement some basic levels of it. The second one(that I like the most) is to incentivize people to use open/public federated standards, instead of private ones. I searched here(LTT forums) before I wrote this to search peoples opnions here about both protocols, while I didn't found a lot I know that most of the complains about them are the lack of features(stickers for example) and the lack of commom people/community(userbase) there. Unfortunately those are real and valid reasons of why someone doesn't want to join it but they can be tackled. While the userbase fix is probably the hardest one to fix but a way to do it is for people that belongs or commands larger communities(youtubers, forum chats, software developers, ...) to began to use it too. I'm not saying for they to drop discord(or any other plataform) all together but to use XMPP/Matrix for the community too. Because those are federated software(where if you are a user from the 404.city server, you can talk and join communities on conversations.imand vice-versa), communities(like LTT) maybe could incentivize the use by giving usernames for supporters. The lack features is one of the interesting ones in those plataforms, unlike proprietary plataforms, people who have the knowledge and time can add features into theme, because they're open-source and a open-standard, the biggest example in XMPP is omemo end-to-end cryptography on it, that was created as an idea in Google Summer of Code and it ended up being part of the XMPP protocol a year later. So custom-emojis and more can be done if someone who have the knowledge, time and will to implement it. The lack of community and money is also a big problem with those softwares, an example is Matrix that it for some time had a third-party company funding the project, than they dropped the funding, during the funding phase the project evolved a lot in conparison to now, so increasing the community can lead to more money and making those plataforms better. Sorry for the long post...

Im going to be getting an older lenovo think station used as a server from a friend thats giving it to me in turn for setting up a plex server for him on it. Along with a plex server i want to set up an xmpp server, a mail server(going to mention a domain) and host a few occasional game servers as well as a plain storage server i can access from school on my laptop or remote into a virtual machine when i need more power than my lenovo t410. I was also thinking about buying a domain since i can get ones i like for around $6 a year, however since im doing this from home and have a dynamic public ip i recognize i need to use a DDNS, i was planing on using dyn.com but have never done anything with servers or domains apart from my MTA in server administration in high school. If i buy a domain from somewhere like domain.com how do i go about setting up the DDNS for it using dyndns? And if anyone can get me some useful information on SRV Records and how to set them up that would be great too. Server is a lenovo thinkstation, dont know the exact specs at the moment but i will be running Windows Server 2016.