Bug 29797

Summary: some sort of support for "verb-like" URIs
Product: Telepathy Reporter: Simon McVittie <smcv>
Component: tp-specAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: enhancement    
Priority: lowest CC: eitan.isaacson, mikhail.zabaluev
Version: git master   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Bug Depends on: 26866    
Bug Blocks:    

Description Simon McVittie 2010-08-25 04:57:50 UTC 
From Bug #26866:

wjt:
> Note that you might also want to support URIs such as
> 'xmpp:smcv@example.com?subscribe' or, more troublingly,
> 'aim:goaway?message=bonghits+in+the+hood'.

...

smcv:
> Yeah, those URIs are more troublesome. My thought was that initially, we'd just
> support URIs as nouns (the way the architecture of the Web claims they should
> be used) mapping to contacts.
>
> If we want to support URIs (mis)used as verbs as well, we'd need to add a
> separate ActOnURI(s: URI) option that did "something appropriate".
>
> However, I think URIs as verbs are likely to need rather more UI than the CM
> can offer on its own, and contain additional cans of worms that I don't want
> blocking the simpler feature. URIs for many (all?) actions shouldn't actually
> perform the action, they should just open up appropriate UI to prepare to do it
> (e.g. fill in the message as a draft, or whatever, so the user just has to
> press Send to confirm).

with more discussion near <https://bugs.freedesktop.org/show_bug.cgi?id=26866#c14>.
Comment 1 GitLab Migration User 2019-12-03 20:22:02 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/78.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.