The problem with encrypting with memo keys is it requires both the authors and recipients memo keys to encrypt the content, I think it's either both public keys or the authors private key and the recipients public key, not 100% sure.

But anyway it would be encrypting the content uniquely for each and every subscriber or something which doesn't seem practical for locking a post behind a pay wall.

I do wonder how feasible it'd be to make functionality that allows for posts to be encrypted and access be given, either via users personal subscription systems or something built into hive, maybe a recurrent payment with a special memo.

I think my thought process with basic universal implementations is that it probably wouldn't be best being built into the core chain, it would likely serve better as a HAF app, it depends really, Encryption of posts to allow for gated content could be a vary useful feature. But likely the ability to encrypt and give access will be the only part that is added to the core chain software, everything else would probably be custom stuff handled by front ends or HAF apps perhaps.

I guess I'm more or less saying a complete subscription/content gating system wouldn't likely be part of the core chain software but rather certain parts make sense to be core chain stuff cause it's required but certain aspects of these systems can be delegated to other things like front ends or HAF apps.

I donno I sometimes wonder if I even know what I'm talking about these days.