-
c3p0
c3p0-slidge pushed 1 commit(s) to slidgram - build(lockfile): automatic update (c3p0) https://codeberg.org/slidge/slidgram/compare/be6f425d7..96eb9a0d6
-
c3p0
c3p0-slidge pushed 1 commit(s) to matteridge - build(lockfile): automatic update (c3p0) https://codeberg.org/slidge/matteridge/compare/918a0fb5f..9493dcbc7
-
c3p0
c3p0-slidge pushed 1 commit(s) to matridge - build(lockfile): automatic update (c3p0) https://codeberg.org/slidge/matridge/compare/431516323..97f07e20e
-
c3p0
c3p0-slidge pushed 1 commit(s) to sleamdge - build(lockfile): automatic update (c3p0) https://codeberg.org/slidge/sleamdge/compare/e49159e22..5dddc214e
-
c3p0
c3p0-slidge pushed 1 commit(s) to slidge-whatsapp - build(lockfile): automatic update (c3p0) https://codeberg.org/slidge/slidge-whatsapp/compare/7a2913558..2f1577669
-
c3p0
c3p0-slidge pushed 1 commit(s) to slidcord - build(lockfile): automatic update (c3p0) https://codeberg.org/slidge/slidcord/compare/086e58a09..7df1a60ca
-
alberic89
Hello, I have a problem with slide-whatsapp. I configured it to be a priviligied component but I get the error `WARNING:slidge.core.gateway:IQ privileges not granted for pubsub namespace, we cannot create the MDS node of alberic@mydomain.com WARNING:slidge.core.gateway:IQ privileges not granted for pubsub#owner namespace, we cannot listen to the MDS events of alberic@mydomain.com`
-
alberic89
My Prosody config : ``` VirtualHost "mydomain.com" privileged_entities = { ["whatsapp.mydomain.com"] = { roster = "both"; message = "outgoing"; iq = { ["http://jabber.org/protocol/pubsub"] = "both"; ["http://jabber.org/protocol/pubsub#owner"] = "set"; }; } } Component "whatsapp.mydomain.com" component_secret = "my_secret" ```
-
alberic89
My Slide-Whatsapp config : ``` use-attachment-original-urls=true no-upload-file-read-others=true no-upload-path="/var/lib/slidge/attachements" no-upload-url-prefix="https://mydomain.com:5281/files" last-message-correction-retraction-workaround=true fix-filename-suffix-mime-type=true user-jid-validator=".*@mydomain.com" jid="whatsapp.mydomain.com" secret="my_secret" log-file="/var/log/slidge/slidge-whatsapp.log" log-format="%(asctime)s:%(levelname)s:%(name)s:%(message)s" ```
-
ThUnD3r|Gr33n
alberic89 I have the same issue, are you running prosody 13x ?
-
ThUnD3r|Gr33n
you miss something:
-
alberic89
> alberic89 I have the same issue, are you running prosody 13x ? yes, 13.0.1 ↺
-
ThUnD3r|Gr33n
Component "pubsub.yourdomain.tld" component_secret = "yourpassword" modules_enabled = {"privilege"}
-
ThUnD3r|Gr33n
but it does not work for me either after upgrading from 12 to 13
-
Orjan
Same persisting issue with latest Ejabberd, we finally had to switch off privilege_mod at all(
-
ThUnD3r|Gr33n
what the henk is going on ?
-
ThUnD3r|Gr33n
we need aa fix then! :)
-
ThUnD3r|Gr33n
first i thought maybe config change .. but seems like privilege is broken for ejabberd and prosody?
-
ThUnD3r|Gr33n
sourcce : https://modules.prosody.im/mod_privilege.html
-
fabrixxm
I'm on prosody 13 and mod_privilege looks like is working
-
fabrixxm
(but I'm not on the latest code of slidge)
-
fabrixxm
``` Component "whatsapp.mydomain.com" component_secret = "my_secret" ``` is missing ``` modules_enabled = {"privilege"; } ```
-
alberic89
> ``` > Component "whatsapp.mydomain.com" > component_secret = "my_secret" > ``` > is missing > ``` > modules_enabled = {"privilege"; } > ``` Yes, with this all is working. Thank you! I didn't remender seeing that it in the documentation. I will check later, for now codeberg is down. ↺
-
alberic89
There is a remaining error but doesn't seems to be important : `slidge-whatsapp[5568]: time=2025-04-23T11:39:48.673Z level=ERROR msg="Error reading from websocket: websocket: close 1006 (abnormal closure): unexpected EOF" module=Slidge.Socket`
-
ThUnD3r|Gr33n
fabrixxm so you did NOT add "modules_enabled" to your component config?
-
fabrixxm
I did. is alberic89 which didn't 🙂
-
ThUnD3r|Gr33n
o ok fabrixxm i just saw it.. is the semicolon needed after privilege? .. let me test this .
-
fabrixxm
maybe? I don't really know lua syntax...
-
alberic89
I didn’t used semicolon in m'y config.✎ -
alberic89
I didn’t used semicolon in my config. ✏
-
fabrixxm
here is the bit about enabling the module in slidge component https://slidge.im/docs/slidge/main/admin/component.html#id1
-
fabrixxm
and here about installing and configuring mod_privilege in prosody https://slidge.im/docs/slidge/main/admin/privilege.html#privileges-configuration
-
fabrixxm
note that it sould be added also in 'modules_enabled' prosody.cfg.lua
-
fabrixxm
(or at least, that what I get from docs 🙂 )✎ -
fabrixxm
(or at least, that is what I get from docs 🙂 ) ✏
-
morsmortium
fabrixxm: On the second link there is a bit of an error ``` In prosody.cfg.lua, add mod_privilege to the modules_enabled list. ``` You have to add privilege, not mod_privilege
-
fabrixxm
yes there is
-
ThUnD3r|Gr33n
i never put a semicolon there, but who knows .. it might work with.. i will try that later this evening and will report back
-
alberic89
For why there is no more slidcord package published on PyPi ?
-
projectmoon
hi, i am configuring the matrix bridge with a docker container. shouldn't the container respect `JID` as an environment variable?
-
projectmoon
ah, `SLIDGE_JID` and `SLIDGE_SECRET`...
-
projectmoon
so it's now running and connected... should i expect all my matrix users to appear in my xmpp contact list? because that isn't happening, exactly.
-
projectmoon
i see... list groups -> add as MUC.
-
projectmoon
are the MUCs created for 1:1 private?
-
SavagePeanut
In matridge? Yes. Matrix does not have a concept of a dedicated 1:1 room for a contact (or the concept of a contact at all, really). Bifrost fakes it by picking a room to treat as the 1:1, but I think the way slidge handles it by not pretending is less prone to breaking