Ah, ok. Exclude feature would still be cool non the less so still adding that, lol. Wildcards are supported so you can use the below.
events.* or events.% (either works)
To have profile asset and that events asset you can do the following asset.
profile,events.*
The first asset supplied will be the "primary" asset of the stream as well, which is mostly only relevant if you allow new activity to be created on that stream as it'll use the primary asset for access checks and newly created activity will use that asset.
I've never tested multiple wildcards, but the below might work too if you need to enforce the 2 ids.
events.*.*
The * wildcard converts to % for the purpose of the database query, which will just do a LIKE usage. So it's same as doing the below directly in a query.
`asset` LIKE 'events.%.%'