diff options
author | nodiscc <nodiscc@gmail.com> | 2017-07-04 21:37:30 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-07-04 21:37:30 +0200 |
commit | 5b25a9635fe808bc1c4f3eee8cdf8485115da75d (patch) | |
tree | d5c46525f3c739d9c63de860427e0b3cadd688e5 /doc/md/FAQ.md | |
parent | d5d22a6d07917865c44148ad76f43c65a929a890 (diff) | |
parent | 8bf94136e10c64496711c8f66a4f58f89c515360 (diff) | |
download | Shaarli-5b25a9635fe808bc1c4f3eee8cdf8485115da75d.tar.gz Shaarli-5b25a9635fe808bc1c4f3eee8cdf8485115da75d.tar.zst Shaarli-5b25a9635fe808bc1c4f3eee8cdf8485115da75d.zip |
Merge pull request #772 from nodiscc/rtfd
Generate HTML documentation using MkDocs
Diffstat (limited to 'doc/md/FAQ.md')
-rw-r--r-- | doc/md/FAQ.md | 43 |
1 files changed, 43 insertions, 0 deletions
diff --git a/doc/md/FAQ.md b/doc/md/FAQ.md new file mode 100644 index 00000000..151dcef5 --- /dev/null +++ b/doc/md/FAQ.md | |||
@@ -0,0 +1,43 @@ | |||
1 | ### Why did you create Shaarli ? | ||
2 | |||
3 | I was a StumbleUpon user. Then I got fed up with they big toolbar. I switched to delicious, which was lighter, faster and more beautiful. Until Yahoo bought it. Then the export API broke all the time, delicious became slow and was ditched by Yahoo. I switched to Diigo, which is not bad, but does too much. And Diigo is sslllooooowww and their Firefox extension a bit buggy. And… oh… **their Firefox addon sends to Diigo every single URL you visit** (Don't believe me ? Use [Tamper Data](https://addons.mozilla.org/en-US/firefox/addon/tamper-data/) and open any page). | ||
4 | |||
5 | Enough is enough. Saving simple links should not be a complicated heavy thing. I ditched them all and wrote my own: Shaarli. It's simple, but it does the job and does it well. And my data is not hosted on a foreign server, but on my server. | ||
6 | |||
7 | ### Why use Shaarli and not Delicious/Diigo ? | ||
8 | |||
9 | With Shaarli: | ||
10 | |||
11 | * The data is yours: It's hosted on your server. | ||
12 | * Never fear of having your data locked-in. | ||
13 | * Never fear to have your data sold to third party. | ||
14 | * Your private links are not hosted on a third party server. | ||
15 | * You are not tracked by browser addons (like Diigo does) | ||
16 | * You can change the look and feel of the pages if you want. | ||
17 | * You can change the behaviour of the program. | ||
18 | * It's magnitude faster than most bookmarking services. | ||
19 | |||
20 | ### What does Shaarli mean? | ||
21 | |||
22 | Shaarli is for shaaring your links. | ||
23 | |||
24 | ### My Shaarli is broken! | ||
25 | First of all, ensure that both the [web server](Server-configuration) and [Shaarli](Shaarli-configuration) are correctly configured, and that your installation is [supported](Server-requirements). | ||
26 | |||
27 | If everything looks right but the issue(s) remain(s), please: | ||
28 | - take a look at the [troubleshooting](Troubleshooting) section | ||
29 | - come [chat with us](https://gitter.im/shaarli/Shaarli) on Gitter, we'll be happy to help ;-) | ||
30 | - browse active [issues](https://github.com/shaarli/Shaarli/issues) and [Pull Requests](https://github.com/shaarli/Shaarli/pulls) | ||
31 | - if you find one that is related to the issue, feel free to comment and provide additional details (host/Shaarli setup) | ||
32 | - else, [open a new issue](https://github.com/shaarli/Shaarli/issues/new), and provide information about the problem: | ||
33 | - _what happens?_ - display glitches, invalid data, security flaws... | ||
34 | - _what is your configuration?_ - OS, server version, activated extensions, web browser... | ||
35 | - _is it reproducible?_ | ||
36 | |||
37 | ### Why not use a real database? Files are slow! | ||
38 | |||
39 | Does browsing [this page](http://sebsauvage.net/links/) feel slow? Try browsing older pages, too. | ||
40 | |||
41 | It's not slow at all, is it? And don't forget the database contains more than 16000 links, and it's on a shared host, with 32000 visitors/day for my website alone. And it's still damn fast. Why? | ||
42 | |||
43 | The data file is only 3.7 Mb. It's read 99% of the time, and is probably already in the operation system disk cache. So generating a page involves no I/O at all most of the time. | ||