General discussion

[nodiscc]

Followup to #44

[nicolasdanelon]

Alright then I got two ideas for shaarli.

• Add a view private links button (if you click on this link will show only private links)
• Add a database integrity testing (check old links for URL parameters. Title & description for replace HTML entities
  What do you think ?

[ArthurHoaro]

Add a view private links button (if you click on this link will show only private links)

But...

Add a database integrity testing (check old links for URL parameters. Title & description for replace HTML entities

I'm not sure to understand. You want a system which apply new devs (such as title format) on previous entries?

[nicolasdanelon]

Private links: that button is visible?
Database integrity: just a information check for users who update shaarli from sebsauvage version.

[nodiscc]

Private links: that button is visible?

Yes it should appear when you're logged in. If it doesn't, check that your ad blocker doesn't filter it.

[mro]

Hi all,
a few days ago, I published https://github.com/mro/ShaarliOS on the Apple App Store.

Here are a few codes to get free copies from Apple, please write a comment which one you used and how you like it.

XP73J6J7W4PP A6TNRTAKR4AP F6NTRJLLT64N 396FFEFK4J7F WNEJTK9TYK7F 4RK3F4KH7LWH XHJJ7AXWA49H K7WTHFTLF3F3 ERXFTYWT93FK L349HLFNJT6H

They do expire in 4 weeks.

See also at https://github.com/shaarli/Shaarli/wiki/Community-%26-Related-software#mobile-apps

[ArthurHoaro]

I don't own any Apple device but the screenshots look nice. Good luck with your app! :)

[virtualtam]

Private links: that button is visible?

@nicolasdanelon it is, though it'd be worth having a more explicit button to improve accessibility

ShaarliOS on the Apple App Store

@mro nice ;-)

[fbartels]

@mro thanks for the promo codes. Just used L349HLFNJT6H.

I will take a deeper look into the app later.

[ParoTheParrot]

ShaarliOS on the Apple App Store: ERXFTYWT93FK - Thanks! 👍

[Eragos]

@mro instead of taking one of your promocode, I bought your App :) Thanks for your work!

[mro]

@nodiscc when working on posting new links from an App, I found that it's nowadays hard to detect a successful add. Prior to 35c2c4d the final redirect to the added hash link was a very good indication that the link was really added.

