Provide guidance on file naming about ftr-site-config HOT 4 CLOSED

Thanks @j0k3r. In that case, until the situation improves, we can summarise the file naming advice as:

Use example.com.txt for

• www.example.com
• example.com

Use .example.com.txt for

• sport.example.com
• news.example.com
• environment.example.com
• etc.

Use sport.example.com.txt to target just that sub-domain:

• sport.example.com

Note: .example.com.txt will not match www.example.com or example.com

I've now added this to the Readme

from ftr-site-config.

.example.com.txt wil work for any subdomain of example.com: video.example.com, news.example.com, www.example.com, m.example.com, etc.

www.example.com.txt will only work for www.example.com.

In fact, it's not a problem to add .example.com.txt instead of www.example.com.txt it's just less accurate.

I fixed one of your added file yesterday but missed other one.

from ftr-site-config.

The confusion might be around the way this is handled in Full-Text RSS. In the past I've edited pull requests where, e.g. .example.com.txt was targeting www.example.com (in test_url) because in Full-Text RSS this won't match www.example.com. I wonder if that's what's confused @burkemw3. The www subdomain is treated as a special case so example.com.txt is needed to match www.example.com and example.com. .example.com.txt will match everything else except the above two.

This also creates a problem when a site has essentially the same layout under example.com and all its subdomains. We can't use one file to target the site, we have to duplicate the contents of example.com.txt in .example.com.txt.

This isn't very intuitive, and I've realised that most people assume .example.com.txt will match all variations (example.com, www.example.com, news.example.com, etc.).

@j0k3r if I'm understanding correctly in your case (Graby/Wallabag) the difference with what I've described is that .example.com.txt will match www.example.com. Is that right?

from ftr-site-config.

@fivefilters I think I made a confusion by replying too fast. I use the same behavior as in Full-Text RSS (not what I said in my minimized comment)

from ftr-site-config.