Tent URL Scheme

This document will try to define what exactly the Tent URL Scheme could be used for.

Follow an entity

tent://follow?<entity_full_uri>

Unfollow an entity

tent://unfollow?<entity_full_uri>

View an Entity’s profile

tent://profile?<entity_full_uri>

View an Entity’s post

tent://posts
  ?<entity_full_uri>
  &<post_id>

New Post

More on what can be included in POST query see in tent-schemas

tent://post
    ?type=<post_type>
    &content=<post_content>
  [ &mentions=<entities_list> ]
  [ &published_at=<timestamp> ]
  [ &permissions=
      <public=( true | false )
    [ &( groups=<groups_list> | <entities_list> ) ]> ]
  [ &licenses=<licenses_list> ]
  [ &<all_other_possible_post_properties> ]

Alternative scheme

Proposed by ^graue: The entity should come first, followed by the resource or action.

tent://<entity_full_uri>
tent://<entity_full_uri>/follow
tent://<entity_full_uri>/unfollow
tent://<entity_full_uri>/profile
tent://<entity_full_uri>/posts/<post_id>
tent://<entity_full_uri>/post?<all_those_post_content_and_details>

This allows links (including mentions) and transclusions from HTML ‘essay’ posts in a natural way.

Fictional example

Just got back from the first Tent conference. <a href="tent://marco.tent.is/posts/ockwsl">Marco Ferreira's talk</a> was my favorite. In addition to him, I got to hang out with <a href="tent://daniel.tent.is">Daniel Siders</a>, and here's a picture: <img src="tent://graue.tent.is/posts/jookxw/attachments/image.jpg">

A webapp can translate those links into https:// URLs for a browser. Actions could still be specified using URIs like tent://someone.tent.is/follow.

Discussions on alternative scheme

Q: Don’t we need to know if the entity URL is http or https?

A: Yes and no. If no http(s) is given in the url, it should default to https.