@aljoscha we could have really any number of types of feeds. I think I'd keep '@' to id a feed, and just append something else to the other end .ed25519 okay, so that is the signature algorithm the feed uses, but it doesn't actually do anything yet. We just put some sort of signifier there so that it would be possible to distinguish with other variations we might use in the future. In a binary format, that would be replaced with a varint (and I guess, allocate ranges to people experimenting here) probably, just use multiformats

In particular, I'm really interested in bls group signatures ... that will also require some additional validation rules if you want to be able to add or remove directors (because the key will change)

Supporting partial replication ranges for a feed will break somethings (indexes where the latest of a type sets the value) but would be very useful for things where having the latest record is more important than the entire history - for example, the weather forecast.

But, all these things are extras that would be cool to have, but that we can work on later.