older messages not loading. about profanity

[jubalh]

my server doesn't support MAM

So we have the fault why you dont see your old messages.
But still Profanity shouldn't just print Loading older messages... and that's it. It should 1) not try to load MAM (probably its doing that) 2) load from SQL DB what's there and then stop this action.

[ShroomiePerson]

forgot to add a photo, sorry.

[jubalh]

Did you set /mam on?

Weird that it prints Loading older messages... without doing anything.
Even if MAM is off it should do something, we might have to investigate.

[ShroomiePerson]

/mam is on.

[ShroomiePerson]

update: according to the console-thing in tab one, my server doesn't support MAM. ig i'll bring this up with them then.

[sjaeckel]

I recently looked into this and the mechanism that determines whether MAM is supported, resp. whether this error message should be printed, is not correct. I'll create a write-up when I have the time, but for now we should treat MAM as "works if the stars align" a.k.a "incomplete". This error message can be ignored in most of the cases, especially when it's printed at profanity start-up time.

FTR: #1944 was also incomplete. The PR doesn't make the situation worse, but it also didn't improve it.

[sjaeckel]

As a work-around you can close that window and once the connection setup is finished you can re-open it again and then 1-on-1 MAM should work, if it's supported by the server.

This "connection setup" should take around 30-60 seconds, sometimes also longer, depending on various things like how many MUCs you auto-join and others.

[ShroomiePerson]

hey it's just a server issue, i moved somewhere else and everything's good now.