repost feature

[caryoscelus]

No description provided.

[Zauzolkov]

I see at least two approaches to implement this functionality:

1. Create a new table and store a link to original post. Old clients will ignore unknown table (any repost will be invisible). Draft is implemented in Repost feature #2. Also we can add some other fields, like a user comment to the original post (something like a "reply to post" feature)
2. Add new fields to an existing post table. In this case we are able to add a placeholder for old clients. For example we can clone post body and add a custom header in the beginning. Also this technique allows to preserve / archive the original message (in case of modification by author of original post).

[caryoscelus]

wow , you're quick !

those were two approaches i've been considering .

Also this technique allows to preserve / archive the original message (in case of modification by author of original post).

that's a good point and feature (the feature however could be implemented in first solution as well) . unfortunately one could also create pseudo-repost . 0me like all the 0net sites signs all of the user's file so there's little chance to store all the versions and make sure everything is kept nicely signed and proofs are everywhere

overall i was thinking of attracting more people to discuss features and their impl . basically first solution can only be implemented if enough users are ready to back it and jump client

[caryoscelus]

given the inertia of 0net users , i'm inclined to think second option is better

(unless we somehow achieve new users flood that will outnumber current ranks)