~nicoco

Trackers

~nicoco/slidge

Last active 6 days ago

~nicoco/slidgram

Last active 12 days ago

~nicoco/slidge-whatsapp

Last active 13 days ago

~nicoco/matridge

Last active 26 days ago

~nicoco/slidcord

Last active a month ago

~nicoco/messlidger

Last active 2 months ago

~nicoco/sleamdge

Last active 2 months ago

~nicoco/slidgnal

Last active 4 months ago

~nicoco/matteridge

Last active 7 months ago

~nicoco/jellyfix

Last active 7 months ago
View more

#27 Poll support a day ago

Comment by ~nicoco on ~nicoco/slidge-whatsapp

It is planned. There is no dedicated UI in XMPP clients, but I hacked something with emojis for slidgram, we could do the same for WA.

#14 RAM usage spike when sending a series of pictures 12 days ago

Ticket created by ~nicoco on ~nicoco/slidgram

#194 Whatsapp re-login in advance 13 days ago

Comment by ~nicoco on ~nicoco/slidge

Oh I forgot to reply to this earlier, apologies... Thanks for the suggestion!

It looks a bit complicated to do since we have no clue when the unlink will be triggered. I have it every 2 weeks on average, but it's sometimes longer, sometimes shorter... And my partner who didn't uninstall the whatsapp client from their phone just never had to repair in more than a year. Slidge-whatsapp should notify you when you need to re-pair, I think it's fine this, except that you miss messages on the XMPP side in between re-pairs. I'm closing this in favor of https://todo.sr.ht/~nicoco/slidge-whatsapp/31

REPORTED RESOLVED NOT_OUR_BUG

#31 Missing WA messages between re-pair 13 days ago

enhancement added by ~nicoco on ~nicoco/slidge-whatsapp

#31 Missing WA messages between re-pair 13 days ago

Ticket created by ~nicoco on ~nicoco/slidge-whatsapp

When you re-pair, slidge-whatsapp should fetch the messages since it was last 'linked' to whatsapp, to ensure no 'holes' (missing messages) on the XMPP side.

This is currently not doable easily because we miss history persistence-across restarts in slidge core.

Also, since you need to open the official WA client to re-pair anyway, it's not that bad: you can see potential messages you've missed in official client. But it would be nice to have...

#30 Status messages appear in a weird unnamed-muc 14 days ago

Comment by ~nicoco on ~nicoco/slidge-whatsapp

According to Peter, statuses and broadcast lists are not the same. We should probably do some testing with official clients, one day. But I suggest we handle it all as a read-only MUC anyway, and make sure we don't try to fetch info for an invalid group JID as this might look very suspicious from the Meta side.

#30 Status messages appear in a weird unnamed-muc 14 days ago

Comment by ~nicoco on ~nicoco/slidge-whatsapp

From https://github.com/tulir/whatsmeow/blob/main/types/message.go#L19

IsGroup bool // Whether the chat is a group chat or broadcast list

#30 Status messages appear in a weird unnamed-muc 14 days ago

bug added by ~nicoco on ~nicoco/slidge-whatsapp

#30 Status messages appear in a weird unnamed-muc 14 days ago

Ticket created by ~nicoco on ~nicoco/slidge-whatsapp

According to tulir, the man, himself:

they're perfectly ordinary messages, the chat jid is status@broadcast

Apparently slidge-whatsapp think they are group messages, which creates a unnamed MUC.

We should handle that case with contact.online(status='the text') instead. It can be something else than a text, so this does not work. Keeping it a read-only MUC. To make XMPP clients know that it's read only, there is no helper in slidge yet, but the idea is to:

part = await muc.get_user_participant()
part.affiliation = "member"
part.role = "visitor"

#192 XEP-0486 compliance 27 days ago

Comment by ~nicoco on ~nicoco/slidge

REPORTED RESOLVED IMPLEMENTED