Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Text list of Supported Websites in domain (or hosts) format #4903

Open
realAzazello opened this issue Aug 31, 2024 · 5 comments · May be fixed by web-scrobbler/website-resources#19
Open

Text list of Supported Websites in domain (or hosts) format #4903

realAzazello opened this issue Aug 31, 2024 · 5 comments · May be fixed by web-scrobbler/website-resources#19
Labels
feature New feature or request

Comments

@realAzazello
Copy link

realAzazello commented Aug 31, 2024

With the growing list of supported websites - which will continue to evolve - it would be useful to have a straight, simple textual list of them in domain format. e.g. yaymusic**.com**

A major use-case is to allow-list them in a hosts file or content blocker.

I don't know and haven't found if one of the sourcefiles has that structure; and a search of Issues doesn't pull up this kind of request before.

@realAzazello realAzazello added the feature New feature or request label Aug 31, 2024
@inverse
Copy link
Member

inverse commented Sep 2, 2024

What format would work best for this? currently on release we publish a list of connectors which is included onto the website.

See: https://raw.githubusercontent.com/web-scrobbler/website-resources/master/resources/connectors.json

What would the format you require need to look like?

@realAzazello
Copy link
Author

realAzazello commented Sep 3, 2024

I wonder, could we get that json list
e.g.
"AzuraCast",
"scrobblerad.io",
"weareone.fm",
"Bollerwagen",
"МТС Музыка",
"ChirpRadio"

copied to another file in format--

# AzuraCast
azuracast.xyz
# scrobblerad.io
scrobblerad.io
# weareone.fm
weareone.fm
# МТС Музыка
mtcmузыка.wtf

@inverse
Copy link
Member

inverse commented Sep 6, 2024

That could work but how should we handle cases where the matches are defined as things like

*://*.wdr.de/radio/*

Would matching the root domain of wdr.de be fine?

*://music.amazon.*/*
*://www.amazon.*/gp/dmusic/cloudplayer/*

For these it could be any tld :/

@realAzazello
Copy link
Author

Very interesting cases!

Yes, the root domains are all that's needed.

Remind that hosts-file format i.e. root domains should be sufficient. Content blockers already presume a barebones list of domains should be blocked. If someone wants to use fuller paths, they'll have to make custom blocking filters.

As for the TLD wildcards, hmm... Perhaps for those cases, actually label as ".tld" (".TLD"): useful because it quickly flags that those'll need to be manually modified.

e.g. I already use a hosts file manager that can allowlist domains even on the TLD.
I would also convert some TLDs to ".com" or whatever, based on my specific usage of the site.

IF possible, the addition of comment lines (# МТС Музыка) would be useful data.

@inverse inverse linked a pull request Sep 8, 2024 that will close this issue
@inverse
Copy link
Member

inverse commented Sep 8, 2024

Started work in web-scrobbler/website-resources#19

Some edge cases will need to be worked out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants