Skip to content

Conversation

brian6932
Copy link

The style works the same on wikiless domains
Instance list: https://wikiless.org/instances.json

@devidw
Copy link
Owner

devidw commented Dec 18, 2022

Hey @brian6932

Thanks for your PR

I would like to keep one clean version of the user style for the main site wikipedia.org without a huge list of wikiless instances

Instead, I would suggest setting up a GH action that parses the instance list provided by you and then turns this into a user style we can subscribe to

The GH action could have a cron trigger to run something like daily and would write into the repo

What do you think? Feel free to PR

@brian6932
Copy link
Author

brian6932 commented Dec 18, 2022

I'm not against using actions for this, tbh I think it's a pretty good idea, I'm down to make a ci for this when I have some extra time.

However, I don't really see why 2 userstyles would be needed here, as the support extends to basically all of these sites, they all use basically the same frontend, with very minor differences (mostly in the use of js link hovercards). I think it will just end up becoming more of a burden to upkeep 2 files instead of one here.

@devidw
Copy link
Owner

devidw commented Dec 18, 2022

As output, we could keep one stylesheet, but for development in the codebase there should be a version with only wikipedia.org.

As wikiless grows, I would like to avoid writing styles in a file that's first 200 lines are a different target domain - that's my only point here.

I'm thinking of a simple setup of a source stylesheet with only the wikipedia.org domain "dev" used to write styles and a script that processes the wikiless instance list and outputs another stylesheet with all those different domains added.

For the end user, it could always be the same output sheet with everything in there, just to keep development experience easy.

Does this make sense to you? @brian6932

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

Successfully merging this pull request may close these issues.

2 participants