Prosody Docker Container and Integration #1
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: q/thirdculture#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We need a way to communicate as a group done the DIY self hosted way. I think we will go with the XMPP protocol and run the service using prosody under docker. Should be 100% compliant with this tool: https://compliance.conversations.im/ and federate so it can connect with other member services. Account creation should be tied to the werc user sign up to members can use the same username and password. I believe this can be done by creating the hashes like the https://thirdculture.top/_tools/hash services does just for prosody and then it can be used to create an account with that username and password.
undefinedto mainAfter researching this will probably involve database manipulation :(
we now have a working server live just need to create scripts to add user to database given hash and test
Integrating the hash service with the xmpp integration proved way to hard and cumbersome. So I just used the internal prosody https://prosody.im/doc/modules/mod_invites. This uses bloated shit like bootstrap and jquery but it works for now.
Right now it mostly works but with an error with IOS clients when going to register, from my digging into the logs this is the output that happens before the connection is dropped and the client is thrown an error:
Unhandled c2s_unauthed stanza: iq; xmlns=jabber:iq:register
IDK how to fix this and tried for a while, workaround is just to make and account then login.
The invite page uses a lot of bloated software I don't like so I also want to make our own external login service thats ideally just a page with info then the register link and invite link. Most clients have a feature to allow registration with a invite link but as previously discovered this is not reliable so we will need a registration form as well, given the link.
Closing this issue for now I'll make a repo with the prosody configs and shit to put these issues to. Prosody is external to the werc site stack so thats nice in a way :). Anyway it works* and we got 100% compliance.