Personally, I've frequently cloned repos to read and play around with the code. Making changes to the code is a good way for me to verify that I understand what's going on: if a change does what I expect it to do, then it means I probably understood the code. In that case, I don't really care if I miss updates.
As for people not knowing what the real repository is: there's not really a such thing as the "real" repo. Git just isn't centralized like that. Probably since you are the original coder, yours will be the most popular, but if you're worried about not getting credit for your work, there are a few things you can do:
1. As viraptor said, you can put a link to your repo in the README.
2. It's a good idea to put a LICENSE file in your repo. You can choose one which requires people to give you credit.
Keep in mind that you can't force people to pull your code with these changes, and if they've already cloned it they have it under the original license (which may be no license at all). So this doesn't really fix the problem you have now, it only prevents more people from cloning w/o a link back in the future.