Slidge - XMPP gateways - 2025-02-17

debacle: it is public domain, sorry for pinging you for nothing

nicoco pushed 3 commit(s) to matridge - fix: clear matrix state files after unregistration (nicoco) - feat: implement session emoji verification (nicoco) - docs: mention that one needs to be patient with matridge (nicoco) https://codeberg.org/slidge/matridge/compare/35b99524f..3b803473a

@nicoco don't remember where you said it but is there plans to build again debian packages?

Yes. Right now it's not automated anymore but I'll give it a small bump soon

Thanks ❤️

The plan (later) is to move it to codeberg too and have a release/bleeding-edge distinction

right now it's a frankenstein thing where slidge core is "latest release" and other ones are bleeding edge. I'd like to clean that up at some point

> The plan (later) is to move it to codeberg too and have a release/bleeding-edge distinction Looking forward to it, I loooooove nightly builds 🥰 ↺

(be aware, the latest prosody-trunk is broken)

I run debian stable and almost nothing bleeding edge except slidge ;)

Weird

Today's Prosody trunk ... Works for me. Did you mean latest slidge?

When listing legacy contacts in matteridge, it shows instance-wide contacts, not only those inside the team

@Menel

https://upload.postblue.info:5281/file_share/067b2f67-1814-72bc-9240-a342ef1d5d24/56a5d62a-64d7-444a-b0b0-a13a0151ed20.png

I don't understand your statement then x)

There is a tracebacks when using a specific command, the command executes how it should regardless and prosody doesn't crash. It is only a newly intruduced command. ... So not what I call prosody is broken. It Jsut generates an unessesary trace upon an "prosodyctl check features" ✏

haaaa, ok, I can apt upgrade then, thank you

deuill closed a pull request for slidge-whatsapp docs(readme): fix container repo https://codeberg.org/slidge/slidge-whatsapp/pulls/17

deuill pushed 1 commit(s) to slidge-whatsapp - docs(readme): fix container repo (nicoco) https://codeberg.org/slidge/slidge-whatsapp/compare/28932faf7..87fa82982

nicoco: the discord double-puppeting bridge works now, len can probably provide you sources

double-puppeting bridge works now

wasn't discord all the time double puppeting ?

> When listing legacy contacts in matteridge, it shows instance-wide contacts, not only those inside the team it's supposed to show contacts you have interacted with, and you can be part of several teams... at least that's how inria's instance is configured ↺

qy: link to the working fork?

Kris: ask len, I do not have the sources

Who is len?

https://git.linux.ucla.edu/jshiffer/xmpp-discord-bridge

Ah, thanks

nicoco pushed 2 commit(s) to matridge - fix: unregistration (nicoco) - fix: verbose logging of matrix events (nicoco) https://codeberg.org/slidge/matridge/compare/3b803473a..1e10d6603

c3p0-slidge published a release for matridge v0.2.0 https://codeberg.org/slidge/matridge/releases/tag/v0.2.0

debacle: a tagged release for you! apologies for not doing it before. :(

> debacle: a tagged release for you! apologies for not doing it before. :( Wonderful, a release just for me! ;-) Thank you and don't worry. I'll try to upload to Debian ASAP. ↺

> it's supposed to show contacts you have interacted with, and you can be part of several teams... at least that's how inria's instance is configured I checked and they are not in the team oO ↺

AFAIK there is a mattermost instance and teams are not segregated, you _can_ chat with members of other teams. What's the actual issue you are facing?

OK, good to know

Also, you can be in several teams, which I find quite messy in the official mattermost UI, I never know under which "team" my 1:1 chats are (because we have common teams with some contacts)

I'm only in one at the moment

Update Slidgerepo to Buildprozess 1432269 from: 0.0.0-dev+20250209-git0f4cf59629 to: 0.0.0-dev+20250217-git66ce10b7f0