Open webVerts opened 1 year ago
Temporary workaround for this issue is similar to the linktr.ee filter added in authifyWeb/URL-Frontend#101.
First the code should check for certain pages like twitter.com/legal, twitter.com/tos etc and if it is not part of those sites, then add the pathname to the hostname to be checked. If it belongs to any of the custom declared structure then hostname itself will be served as the link that will be sent to verify. So for Twitter, twitter.com
will be sent.
Not a blocker for authifyFame Profile Cards.
Currently whenever the site detects a link related to github, twitter etc, it automatically modifies the string to accept parts of the pathname accordingly and uses this new string, to compare with the database. Adding this feature helped to verify social media pages related with a company.
Now the problem is a page like
twitter.com/tos
, is part of twitter, but are not added to the Twitter database URLs. So when the user choose the company as Twitter and submit a link like this, the verification shows as failed, though it is a valid link.In the case for a site where links like the above are very less, it is acceptable to add upto 4-5 links like the above to the database, but when the number increases, it creates more confusion and end up causing many false negatives.