Of forks and clones

Initially my repository was a direct fork. It seemed convenient at first, but soon I ran into some problems.

The thing is that forks doesn't fit well, when you do something stand-alone, they fit more for pull requests.

Forks' features:
• No more than one fork for one account. You can make organization and fork there, but if there is already fork of original repo, then you get no more than one direct fork.
• Comparsion with default branch of oringinal repo. On main page of your fork you see difference with original.
• No converting to private repo if original is public. You should copy it to yours repo first.
• Fork commits are excluded from profile statistics. Instead they are included for original repo after merge. Bonus: you can't pin fork in your profile if you don't have it on account, even if you're working on it.
• Can't search repository code. It might come in handy, when you're doing something standalone.

Maybe forks have some other restrictions, but I switched from fork to clone because of search. Since my client is at early stage, it wasn't long. I lost only 1 watch and 3 stars.

I changed links, so new repo is available on old link: github.com/kotatogram/kotatogram-desktop

Old one was archived. It's available for now, but I plan to remove it soon since there is no need in it.