Provide an option to disable rss publication for a shaarlink while adding it

[jeekajoo]

Hi,

Shaarli is very convenient to store bookmarks for our personal use, but it is also more and more used as a µblogging tool.
Do you think it would be possible to add a tick box in "addlink" page to disable the publication of a shaarlink that we don't want our atom/rss "followers" to bother with?

Thanks
J.

[Sbgodin]

There's a private checkbox for this purpose. The link only remains visible for the connected user, not in the public view of Shaarli, nor in the RSS.

[nodiscc]

Agreed. If you want to keep you links public but separate blog-like activity from bookmarks, you could setup 2 separate shaarli instances. Or tag your microblog entries with blog then use https://your.shaarli.url/?do=rss&searchtags=blog as RSS feed.

Feel free to reopen this if you think of a simple implementation for this (this is similar to what's described at #15 (comment) and was considered too complex)

[jeekajoo]

@Sbgodin : I had in mind to keep those shaarlinks public because I've no reason to hide them. Moreover I don't want to login to find them.
@nodiscc : Thanks, I didn't know about this trick :) but it means you have to make sure your 'followers' use this specific feed, and most of them won't ; unless you force them. Anyway, I'm fine with that.

[nodiscc]

@jeekajoo I am in the same situation.

you have to make sure your 'followers' use this specific feed

What you could do is set up a RSS aggregator on your server that filters only specific tags and have your followers subscribe to that. I've had good results with moonmoon (server-side, PHP).

FeedEk can display a feed client side (JavaScript) but uses Google Feed API and has no subscription option.

The other way around is to add buttons in the toolbar linking to each feed (RSS: blog and RSS: all articles) for easy access. Note that custom page elements like custom buttons will be erased if you upgrade Shaarli, adding page elements as "plugins" that are independent of Shaarli's codebase is being discussed in #14

[jeekajoo]

well, I tweaked my nginx vhost to overcome this.
this is a ugly hack, but it works (https://fralef.me/links/?stwNvw)

[nodiscc]

cool hack. I suppose you could do the same thing on apache using mod_rewrite