Jason Rhinelander
Jason Rhinelander
There are currently some limitations on the Session side in terms of being able to manipulate the permissions; in order to properly make an invite-only room, you'd have set to...
Actually I quite like the idea of being able to generate an "invite token" that you can send to a user to join a room without having to know their...
> If I add moderators in Session messenger, not on CLI, they all are admins and would be allowed to remove other admins as I was reading. Means it would...
> But I do think, to make sure only the right ones joins, there should be so invite based on session id too. like creating some time based auto deleting...
Yes and no: From the SOGS perspective, yes, SOGS allows admins to pin/unpin multiple messages per room. Session clients, however, have not yet implemented this functionality so that the moment...
> Ah. Is it possible, then, to manipulate the database to pin a message? Session clients aren't currently *reading* the pinned message status so it won't accomplish much. I'll see...
The room "URL" isn't ever accessed directly; rather Session just uses a fake URL to encode the base URL + room name + public key. All actual requests go via...
There should be info in the log file (~/.config/Session/logs/log.log or something like that). It can take some sifting through. though.
I've seen this on desktop when the room token contains upper-case letters. If so, the session-desktop devs are aware of it and it needs a fix in Session.
I believe this will be fixed now and the fix will be available in the next session-desktop release.