While I understand the wish for a redirect to the link-list after adding (#115), I wonder why it wasn't done via setting the returnurl from the bookmarklet/add link.

@nodiscc what was the reason?

[nodiscc]

@mro the previous behavior was what is described in #115, so that was not ideal either (returning to ?do=addlink). Redirecting to the added link (with an anchor) would also be OK, I guess.

[mro]

Redirecting to the added link (with an anchor) would also be OK, I guess.

that'll be awesome - IMO both in terms of user experience and success verification.

Update: strange - doesn't index.php#1359 look like as if this should be the case already? But when testing, it failed. Also fails on http://shaarlidemo.tuxfamily.org/Shaarli/

@nodiscc Any clues?

[nodiscc]

Hi,

I have been working on this home server deployment/maintenance tool: https://github.com/nodiscc/srv01 for my own needs. It is still work in progress, but feel free to give it a try. It allows unattended deployment of various services and web applications on a Debian machine (including Shaarli).

It uses ansible and was inspired by sovereign, but focuses on a simplified and more modular setup (deploys only the services you need, leaves out the most complex parts such as the mail server). The full process to install shaarli, after installing a minimal Debian system is:

aptitude install ansible git sudo pwgen python-mysqldb
git clone https://github.com/nodiscc/srv01
cd srv01
nano config.yml #change required configuration values
./srv01 setup #setup the base system
./srv01 install apache
./srv01 install shaarli

As always feedback is welcome.

[mro]

@nodiscc #308 (comment): I shall see this talk soon: https://events.ccc.de/congress/2015/wiki/Lightning:Holo

Anybody interested, should I report?

[nodiscc]

Nice! Yes please, a short report of what you've learned there would be great! Wish I could attend the CCC, if you can send the link to the video of the talk I'd watch it.

For the record I found ansible remarkably easy to use/learn, and powerful enough that it had a built-in solution to every problem I encountered. There are still a number of features (srv01 maintenance...) that I'm considering moving into a shell script (the ansible task is rather convoluted). I prefer ansible/config management over Docker-style maintenance since it uses the system's provided tools/capabilities, I find Docker is a somewhat overengineered implementation of LXC, which is still in it's early ages. In the future I will certainly use plain LXCs to compartmentalize applications services (a good read at https://l3net.wordpress.com/category/virtualization-2/).

[mro]

here's the slides of above talk, I think I will give it a try in the next weeks: https://rawgit.com/holocm/holo-docs/slides/promo/32c3-lightning-talk/slides.pdf

[ArthurHoaro]

I've create a Plugin list page in the wiki, listing 'official' and known 3rd party plugin. Feel free to add your own.

BTW if your plugin is generic enough and if you want to, you can submit a pull request to add it in Shaarli's repo.

[nodiscc]

Should we mirror the git repository somewhere else? There are a few non-profits that offer Git hosting and project management interfaces (GitLab). I was thinking about https://git.framasoft.org and https://git.laquadrature.net/.

[mro]

@nodiscc #308 (comment): for what purpose?

[alexisju]

@mro for that : http://framablog.org/2016/01/28/github-et-les-libristes-un-danger-et-un-defi/

[mro]

ic, as far as I understand (I don't read french) it's considered dangerous to depend on a non-free-software platform.

P.S.: I have a mirror of my fork: http://mirror.mro.name/github.com/mro/Shaarli.git/ for quite some time.

[alexisju]

Yes, sorry for this french article. Indeed this article talking about that, about centralisation, standardization and non-free plateform who is Github Inc. The author of the article, there is a risk for FLOSS projects to become to much dependent on this platform...

[mro]

as a minimal means, I personally use mirrors as mentioned above plus URLs under my control as official, "permanent" or "canonical" project URLs, like e.g. http://app.mro.name/ShaarliOS

But that's not so easy for a de-central, fundless community project. At least the domain needs funding and also implies a bit of control over the project. E.g. I myself am such a domain owner/sponsor for http://piccolo2d.org/community.html which had to leave google code when they shut down.

[kalvn]

@heimpogo I'm not sure current plugin possibilities would allow to create this kind of pages 🤔

[nicolasdanelon]

@heimpogo why would you do that!? the original shaarli works like that..

[heimpogo]

@kalvn Ok, I didn't check this yet. Thanks for pointing this out.
@nicolasdanelon Shaarli allows very different ways of using it. And some might consider a tag cloud a Web 2.0 relict they don't really need.

[nodiscc]

@heimpogo The tag cloud/daily views have no impact on the rest of the application and you can hide those links using custom css, and block access to the pages using .htaccess or other server configuration if you're really into that... But given the fact that they work as expected, have no other implcations, and maintenance time is already thin as is, it's unlikely they will be ported as plugins.

[ArthurHoaro]

Github has informed us maintainers that there is a vulnerability in node tar which is included as a dev javascript dependency in Shaarli (CVE-2018-20834).

Vulnerable version of tar is included by node-sass, and fixing this issue is requires sass/node-sass#2625 to be fixed.

I'm not sure what the security implications are, but as it is only a dev dependency, I recommend as a good practice that you remove node_modules folder in production.

You are not impacted if you used the release archive during the install or the Docker image.

[elwinschmitz]

Re: @heimpogo :

Have you ever thought about re-packaging the daily view and the tag cloud as plugins? I do not consider these essential. This would allow people to just turn it off it they don't need them.

I'd like to +0.5 that. :)
Personally I like the Tag-cloud feature/look, but don't really use the Daily-page or RSS/Atom feeds.

@heimpogo The tag cloud/daily views have no impact on the rest of the application and you can hide those links using custom css, and block access to the pages using .htaccess or other server configuration if you're really into that... But given the fact that they work as expected, have no other implcations, and maintenance time is already thin as is, it's unlikely they will be ported as plugins.

I agree it would be not be worth the effort to completely port them to plugins (as the current plugin-system would need to be changed as well).

But would it be an idea to add some more configuration-options/flags? Like the current setting for Thumbnails? So for example:

• Enable RSS/Atom feeds
• Enable Tag-cloud
• Enable Daily-view

(Or change them around by making them "Disable X").

Then in the templates/routing simple switches could be added, like for example in the menu:

{if="$feature_tag_cloud_enabled"}<a href="?do=tagcloud">Tags</a>{/if}

I'd also like these configuration-options for my own theme, so I could make it usable for other people that would like to use the Daily-view AND my theme. ;)

[ArthurHoaro]

Would you mind moving this discussion to its own issue?

…

On Thu, Jun 13, 2019, at 10:42, Elwin Schmitz wrote: Re: @heimpogo <https://github.com/heimpogo> : > Have you ever thought about re-packaging the daily view and the tag cloud as plugins? I do not consider these essential. This would allow people to just turn it off it they don't need them. I'd like to +0.5 that. :) Personally I like the Tag-cloud feature/look, but don't really use the Daily-page or RSS/Atom feeds. > @heimpogo <https://github.com/heimpogo> The tag cloud/daily views have no impact on the rest of the application and you can hide those links using custom css, and block access to the pages using `.htaccess` or other server configuration if you're really into that... But given the fact that they work as expected, have no other implcations, and maintenance time is already thin as is, it's unlikely they will be ported as plugins. I agree it would be not be worth the effort to completely port them to plugins (as the current plugin-system would need to be changed as well). But would it be an idea to add some more configuration-options/flags? Like the current setting for Thumbnails? So for example: * Enable RSS/Atom feeds * Enable Tag-cloud * Enable Daily-view (Or change them around by making them "Disable X"). Then in the templates/routing simple switches could be added, like for example in the menu: {if="$feature_tag_cloud_enabled"}<a href="?do=tagcloud">Tags</a>{/if} I'd also like these configuration-options for my own theme, so I could make it usable for other people that would like to use the Daily-view AND my theme. ;) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#308?email_source=notifications&email_token=AAO7FNUC34H4UIL3YY7ONJLP2IB6TA5CNFSM4BMQTAI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXS7EKQ#issuecomment-501609002>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAO7FNTX4HX7U5OR2EN2OZLP2IB6TANCNFSM4BMQTAIQ>.

[heimpogo]

A feature request for the markdown plugin: It would be wonderful to have a one-click copy button at the top of code blocks. This would make using Shaarli as a code snippet collection much more comfortable.

[nodiscc]

@heimpogo at the top of each code block inside the shaare? That would be difficult since markdown generation is handled by parsedown, which does a single thing, consuming markdown and returning the corresponding HTML. You would have to open an issue there.

A button to copy the whole shaare description would be doable, but I think it would considerably affect performance (we would have to load the rendered and raw descriptions into the page).

Please correct me if I'm wrong.

[ArthurHoaro]

This shouldn't be done on server side, as you said it would be very difficult.

One easy solution would be to add this Copy-to-Clipboard plugin to my code coloration plugin, which rely on Prism.JS. Note that Prism is not really a lightweight library, as it supports many languages.

[MarceauKa]

Hi all!
I built a Shaarli version with Laravel: https://github.com/MarceauKa/laravel-shaarli
At first it was just a 2 hours challenge to train a friend with Laravel but it's now a real package.

[ArthurHoaro]

That's interesting, thank you for sharing!

[virtualtam]

Hey @MarceauKa, and thanks for sharing!

I would strongly advise you to rename your application and source repository though, as naming it after Shaarli is misleading to users:

• the project is not affiliated with the Shaarli community;
• there is no shared codebase with the Shaarli application;
• the project is not on-par with Shaarli feature-wise (e.g. Netscape import/export, Docker images, documentation);
• the underlying technologies (save the choice of the PHP language) are different.

Thanks for your understanding :)

[nodiscc]

This is also what I strongly recommended here awesome-selfhosted/awesome-selfhosted#1864. It is misleading.

[MarceauKa]

@virtualtam @nodiscc
Yep, it was planned but it needs time to rename an application. It's done, Laravel Shaarli is now Shaark

[nodiscc]

the future is now

[nodiscc]

Moved from #1446:

I'm proud to announce a new version of the iOS share extension. 🍏 📱

For those who want to give it a try, there's free copies at https://github.com/mro/ShaarliOS/issues/40

Pinging #308 and #323
Happy shaaring! 🎉

[ArthurHoaro]

Cute:

[ArthurHoaro]

There have been quite a few new features for v0.12.1, which I plan to release in one or two weeks.
I have pushed all remaining issues (with milestone v0.12.1) tagged as feature for v0.12.2.

[Arthinsx]

Hello

I want to use the plugin system to add some new data. So I check how it works in the demo pluggin for the data "Stuff". But it seems it does not work properly because when I save a new value in the stuff property I can't retrieve it when I try to edit the link.

I look directly in the datastore.php file and I can't see any new value added in the file either.

I'm not sure I'm doing right. Is that functionality available already ? Is that a bug ?

For information, CONTRIBUTING.md indicates that the general discussion is in #44 (you should update to #308).

[Knah-Tsaeb]

Already report #1646

[nodiscc]

I'm thinking about "detaching" this project from the original https://github.com/sebsauvage/Shaarli (remove the fork relationship), since currently shaarli/Shaarli cannot be found in Github search results (see for yourself: https://github.com/search?q=shaarli&type=repositories, the search does not show forks, only sebsauvage/Shaarli - which has not been updated since 2016 - is returned).

This can be done through https://support.github.com/contact?tags=rr-forks&subject=Detach%20Fork&flow=detach_fork without losing issues/PRs/stars and project-related data.

I already did it in the past for https://github.com/awesome-foss/awesome-sysadmin/ (detached from https://github.com/kahun/awesome-sysadmin), it took only a few minutes, and I'm not aware of any problems ever since.

If there are no objections to this, I will probably proceed in about ~a month.

[kalvn]

As long as we keep credit to Sebsauvage for the original project somewhere in the README, it sounds like a good idea.

[nodiscc]

keep credit to Sebsauvage

Sure, he's forever in the commit log and AUTHORS file. The original repo is linked from https://shaarli.readthedocs.io/en/master/index.html#about, the original Shaarli instance https://sebsauvage.net/links/ is also at the top of https://shaarli.readthedocs.io/en/master/Community-and-related-software.html#community (30k shaares and still going :) )

[RolandTi]

I'm thinking about "detaching" this project from the original https://github.com/sebsauvage/Shaarli (remove the fork relationship), since currently shaarli/Shaarli cannot be found in Github search results (see for yourself: https://github.com/search?q=shaarli&type=repositories, the search does not show forks, only sebsauvage/Shaarli - which has not been updated since 2016 - is returned).

I wanted to open a ticket for months about this strange behaviour from Github.

[bttrx]

Hi all! I'm new to Shaarli and I don't get what those QR codes are for. What's the use case?