Re: Indicating Messages' Urgencies and Importances

Thank you. I opened a discussion thread on SocialHub ( https://socialhub.activitypub.rocks/t/message-priority-urgency-or-importance/4327 ) and an issue on Codeberg ( https://codeberg.org/fediverse/fediverse-ideas/issues/69 )!


Best regards,
Adam

________________________________
From: Bumblefudge <bumblefudge@learningproof.xyz>
Sent: Wednesday, June 19, 2024 4:02 AM
To: Adam Sobieski <adamsobieski@hotmail.com>
Cc: public-swicg@w3.org <public-swicg@w3.org>
Subject: Re: Indicating Messages' Urgencies and Importances

Hey Adam!

Your followup message (and book link) made this much more interesting to me, who has always thought that AP was specified as a messaging protocol but is increasingly implemented as a publishing protocol. Evan is correct that the best way to get this built is to find 2 or 3 implementations that already have the user stories and the authN/authZ to build out more robust messaging. (Maybe this will be easier after [E2EE goes live][^1] on implementations?). Perhaps the best way to encourage more enthusiasm for (and, to be blunt, investment in) messaging is to contribute to the E2EE prototyping, specification, and subsequent adoption push that's upstream of it?

More generally, a great place for putting ideas that may be too early for the Fediverse (i.e., ideas waiting on certain kinds of implementations to...exist, AND have resources to invest in new features on top of that) is the issues of the [`fediverse-ideas` repo][^2], which is a kind of issue-tracker for future FEPs.  It's a community venue, like SocialHub and the FEPs, and lots of ideas sit there for years before someone picks them up and implements them, then shares a FEP of how they did so for others to consider interoperably implementing elsewhere. For an idea like this, we may need to wait for a RichMailiverse or Groupchativerse to form, along the lines of today's Threadiverse (which is currently speed-running the creation of shared data semantics and UX primitives to smoothly federate with non-threaded publishing implementations). As that group is showing us, these things can move quite fast with just a few people working fulltime to engineer a whole new flavor of Fedi!

[^1]: https://lists.w3.org/Archives/Public/public-swicg/2024Jun/0007.html

[^2]: https://codeberg.org/fediverse/fediverse-ideas

Thanks,
__juan

On Wed, Jun 19, 2024 at 9:30 AM Adam Sobieski <adamsobieski@hotmail.com<mailto:adamsobieski@hotmail.com>> wrote:
Evan,

Thank you. I'm glad that these ideas are also interesting to you.

While it is a big ask – putting on my idea-pitching hat – benefits include that learners would be able to more easily complete sessions of uninterrupted homework, workers more easily complete sessions of uninterrupted work, while simultaneously feeling connected to their peers, co-workers, and communities, not concerned about missing any urgent or important message.

Some operating systems (e.g., Windows 11) provide their users with "focus sessions". During these sessions, notifications and interruptions from applications are reduced or minimized. I don't know whether these sessions can be automatically synchronized across devices for users, e.g., with their connected smartphones.

In theory, messages having priorities, urgencies, or importances would enable new possibilities, new settings and configurations, for focus sessions. Users would be able to indicate that certain instant-messaging, social-media, and productivity-collaboration applications only be able to notify or interrupt them when a message was sufficiently urgent, sufficiently urgent from a co-worker or teammate, and so forth.

As envisioned, messages' priorities, urgencies, or importances might be from enumerated sets (e.g., "low", "normal", "high"), from more granular ranges of values (e.g., #00 - #FF), or from floating-point intervals (e.g., between 0.0 and 1.0). If from a numerical range or interval, text-string values could be mapped to certain numerical values.


Best regards,
Adam

P.S.: I thought of these ideas while reading a book on attention span, productivity, and modern technology:

Mark, Gloria. Attention Span: A Groundbreaking Way to Restore Balance, Happiness and Productivity. Hanover Square Press, 2023.

________________________________
From: Evan Prodromou <evan@prodromou.name<mailto:evan@prodromou.name>>
Sent: Tuesday, June 18, 2024 10:13 PM
To: Adam Sobieski <adamsobieski@hotmail.com<mailto:adamsobieski@hotmail.com>>; public-swicg@w3.org<mailto:public-swicg@w3.org> <public-swicg@w3.org<mailto:public-swicg@w3.org>>
Subject: Re: Indicating Messages' Urgencies and Importances


Hey, Adam. The right way to do this is to define an extension namespace for ActivityPub that includes properties for the author's estimated urgency.

However, that also requires support by client software and some server software. So it's a big ask!


I think it's an interesting problem, though.


Evan


On 2024-06-17 2:23 p.m., Adam Sobieski wrote:
Social Web Incubator Community Group,


Hello. I have some ideas that I would like to share and discuss with respect to indicating messages' urgencies and importances.

With email, authors can indicate their messages to be of low, normal, and high importances. Similarly, with modern productivity collaboration software, authors can indicate delivery options indicating a message to be of high importance or urgency.

With means of manually differentiating mentions and public and private messages with respect to their urgencies or importances, users' applications could better determine whether, when, and how to notify and to potentially interrupt recipients (and when not to) upon receiving messages – in accordance with users' settings and configurations.

Providing users the means to differentiate their messages with respect to urgency and importance may involve extending schemas and vocabularies.

Any thoughts on enabling users to be able to manually indicate urgency or importance with respect to their public and private messages? Thank you.


Best regards,
Adam Sobieski

P.S.: A related syntax idea involves appending an exclamation mark to signal a matter of urgency or importance to a mentioned user:

@alice@example.com<mailto:alice@example.com>, @bob@example.com<mailto:bob@example.com>, and @charles@example.com<mailto:charles@example.com>! the meeting is rescheduled to Thursday.

Above, the author utilized an "!" to indicate that they felt that the message was particularly urgent or important for "@charles@example.com"<mailto:@charles@example.com> who might have been preparing to present a slideshow at that meeting.