The context of updating web applets, possibly/often including timely news raises a focus on the desirability of meta content that describes how the applet stream can be chopped into timelines & sub-sequences by curators & sites.

Let’s say that the minimal meta structure includes features like this:

a) General brand/url or an orginator (of course they can have more than 1, but here I leave the option of connecting them to some other device)

b) Sections within the given brand/url that include

a number referring to original first publication time,
a number referring to current serialization time,
some other arbitrary alphanumeric string for app specific usage – for example a set of sub-parts of the current serialization may be described as sharing common content tags and the format may be used to specify that they should only be used as a complete sequence (artists license)

a set of tags describe content/format etc of subsequences and which can be used for filtering. It’s important for site producers & suppliers to agree on types of tags & their meaning. In general, the agents in the role of curator should coordinate this & post known standards.

a given section may include a minimum viewing time or maximum scroll speed along with some estimate or distributional assumption about the time to arrival of the next item in the sequence.

The info above should let curation tools adjust the timing descriptions when different subsequences are selected & then combined from multiple sources.

Security issues, to prevent hacking on the back end are similar to security issues for other message oriented communications and web production/content. GT specific crypto can be a lot better than than the mainstream solutions, while they may provide contributions that outside parties are less likely to challenge as irresponsible. A mix can be considered.

Edit: I believe there will be a popular GT “web of landing pages & sites” that is different than the WWW, but not a “darknet”. The descriptions above apply equally well to both.

Example: Someone curates a group of links that show in a box as a grid of icons. This directory updates once in a while.

One site can continuously show the box & poll once in a while for updated veresion. Another site inserts the box in some rotating stream of directory related content. Another takes a snapshot for a demo. All of those usages should be supported without difficulty or changes to what the upstream directory compiler is doing when various outlets are added or dropped.

My thought process started with applets on landing pages. From a technological POV, there is no barrier to featuring other people’s applets as the main feature on a page. To support that, it would make sense to pre-format some “MC styles” that could be completed via smart forms.