Feature Request: Message Archive Management #660
Comments
|
Definitely something I'd like to add, just need to find the time. |
|
XEP-0313 is an improvement over XEP-0136 which was requested in #264 . |
|
Could this be implemented as a plugin? |
|
Without having looked too deep into the XEP my guess is the plugins API probably doesn't yet have enough to be able to implement it. I could be wrong though, some investigation into the XEP and an overview of the flow of stanzas and UI operations would help. |
|
Anything new here? It's been two years almost.. |
|
Not had a look at this feature yet, it's quite a large one and others have taken priority. I would like to add it in the future though. |
|
|
|
@boothj5 ping :) |
|
Together with Message Carbons, this would make for a perfect console client. Following :) |
XEP-0184: Message Delivery Receipts, *requires* the id attribute. Generally this is not the case. For this reason the id was only present in the DeliveryReceipt struct since it was only used for XEP-0184. For #660 XEP-0313 MAM and #805 XEP-0308 Last Message Correction we will also need the id. So in preparation for further work let's move the id to the general ProfBuffEntry. We will need to adapt code so that we actually always write the ID if we receive one.
I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (#660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (#660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (#660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (#660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (#660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (#660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (#660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (#660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (#660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (#660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (#660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
Send a request (which we can't handle yet) :-) Regards #660
Send a request (which we can't handle yet) :-) Regards #660
Send a request (which we can't handle yet) :-) Regards #660
|
#1306 with basic MAM support has been merged. Only contains basic support. |
|
When implementing MUC MAM we need to tell the MUC that we dont want to get MUC history upon joining anymore. |
|
#1724 got merged! |
|
Todo:
|
|
Also maybe trigger fetching mam when connection gets re-established. Be careful though because if a new message is received before the mam request gets triggered messages that were sent whilst connection was down might get lost |
|
@MarcoPolo-PasTonMolo are you maybe in the mood to take a look at MUC MAM? |
|
Sadly no. I'm starting to get busy again |
TODO split this commit later and see if all its changes are needed See profanity-im#660
Show correct timestamp for mentions and triggers (it used to show current timestamp instead of the message's one), and flip commands when displaying history. See profanity-im#660
Disable muc history when MAM is enabled see profanity-im#660
|
I’m not sure I understand what I’m seeing, but my client reports mam is not enabled on my server when i know it is enabled and working on prosody for other clients. Is this not fully implemented yet? |
|
MAM is implemented for regular chats just not for MUC (group) chats. |
|
On July 30, 2024 4:06:38 AM UTC, Michael Vetter ***@***.***> wrote:
MAM is implemented for regular chats just not for MUC (group) chats.
The message you are seeing should only appear when the server really doesn't support it.
My other clients claim XEP-0313 is available and function with it. How can I debug this?
…--
Emma Tebibyte (fae/faer)
http://tebibyte.media/~emma
|
Are you running in Proanity in any special way? Like enabling some scripts/plugins or do something before it completely is set up? For example after it connected do you see this message immediately or do you already try to join a couple of MUCs/start chats? |
|
On July 30, 2024 4:32:15 AM UTC, Michael Vetter ***@***.***> wrote:
> My other clients claim XEP-0313 is available and function with it. How can I debug this?
Are you running in Proanity in any special way? Like enabling some scripts/plugins or do something before it completely is set up? For example after it connected do you see this message immediately or do you already try to join a couple of MUCs/start chats?
Profanity is set up however OpenBSD ships it. The message appears when I try to request mam for a chat by paging up in a chat with someone.
…--
Emma Tebibyte (fae/faer)
http://tebibyte.media/~emma
|
|
Which server/version? And which Profanity version? |
|
On July 30, 2024 5:05:57 AM UTC, Michael Vetter ***@***.***> wrote:
Which server/version? And which Profanity version?
Profanity is version 0.14.0 and prosody is version 0.12.4
…--
Emma Tebibyte (fae/faer)
http://tebibyte.media/~emma
|
|
Update: MAM works if I wait to open a chat with someone until I’ve closed all open MUC windows. |
|
Actually, it seems MAM doesnt work if I receive messages at the start of a session, but if I quit and restart profanity it works. |
|
Hi! Any progress on this? Still no history of messages in the latest release… |
|
No |
Greetings,
I was wondering if there were any plans to support XEP-0313. I found an issue dated back in 2014 where an issue was tagged as a feature for a Milestone but later removed so I was wondering if Profanity would get support for that in the future. Thanks in advanced!
The text was updated successfully, but these errors were encountered: