Make a shaare private or delete it after X hours/days/months

[NerosTie]

I would want to suggest an idea: make a public shaare private or delete it after X hours/days/months.

Sometimes I want to share a link but I don't see the purpose to let it public or to keep it after a certain time (e.g. a link to a direct live video).

Or, I'm a little bit afraid to have thousands of links and tags over a period of several years. With all these datas, some people use them to describe your personality or what they think it is.
Twitter had a similar issue (with people digging profiles) and they decided to not show tweets older than 1 month.

What do you think?

[nicolasdanelon]

Maybe as a plugin.. But in shaarli core? I don't know..

[ArthurHoaro]

Definitely a plugin IMHO because most people probably don't need this feature. But I understand it could be interesting regarding privacy.

Now, should it be a global setting? An additional field in editlink?
Making shaares private is probably better than deleting them, because Shaarli is a tool to share links, but also to save them.

EDIT: I'm putting the backlog milestone, but since it's a plugin, anyone is welcome to work on it at any time.

[arnaudmm]

I totally agree with @NerosTie

The hard part is to find a good implementation.. The twitter way is cool I think, make everything private after X days

[NerosTie]

@arnaudmm However, if making everything private is the only option, it'd be too radical I think. But it can be an acceptable first step.

Instead of having to choose for every shaare to hide it or not, the plugin could have the option to hide in function of tags.

Example:
for tag=politic make it private after 14 days
for tag=something make it private after 2 months
for tag=live delete it after 1 day
for tag=note delete it after 1 month

[nodiscc]

We should be extra careful with deletion operations, so making the expired link private is better than deleting it. However users of this system might want to review and delete their expired links. In this case the plugin should also add a tag like expired to the shaare. Batch editing/deletion of links is planned and will make this easier.

the plugin could have the option to hide in function of tags.

I like this idea as well and using values inside of tags could make it even simpler (no configuration). Just tag items with

expire:14d
expire:7m
expire:1d

[ArthurHoaro]

@arnaudmm The twitter way is cool I think, make everything private after X days

I agree.

@NerosTie Instead of having to choose for every shaare to hide it or not, the plugin could have the option to hide in function of tags.

It seems a bit too complicated, especially regarding UI configuration when you can have hundreds of tags.

@nodiscc Just tag items with expire:14d

Yes, it's pretty much the same as "An additional field in editlink?", even easier.

We can probably do something which allow both or just one depending on configuration. Using only days as duration might be enough though.

E.g. 1:

global conf: everything private after 60 days.
tag a few links with expire:0/noexpire (?) and another one with expire:7d

E.g. 2:

no global conf
tag links individually expire:Nd

[arnaudmm]

Is there a plugin out there to add default tag to new link?

If yes, E.g. 2 is really good. If you want it global, just add a default tag to expire:30d for example

[nodiscc]

@arnaudmm If you use the bookmarklet you should be able to edit it's parameters to auto-fill your desired tag.

[virtualtam]

make a public shaare private or delete it after X hours/days/months.

Maybe it would be worth introducing a new archived status for links, so the public/private distinction remains? This way you can choose when links will be flagged as archived, and whether to display archived links or not.

I have a few links I keep private for very specific reasons, usually because they're memos or unpublished drafts that benefit from being tagged; flagging everything as private would make them hard to find and reduce link filtering efficiency.

Just tag items with

expire:14d
expire:7m
expire:1d

@nodiscc That's neat! In a similar fashion, links could be flagged as expired.

Anyway, the implemented solution will require either:

• a periodic task to flag links with the corresponding status
• checking each link when instantiating a LinkDB()

Or, I'm a little bit afraid to have thousands of links and tags over a period of several years. With all these datas, some people use them to describe your personality or what they think it is.
Twitter had a similar issue (with people digging profiles) and they decided to not show tweets older than 1 month.

@NerosTie Anyone subscribing to the Atom/RSS feed will have the complete corpus, though.