#319 - [XMPP] - Enable custom domain - Disroot/Disroot-Project - Disroot Forgejo: Brace yourself, merge conflicts ahead.

muppeth commented

2022-09-07 16:19:41 +02:00

Owner

tbd

muppeth added the

administration

xmpp

labels 2022-09-07 16:19:41 +02:00

meaz commented

2023-10-01 09:52:01 +02:00

Owner

this is done, right? We can close this @muppeth I think, can't we?

muppeth commented

2023-10-01 14:46:31 +02:00

Author

Owner

As mentioned on last meeting. This is kind of done but not properly implemented. So I said last time it's something I wanted to focus on this milestone and finalize it.

muppeth added this to the 23.10 - October milestone 2023-10-01 14:46:34 +02:00

muppeth commented

2023-11-03 12:30:10 +01:00

Author

Owner

The problem I have with the custom domain on xmpp is this:
To add virtual domain to prosody server we need tls certificate. In case of Letsencrypt, this cert needs to be renewed every three months. Leaving it to people to generate and then send it to us IMO is impossible to handle as it will create ton of overhead for us (adding new certs to the server on time). The other solution is if we handle certificates. This is all good except for the issue where someone wants to add domain (mydomain.ltd) but at the same time has a website running under the same domain. We need "A" record pointing to our server as we need to create/renew certificate but if that record is used, we can't. There are two solutions to this and both are bad:

Users then cannot use their root domain and need to use subdomain for their xmpp (chat.domain.ltd)
Users point their A record and we the redirect the traffic to their website (work as a proxy).

In case 1. the issue is that people would most likely like to have the same domain as they use on email (there the issue does not occur) which makes more sense. So I guess people wouldnt like to compromise

In case2. Although you solve the issue with the certificate for xmpp, we would be able to monitor traffic to people's webistes, plus generate more traffic on our IP's. Not only that, we would still have issues with tls on the website side of things (either we would need to send new certs to the website owner, or we would have to setup permanent cert between our server and website server. This adds even more issues.

So there is no easy/good solution to do this. Solution that does not require extra work and complexity. So the solution as I see it now is:

No xmpp linking at all.
No xmpp linking if you are using the domain you want to link for the webiste already
xmpp linking but if you are using the domain you want to link for website you need to specify subdomain.
Offer website hosting.

What do you @Disroot/Owners think?

The problem I have with the custom domain on xmpp is this: To add virtual domain to prosody server we need tls certificate. In case of Letsencrypt, this cert needs to be renewed every three months. Leaving it to people to generate and then send it to us IMO is impossible to handle as it will create ton of overhead for us (adding new certs to the server on time). The other solution is if we handle certificates. This is all good except for the issue where someone wants to add domain (mydomain.ltd) but at the same time has a website running under the same domain. We need "A" record pointing to our server as we need to create/renew certificate but if that record is used, we can't. There are two solutions to this and both are bad: - Users then cannot use their root domain and need to use subdomain for their xmpp (chat.domain.ltd) - Users point their A record and we the redirect the traffic to their website (work as a proxy). In case 1. the issue is that people would most likely like to have the same domain as they use on email (there the issue does not occur) which makes more sense. So I guess people wouldnt like to compromise In case2. Although you solve the issue with the certificate for xmpp, we would be able to monitor traffic to people's webistes, plus generate more traffic on our IP's. Not only that, we would still have issues with tls on the website side of things (either we would need to send new certs to the website owner, or we would have to setup permanent cert between our server and website server. This adds even more issues. So there is no easy/good solution to do this. Solution that does not require extra work and complexity. So the solution as I see it now is: 1. No xmpp linking at all. 2. No xmpp linking if you are using the domain you want to link for the webiste already 3. xmpp linking but if you are using the domain you want to link for website you need to specify subdomain. 4. Offer website hosting. What do you @Disroot/Owners think?

meaz commented

2023-11-03 20:36:05 +01:00

Owner

Offer website hosting.
I don't think we can do that, human resources are missing.

xmpp linking but if you are using the domain you want to link for website you need to specify subdomain.
That is my favorite solution, as it seems simple one for us, and for users.

No xmpp linking at all.
It seems the easiest one :) But I think some people have already paid for that...

> 4. Offer website hosting. I don't think we can do that, human resources are missing. > 3. xmpp linking but if you are using the domain you want to link for website you need to specify subdomain. That is my favorite solution, as it seems simple one for us, and for users. > No xmpp linking at all. It seems the easiest one :) But I think some people have already paid for that...

antilopa commented

2023-11-05 09:45:50 +01:00

Owner

No xmpp linking at all.
It seems the easiest one :) But I think some people have already paid for that...

officially they did not pay for any service but made a donation and get some perks as reward.. We could decided to refund the donation if people demand that.

but i agree that at this point option 3 sounds the most workable.

> > No xmpp linking at all. > It seems the easiest one :) But I think some people have already paid for that... > officially they did not pay for any service but made a donation and get some perks as reward.. We could decided to refund the donation if people demand that. but i agree that at this point option 3 sounds the most workable.

muppeth modified the milestone from 23.10 - October to 23.11 - November

2023-11-07 02:17:29 +01:00

muppeth modified the milestone from 23.11 - November to 23.12 - December

2023-12-03 13:56:47 +01:00