MSC2771: Bookmarks #2771
MSC2771: Bookmarks #2771
Conversation
MTRNord
force-pushed
the
bookmarks-spec
branch
from
aaae8fa
to
72fca4a
Compare
turt2live
added
kind:feature
…n format based on discussions.
|
I am working on a tui based reference impl "utility" (Not a full MX Client but a todo application focused on just this feature) which implements both approaches but defaults to the main versions when sending. The unstable prefixes are (I might also build a small flutter app for this allowing synced todos across devices) https://github.com/MTRNord/mx-bookmarks Edit: Dev stalled for personal reasons |
turt2live
added
the
needs-implementation
| important messages without needing to know a search term. This proposal aims to provide browser or TODO list alike | ||
| bookmarks. | ||
|
|
||
| ## What sets this apart from other Proposals that are similar (like Pinning and MSC2437)? |
There was a problem hiding this comment.
To be honest, I still don't see how this is materially different from #2437, aside from suggesting the ability to store metadata next to the saved event. Perhaps it would be great to work together on advancing #2437 instead of having two mechanisms doing very similar and even overlapping things (out of these two, I see #2437 as more elaborated).
| On the other side of similar MSCs is the MSC2437 which allows hashtag alike tagging of events. This allows to search | ||
| events by topics or displays them based on their topic. You might think that bookmarks would work with this (and they | ||
| might) but this Proposal wants to also cover the specifics of bookmarks and is more aimed to be alike browser bookmarks | ||
| and allows not only marking as bookmarks but also aims to give it some bookmark specific metadata. |
There was a problem hiding this comment.
Browser bookmarks in Firefox have a tags field as well, FWIW (and Chrome bookmarks don't seem to support any metadata at all, or I'm lost in its UI).
| { | ||
| "event_id": "$12345:example.com", | ||
| "title": "Food Choice", | ||
| "comment": "I need to buy stuff for this" |
There was a problem hiding this comment.
Is that an exhaustive example in terms of metadata, or an indicative one? In other words, can there be something on top of title and comment? If it can, I wonder if the stock set of attributes should come in m. namespace.
|
Closing due to not having the time to maintain |
turt2live
added
abandoned
Rendered
Signed-Off-By: MTRNord info@nordgedanken.de