You are viewing a single comment's thread from:

RE: Windows 95 choices

in #hive-1714865 years ago (edited)

I have faith you could do it. 😁

As far as an encrypted DM function, that somewhat exist in the form of the encrypted memo right ... by just adding a # in front of the memo? I did not explicitly state this in my previous comment but it was my assumption that the current method for memo encryption could just be reworked to apply to entire posts. I am sure it is not that easy but that was my thought at least.

Thank you for your reply.

Sort:  

That's correct, though one of the challenges w/ memo key is that if it is changed, none of the old messages will be readable (unless we store these old ones somehow). And currently, the only private memos we have rely on using transfer memo, which requires active key.

Hmmm. Good points. Maybe you could somehow turn that into an intended feature. I am not sure how this could be done (a crude idea below) but the idea would be that only those currently in the community could see the post. Individuals added to the community at a later date would not have access to posts created before their acceptance into the community or afterward.

The crude idea (very crude as I am not a coder) is when an encrypted post is created the key to that post is broadcast to a whitelist all current community members. Every post would have a unique encryption and whitelist pair. That would get complicated but I guess it could be offset with high RC costs if it is resource intensive.

Anyway, thanks for entertaining my ideas. I will let you get back to work on more productive things. Cheers.