[CaoLongyang]

Summary

Upgrades 8 site entries in data.json from insecure HTTP URLs to HTTPS. This improves security and reliability — many of these sites now redirect HTTP to HTTPS, which can cause unexpected behavior during searches.

Changes

The following sites had their url and/or urlMain fields updated from http:// to https://:

Site	Field	Before	After
Gravatar	url	http://en.gravatar.com/{}	https://en.gravatar.com/{}
Gravatar	urlMain	http://en.gravatar.com/	https://en.gravatar.com/
Kik	urlMain	http://kik.me/	https://kik.me/
PromoDJ	url	http://promodj.com/{}	https://promodj.com/{}
PromoDJ	urlMain	http://promodj.com/	https://promodj.com/
Wikidot	url	http://www.wikidot.com/user:info/{}	https://www.wikidot.com/user:info/{}
Wikidot	urlMain	http://www.wikidot.com/	https://www.wikidot.com/
authorSTREAM	url	http://www.authorstream.com/{}/	https://www.authorstream.com/{}/
authorSTREAM	urlMain	http://www.authorstream.com/	https://www.authorstream.com/
datingRU	url	http://dating.ru/{}	https://dating.ru/{}
datingRU	urlMain	http://dating.ru	https://dating.ru
igromania	url	http://forum.igromania.ru/member.php?username={}	https://forum.igromania.ru/member.php?username={}
igromania	urlMain	http://forum.igromania.ru/	https://forum.igromania.ru/
uid	url	http://uid.me/{}	https://uid.me/{}

Rationale

• All 8 sites support HTTPS (most redirect HTTP to HTTPS automatically)
• Using HTTPS directly avoids unnecessary redirects, improving search speed
• HTTPS ensures TLS verification is performed, preventing MITM attacks
• The uid site already had urlMain as HTTPS but url as HTTP — this was inconsistent

Verification

No structural changes were made — only the protocol prefix was updated. Keys, error types, regex patterns, and all other fields remain unchanged.